A healthcare provider is deploying a critical patient scheduling web application on AWS that requires a highly resilient database tier. The database must support automatic failover with a Recovery Time Objective () of less than 60 seconds and a Recovery Point Objective () of (no data loss). Additionally, the application experiences read-heavy traffic spikes during morning scheduling hours that must be scaled efficiently.
Which combination of database configurations will meet these requirements? (Select TWO.)
- Deploy the database as an Amazon Aurora MySQL DB cluster with a primary DB instance and one or more Aurora Replicas in different Availability Zones.Cevap
- Configure the application to connect to the database cluster's reader endpoint for read operations.Cevap
- CDeploy a single-instance Amazon RDS for MySQL database and configure an RDS Read Replica in a different Availability Zone to serve as the automatic failover target.
- DSet up an Amazon RDS for MySQL Multi-AZ DB instance deployment and configure the application to write to the secondary standby replica during peak hours to distribute write load.
- EConfigure an Amazon Route 53 Latency routing policy to redirect database connection traffic to a backup database in a different AWS Region when the primary database is unhealthy.
Cevap
Deploy the database as an Amazon Aurora MySQL DB cluster with a primary DB instance and one or more Aurora Replicas in different Availability Zones, and configure the application to connect to the database cluster's reader endpoint for read operations.
Deploying an Amazon Aurora cluster with Replicas in different Availability Zones provides automated failover within 30 seconds without data loss because of its shared virtual storage volume, meeting both RTO and RPO requirements. Utilizing the reader endpoint allows the application to balance read requests across the replicas, solving the read scaling requirement.
Adım Adım Çözüm
Anahtar Kavram
High availability and read scaling in Amazon Aurora DB clusters