Soru

Zorluk: OrtaResilient Database Configurations and High Availability

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 (RTORTO) of less than 60 seconds and a Recovery Point Objective (RPORPO) of 00 (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.)

  1. 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
  2. Configure the application to connect to the database cluster's reader endpoint for read operations.Cevap
  3. C
    Deploy 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.
  4. D
    Set 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.
  5. E
    Configure 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

1
Evaluate the HA, RTO, and RPO requirements.
The requirement of automatic failover, RTO < 60s, and RPO = 0 points to Amazon Aurora's shared storage architecture with Aurora Replicas, which automatically handles failover in about 30 seconds with no data loss.
Standard RDS Multi-AZ DB instances provide HA but do not natively scale reads without adding separate Read Replicas, whereas Aurora integrates replica failover and cluster-wide read scalability out of the box.
2
Address the read scaling requirement.
Using the Aurora reader endpoint directs read traffic to the Aurora Replicas, offloading read-heavy queries from the primary writer instance.
This scales reads efficiently during morning traffic spikes without impacting write operations.
3
Analyze why other choices are incorrect.
Configurations relying on manual promotion of RDS Read Replicas or attempting to write directly to passive RDS standby replicas fail to meet high availability or operational guidelines.
RDS standby instances in a Multi-AZ deployment do not accept connections, and RDS Read Replicas are asynchronously replicated and cannot failover automatically.

Anahtar Kavram

High availability and read scaling in Amazon Aurora DB clusters
Bu soruyu puanla