Examkin

Soru

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

A global logistics company hosts its shipment tracking database on an Amazon RDS for PostgreSQL DB instance in the us-west-2 Region. The company needs to establish a disaster recovery (DR) plan in the us-east-1 Region. The DR solution must support a Recovery Point Objective (RPO) of 5 minutes and a Recovery Time Objective (RTO) of 30 minutes, while keeping ongoing costs at a minimum. Which combination of actions should a solutions architect take to meet these requirements? (Select TWO.)

  1. Create a cross-Region read replica of the RDS DB instance in the us-east-1 Region. If a disaster occurs, promote the read replica to a standalone DB instance.Cevap
  2. Store the application tier as an AWS CloudFormation template in Amazon S3. In the event of a disaster, deploy the application tier in the us-east-1 Region using the template, and point Amazon Route 53 to the new application endpoints.Cevap
  3. C
    Configure the RDS DB instance with Multi-AZ replication to copy data synchronously to the us-east-1 Region, and configure Amazon Route 53 with an active-active failover policy.
  4. D
    Configure AWS Backup to take hourly snapshots of the RDS DB instance, copy them to an Amazon S3 Glacier Flexible Retrieval vault in the us-east-1 Region, and restore the DB instance from the vault during a disaster.
  5. E
    Create a cross-Region read replica of the RDS DB instance in the us-east-1 Region. Configure Amazon Route 53 with a latency routing policy to automatically route write traffic to the read replica during a primary database failure.

Cevap

Create a cross-Region read replica of the RDS DB instance in the us-east-1 Region and promote it during a disaster, combined with storing the application tier as an AWS CloudFormation template in Amazon S3 to deploy on-demand.
To meet the 5-minute RPO, database replication must be continuous. Creating an Amazon RDS cross-Region read replica provides asynchronous replication with a delay of seconds. During a disaster, promoting this read replica to a primary instance takes only a few minutes, meeting the 30-minute RTO. To meet the goal of minimizing costs, the application tier should not run continuously. Storing the infrastructure as an AWS CloudFormation template in Amazon S3 allows the entire application tier to be spun up on-demand in the secondary region within the 30-minute RTO window, incurring no active EC2 costs during normal operations.

Adım Adım Çözüm

1
Select a replication mechanism that achieves an RPO of 5 minutes across AWS Regions.
Identify that Amazon RDS cross-Region read replicas replicate data asynchronously, typically with a lag of seconds, satisfying the 5-minute RPO requirement.
Hourly backups or multi-region synchronous replication are either too slow or unsupported for Amazon RDS.
2
Determine the database promotion strategy that fits within the 30-minute RTO.
Promoting a cross-Region read replica to a standalone primary database instance takes only a few minutes.
This meets the 30-minute RTO database-tier recovery requirement.
3
Determine the application tier recovery strategy that minimizes ongoing costs.
Keep zero active compute resources running in the disaster recovery region by storing the infrastructure definitions as AWS CloudFormation templates in Amazon S3.
This Pilot Light strategy achieves the lowest possible cost while allowing the environment to be deployed within the 30-minute RTO.

Anahtar Kavram

Disaster recovery (DR) strategies on AWS vary in cost, RTO, and RPO. Cross-Region read replicas meet low RPOs for databases by performing asynchronous replication, while Pilot Light strategies (like deploying via CloudFormation templates on-demand) minimize compute costs in the secondary region at the expense of a slightly higher RTO.
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru