Q35 — AWS DOP-C02 Ch.2

Question 35 of 100 | ← Chapter 2

A company hosts a web application in an AWS Region. For disaster recovery purposes, a second Region is designated as a standby region. Disaster recovery requirements specify that data must be replicated nearly in real time across Regions, and 1% of requests must be routed to the secondary Region to continuously validate system functionality. Additionally, if the primary Region experiences service interruption, traffic must automatically fail over to the secondary Region, and the secondary Region must scale to handle the full traffic load. How should a DevOps engineer meet these requirements?

• A. Deploy the application on AWS Elastic Beanstalk in both Regions and use Amazon DynamoDB Global Tables to store session data. Use Amazon Route 53 weighted routing policy with health checks to distribute traffic across Regions. ✓
• B. Launch the application in Auto Scaling groups in both Regions and use DynamoDB to retrieve session data. Use Route 53 failover routing policy with health checks to distribute traffic across Regions.
• C. Deploy the application in AWS Lambda, exposed by Amazon API Gateway, in both Regions, and use Amazon RDS for PostgreSQL with cross-Region replication for session data. Deploy the web application with client-side logic to call API Gateway directly.
• D. Launch the application in Auto Scaling groups in both Regions and use DynamoDB Global Tables for session data. Enable Amazon CloudFront weighted distribution across Regions. Point the Amazon Route 53 DNS record to the CloudFront distribution.

Correct Answer: A. Deploy the application on AWS Elastic Beanstalk in both Regions and use Amazon DynamoDB Global Tables to store session data. Use Amazon Route 53 weighted routing policy with health checks to distribute traffic across Regions.

Explanation

To meet near-real-time cross-Region data replication and precise traffic splitting (1% to secondary), while supporting automatic failover and scaling, the solution must combine globally consistent state storage with intelligent, health-aware DNS routing. Option A uses DynamoDB Global Tables for low-latency, multi-Region session data replication and Route 53 weighted routing with health checks—enabling both steady-state 1% traffic and automatic failover upon health check failure. Option B’s failover routing only switches traffic entirely during outages, not gradual testing. Option C introduces RDS cross-Region replication, which has higher latency and complexity than DynamoDB Global Tables for session data, and lacks built-in health-aware routing. Option D incorrectly applies CloudFront weighted distribution—CloudFront does not support weighted routing across Regions; it routes to origins based on latency or custom rules, not configurable weights. Thus, option A is the only solution satisfying all stated requirements.