Examkin

Question

Difficulty: HardResilient Database Configurations and High Availability

A logistics company runs a global supply chain portal that uses a PostgreSQL-compatible relational database. The application is deployed in a primary AWS Region (us-east-1) and a secondary AWS Region (us-west-2). The database tier must support a Recovery Point Objective (RPO) of under 11 second and a Recovery Time Objective (RTO) of under 22 minutes for disaster recovery. The secondary region must also serve local read traffic with low latency. Which database configuration meets these requirements with the least operational overhead?

  1. Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. In the event of a regional outage, promote the secondary cluster to primary.Answer
  2. B
    Deploy an Amazon RDS for PostgreSQL Multi-AZ DB cluster in us-east-1, and create a cross-region read replica in us-west-2. Configure the application in us-west-2 to write to the read replica in the event of a failover.
  3. C
    Deploy Amazon RDS for PostgreSQL DB instances in both us-east-1 and us-west-2. Set up AWS Database Migration Service (AWS DMS) in a Pilot Light disaster recovery configuration to replicate transactions continuously.
  4. D
    Deploy standalone Amazon RDS for PostgreSQL DB instances in both regions. Configure Amazon Route 53 with latency-based routing to dynamically route write operations to the database with the lowest latency.

Answer

Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. In the event of a regional outage, promote the secondary cluster to primary.
Amazon Aurora Global Database is designed for globally distributed applications. It uses fast, storage-based replication that keeps lag under 11 second (meeting the RPO of under 11 second). During a regional disaster, the secondary cluster can be promoted to a primary read-write cluster in under 22 minutes (meeting the RTO of under 22 minutes). Local read replicas in the secondary cluster can serve local read traffic with minimal latency, fulfilling the read scaling constraint with minimal operational overhead.

Step-by-Step Solution

1
Analyze the requirements for database engine compatibility, cross-region capability, RTO, RPO, and read scaling.
Identify that the database must be PostgreSQL-compatible, support cross-region read scaling, and have an RPO under 11 second and RTO under 22 minutes.
This establishes the boundaries for evaluating AWS database replication mechanisms.
2
Evaluate Amazon Aurora Global Database performance metrics against the RTO and RPO targets.
Aurora Global Database features typical RPO of less than 11 second and can be promoted to a primary cluster in less than 22 minutes.
This meets both the recovery criteria and local read requirements in the secondary region.
3
Examine alternative database replication solutions such as RDS Multi-AZ with cross-region read replicas or DMS Pilot Light setups.
Determine that RDS read replicas do not support direct write failovers without manual intervention, and Pilot Light configurations fail the RTO target.
This rules out the distractors as they cannot satisfy the combination of recovery speed and replication capability.

Key Concept

Amazon Aurora Global Database provides cross-region replication with sub-second RPO and fast promotion for under 2-minute RTO, while supporting local reads.
Estimated Time:2m 0s
Rate this question

Topics

Resilient Database Configurations and High Availability

More questions from this topic