Examkin

Question

Difficulty: Very hardResilient Database Configurations and High Availability

A financial transaction processing platform is migrating its relational database to AWS. The platform requires a highly resilient database architecture deployed across two AWS Regions: us-east-1 (Primary) and us-west-2 (Secondary). The architecture must meet the following constraints:

1. Intra-region failover must be automatic, with a Recovery Time Objective (RTO) of less than 3030 seconds and a Recovery Point Objective (RPO) of 00.
2. Cross-region disaster recovery must have an RPO of less than 22 seconds and an RTO of less than 55 minutes.
3. The database must dynamically scale read capacity independently in both regions to handle seasonal traffic spikes without manual intervention.
4. During normal operations, the application in the secondary region must be able to issue read and write requests locally, with write requests forwarded to the primary region without needing complex application-side write-routing logic.

Which database configuration meets these requirements with the least operational complexity?

  1. A
    Deploy Amazon RDS for PostgreSQL in us-east-1 with a Multi-AZ DB cluster deployment. Configure a cross-region read replica in us-west-2. Enable Aurora Auto Scaling on the RDS replica in us-west-2. Enable database write forwarding on the cross-region read replica to automatically redirect write transactions to the primary database in us-east-1.
  2. B
    Deploy an Amazon Aurora PostgreSQL DB cluster in us-east-1 as a Multi-AZ deployment. Set up cross-region logical replication to a standalone Amazon RDS for PostgreSQL DB instance in us-west-2. In the event of a primary region failure, configure an AWS Lambda function to promote the RDS instance to primary and update the application endpoint.
  3. C
    Deploy an Amazon Aurora PostgreSQL DB cluster in us-east-1 as a Multi-AZ deployment. Configure a cross-region Aurora Read Replica in us-west-2. Configure Amazon Route 53 Latency routing with health checks to automatically fail over and route write traffic directly to the us-west-2 read replica if the primary region goes offline.
  4. Deploy an Amazon Aurora Global Database with PostgreSQL compatibility. Configure the primary DB cluster in us-east-1 as a Multi-AZ deployment. Deploy a secondary DB cluster in us-west-2 and enable Aurora Auto Scaling for its reader instances. Enable write forwarding on the secondary DB cluster, allowing application clients in us-west-2 to write directly to the local reader endpoint, which forwards the writes to the primary cluster in us-east-1.Answer

Answer

Deploy an Amazon Aurora Global Database with PostgreSQL compatibility. Configure the primary DB cluster in us-east-1 as a Multi-AZ deployment. Deploy a secondary DB cluster in us-west-2 and enable Aurora Auto Scaling for its reader instances. Enable write forwarding on the secondary DB cluster, allowing application clients in us-west-2 to write directly to the local reader endpoint, which forwards the writes to the primary cluster in us-east-1.
The configuration utilizing Amazon Aurora Global Database satisfies all constraints. The local Multi-AZ cluster deployment meets the intra-region RTO/RPO requirements. Aurora Global Database's storage-level replication delivers a cross-region RPO of less than 22 seconds (typically under 11 second) and can be promoted to a primary cluster in under 55 minutes. Additionally, write forwarding on the secondary cluster allows the secondary region application to send reads and writes to its local endpoint, simplifying write routing, while Aurora Auto Scaling dynamically manages read replica capacity.

Step-by-Step Solution

1
Evaluate intra-region resiliency requirements.
Amazon Aurora DB clusters with Multi-AZ deployments replication model satisfies the local RPO of 00 and RTO of under 3030 seconds via automated failover of the writer instance.
Aurora storage is replicated across three Availability Zones within a region, ensuring zero data loss and rapid automated failover.
2
Evaluate cross-region disaster recovery replication lag.
Amazon Aurora Global Database uses dedicated storage-level physical replication to secondary regions, achieving replication lag of under 11 second.
Physical replication bypasses the SQL execution engine, which is much faster than logical database replication or snapshot-based restoration.
3
Assess write routing and read capacity requirements in the secondary region.
Enable write forwarding on the secondary Aurora DB cluster and configure Aurora Auto Scaling for the readers.
Write forwarding routes write requests transparently to the primary region cluster while keeping reads local. Aurora Auto Scaling adjusts read replicas dynamically based on demand.

Key Concept

Amazon Aurora Global Database architecture, cross-region replication mechanics, and write forwarding capabilities.
Rate this question

Topics

Resilient Database Configurations and High Availability

More questions from this topic