AWS Certified DevOps Engineer - Professional
Get started today
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 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?
Explanation:
The correct answer is A. Deploying the application on AWS Elastic Beanstalk in both regions and using Amazon DynamoDB global tables for session data ensures near-real-time replication of session data between regions. Amazon Route 53 with a weighted routing policy and health checks can distribute 1% of the traffic to the secondary region to verify system functionality. In case of a disruption in the main region, Route 53 can reroute the entire traffic to the secondary region, which can scale up to handle the increased load due to the use of Elastic Beanstalk and DynamoDB.