Answer-first summary for fast verification
Answer: Leverage infrastructure as code (IaC) to deploy the required infrastructure in the disaster recovery region. Set up a cross-Region read replica for the database instance. Employ AWS Elastic Disaster Recovery to continuously replicate the EC2 instances to the DR region. Maintain the EC2 instances at minimal capacity in the DR region. Utilize an Amazon Route 53 failover routing policy to enable automatic failover to the DR region during a disaster. Adjust the desired capacity of the Auto Scaling group accordingly.
Option B is the correct answer because it leverages infrastructure as code (IaC) to quickly deploy the required infrastructure in the disaster recovery region. It sets up a cross-Region read replica for the database, ensuring that data is up-to-date with an RPO of 30 seconds. AWS Elastic Disaster Recovery continuously replicates the EC2 instances to the DR region, allowing for a fast failover, which meets the RTO of 10 minutes. Running the EC2 instances at minimal capacity in the DR region is cost-effective, and the Amazon Route 53 failover routing policy ensures automatic failover. This solution is both cost-effective and aligns with the required RPO and RTO.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company requires a cost-effective disaster recovery (DR) solution for their e-commerce website, which is hosted on multiple t3.large Amazon EC2 instances using an Amazon RDS for MySQL database. The EC2 instances are managed by an Auto Scaling group spanning several Availability Zones. In the case of a disaster, the website must seamlessly switch to a secondary environment with a Recovery Point Objective (RPO) of 30 seconds and a Recovery Time Objective (RTO) of 10 minutes. Which of the following solutions best meets these stringent requirements?
A
Implement infrastructure as code (IaC) to establish the necessary infrastructure in the disaster recovery region. Configure a cross-Region read replica for the database instance. Utilize AWS Backup to schedule cross-Region backups for both the EC2 instances and the database instance, with backups triggered every 30 seconds to the DR region. Restore the EC2 instances from the most recent backup. Employ an Amazon Route 53 geolocation routing policy to facilitate automatic failover to the DR region during a disaster.
B
Leverage infrastructure as code (IaC) to deploy the required infrastructure in the disaster recovery region. Set up a cross-Region read replica for the database instance. Employ AWS Elastic Disaster Recovery to continuously replicate the EC2 instances to the DR region. Maintain the EC2 instances at minimal capacity in the DR region. Utilize an Amazon Route 53 failover routing policy to enable automatic failover to the DR region during a disaster. Adjust the desired capacity of the Auto Scaling group accordingly.
C
Configure a backup plan in AWS Backup to execute cross-Region backups for the EC2 instances and the database instance. Schedule backups every 30 seconds to the DR region using a cron expression. Use infrastructure as code (IaC) to set up the new infrastructure in the DR region. Manually restore the backed-up data onto new instances. Implement an Amazon Route 53 simple routing policy to support automatic failover to the DR region during a disaster.
D
Utilize infrastructure as code (IaC) to create the infrastructure in the disaster recovery region. Establish an Amazon Aurora global database. Set up AWS Elastic Disaster Recovery to continuously replicate the EC2 instances to the DR region. Operate the Auto Scaling group of EC2 instances at full capacity in the DR region. Apply an Amazon Route 53 failover routing policy to ensure automatic failover to the DR region during a disaster.