A financial services company is designing a multi-tier application that must achieve a Recovery Time Objective (RTO) of 1 hour and a Recovery Point Objective (RPO) of 15 minutes for a database tier. The application uses Amazon RDS for MySQL with Multi-AZ deployment. Which disaster recovery strategy meets these requirements at the LOWEST cost?
Cross-Region read replicas provide asynchronous replication with low RPO, and promotion takes minutes, meeting RTO at lower cost than other solutions.
Why this answer
A cross-Region read replica for Amazon RDS MySQL provides asynchronous replication with an RPO typically under 15 minutes, and promoting it during a disaster can achieve an RTO of 1 hour. This approach incurs only the cost of the replica instance and cross-Region data transfer, making it the lowest-cost option that meets the stated RTO and RPO requirements.
Exam trap
The trap here is that candidates may confuse Multi-AZ (high availability within a Region) with cross-Region disaster recovery, or assume that Aurora Global Database is always the best choice for low RPO without considering cost constraints, leading them to overlook the simpler and cheaper cross-Region read replica option that still meets the specified RPO of 15 minutes.
How to eliminate wrong answers
Option A is wrong because Multi-AZ is a high-availability feature within a single Region, not a disaster recovery strategy; taking frequent snapshots to another Region cannot achieve an RPO of 15 minutes due to snapshot scheduling overhead and recovery time. Option B is wrong because AWS DMS for continuous replication adds significant cost for a replication instance and ongoing data transfer, and it is not the lowest-cost solution for the given RPO/RTO. Option C is wrong because Amazon Aurora Global Database, while offering very low RPO (~1 second), is more expensive than a cross-Region read replica for MySQL and exceeds the required RPO of 15 minutes, making it over-engineered and not the lowest-cost option.