Examkin

Soru

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

A telehealth company hosts its core patient scheduling application in the us-east-1 Region. The application runs on Amazon EC2 instances in an Auto Scaling group behind an Application Load Balancer, and uses an Amazon RDS for PostgreSQL Multi-AZ DB instance. The company needs to design a disaster recovery (DR) strategy in the us-west-2 Region with a Recovery Time Objective (RTO) of 2 hours and a Recovery Point Objective (RPO) of 15 minutes. The solution must minimize cost during normal operations.

Which combination of actions should the solutions architect take to meet these requirements? (Select TWO.)

  1. Create a cross-region read replica of the RDS DB instance in the us-west-2 Region.Cevap
  2. Create an Auto Scaling group in the us-west-2 Region with the desired capacity set to 0, and prepare AWS CloudFormation templates to deploy the Application Load Balancer during a disaster.Cevap
  3. C
    Configure the RDS DB instance with multi-region replication and enable automatic synchronous failover to the secondary Region.
  4. D
    Set up an Amazon Route 53 latency routing policy to automatically redirect application traffic to the us-west-2 Region when the primary region is down.
  5. E
    Export database snapshots to Amazon S3 daily, transition them to Amazon S3 Glacier Flexible Retrieval, and restore the database from these snapshots during a failover.

Cevap

The correct strategy is to create a cross-region read replica of the RDS DB instance in the secondary Region, and create an Auto Scaling group in the secondary Region with the desired capacity set to 0 while preparing AWS CloudFormation templates to deploy the Application Load Balancer during a disaster.
Establishing a cross-region read replica allows the database changes to be replicated asynchronously, supporting a low RPO. Setting up the Auto Scaling group with a capacity of 0 and using CloudFormation templates to dynamically deploy load balancing infrastructure ensures no active compute costs are incurred, while maintaining the ability to bring up the environment under the 2-hour RTO limit.

Adım Adım Çözüm

1
Address the Recovery Point Objective (RPO) of 15 minutes for the database layer.
Establish a cross-region read replica of the database in the secondary region.
An RDS Cross-Region Read Replica uses asynchronous replication to keep data synchronized with lag that is typically seconds, comfortably meeting the 15-minute RPO.
2
Address the Recovery Time Objective (RTO) of 2 hours for the application layer while minimizing costs.
Create an Auto Scaling group in the secondary region with desired capacity set to 0, and write CloudFormation templates for the load balancing infrastructure.
A desired capacity of 0 ensures no EC2 instances are running (and incurring costs) during normal operations. When a disaster is declared, the CloudFormation templates can deploy the Application Load Balancer and the Auto Scaling group can be scaled up within minutes, well within the 2-hour RTO.

Anahtar Kavram

Configuring a Pilot Light disaster recovery strategy on AWS by combining asynchronous database replication with scaled-down compute infrastructure to satisfy RTO and RPO limits cost-effectively.
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru