How should you handle database failover in RDS Multi-AZ deployments?

Correct answer: AWS handles automatic failover; the primary database fails over to the standby replica

Option A is correct because Amazon RDS Multi-AZ deployments use synchronous replication to a standby instance in a different Availability Zone, and AWS automatically detects primary instance failures and promotes the standby, updating the DNS endpoint so applications reconnect without manual intervention or code changes. Option B is wrong because no application code changes are required for failover; the DNS CNAME for the RDS endpoint is automatically updated by AWS during the failover event. Option C is wrong because failover in Multi-AZ is fully automatic; administrators do not need to manually trigger it, though a manual failover can be initiated for testing purposes. Option D is wrong because providing automatic failover is the primary purpose of Multi-AZ deployments, making this option directly contradictory to the feature's design.