Examkin

Soru

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

A corporate training platform hosts its web application in a single AWS Region. The platform's database is stored on Amazon RDS for PostgreSQL, and application data is on Amazon EBS volumes. The company wants to set up a cost-effective Backup and Restore disaster recovery (DR) strategy in a secondary Region. The company can tolerate a 2424-hour Recovery Point Objective (RPO) and a 2424-hour Recovery Time Objective (RTO). Which combination of actions will meet these requirements at the lowest cost? (Select TWO.)

  1. Configure daily backups of Amazon Elastic Block Store (Amazon EBS) volumes and Amazon RDS DB instances, and copy the snapshots to the secondary AWS Region.Cevap
  2. Use AWS CloudFormation templates to deploy the application infrastructure in the secondary AWS Region during a disaster, and restore the databases from the copied snapshots.Cevap
  3. C
    Deploy scaled-down Amazon EC2 instances in a Pilot Light configuration in the secondary AWS Region and expect them to handle full production traffic immediately without scaling up.
  4. D
    Create an Amazon RDS Read Replica in the secondary AWS Region and configure it to automatically perform Multi-AZ failover for the primary database.
  5. E
    Store all database backups in Amazon S3 Glacier Flexible Retrieval and use standard retrieval to recover data within a 55-minute recovery time window.

Cevap

The correct strategy is to configure daily backups of EBS volumes and RDS instances, copy them to a secondary region, and deploy the application infrastructure on-demand using CloudFormation while restoring the databases from those snapshots when a disaster occurs.
For a 2424-hour RPO and RTO, a Backup and Restore strategy is the most cost-effective option. The two correct options accomplish this by first setting up daily backups of EBS volumes and RDS databases and copying them to a secondary region (satisfying the 2424-hour RPO), and second, deploying the architecture on-demand during a disaster using AWS CloudFormation and restoring the databases from the copied snapshots (satisfying the 2424-hour RTO without incurring compute costs during normal operations).

Adım Adım Çözüm

1
Evaluate the RPO and RTO requirements to select the appropriate disaster recovery (DR) pattern.
An RPO of 2424 hours and an RTO of 2424 hours point to a Backup and Restore strategy as the most cost-effective solution.
Backup and Restore has the lowest cost because it does not require active compute or fully-scaled databases to run in the disaster recovery region during normal operations.
2
Identify the mechanism for meeting the 2424-hour RPO.
Daily snapshots of EBS volumes and RDS DB instances are copied to the secondary Region.
By taking and copying snapshots every 2424 hours, data loss is capped at a maximum of 2424 hours, satisfying the RPO.
3
Identify the mechanism for meeting the 2424-hour RTO.
Using CloudFormation to provision the network and compute resources, then restoring the database from the copied snapshots.
Rebuilding the environment on-demand easily fits within the generous 2424-hour RTO window, keeping disaster recovery costs minimal.

Anahtar Kavram

Backup and Restore Disaster Recovery Strategy
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru