How can these requirements be met?
Create read replicas for the RDS database and use them in case of a database failure
Create a new RDS instance from the snapshot of the original RDS instance if a failure occurs
Keep a separate RDS database running and switch the endpoint in the web application if a failure occurs
Modify the RDS instance to be a Multi-AZ deployment
Explanations:
Read replicas are intended for read scalability, not failover. They do not automatically handle failover in case of database unresponsiveness.
Creating a new RDS instance from a snapshot is a manual process that would require downtime. It doesn’t provide automatic failover.
Maintaining a separate RDS instance for failover requires manual intervention to switch endpoints, which would lead to downtime and is not an automated failover solution.
A Multi-AZ deployment provides automatic failover to a standby database in case of failure, ensuring high availability for the RDS instance.