SAP-C02 · Question #797
A company hosts an ecommerce site using EC2, ALB, and DynamoDB in one AWS Region. The site uses a custom domain in Route 53. The company wants toreplicate the stack to a second Region for disaster rec
The correct answer is A. Use CloudFormation to deploy to the second Region. Use Route 53 latency-based routing.. This solution employs CloudFormation for consistent infrastructure replication to a second region and Route 53 latency-based routing to provide both disaster recovery and optimized access for global customers.
Question
A company hosts an ecommerce site using EC2, ALB, and DynamoDB in one AWS Region. The site uses a custom domain in Route 53. The company wants toreplicate the stack to a second Region for disaster recovery and faster access for global customers. What should the architect do?
Options
- AUse CloudFormation to deploy to the second Region. Use Route 53 latency-based routing.
- BUse the console to recreate the infra manually in the second Region. Use weighted routing.
- CReplicate only the S3 and DynamoDB data. Use Route 53 failover routing.
- DUse Beanstalk and DynamoDB Streams for replication. Use latency-based routing.
How the community answered
(16 responses)- A81% (13)
- C13% (2)
- D6% (1)
Why each option
This solution employs CloudFormation for consistent infrastructure replication to a second region and Route 53 latency-based routing to provide both disaster recovery and optimized access for global customers.
CloudFormation allows programmatic and consistent deployment of the entire application stack (EC2, ALB, DynamoDB with Global Tables) to the second region, while Route 53 latency-based routing efficiently directs global users to the closest healthy region for faster access and implicitly supports disaster recovery.
Manually recreating infrastructure is error-prone, time-consuming, and not repeatable, and weighted routing is not optimal for directing users to the lowest latency endpoint for global access.
Replicating only data (S3 and DynamoDB) is insufficient; the application's compute resources (EC2, ALB) are also part of the 'stack' and must be present in the second region for full disaster recovery.
Introducing Elastic Beanstalk is a re-platforming effort not requested for simply replicating the existing EC2/ALB stack, and DynamoDB Global Tables are a more managed solution for cross-region data replication than streams for 'faster access'.
Concept tested: Multi-Region deployment for DR and global access using IaC and advanced DNS routing
Source: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-latency.html
Community Discussion
No community discussion yet for this question.