Cross-Region read replica plus AMI copy and S3 CRR for disaster recovery
A company needs to implement disaster recovery for a critical application that runs in a single AWS Region. The application's users interact with a web frontend that is hosted on Amazon EC2 instances behind an Application Load Balancer (ALB). The application writes to an Amazon RDS for MySQL DB instance. The application also outputs processed documents that are stored in an Amazon S3 bucket. The company’s finance team directly queries the database to run reports. During busy periods, these queries consume resources and negatively affect application performance. A solutions architect must design a solution that will provide resiliency during a disaster. The solution must minimize data loss and must resolve the performance problems that result from the finance team's queries. Which solution will meet these requirements?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
A cross-Region read replica serves the finance reporting load continuously and can be promoted in seconds during a disaster, so recovery point is near zero and the reporting problem is solved by the same component.
A single-Region application behind an ALB writes to RDS for MySQL and outputs documents to S3, while finance queries on the primary database hurt application performance. The design must survive a regional disaster, minimize data loss, and fix the query contention.
Assuming an ALB can front instances in another Region. An Application Load Balancer is a regional service, so EC2 instances in a different Region cannot be added to an existing ALB, which is why option B cannot work.
Community Discussion (7 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Creating an RDS read replica in a second Region offloads the finance queries from the primary instance, resolving the performance problem, and it continuously replicates so a disaster loses almost no committed transactions. Copying AMIs of the frontend instances to that Region provides ready-to-launch capacity, S3 Cross-Region Replication keeps the processed documents mirrored, and during a disaster the replica is promoted to a standalone instance and EC2 plus ALB are launched from the copied AMIs.Why the Other Options Are Wrong
A: Migrating a relational workload to DynamoDB is a re-architecture, not a disaster recovery mechanism, and a periodically invoked Lambda sync to S3 introduces data loss. B: An Application Load Balancer is a regional service, so EC2 instances in a separate Region cannot be added to the existing ALB. D: Hourly snapshots give an RPO of up to one hour, which fails the minimize-data-loss requirement, and ElastiCache does not resolve the reporting contention on a relational database.Community Comment Notes
The community voted 92 to 1 for C. One commenter argued for B on the grounds that C omits redirecting the application to the promoted instance, but the standard answer holds because C explicitly covers replica promotion, AMI-based recovery, and S3 replication in a single Region-independent design.Official Reference
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →