Examkin

Question

Difficulty: Very hardResilient Database Configurations and High Availability

A logistics company is designing the database architecture for a global fleet tracking system. The system uses a PostgreSQL database located in the eu-west-1 Region, with a disaster recovery (DR) target in the ap-southeast-1 Region. The system has a strict Recovery Time Objective (RTO) of under 5 minutes and a Recovery Point Objective (RPO) of under 1 minute. Local regional offices in the Asia-Pacific region must also run read-only telemetry reports with low latency, without affecting write performance in Europe.

Which database configuration will meet these requirements with the minimum operational complexity?

  1. Configure an Amazon Aurora PostgreSQL Global Database with the primary cluster in the eu-west-1 Region and a secondary cluster in the ap-southeast-1 Region. Use the secondary cluster's local endpoints for the Asia-Pacific telemetry reports, and perform a managed failover to promote the secondary cluster if the primary region fails.Answer
  2. B
    Migrate the database to Amazon RDS for PostgreSQL in eu-west-1. Create a cross-region read replica in ap-southeast-1 to serve local telemetry reports. Configure an Amazon Route 53 latency routing policy with health checks to automatically redirect write traffic and promote the read replica to primary during a failover.
  3. C
    Deploy Amazon RDS for PostgreSQL in eu-west-1 and configure cross-region automated snapshot copying to ap-southeast-1 every 30 minutes. In the event of a disaster, restore the database from the copied snapshot in ap-southeast-1 and direct the telemetry reports to a newly created read replica.
  4. D
    Deploy independent Amazon Aurora PostgreSQL clusters in both eu-west-1 and ap-southeast-1. Set up an Amazon Route 53 latency routing policy to route write queries to the cluster with the lowest latency, using standard Route 53 health checks to handle automatic failover between regions.

Answer

Configure an Amazon Aurora PostgreSQL Global Database with the primary cluster in the eu-west-1 Region and a secondary cluster in the ap-southeast-1 Region. Use the secondary cluster's local endpoints for the Asia-Pacific telemetry reports, and perform a managed failover to promote the secondary cluster if the primary region fails.
The configuration utilizing Amazon Aurora Global Database is correct because it uses storage-level replication to achieve cross-region replication lag of less than 1 second, fulfilling the 1-minute RPO requirement. Furthermore, it supports managed failover, which promotes the secondary region to primary in less than a minute, meeting the 5-minute RTO. The local cluster in ap-southeast-1 provides local read endpoints for reporting workloads, keeping read latencies low and isolating reporting performance from primary write workloads.

Step-by-Step Solution

1
Analyze the disaster recovery constraints (RTO < 5 minutes, RPO < 1 minute).
Identify that the solution must support sub-minute replication lag (for RPO) and rapid failover (for RTO) across AWS Regions.
This rules out snapshot-based recovery (which has RTO in hours and RPO determined by snapshot intervals) and standard RDS replica promotion (which is manual and slow).
2
Analyze the read scalability and latency requirements (local Asia-Pacific reports with low latency, no impact on write performance).
Determine that a local read replica or secondary read-only database cluster must be placed in ap-southeast-1.
Routing read queries across regions from ap-southeast-1 to eu-west-1 would introduce unacceptable network latency.
3
Evaluate Amazon Aurora Global Database capabilities against the requirements.
Aurora Global Database replicates data storage-to-storage with a typical lag of under 1 second (meeting the RPO of < 1 minute) and supports managed failover with RTO of under 1 minute.
Aurora Global Database is the native AWS feature designed exactly for multi-region resilience and local read scaling under strict RTO/RPO limits.

Key Concept

Amazon Aurora Global Database provides storage-based cross-region replication for low-latency local reads, sub-minute replication lag, and rapid managed regional failover to meet strict RTO/RPO requirements.
Estimated Time:3m 0s
Rate this question

Topics

Resilient Database Configurations and High Availability

More questions from this topic