Examkin

Soru

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

A digital publishing company hosts a web application in the us-east-1 Region. The application uses an Amazon RDS for MySQL database to store article metadata. The company wants to implement a disaster recovery (DR) strategy in the us-west-2 Region. The solution must achieve a Recovery Point Objective (RPO) of 1515 minutes and a Recovery Time Objective (RTO) of 22 hours while minimizing ongoing infrastructure costs.

Which strategy should a solutions architect recommend to meet these requirements?

  1. A
    Export daily database backups to Amazon S3, copy the backups to an Amazon S3 Glacier Flexible Retrieval vault in the secondary Region, and restore the database from Glacier during a failover event.
  2. B
    Configure Amazon RDS Multi-AZ replication across both Regions. Use Amazon Route 53 with a latency routing policy to route traffic to active application servers running in both Regions.
  3. Replicate the database to the secondary Region. Keep application servers in the secondary Region turned off, or deploy them using AWS CloudFormation templates only during a failover event.Cevap
  4. D
    Replicate the database to the secondary Region. Keep a scaled-down, active fleet of application instances running in the secondary Region to scale up immediately during a failover event.

Cevap

Replicate the database to the secondary Region. Keep application servers in the secondary Region turned off, or deploy them using AWS CloudFormation templates only during a failover event.
The correct strategy is a Pilot Light approach. Replicating the database to the secondary Region ensures the data is ready and meets the 15-minute RPO. Keeping application servers shut down or deploying them on demand using templates minimizes ongoing infrastructure costs while comfortably meeting the 2-hour RTO.

Adım Adım Çözüm

1
Identify the target constraints
RPO is 1515 minutes, RTO is 22 hours, and ongoing infrastructure costs must be minimized.
The solution must satisfy all constraints, especially the balance between speed of recovery (RTO/RPO) and cost.
2
Evaluate database replication options
Database must be actively replicated to the secondary Region (e.g., using cross-region read replicas) to meet the 1515-minute RPO.
Traditional daily backups do not meet a 1515-minute RPO constraint.
3
Evaluate compute scaling options
Since the RTO is 22 hours, application servers do not need to be running continuously. They can be created on-demand or kept turned off.
Keeping compute resources powered down or provisioning them on-demand via templates (Pilot Light) minimizes ongoing costs while easily fitting into the 22-hour window.

Anahtar Kavram

Disaster Recovery (DR) Strategies (Pilot Light vs. Warm Standby)
Tahmini Süre:1m 0s
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru