Question

Difficulty: EasyHigh Availability and Disaster Recovery Design

A company runs a critical web application on AWS with a primary deployment in the us-east-1 Region. The company wants to establish a disaster recovery (DR) solution in the us-west-2 Region. The application requires a Recovery Time Objective (RTO) of less than 15 minutes and a Recovery Point Objective (RPO) of less than 5 minutes. The solution must minimize monthly running costs. Which DR architecture should a solutions architect recommend to meet these requirements?

  1. A
    Implement a Backup and Restore DR pattern. Back up the application data and database to Amazon S3 buckets in us-east-1, and replicate the S3 buckets to us-west-2 daily. Provision the application servers in us-west-2 using AWS CloudFormation templates only after a disaster is declared in the primary Region.
  2. B
    Implement a Multi-Region Active-Active DR pattern. Deploy fully scaled application fleets in both us-east-1 and us-west-2. Replicate the database to us-west-2 using an Amazon RDS Multi-AZ deployment to serve read and write traffic simultaneously across both Regions.
  3. Implement a Warm Standby DR pattern. Deploy a scaled-down fleet of application instances in the us-west-2 Region. Replicate the database to us-west-2 using Amazon Aurora Global Database. Configure Amazon Route 53 active-passive failover routing with health checks to automatically redirect traffic to us-west-2 if the primary Region becomes unhealthy.Answer
  4. D
    Implement a Warm Standby DR pattern. Deploy a scaled-down fleet of application instances in the us-west-2 Region. Replicate the database using Amazon Aurora Global Database. Use Amazon Route 53 latency-based routing to split traffic between both Regions, without configuring health checks on the routing records.

Answer

Implement a Warm Standby DR pattern with scaled-down instances in us-west-2, database replication using Amazon Aurora Global Database, and Amazon Route 53 active-passive failover routing with health checks.
The correct answer is the Warm Standby DR pattern. A Warm Standby pattern meets the 15-minute RTO requirement by having a scaled-down fleet of application instances already running in the recovery Region, allowing them to scale up quickly. Amazon Aurora Global Database provides cross-region replication with an RPO of under 1 second, satisfying the 5-minute RPO requirement. Amazon Route 53 failover routing with health checks ensures that traffic is automatically redirected to the secondary Region when the primary Region's endpoints fail.

Step-by-Step Solution

1
Analyze RTO and RPO requirements
An RTO of less than 15 minutes rules out Backup and Restore, while an RPO of less than 5 minutes requires continuous cross-region database replication.
To identify which DR architectures can meet the time-bound objectives.
2
Evaluate the database replication options
Amazon Aurora Global Database provides cross-region replication with sub-second lag, while Amazon RDS Multi-AZ does not replicate across Regions.
To select a valid cross-region database replication mechanism that meets the RPO constraint.
3
Assess Route 53 routing policies and cost constraints
Active-passive failover routing with health checks redirects traffic within minutes, meeting the RTO. Running a scaled-down application fleet in the standby region minimizes running costs compared to a fully scaled active-active setup.
To ensure traffic redirection is automated and complies with the cost optimization constraint.

Key Concept

Disaster recovery strategy selection (Warm Standby vs. Backup & Restore) and DNS failover configuration based on RTO and RPO constraints.
Rate this question