Examkin

Soru

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

A company runs an inventory tracking application on AWS. The application tier runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer. The database tier uses an Amazon RDS for PostgreSQL Multi-AZ deployment. The company wants to establish a disaster recovery (DR) strategy in a secondary AWS Region. The strategy must support a Recovery Point Objective (RPO) of 5 minutes and a Recovery Time Objective (RTO) of 30 minutes, while keeping ongoing replication and idle infrastructure costs to a minimum. Which of the following database and application configurations will meet these requirements?

  1. Configure an Amazon RDS cross-region read replica in the secondary Region. Maintain an Auto Scaling group in the secondary Region with the desired capacity set to 0, and configure an Amazon Route 53 failover routing policy with health checks. In a disaster, promote the read replica to a primary instance, scale up the Auto Scaling group, and let Route 53 redirect traffic.Cevap
  2. B
    Configure an Amazon RDS cross-region read replica in the secondary Region. Deploy a Warm Standby architecture by running a minimum number of EC2 instances in the secondary Region's Auto Scaling group to handle baseline traffic. In a disaster, promote the read replica to a primary instance and scale up the Auto Scaling group.
  3. C
    Configure an Amazon RDS cross-region read replica in the secondary Region. Maintain an Auto Scaling group in the secondary Region with the desired capacity set to 0. In a disaster, update the application configuration in the secondary Region to direct all read and write traffic directly to the read replica without promoting it, and scale up the Auto Scaling group.
  4. D
    Configure daily automated exports of the database snapshots to Amazon S3 in the secondary Region, and transition those snapshots to Amazon S3 Glacier Flexible Retrieval. Maintain an Auto Scaling group in the secondary Region with the desired capacity set to 0. In a disaster, retrieve the snapshot from Glacier and restore it to a new RDS instance.

Cevap

Configure an Amazon RDS cross-region read replica in the secondary Region. Maintain an Auto Scaling group in the secondary Region with the desired capacity set to 0, and configure an Amazon Route 53 failover routing policy with health checks. In a disaster, promote the read replica to a primary instance, scale up the Auto Scaling group, and let Route 53 redirect traffic.
The correct option outlines a Pilot Light strategy, which satisfies the 5-minute RPO through RDS cross-region read replica replication and the 30-minute RTO by promoting the replica and scaling up the application tier. Keeping the Auto Scaling group's desired capacity at 0 minimizes ongoing compute costs in the secondary region.

Adım Adım Çözüm

1
Evaluate the disaster recovery objectives (RTO of 30 minutes, RPO of 5 minutes) and the cost constraint.
The target strategy must support database replication with lag under 5 minutes, support application recovery within 30 minutes, and minimize idle infrastructure costs in the secondary region.
Establishes the criteria for selecting the most cost-effective disaster recovery design.
2
Compare database replication options to meet the 5-minute RPO.
An Amazon RDS cross-region read replica provides continuous, asynchronous replication with lag typically under a few seconds, satisfying the RPO.
Eliminates snapshot-based backup strategies which cannot guarantee a 5-minute RPO.
3
Determine the application tier deployment strategy to meet the 30-minute RTO and minimize cost.
Keeping an Auto Scaling group in the secondary Region with a desired capacity of 0 ensures no EC2 instances run during normal operations, minimizing cost (Pilot Light). During a disaster, promoting the replica and scaling up the Auto Scaling group can be completed within the 30-minute RTO.
This Pilot Light strategy meets all requirements at a lower cost than a Warm Standby strategy (which runs active instances continuously).

Anahtar Kavram

Disaster recovery (DR) strategies on AWS balance Recovery Time Objective (RTO), Recovery Point Objective (RPO), and cost. A Pilot Light strategy uses continuous database replication (such as RDS cross-region read replicas) while keeping application compute resource counts at zero until a failover event occurs, minimizing idle costs while meeting moderate recovery time limits.
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru