Q: 18
A company manages a web application that runs on Amazon EC2 instances behind an Application
Load Balancer (ALB). The EC2 instances run in an Auto Scaling group across multiple Availability
Zones. The application uses an Amazon RDS for MySQL DB instance to store the dat
a. The company has configured Amazon Route 53 with an alias record that points to the ALB.
A new company guideline requires a geographically isolated disaster recovery (DR> site with an RTO
of 4 hours and an RPO of 15 minutes.
Which DR strategy will meet these requirements with the LEAST change to the application stack?
Options
Discussion
Option D
Least changes since you just add a cross-region read replica and DR stack, then promote if needed. RPO and RTO requirements are met pretty cleanly this way. Pretty sure that’s what AWS recommends for MySQL DR. Anyone see a reason B would actually be better?
Least changes since you just add a cross-region read replica and DR stack, then promote if needed. RPO and RTO requirements are met pretty cleanly this way. Pretty sure that’s what AWS recommends for MySQL DR. Anyone see a reason B would actually be better?
B tbh, this setup feels right based on official guide and practice test questions.
D is the best pick here. Promoting the RDS read replica in another AWS Region matches the RPO/RTO with minimal app changes. B is tempting but latency routing isn’t DR-focused, and you really want failover for this scenario.
Be respectful. No spam.
