Soru

Zorluk: ZorResilient Database Configurations and High Availability

A healthcare provider is deploying a patient prescription tracking application across two AWS Regions: useast1us-east-1 (Primary) and uswest2us-west-2 (Secondary). The application backend uses an Amazon Aurora PostgreSQL DB cluster. The solutions architect must design a highly resilient architecture that meets a Recovery Time Objective (RTO) of under 55 minutes and a Recovery Point Objective (RPO) of under 11 minute for regional disaster recovery, while also providing high availability within the primary region (RTO of under 6060 seconds, RPO of 00) and scaling read traffic locally in uswest2us-west-2. Which two configurations should the solutions architect implement to meet these requirements? (Select two.)

  1. Deploy the primary Amazon Aurora PostgreSQL DB cluster in useast1us-east-1 across multiple Availability Zones, ensuring at least one reader instance is running in a different Availability Zone than the writer instance.Cevap
  2. Configure an Amazon Aurora Global Database with the primary cluster in useast1us-east-1 and a secondary cluster in uswest2us-west-2, provisioning at least one reader instance in the secondary cluster.Cevap
  3. C
    Provision a single-AZ Aurora PostgreSQL DB cluster in useast1us-east-1 and set up an Aurora Read Replica in uswest2us-west-2, using a custom script to promote the replica to a standalone cluster if the primary region fails.
  4. D
    Use Amazon Route 53 with latency-based routing to distribute write operations to both useast1us-east-1 and uswest2us-west-2 database endpoints simultaneously to minimize write latency for global users.
  5. E
    Implement a Warm Standby strategy by copying automated snapshots of the primary database to uswest2us-west-2 hourly, and provision a new Aurora DB cluster from the latest snapshot only during a regional disaster.

Cevap

Deploying the primary Amazon Aurora PostgreSQL DB cluster in us-east-1 across multiple Availability Zones, ensuring at least one reader instance is running in a different Availability Zone than the writer instance, and configuring an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2 containing at least one reader instance.
Deploying the primary Amazon Aurora PostgreSQL database cluster in a Multi-AZ configuration ensures that the storage layer replicates data across multiple Availability Zones synchronously. If the primary writer instance fails, Aurora automatically promotes a reader instance in a different Availability Zone in under 60 seconds with zero data loss, achieving the local high availability goals. Meanwhile, configuring an Amazon Aurora Global Database creates a dedicated cross-region replication channel. The database is replicated asynchronously at the physical storage level with replication lag typically under 1 second, meeting the 1-minute RPO. The secondary cluster reader instance in the secondary region scales local reads and can be promoted to a writer within minutes to meet the 5-minute RTO during a disaster recovery scenario.

Adım Adım Çözüm

1
Evaluate the high availability (HA) constraints in the primary region (useast1us-east-1).
An RTO of under 6060 seconds and RPO of 00 is identified. To meet this, the primary database must be deployed across multiple Availability Zones with synchronous storage replication and a standby reader instance ready for automatic failover.
Ensures that local infrastructure or AZ failure triggers automated failover with no data loss.
2
Evaluate the regional disaster recovery (DR) and read-scaling requirements in the secondary region (uswest2us-west-2).
An RTO of under 55 minutes and RPO of under 11 minute is identified, along with the need to serve local reads. A cross-region replication mechanism with sub-minute lag is required.
Determines the target disaster recovery mechanism that also allows active read workloads.
3
Select the correct combination of Amazon Aurora features to satisfy the constraints.
Aurora Multi-AZ deployment is selected for primary region HA, and Aurora Global Database with a secondary reader in us-west-2 is selected for regional DR and local read scaling.
Aurora Global Database replicates data storage-to-storage with a typical lag of under 11 second and supports seamless, low-RTO failovers.

Anahtar Kavram

Combining Amazon Aurora Multi-AZ deployment for local high availability with Amazon Aurora Global Database for cross-region disaster recovery and local read scaling.
Bu soruyu puanla