AWS Certified DevOps Engineer - Professional
Get started today
Ultimate access to all questions.
Comments
Loading comments...
Ultimate access to all questions.
A company is operating a web application in one AWS Region and has established a standby region for disaster recovery. The recovery strategy mandates near-real-time replication of session data between the regions, with a continuous verification mechanism where 1% of user requests are directed to the secondary region. In the event of a service disruption in the primary region, all traffic must be seamlessly redirected to the secondary region, which should be capable of scaling to accommodate the full load. What is the most appropriate approach for a DevOps engineer to implement these disaster recovery requirements?
A
Deploy the application in both regions using AWS Elastic Beanstalk and utilize Amazon DynamoDB global tables for session data synchronization. Configure Amazon Route 53 with a weighted routing policy and health checks to manage traffic distribution.
B
Launch the application in Auto Scaling groups across both regions and use DynamoDB for session data. Set up a Route 53 failover routing policy with health checks to handle traffic redirection between the regions.
C
Deploy the application in AWS Lambda in both regions, fronted by Amazon API Gateway, and use Amazon RDS for PostgreSQL with cross-region replication for session data. Implement client-side logic in the web application to interact directly with the API Gateway.
D
Launch the application in Auto Scaling groups in both regions and employ DynamoDB global tables for session data. Enable an Amazon CloudFront weighted distribution across regions and direct the Amazon Route 53 DNS record to the CloudFront distribution.