Examkin

Soru

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

A financial technology company hosts a transactional banking application on AWS. The architecture consists of Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer, and a Multi-AZ Amazon RDS for PostgreSQL database. To meet regulatory compliance, the company must establish a cross-region disaster recovery (DR) plan with a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 2 hours. The solutions architect must design a solution that minimizes ongoing infrastructure costs in the secondary region. Which disaster recovery strategy should the solutions architect recommend to meet these requirements?

  1. Replicate the database to the secondary region using an Amazon RDS cross-region read replica. Store the application AMIs in the secondary region and maintain AWS CloudFormation templates to provision the Application Load Balancer and Auto Scaling group only during a failover event.Cevap
  2. B
    Deploy a scaled-down application tier with a minimum capacity of EC2 instances running behind an Application Load Balancer in the secondary region. Replicate the RDS database using a cross-region read replica, and scale up the EC2 instances during a failover.
  3. C
    Export RDS automated snapshots hourly and copy them to an Amazon S3 Glacier Flexible Retrieval vault in the secondary region. In the event of a disaster, initiate standard retrieval of the database snapshots, restore the database, and deploy the application resources.
  4. D
    Configure Amazon RDS Multi-AZ in the primary region. Use Amazon Route 53 latency-based routing to automatically redirect user traffic to the secondary region and promote the standby database instance in the secondary region during an outage.

Cevap

Replicate the database to the secondary region using an Amazon RDS cross-region read replica. Store the application AMIs in the secondary region and maintain AWS CloudFormation templates to provision the Application Load Balancer and Auto Scaling group only during a failover event.
The correct option proposes a Pilot Light disaster recovery strategy. By replicating the database using an Amazon RDS cross-region read replica, the solution ensures that transactional data is continuously copied, satisfying the 15-minute RPO. Since the RTO is relatively generous (2 hours), compute resources such as Application Load Balancers and Auto Scaling groups do not need to run continuously. Deploying these resources dynamically using stored AMIs and pre-configured CloudFormation templates minimizes ongoing infrastructure costs in the secondary region while comfortably meeting the 2-hour RTO.

Adım Adım Çözüm

1
Evaluate the RPO requirement (15 minutes) against data replication options.
Cross-region RDS read replicas provide continuous asynchronous replication, keeping data lag to a few seconds or minutes, which easily satisfies the 15-minute RPO.
Ensures that the secondary database is up-to-date and ready for promotion with minimal data loss.
2
Evaluate the RTO requirement (2 hours) and cost-minimization constraint.
A Pilot Light strategy allows the database to run as a read replica in the secondary region while keeping compute resources shut down or unprovisioned. Deploying compute resources via CloudFormation templates and AMIs takes less than 30 minutes, which is well within the 2-hour RTO limit and minimizes compute costs.
Allows the company to avoid paying for running EC2 instances and load balancer idle time in the secondary region during normal operations.
3
Compare against the Warm Standby and Backup and Restore alternatives.
Warm Standby is rejected due to unnecessary ongoing compute cost. Backup and Restore with Glacier is rejected because Glacier retrieval times exceed the 2-hour RTO, and hourly snapshots violate the 15-minute RPO.
Selects the optimal strategy that meets all recovery goals while staying cost-optimized.

Anahtar Kavram

Disaster Recovery strategies (Pilot Light vs. Warm Standby) and cross-region database replication in AWS.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru