Soru

Zorluk: KolayHigh Availability and Disaster Recovery Design

A company is designing a disaster recovery (DR) strategy for a critical web application to achieve a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 minutes. The production environment is in the primary region. The database is hosted on Amazon RDS for PostgreSQL. The company wants to minimize costs while ensuring that a minimal standby environment is running in a secondary recovery region. Which TWO actions should the solutions architect take to meet these requirements?

  1. Create a cross-region Read Replica of the primary database in the disaster recovery region to ensure continuous data replication.Cevap
  2. Deploy an Auto Scaling group of application servers in the disaster recovery region with a minimum capacity of 1, configured to scale out when traffic is redirected.Cevap
  3. C
    Configure a single NAT Gateway in one Availability Zone in the recovery region to handle outbound traffic for all private subnets across multiple Availability Zones to ensure high availability.
  4. D
    Configure a Route 53 Private Hosted Zone for public client failover routing, and associate it only with the primary VPC.
  5. E
    Use Amazon RDS Multi-AZ standby instances in the primary region to automatically serve read traffic during normal operations to reduce query latency.

Cevap

Create a cross-region Read Replica of the primary database in the disaster recovery region to ensure continuous data replication, and deploy an Auto Scaling group of application servers in the disaster recovery region with a minimum capacity of 1, configured to scale out when traffic is redirected.
The correct options are to create a cross-region database Read Replica and deploy a low-capacity Auto Scaling group in the recovery region. The Read Replica maintains continuous, asynchronous database replication to satisfy the 5-minute RPO constraint. Running a single application server in the recovery region that can quickly scale out meets the 15-minute RTO constraint while minimizing standby costs.

Adım Adım Çözüm

1
Select a replication strategy to meet the 5-minute RPO target.
Identify that a cross-region RDS Read Replica provides continuous, asynchronous data replication to the secondary region.
Nightly backups or snapshots will not satisfy a 5-minute RPO because data loss could be up to 24 hours.
2
Select an application hosting strategy that minimizes cost while meeting the 15-minute RTO.
Identify that running a minimal application tier (e.g., minimum capacity of 1 in an Auto Scaling group) in the recovery region satisfies the warm standby pattern.
Keeping a full-sized duplicate infrastructure is expensive, while starting from scratch (backup and restore or pilot light with zero instances) might exceed the 15-minute RTO due to bootstrapping delays.

Anahtar Kavram

Warm Standby Disaster Recovery Pattern
Bu soruyu puanla