Question

Difficulty: HardResilient Database Configurations and High Availability

A logistics company is designing the database tier for a real-time package tracking system. The database must be compatible with MySQL, support automatic failover within the primary AWS Region with a Recovery Time Objective (RTO) of less than 30 seconds and a Recovery Point Objective (RPO) of 0, and provide a cross-Region disaster recovery (DR) solution with an RTO of under 15 minutes and an RPO of under 5 seconds. Which combination of AWS database configurations will meet these requirements? (Select TWO.)

  1. Deploy the primary database as an Amazon Aurora MySQL DB cluster with a writer instance in one Availability Zone and a reader instance in another Availability Zone.Answer
  2. Configure an Amazon Aurora Global Database by adding a secondary Aurora DB cluster in the recovery Region, utilizing storage-level replication.Answer
  3. C
    Deploy a single-instance Amazon RDS for MySQL database in the primary Region, and create a cross-Region read replica in the recovery Region to handle automatic failover.
  4. D
    Use Amazon Route 53 latency routing to automatically redirect database write traffic between the primary and recovery database endpoints during a failover event.
  5. E
    Implement a Pilot Light disaster recovery strategy by copying hourly database backups to the recovery Region and provisioning a scaled-down database instance that remains in a stopped state until a failover is initiated.

Answer

Deploying the primary database as an Amazon Aurora MySQL DB cluster with a writer and a reader instance in different Availability Zones, and configuring an Amazon Aurora Global Database by adding a secondary cluster in the recovery Region.
The correct combination consists of deploying the primary database as an Amazon Aurora MySQL DB cluster with a reader instance in a different Availability Zone (providing local Multi-AZ high availability with RTO < 30 seconds and RPO = 0 via shared storage replication) and configuring an Amazon Aurora Global Database with a secondary cluster in the recovery Region (meeting the RTO of under 15 minutes and RPO of under 5 seconds through low-latency storage-level replication).

Step-by-Step Solution

1
Evaluate the database compatibility and local resilience requirements.
The requirement for MySQL compatibility, local RTO < 30 seconds, and local RPO = 0 points to Amazon Aurora MySQL. Deploying an Aurora cluster with a writer in one Availability Zone and a reader in a different Availability Zone enables automatic failover in under 30 seconds with 0 data loss (RPO = 0) because the underlying storage volume is replicated across three Availability Zones.
Traditional RDS read replicas or single-instance databases do not support automatic failover or fail to meet the 30-second RTO.
2
Evaluate the disaster recovery requirements for the secondary Region.
The requirements of RTO < 15 minutes and RPO < 5 seconds are met by Amazon Aurora Global Databases. Aurora Global Databases use storage-based replication to copy data to a secondary Region with a latency of less than 1 second (meeting the RPO of under 5 seconds). If a failover is needed, the secondary cluster can be promoted to a standalone read/write cluster in under a minute (meeting the RTO of under 15 minutes).
Backup-based strategies (like Pilot Light with hourly copies) fail the 5-second RPO, and standard RDS replica failover across Regions is not automated.

Key Concept

Amazon Aurora Multi-AZ deployment and Aurora Global Databases for high availability and low-RPO/RTO cross-Region disaster recovery.
Estimated Time:2m 30s
Rate this question