Examkin

Soru

Zorluk: OrtaMulti-AZ, Multi-Region Architectures and Disaster Recovery (DR)

A logistics company runs a fleet tracking application on AWS. The application database is hosted on Amazon RDS for PostgreSQL in a Multi-AZ deployment within the primary Region. The company requires a disaster recovery (DR) strategy in a secondary Region with a Recovery Time Objective (RTO) of 30 minutes and a Recovery Point Objective (RPO) of 15 minutes, while minimizing ongoing costs. Which architecture will meet these requirements at the lowest cost?

  1. A
    Configure a cross-region Amazon RDS read replica and a duplicate application tier in the secondary Region. Implement Amazon Route 53 Latency routing without health checks to automatically redirect traffic to the secondary Region when the primary Region experiences an outage.
  2. B
    Configure a Pilot Light environment with application servers running at a minimal scale in the secondary Region. Rely on the Pilot Light servers to handle the immediate full production traffic load with zero startup or scaling latency during a failover event.
  3. Configure a cross-region Amazon RDS read replica in the secondary Region. Deploy a Pilot Light environment for the application tier in the secondary Region with Auto Scaling group capacity set to zero. Upon failover, promote the read replica to a standalone DB instance, scale up the Auto Scaling groups, and update Route 53 failover records.Cevap
  4. D
    Configure a cross-region Amazon RDS read replica in the secondary Region. If a disaster occurs, redirect all application write traffic directly to the read replica without promoting it, assuming the database will automatically promote itself to a primary instance upon receiving write requests.

Cevap

Configure a cross-region Amazon RDS read replica in the secondary Region, deploy a Pilot Light environment for the application tier with Auto Scaling group capacity set to zero, and promote the replica and scale the instances during failover.
The configuration utilizing a cross-region RDS read replica satisfies the 15-minute RPO requirement because data is continuously replicated asynchronously. Using a Pilot Light strategy with Auto Scaling groups set to zero instances minimizes running compute costs during normal operations while allowing the servers to boot and scale within the 30-minute RTO during a disaster scenario.

Adım Adım Çözüm

1
Set up a cross-region Amazon RDS read replica in the secondary Region.
Asynchronous replication is established, achieving an RPO of under 15 minutes.
Ensures that database changes in the primary Region are continually replicated to the recovery Region.
2
Deploy a Pilot Light environment for the application servers in the secondary Region, configuring the Auto Scaling groups with a desired capacity of zero.
Compute costs are minimized since no instances run during normal operations, but launch configurations/templates are prepared.
Allows quick provisioning of the compute layer within the 30-minute RTO window when a disaster is declared.
3
Configure a Route 53 routing policy with health checks to manage failover.
Traffic can be redirected to the secondary Region after promotion and scaling are complete.
Ensures client traffic is pointed to the promoted infrastructure in the disaster recovery Region.

Anahtar Kavram

Disaster recovery strategies involving Pilot Light environments and RDS cross-region replication to balance RTO, RPO, and cost.
Bu soruyu puanla

Konular

Multi-AZ, Multi-Region Architectures and Disaster Recovery (DR)

Bu konudan daha fazla soru