Replicate an ecommerce stack with CloudFormation, Route 53 latency routing, and a DynamoDB global table
Short answer
ADE Use a Region-parameterised CloudFormation template, latency-based routing in Route 53, and a DynamoDB global table with Streams enabled.
Question
Key Takeaways
A parameterised CloudFormation template makes the second Region a deployment rather than a rebuild, and DynamoDB global tables replicate the data layer across Regions automatically, so both halves of the stack become multi-Region without a second team maintaining parallel infrastructure by hand.
A single-Region ecommerce site runs a web application on EC2 behind an Application Load Balancer with a DynamoDB table, a custom domain in Route 53, and an ACM certificate on the ALB, with no CDN in the design. The whole stack must be replicated to a second Region for disaster recovery, future growth, and improved user access time with minimal administrative overhead.
Common mistake: Using weighted routing to send fifty percent of traffic to each Region. That is an even split, not a closest-Region decision, so it does not provide the improved access time the requirement asks for, and the ACM certificate is regional so each ALB needs its own certificate anyway.
Expert Analysis
Why the Answer Is Correct
The requirement is a second copy of the entire stack with minimal administrative overhead, and a CloudFormation template with parameters including the Region is what makes that repeatable, so A is correct. Deploying the same template in the second Region reproduces the EC2 instances, the load balancer, and the certificate attachment without anyone rebuilding the environment by hand, which is exactly what minimises administrative effort. For the data layer, enabling DynamoDB Streams and adding the second Region to create a global table makes the table multi-Region with automatic replication, so the replicated stack has a synchronised data layer without a separate replication mechanism, which is why E is correct. For user access time, updating the Route 53 record to use latency-based routing sends each user to the ALB in the Region with the lowest measured latency, which delivers the improved access time requirement, so D is correct. Disaster recovery follows from the second Region existing with a live data replica.
Why the Other Options Are Wrong
B: Documenting the current infrastructure in the console and recreating it in the second Region by hand is exactly the administrative overhead the requirement asks to minimise, and the result is configuration that drifts from the original instead of being reproducible. C: Weighted routing with a fifty percent split sends an equal share of users to each Region regardless of where they are, so users in Europe would still be routed to the other Region half the time and the improved access time goal is not met. It also has no failover semantics, since weighted routing does not automatically move all traffic away from an unhealthy Region the way latency routing with health evaluation does.
Community Comment Notes
The community voted 100 to 0 for A, D, and E, and the top-voted comment explained the combination, with CloudFormation providing repeatable infrastructure deployment, latency-based routing in Route 53 directing users to the nearest Region, and the DynamoDB global table providing the replicated data layer for disaster recovery. Several other commenters independently confirmed the same three options.
Official Reference
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/-global-tables.html
This link opens the official vendor documentation in a new tab.
Community Votes
100% of anonymous learners picked answer ADE. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 5
-
0b43291 👍 1By combining CloudFormation for infrastructure deployment, latency-based routing in Route 53, and creating a global DynamoDB table, the solutions architect can achieve the goals of disaster recovery, future growth, and improved access time while minimizing administrative overhead and ensuring data consistency across both Regions. The other options are either not necessary or do not fully meet the requirements: B. Using the AWS Management Console to document and create the infrastructure manually would be time-consuming and prone to human error, increasing administrative overhead. C. Using weighted routing in Route 53 would distribute traffic based on predefined weights, which may not provide the best user experience or account for future growth or changes in traffic patterns. F. Creating a new DynamoDB table and copying data as a one-time operation would not provide continuous replication and could lead to data inconsistencies or data loss in case of a Regional outage.
-
AzureDP900 👍 1ADE is best option for given scenario.
-
mifune 👍 1A-D-E makes more sense to me here
-
awsaz 👍 3A and D And E
-
NoinNothing 👍 2A, D , E is correct
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →