A team runs an Amazon RDS for MySQL database in a single Availability Zone. They want automatic failover with minimal downtime if the primary database instance becomes unavailable. Automated backups are already enabled. Which configuration change best meets the requirement?
Trap 1: Keep the deployment as single-AZ, but increase automated backup…
Increasing automated backup retention from the default to 35 days only extends the window for point-in-time recovery and allows you to restore a historical database state. It does nothing to create a second, synchronized instance in another Availability Zone — no standby exists to take over if the primary fails. Because RDS remains single-AZ, an AZ outage or instance failure will still cause downtime until a manual restore or restart completes, so this does not satisfy the requirement for automatic failover.
Trap 2: Create a read replica in another Availability Zone, but keep…
A read replica provides additional read capacity and offloading, but it is not the same as the managed Multi-AZ synchronous standby used for automatic failover. Read replicas generally do not provide the same automated promotion behavior for the primary endpoint during an AZ outage.
Trap 3: Rely on restoring from the most recent manual snapshot after an…
Restoring from a manual snapshot after an outage is a manual recovery procedure, not an automatic one. It requires you to notice the failure, initiate a restore operation that typically provisions a new DB instance, and then wait for the restore to complete — minutes to hours depending on database size. Moreover, a snapshot only captures a point in time, so any transactions committed after the snapshot was taken are lost, unlike Multi-AZ's synchronous replication that maintains a fully current standby for automatic failover.
- A
Keep the deployment as single-AZ, but increase automated backup retention to 35 days.
Why it fails: Increasing automated backup retention from the default to 35 days only extends the window for point-in-time recovery and allows you to restore a historical database state. It does nothing to create a second, synchronized instance in another Availability Zone — no standby exists to take over if the primary fails. Because RDS remains single-AZ, an AZ outage or instance failure will still cause downtime until a manual restore or restart completes, so this does not satisfy the requirement for automatic failover.
- B
Create a read replica in another Availability Zone, but keep Multi-AZ disabled.
Why it fails: A read replica provides additional read capacity and offloading, but it is not the same as the managed Multi-AZ synchronous standby used for automatic failover. Read replicas generally do not provide the same automated promotion behavior for the primary endpoint during an AZ outage.
- C
Enable RDS Multi-AZ so AWS maintains a standby in another Availability Zone for automatic failover.
RDS Multi-AZ creates a standby instance in a different AZ and replicates data to it. If the primary becomes unavailable, AWS performs an automatic failover, promoting the standby and maintaining high availability with minimal application disruption.
- D
Rely on restoring from the most recent manual snapshot after an outage.
Why it fails: Restoring from a manual snapshot after an outage is a manual recovery procedure, not an automatic one. It requires you to notice the failure, initiate a restore operation that typically provisions a new DB instance, and then wait for the restore to complete — minutes to hours depending on database size. Moreover, a snapshot only captures a point in time, so any transactions committed after the snapshot was taken are lost, unlike Multi-AZ's synchronous replication that maintains a fully current standby for automatic failover.