Question

Difficulty: MediumResilient Database Configurations and High Availability

A hospitality company manages its central reservation system using an Amazon Aurora MySQL-Compatible Edition database cluster in the us-east-1 Region. To ensure business continuity, the company requires a disaster recovery (DR) solution in the us-west-2 Region. The DR architecture must support a Recovery Point Objective (RPO) of less than 11 second and a Recovery Time Objective (RTO) of less than 11 minute. Which database configuration meets these requirements?

  1. A
    Configure Amazon Route 53 latency-based routing to distribute database write operations between the database cluster in the us-east-1 Region and a new independent Aurora DB cluster in the us-west-2 Region.
  2. B
    Deploy a single-region Amazon RDS MySQL DB instance in the us-east-1 Region, create a cross-region read replica in the us-west-2 Region, and configure the replica to perform automatic multi-region failovers.
  3. Create an Amazon Aurora Global Database with the primary cluster in the us-east-1 Region and a secondary cluster in the us-west-2 Region, and promote the secondary cluster in the event of a disaster.Answer
  4. D
    Implement a Pilot Light disaster recovery strategy by scheduling hourly database snapshots in the us-east-1 Region, copying them to the us-west-2 Region, and restoring them to a new DB cluster upon failure.

Answer

Create an Amazon Aurora Global Database with the primary cluster in the us-east-1 Region and a secondary cluster in the us-west-2 Region, and promote the secondary cluster in the event of a disaster.
The correct option is to create an Amazon Aurora Global Database. Aurora Global Database uses storage-based, asynchronous replication that achieves a lag of less than 11 second. If the primary region experiences an outage, the secondary cluster in the target region can be promoted to a standalone primary cluster with read and write capabilities in less than 11 minute, satisfying both the RPO and RTO requirements.

Step-by-Step Solution

1
Analyze recovery objectives and replication constraints.
The requirements dictate a Recovery Point Objective (RPO) of less than 11 second (near-real-time replication) and a Recovery Time Objective (RTO) of less than 11 minute (extremely fast failover or promotion).
Understanding the RTO and RPO limits helps filter out backup-and-restore or slow replication methods.
2
Evaluate cross-region replication technologies for Amazon Aurora.
Amazon Aurora Global Database utilizes dedicated infrastructure at the storage layer to replicate data to secondary regions with typical latencies of less than 11 second, and supporting promotion of the secondary cluster within 11 minute.
Selecting the native high-availability cross-region feature that directly maps to sub-second RPO and sub-minute RTO.
3
Eliminate incorrect options that fail the target recovery metrics or are architecturally invalid.
Route 53 latency routing cannot handle write synchronization; RDS MySQL read replicas do not support automated cross-region failover; hourly snapshots fail both the 11-second RPO and 11-minute RTO constraints.
Ensuring the selected solution is the only one that meets all constraints while avoiding common operational misconceptions.

Key Concept

Cross-Region Disaster Recovery with Amazon Aurora Global Database
Rate this question