Examkin

Soru

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

A public transit ticketing platform hosts its core application in the us-west-2 Region. The database tier runs on an Amazon RDS for MySQL Multi-AZ DB instance. The company needs to design a disaster recovery (DR) plan in the us-east-1 Region. The DR strategy must achieve a Recovery Point Objective (RPO) of less than 15 minutes and a Recovery Time Objective (RTO) of less than 30 minutes, while keeping costs as low as possible.

Which TWO configurations should a solutions architect implement to meet these requirements? (Select TWO.)

  1. Create a cross-region read replica of the RDS DB instance in the us-east-1 Region.Cevap
  2. Deploy a scaled-down application tier in the us-east-1 Region, and configure Amazon Route 53 failover routing with health checks.Cevap
  3. C
    Configure an Amazon Route 53 latency-based routing policy to automatically redirect database and application traffic to the us-east-1 Region during an outage.
  4. D
    Enable Amazon RDS Multi-AZ replication across both the us-west-2 and us-east-1 Regions to automate database failover.
  5. E
    Export daily database snapshots to Amazon S3 Glacier Flexible Retrieval in the us-east-1 Region, and restore the database during a failover event.

Cevap

Create a cross-region read replica of the RDS DB instance in the us-east-1 Region, and deploy a scaled-down application tier in the us-east-1 Region with Amazon Route 53 failover routing and health checks.
To meet the 15-minute RPO, the database must replicate continuously to the secondary region. An RDS cross-region read replica meets this requirement by replicating data asynchronously with very low latency. To meet the 30-minute RTO, the database replica can be promoted to a standalone primary instance in minutes. To minimize costs, the application tier should be kept scaled down (Pilot Light pattern) and only scaled up when a failover is initiated. Amazon Route 53 failover routing with health checks handles the redirection of user traffic to the secondary region during a disaster.

Adım Adım Çözüm

1
Select a database replication method that meets the RPO of less than 15 minutes.
Using an Amazon RDS cross-region read replica provides asynchronous data replication across regions, which typically keeps replication lag under a few minutes, meeting the 15-minute RPO.
Asynchronous replication to a cross-region read replica provides a cost-effective, low-lag copy of the database in the recovery region.
2
Choose a compute deployment model that minimizes costs and supports the 30-minute RTO.
Pre-deploying a scaled-down (Pilot Light) application tier in us-east-1 ensures that the core resources exist and can be scaled up rapidly via Auto Scaling groups or instance resizing during a disaster.
A Pilot Light pattern avoids the cost of running a full-capacity environment continuously while still meeting the RTO.
3
Configure DNS routing to handle traffic redirection during failover.
Setting up Amazon Route 53 failover routing policies associated with health checks allows the architect to redirect client traffic to the secondary region once the database is promoted and the application tier is scaled up.
Failover routing provides the mechanism to switch active user traffic to the backup site when the primary region is unavailable.

Anahtar Kavram

Disaster recovery planning using a cross-region Pilot Light strategy with Amazon RDS cross-region read replicas and Amazon Route 53 failover routing to meet strict RTO/RPO objectives while minimizing idle resource costs.
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru