Examkin

Question

Difficulty: MediumResilient Database Configurations and High Availability

A pharmaceutical research company operates a clinical trial monitoring application. The application stores real-time patient telemetry data in an Amazon Aurora PostgreSQL DB cluster. The company requires a disaster recovery strategy across two AWS Regions. The database configuration must achieve a Recovery Point Objective (RPO) of less than 22 seconds and a Recovery Time Objective (RTO) of less than 22 minutes. Additionally, researchers in both regions need low-latency access to read the telemetry data. Which database configuration meets these requirements with the least operational complexity?

  1. Deploy an Amazon Aurora Global Database with the primary DB cluster in the main region and a secondary DB cluster in the recovery region.Answer
  2. B
    Deploy an Amazon RDS for PostgreSQL database in the primary region, create a cross-region Read Replica in the recovery region, and configure the application to automatically promote the replica during an outage.
  3. C
    Configure a Pilot Light disaster recovery strategy by deploying a stopped Amazon Aurora DB cluster in the recovery region, copying snapshots hourly, and restoring them during a failure.
  4. D
    Deploy independent Amazon Aurora DB clusters in both regions, and configure Amazon Route 53 latency-based routing to dynamically route write requests and handle failover.

Answer

Deploy an Amazon Aurora Global Database with the primary DB cluster in the main region and a secondary DB cluster in the recovery region.
The correct database configuration is to deploy an Amazon Aurora Global Database. Aurora Global Databases use storage-based replication to copy data to secondary regions with a typical replication lag of less than 11 second, fulfilling the RPO constraint of less than 22 seconds. The secondary cluster allows read scaling with local low latency for remote users. In the event of a primary region outage, the secondary cluster can be promoted to a primary read-write cluster in less than 22 minutes, meeting the RTO constraint.

Step-by-Step Solution

1
Analyze the disaster recovery constraints, specifically the Recovery Point Objective (RPO) of less than 22 seconds and the Recovery Time Objective (RTO) of less than 22 minutes.
The solution must support near real-time data replication (under 22 seconds) and rapid failover (under 22 minutes) between regions.
This filters out backup-and-restore or pilot-light strategies that introduce recovery delays.
2
Analyze the read scalability requirement for researchers in both regions to access data with low latency.
The target configuration must allow active read operations in the secondary region.
This requires a database engine that supports active read replicas or secondary active reader clusters in the remote region.
3
Compare Aurora Global Database capabilities against Amazon RDS cross-region replication.
Amazon Aurora Global Database provides storage-level replication with lag under 11 second and managed regional failover that takes less than 22 minutes, meeting all criteria with minimal operational overhead.
Aurora Global Database is the native AWS solution designed for low-latency multi-region read scaling and fast cross-region failover.

Key Concept

Amazon Aurora Global Database replication and regional failover capabilities.
Estimated Time:1m 30s
Rate this question

Topics

Resilient Database Configurations and High Availability

More questions from this topic