Question

Difficulty: MediumHigh Availability and Disaster Recovery Design

A company is designing a multi-region disaster recovery (DR) architecture for its customer portal. The primary infrastructure is deployed in us-east-1, and the standby infrastructure is in us-west-2. The database tier uses Amazon Aurora PostgreSQL. The business requirements state a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 2 minutes. Outbound database traffic to external APIs must be resilient to Availability Zone (AZ) failures in both regions. Which architecture should a solutions architect design to meet these requirements with the lowest operational complexity?

  1. Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy NAT Gateways in multiple Availability Zones in each region. Configure Route 53 with failover routing using active-passive health checks on the application endpoints.Answer
  2. B
    Deploy Amazon RDS for PostgreSQL in us-east-1 with a Multi-AZ deployment, and configure daily cross-region snapshots to us-west-2. Configure read scaling by directing read traffic to the passive RDS standby instance. Configure Route 53 with geolocation routing.
  3. C
    Deploy Amazon Aurora PostgreSQL cross-region read replicas from us-east-1 to us-west-2. Deploy a single NAT Gateway in the primary Availability Zone of each region to centralize outbound traffic. Configure Route 53 with latency-based routing policies.
  4. D
    Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Configure a Route 53 Private Hosted Zone for private service resolution, but associate it only with the us-east-1 VPC. Keep the application servers in us-west-2 powered down under a pilot light configuration.

Answer

Deploy an Amazon Aurora Global Database with the primary cluster in us-east-1 and a secondary cluster in us-west-2. Deploy NAT Gateways in multiple Availability Zones in each region. Configure Route 53 with failover routing using active-passive health checks on the application endpoints.
The correct architecture uses Amazon Aurora Global Database to achieve low-latency replication that satisfies the sub-2-minute RPO constraint. Setting up Route 53 failover routing handles active-passive failover automatically, which allows the application to meet the 15-minute RTO constraint. Additionally, deploying NAT Gateways across multiple Availability Zones in each region ensures that outbound traffic routes are highly available and resilient to individual Availability Zone failures.

Step-by-Step Solution

1
Select a cross-region replication method that meets the RPO constraint of less than 2 minutes.
Amazon Aurora Global Database provides fast, physical replication with lag typically under one second.
This satisfies the strict RPO requirement, whereas snapshot restoration would exceed the RPO limit.
2
Configure the DNS routing strategy to automate failover and meet the RTO constraint of less than 15 minutes.
Route 53 active-passive failover routing policy routes traffic based on health check statuses.
Active-passive configuration ensures traffic is dynamically rerouted to the secondary region if the primary region goes offline.
3
Verify high availability for outbound traffic paths in both regions.
Deploy NAT Gateways in multiple Availability Zones in each VPC.
Outbound API calls must not fail if a single Availability Zone experiences an outage, so redundant NAT Gateways are required.

Key Concept

High Availability and Disaster Recovery Design
Estimated Time:2m 0s
Rate this question