Question

Difficulty: HardResilient Database Configurations and High Availability

A financial services company is deploying a critical online transaction processing (OLTP) application on AWS that requires a multi-region database architecture. The primary database cluster will be hosted in `us-east-1`, and the disaster recovery (DR) cluster will be located in `us-west-2`. The architecture must achieve a Recovery Point Objective (RPO) of less than 11 second and a Recovery Time Objective (RTO) of less than 11 minute. The database tier must support scaling read traffic in the secondary region while keeping the write path resilient to regional failures. Which two database configurations or actions should a solutions architect recommend to meet these requirements? (Select TWO.)

  1. Deploy an Amazon Aurora PostgreSQL Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2.Answer
  2. Configure Aurora Auto Scaling for the reader instances in the us-west-2 secondary cluster to handle fluctuating read query workloads.Answer
  3. C
    Provision an Amazon RDS for PostgreSQL DB instance with Multi-AZ enabled in us-east-1 and set up a cross-region read replica in us-west-2 to act as the primary failover target.
  4. D
    Use Amazon Route 53 latency-based routing to distribute database write and read requests directly between the database endpoints in both regions.
  5. E
    Configure a Pilot Light disaster recovery strategy by scheduling hourly database snapshots in us-east-1 and copying them to us-west-2 to restore on demand.

Answer

To meet the requirements, the solutions architect should deploy an Amazon Aurora PostgreSQL Global Database across the primary and secondary regions, and configure Aurora Auto Scaling for the reader instances in the secondary region cluster.
Deploying an Amazon Aurora PostgreSQL Global Database ensures storage-level replication lag remains under 11 second, fulfilling the low RPO limit. If a regional outage occurs, the secondary cluster in the recovery region can be promoted to primary in under 11 minute, satisfying the RTO limit. Furthermore, configuring Aurora Auto Scaling on the reader instances in the secondary region allows the secondary cluster to handle dynamic read request volumes independently of the primary write path.

Step-by-Step Solution

1
Select a multi-region database engine that supports low-latency replication.
Amazon Aurora Global Database provides storage-level asynchronous replication across AWS regions with typical latencies of less than 11 second.
This satisfies the strict RPO requirement of less than 11 second.
2
Ensure the disaster recovery failover capability fits the target recovery window.
Aurora Global Database secondary clusters can be promoted to a standalone primary cluster with full read-write capabilities in less than 11 minute.
This allows the database to meet the RTO requirement of less than 11 minute.
3
Configure scaling for the read workload in the secondary region.
Enable Aurora Auto Scaling on reader instances in the secondary region cluster.
This allows the reader endpoints to dynamically scale out or scale in based on query volume without affecting the primary cluster.

Key Concept

Resilient Database Configurations and High Availability
Rate this question