How to Replicate Aurora MySQL Cross-Region for DR at Lowest Cost?
A company runs an ecommerce application in a single AWS Region. The application uses a five-node Amazon Aurora MySQL DB cluster to store information about customers and their recent orders. The DB cluster experiences a large number of write transactions throughout the day. The company needs to replicate the data in the Aurora database to another Region to meet disaster recovery requirements. The company has an RPO of 1 hour. Which solution will meet these requirements with the LOWEST cost?
Community Insight
The question tests cross-Region DR for Aurora and the trap is choosing DMS CDC or hourly backups because they seem cheaper while ignoring restorability and Aurora backup constraints.
Aurora Global Database is the valid cross-Region disaster recovery solution for an Aurora MySQL cluster with a one-hour RPO. The page explains why the lower-cost-sounding DMS-to-S3 and hourly backup options do not provide a directly restorable Aurora database.
A common wrong choice is DMS change data capture to S3 in another Region; it can replicate changes, but the resulting Parquet or CSV files are not a restorable Aurora disaster recovery copy.
Community Discussion (71 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Aurora Global Database is AWS's managed cross-Region replication feature for Aurora. It creates a secondary Aurora cluster in the DR Region and continuously replicates storage, giving an RPO far below the required one hour and a directly promotable Aurora database. For a five-node write-heavy MySQL cluster, this avoids building and operating a separate CDC and ETL pipeline. Although the secondary Region has instance and cross-Region transfer costs, among the options that actually deliver restorable Aurora DR it is the lowest-cost valid solution. The question's LOWEST cost requirement must be read together with the DR and RPO requirements, not as permission to store unusable change files.Why the Other Options Are Wrong
B uses Backtrack, which only rewinds the same cluster in place, and a daily Lambda snapshot copy gives an RPO of up to 24 hours, not 1 hour. C's DMS CDC task to S3 can capture changes within the RPO window, but S3 Parquet or CSV change files are not an Aurora backup and cannot be promoted or restored directly as a database in the DR Region; using them for DR requires ETL and reload, which does not meet the stated objective. D suggests turning off Aurora automated backups, which is not possible for Aurora, and hourly backup copies would still be snapshot-based rather than continuous replication for a reliable one-hour RPO. That makes D unimplementable as written and still weaker for DR than an Aurora global database.Community Comment Notes
TonytheTiger focused on the key requirements, including RPO under one hour, DR, and lowest cost, and pointed to the Aurora Global Database documentation, which aligns with A. Wardove argued that DMS-to-S3 is "not a Disaster Recovery" because Parquet or CSV files are not directly restorable into a database. kjcncjek noted that "You can't disable automated backups on Aurora," which undermines option D. kgpoj observed that Global Database can achieve a one-second RPO but is more expensive; that cost point is real, yet C and D do not provide a valid restorable Aurora DR target, so cost alone cannot make them correct. Some learners selected C, but their rationale stops at replication-to-S3 rather than database recovery.Official Reference
Exam Strategy
For SAP-C02 DR questions, first verify that the option creates a restorable workload in the target Region, then compare cost and RPO. Eliminate choices that only copy change files or snapshots when the requirement is database recovery, and watch for unsupported actions such as disabling Aurora automated backups.
Frequently Asked Questions
Why is DMS CDC to S3 not a valid Aurora DR solution here?
DMS writes change data as CSV or Parquet in S3, not a restorable Aurora cluster. Restoring would require ETL and reload, so it does not meet the database DR requirement.
Can Aurora automated backups be disabled to use hourly cross-Region backups?
Aurora automated backups cannot be disabled; retention is managed at the DB cluster level. That makes option D not implementable as written.
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →