Q20 — AWS SAA-C03 Ch.14

Question 20 of 100 | ← Chapter 14

Q1020. A company runs a web application on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer (ALB). The application stores data in an Amazon Aurora MySQL DB cluster.The company needs to create a disaster recovery (DR) solution. The acceptable recovery time for the DR solution is up to 30 minutes. The DR solution does not need to support customer usage when the primary infrastructure is healthy.Which solution will meet these requirements?

Correct Answer: A. Deploy the DR infrastructure in a second AWS Region with an ALB and an Auto Scaling group. Set the desired capacity and maximum capacity of the Auto Scaling group to a minimum value. Convert the Aurora MySQL DB cluster to an Aurora global database. Configure Amazon Route 53 for an active- passive failover with ALB endpoints.

Explanation

To create a disaster recovery (DR) solution that meets the requirements of a recovery time of up to 30 minutes without needing to support customer usage when the primary infrastructure is healthy, the best solution is:A. Deploy the DR infrastructure in a second AWS Region with an ALB and an Auto Scaling group. Set the desired capacity and maximum capacity of the Auto Scaling group to a minimum value. Convert the Aurora MySQL DB cluster to an Aurora global database. Configure Amazon Route 53 for an active-passive failover with ALB endpoints.Explanation:\1. DR Infrastructure in a Second Region: - Deploying the infrastructure in a separate AWS Region ensures that the DR solution is geographically isolated from the primary infrastructure, which is essential for effective disaster recovery.\2. Aurora Global Database: - Converting the Aurora MySQL DB cluster to an Aurora global database allows for low-latency replication across regions. This ensures that the data is nearly up to date in the DR region, facilitating a quick recovery.\3. Auto Scaling Group Configuration: - Setting the desired capacity and maximum capacity of the Auto Scaling group to a minimum value allows for the DR resources to be provisioned and ready to respond quickly when needed, without incurring high costs during normal operations.\4. Route 53 Active-Passive Failover: - Configuring Route 53 for active-passive failover allows traffic to switch to the DR infrastructure only when the primary infrastructure fails. This approach minimizes unnecessary costs while still ensuring a quick failover.Evaluation of Other Options:B. Deploy the DR infrastructure in a second AWS Region with an ALB: - This option suggests active-active failover, which is not needed as the requirement states that the DR does not need to support customer usage when the primary infrastructure is healthy. Active-active configurations can be more complex and costly.C. Back up the Aurora MySQL DB cluster data by using AWS Backup: - While this option involves creating a new Aurora cluster from backups, it may exceed the 30-minute recovery time requirement due to the time taken to restore data. Additionally, the complexity of managing active-active failover is not necessary.D. Back up the infrastructure configuration by using AWS Backup: - This option involves creating the infrastructure in the DR region but does not directly address the need for an Aurora global database for quick data recovery. Setting the Auto Scaling group desired capacity to zero may delay the recovery process.Conclusion:Option A provides an efficient and cost-effective way to implement a disaster recovery strategy that aligns with the company’s requirements for a 30-minute recovery time while ensuring minimal operational costs during normal conditions.