Soru

Zorluk: ZorResilient Database Configurations and High Availability

A global financial technology enterprise is migrating its transaction auditing system to AWS. The system must run across two AWS Regions: us-east-1 as the primary region and us-west-2 as the disaster recovery region. The database layer must support high-performance local read operations in both regions while routing all write operations to us-east-1. The disaster recovery requirements dictate a Recovery Point Objective (RPO) of less than 1 second and a Recovery Time Objective (RTO) of less than 1 minute. Which database configuration best meets these requirements with the least operational complexity?

  1. A
    Configure an Amazon RDS for PostgreSQL DB instance in us-east-1 with a cross-region read replica in us-west-2, and configure Amazon Route 53 to automatically promote the replica to primary if the primary region fails.
  2. Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, using Aurora physical replication to maintain synchronization.Cevap
  3. C
    Provision an Amazon RDS for PostgreSQL Multi-AZ DB instance in us-east-1 and a stopped pilot light DB instance in us-west-2, automating the startup and transaction log restoration from Amazon S3 upon failover.
  4. D
    Set up Amazon RDS for PostgreSQL Multi-AZ deployments in both us-east-1 and us-west-2, and use Amazon Route 53 latency-based routing with active health checks to synchronize write transactions across both regions.

Cevap

Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2, using Aurora physical replication to maintain synchronization.
Deploying an Amazon Aurora PostgreSQL Global Database is the most resilient design for these requirements. It replicates data across regions at the storage tier using physical replication, keeping replica lag under 1 second to meet the RPO requirement. In a failover scenario, the secondary cluster can be promoted to primary in under 1 minute to meet the RTO requirement, while natively supporting high-performance local reads in both regions.

Adım Adım Çözüm

1
Analyze RPO, RTO, and multi-region read/write requirements.
Identify that the system needs storage-level cross-region replication with lag under 1 second and regional recovery orchestration under 1 minute.
Narrow down database architectures to those capable of meeting the strict high-availability and disaster recovery thresholds.
2
Evaluate the replication mechanics of Amazon Aurora Global Databases.
Confirm that Aurora physical replication operates at the storage layer with typical lag of less than 1 second (satisfying the RPO) and can be promoted to primary in under 1 minute (satisfying the RTO).
Ensure the selected configuration natively aligns with the target metrics.
3
Assess and eliminate alternative configurations that introduce lag, manual steps, or incorrect routing.
Identify that RDS read replica promotion is manual, pilot light startup is too slow, and Route 53 cannot replicate transactional writes.
Eliminate distractors that fail to meet either the performance or recovery requirements.

Anahtar Kavram

Using Amazon Aurora Global Databases to achieve multi-region read scaling, sub-second RPO storage-level replication, and sub-minute RTO failover capabilities.
Tahmini Süre:2m 30s
Bu soruyu puanla