DOP-C02 · Question #29
A company's application is currently deployed to a single AWS Region. Recently, the company opened a new office on a different continent. The users in the new office are experiencing high latency…
The correct answer is C. Create new ALB and Auto Scaling group resources in the new Region and configure the new ALB D. Create Amazon Route 53 records, health checks, and latency-based routing policies to route to F. Convert the DynamoDB table to a global table. Explanation To minimize latency for users on a different continent, the solution requires deploying infrastructure closer to those users, which means creating regional resources (ALB and Auto Scaling group) in the new Region (C), not global resources as option B incorrectly…
Question
A company's application is currently deployed to a single AWS Region. Recently, the company opened a new office on a different continent. The users in the new office are experiencing high latency. The company's application runs on Amazon EC2 instances behind an Application Load Balancer (ALB) and uses Amazon DynamoDB as the database layer. The instances run in an EC2 Auto Scaling group across multiple Availability Zones. A DevOps engineer is tasked with minimizing application response times and improving availability for users in both Regions. Which combination of actions should be taken to address the latency issues? (Choose three.)
Options
- ACreate a new DynamoDB table in the new Region with cross-Region replication enabled.
- BCreate new ALB and Auto Scaling group global resources and configure the new ALB to direct
- CCreate new ALB and Auto Scaling group resources in the new Region and configure the new ALB
- DCreate Amazon Route 53 records, health checks, and latency-based routing policies to route to
- ECreate Amazon Route 53 aliases, health checks, and failover routing policies to route to the ALB.
- FConvert the DynamoDB table to a global table.
How the community answered
(16 responses)- A6% (1)
- B13% (2)
- C44% (7)
- E38% (6)
Explanation
Explanation
To minimize latency for users on a different continent, the solution requires deploying infrastructure closer to those users, which means creating regional resources (ALB and Auto Scaling group) in the new Region (C), not global resources as option B incorrectly suggests. Latency-based routing via Route 53 (D) is the correct DNS strategy here because it automatically directs users to the nearest, lowest-latency endpoint - whereas option E's failover routing is designed for disaster recovery, not latency optimization. Converting DynamoDB to a global table (F) is the cleanest way to replicate data across Regions with managed multi-master replication, while option A's approach of manually creating a new table with cross-Region replication is not a native DynamoDB feature and is therefore incorrect.
Why Distractors Fail:
- A: DynamoDB doesn't support "cross-Region replication" as a table creation option; Global Tables (F) is the correct mechanism.
- B: ALBs and Auto Scaling groups are regional, not global resources - this option is architecturally invalid.
- E: Failover routing serves high availability/DR purposes, not latency reduction.
Memory Tip:
Think "3 R's" - Regional deployment (C), Route 53 latency routing (D), and Replicated global DynamoDB (F). Any time users are far away, you need infrastructure near them, smart DNS routing, and replicated data.
Topics
Community Discussion
No community discussion yet for this question.