A financial services company runs a critical transactional application backed by an Amazon RDS PostgreSQL DB instance. Currently, the database is deployed in a single Availability Zone (AZ). Due to compliance regulations, the database layer must be redesigned to ensure high availability. The solution must achieve a Recovery Point Objective (RPO) of zero (no data loss) and a Recovery Time Objective (RTO) of under two minutes in the event of an AZ failure. Which database configuration should a solutions architect recommend to meet these requirements?
- Modify the existing Amazon RDS DB instance to be a Multi-AZ deployment.Cevap
- BCreate an Amazon RDS Read Replica in a different Availability Zone, and configure a custom monitoring script to promote the read replica to primary if the primary instance fails.
- CDeploy a warm standby Amazon RDS PostgreSQL DB instance in a different AWS Region, and use AWS Database Migration Service (AWS DMS) to continuously replicate data.
- DDeploy an Amazon RDS Read Replica in a second Availability Zone, and configure Amazon Route 53 latency-based routing to automatically fail over database connection endpoints.
Cevap
Modify the existing Amazon RDS DB instance to be a Multi-AZ deployment.
Modifying the existing DB instance to a Multi-AZ deployment matches all criteria. It synchronously replicates database changes to a standby instance in a different Availability Zone, ensuring zero data loss (RPO = 0). If the primary instance fails, Amazon RDS automatically performs a failover by updating the database DNS CNAME record to point to the standby instance, which typically takes between one and two minutes (RTO < 2 minutes).
Adım Adım Çözüm
Anahtar Kavram
Amazon RDS Multi-AZ deployments provide high availability, data redundancy, and automatic failover by utilizing synchronous replication to a standby instance in a different Availability Zone.