A bank runs Amazon RDS for PostgreSQL as a single Availability Zone instance. The database must fail over on its own if that Availability Zone is lost, without an operator promoting a replica. Which configuration meets that requirement?
Select an answer to reveal the explanation.
Short Explanation
A read replica is a spare you still have to promote, and placing it in the same Availability Zone won’t protect you if that zone is lost. With Multi-AZ, you get an in-sync standby that takes over automatically; Performance Insights and a Friday snapshot don’t provide that failover.
Full Explanation
Converting the DB instance to a Multi-AZ deployment meets the requirement because it maintains a synchronous standby in another Availability Zone and fails over to it without an operator promoting anything. A read replica in the same Availability Zone does not survive loss of that zone, and promotion is a deliberate step, so it does not provide the automatic failover the bank requires. Performance Insights shows database load and waits, but it does not add a standby or change the single Availability Zone deployment’s failure behavior. A manual Friday snapshot is a backup, not a running failover target, and storing it in the same Region does not make it an automatic replacement for the instance. Exam caveat: the standby in a Multi-AZ DB instance is for failover, not for serving read traffic. Practical check: confirm that Multi-AZ is enabled and note the standby’s Availability Zone before considering the change complete.