A company runs a critical transactional workload on a single-instance Amazon RDS for MySQL database in a single Availability Zone. The database tier must be redesigned to survive an Availability Zone outage with a Recovery Point Objective (RPO) of zero (no data loss) and a Recovery Time Objective (RTO) of less than 2 minutes. Which configuration will meet these requirements with the least administrative effort?
- Modify the Amazon RDS for MySQL database instance to a Multi-AZ DB instance deployment.Answer
- BCreate an Amazon RDS Read Replica in a different Availability Zone and configure the application to promote it manually during a failover.
- CConfigure AWS Backup to take hourly database snapshots and restore them to a new DB instance in a different Availability Zone upon failure.
- DDeploy a second independent RDS DB instance in a different Availability Zone and use Route 53 latency-based routing to distribute database traffic.
Answer
Modify the Amazon RDS for MySQL database instance to a Multi-AZ DB instance deployment.
Modifying the DB instance to a Multi-AZ deployment is correct because Amazon RDS automatically provisions and maintains a synchronous standby replica in a different Availability Zone. Updates are synchronously committed to both the primary and standby databases, achieving an RPO of zero. In the event of an AZ outage, RDS automatically handles failover to the standby instance, typically completing in under 2 minutes (meeting the RTO requirement) without manual intervention.
Step-by-Step Solution
Key Concept
Amazon RDS Multi-AZ Deployment