Examkin

Question

Difficulty: Very hardResilient Database Configurations and High Availability

An enterprise organization is migrating a high-volume PostgreSQL database to AWS. The application demands a multi-region disaster recovery architecture that can survive a complete AWS Region outage. The business specifies a Recovery Point Objective (RPO) of less than 1 second and a Recovery Time Objective (RTO) of less than 2 minutes. Additionally, read requests from users in the recovery region must be served locally with sub-second latency to optimize user experience. Which combination of actions should a solutions architect recommend to satisfy these resilience and performance criteria? (Select TWO.)

  1. Create an Amazon Aurora PostgreSQL Global Database with the primary cluster located in the primary region and a secondary cluster in the recovery region.Answer
  2. In the event of a primary region outage, initiate a managed failover of the Aurora Global Database to promote the secondary cluster to primary.Answer
  3. C
    Deploy an Amazon RDS for PostgreSQL Multi-AZ DB instance in the primary region and configure a cross-region read replica in the recovery region with automatic failover enabled in the RDS console.
  4. D
    Configure a Pilot Light disaster recovery strategy where AWS Backup copies automated database snapshots to the recovery region every hour, and use custom scripts to restore the database during a regional failover.
  5. E
    Configure Amazon Route 53 with latency-based routing to dynamically distribute database write operations between the two regions to reduce database replication lag.

Answer

Deploying an Amazon Aurora PostgreSQL Global Database and using managed failover during a regional outage satisfies the strict recovery and latency requirements.
Deploying an Amazon Aurora PostgreSQL Global Database ensures storage-level replication to the secondary region with lag typically below 1 second, which satisfies the sub-second RPO. The secondary cluster allows read requests in the backup region to be served locally with sub-second latency. In the event of a regional failure, initiating a managed failover promotes the secondary cluster to primary, maintaining the global database layout and meeting the RTO of under 2 minutes.

Step-by-Step Solution

1
Analyze recovery objectives and read latency constraints.
Identified RPO < 1 second, RTO < 2 minutes, and local read scaling in the recovery region.
This establishes the architectural boundary and eliminates low-performance backup or standard asynchronous replication models.
2
Evaluate database engine replication capabilities.
Amazon Aurora Global Database provides storage-level replication with lag under 1 second, supporting local read replicas in the secondary region.
Standard RDS replication has higher latency overhead and does not support native cross-region failover automation.
3
Identify failover mechanism to meet target RTO.
Managed failover of Aurora Global Database automates the promotion of the secondary cluster with minimal disruption.
Manual promotion of replicas takes longer and breaks the global database replication topology.

Key Concept

High availability and disaster recovery design using Amazon Aurora Global Databases.
Rate this question

Topics

Resilient Database Configurations and High Availability

More questions from this topic