Soru

Zorluk: OrtaResilient Database Configurations and High Availability

An enterprise is migrating a critical SQL-based inventory application to AWS. The database must be highly available within a single AWS Region. The architecture must achieve a Recovery Time Objective (RTO) of less than 30 seconds and a Recovery Point Objective (RPO) of zero (no data loss) during an Availability Zone outage. Additionally, the application experiences sudden spikes in read traffic that must be scaled independently without affecting the primary write database. Which two database configurations or actions should a solutions architect recommend to satisfy these requirements? (Select TWO.)

  1. Deploy an Amazon Aurora PostgreSQL DB cluster with a primary DB instance and at least one Aurora Replica in a different Availability Zone.Cevap
  2. Configure the application's read operations to use the DB cluster reader endpoint.Cevap
  3. C
    Create a single-instance Amazon RDS PostgreSQL DB instance and set up an RDS Read Replica in a different Availability Zone to serve as the automatic failover target.
  4. D
    Configure an Amazon RDS PostgreSQL Multi-AZ DB instance and use Amazon Route 53 latency-based routing to distribute read queries to the standby database instance.
  5. E
    Set up an Amazon RDS PostgreSQL DB instance in one Availability Zone and configure AWS Database Migration Service (AWS DMS) to sync data to a scaled-down warm standby instance in another Availability Zone.

Cevap

Deploying an Amazon Aurora PostgreSQL DB cluster with a primary DB instance and at least one Aurora Replica in a different Availability Zone, and configuring the application's read operations to use the DB cluster reader endpoint.
Deploying an Amazon Aurora PostgreSQL DB cluster with a replica in another Availability Zone ensures automatic failover in less than 30 seconds with zero data loss, satisfying both the RTO and RPO requirements. Directing read traffic to the Aurora reader endpoint allows read queries to be load-balanced across replicas, scaling the read workload independently of the primary write instance.

Adım Adım Çözüm

1
Evaluate the HA failover time (RTO) and data loss (RPO) requirements.
Identify that a database configuration with automatic failover under 30 seconds and synchronous replication (RPO of 0) is necessary. Amazon Aurora PostgreSQL with an Aurora Replica fits this requirement.
Amazon Aurora automates failover to a replica within 30 seconds, and its shared storage architecture replicates writes synchronously across three Availability Zones to prevent data loss.
2
Address the requirement to scale read traffic independently without impacting write operations.
Determine that read operations should be routed away from the primary writer instance using a read-scaling mechanism. In Aurora, this is handled by connecting to the reader endpoint.
The Aurora reader endpoint automatically load balances read-only connections among available Aurora Replicas, isolating read-heavy spikes from the primary writer instance.
3
Eliminate options that fail to meet high availability, replication, or read-scaling constraints.
Exclude configurations using RDS Read Replicas for primary failover (requires manual intervention), RDS standby instances for read traffic (standbys are passive), or AWS DMS to a warm standby (asynchronous replication with higher RTO).
These configurations violate basic AWS RDS/Aurora architectural constraints regarding read routing, synchronous replication, and automated failover capabilities.

Anahtar Kavram

Amazon Aurora high availability architecture relies on synchronous storage replication across multiple Availability Zones, automated failover to Aurora Replicas within 30 seconds, and endpoint management (writer and reader endpoints) to decouple read and write traffic.
Bu soruyu puanla