Soru

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

A logistics tracking company hosts its web application on Amazon EC2 instances in an Auto Scaling group with an Amazon RDS for PostgreSQL DB instance. The company needs to design a disaster recovery (DR) strategy in a secondary AWS Region. The strategy must achieve a Recovery Point Objective (RPO) of 24 hours and a Recovery Time Objective (RTO) of 12 hours while keeping costs to a minimum.

Which combination of actions will meet these requirements at the lowest cost? (Select TWO.)

  1. Configure AWS Backup to schedule daily backups of the RDS DB instance and copy them to the secondary Region.Cevap
  2. Copy the Amazon Machine Image (AMI) of the application EC2 instances to the secondary Region.Cevap
  3. C
    Launch a scaled-down, active EC2 instance in the secondary Region to run the application continuously as a pilot light.
  4. D
    Deploy a cross-region Amazon RDS Read Replica in the secondary Region to act as the primary database failover.
  5. E
    Store daily database backups in an Amazon S3 Glacier Deep Archive bucket in the secondary Region.

Cevap

Configure AWS Backup to schedule daily database backups and copy them to the secondary Region, and copy the application server Amazon Machine Image (AMI) to the secondary Region.
To meet an RPO of 24 hours and RTO of 12 hours at the lowest cost, a Backup and Restore disaster recovery (DR) strategy is ideal. Configuring AWS Backup to schedule daily database backups and copying them to the secondary Region satisfies the 24-hour RPO. Copying the application AMI to the secondary Region ensures that compute resources can be provisioned quickly from the AMI during a disaster event to satisfy the 12-hour RTO. Both of these actions store data at rest and do not run compute or database instances continuously, minimizing costs.

Adım Adım Çözüm

1
Identify the recovery requirements (RPO of 24 hours, RTO of 12 hours, minimum cost).
This indicates a Backup and Restore disaster recovery (DR) strategy is appropriate, as it is the most cost-effective and easily fits within a 12-hour window.
Backup and Restore does not require running active compute or database resources in the secondary Region, keeping idle costs at zero.
2
Select the database DR mechanism.
Configure AWS Backup to perform daily database backups and copy them to the secondary Region.
Daily database snapshots meet the 24-hour RPO and can be restored to a new RDS instance within the 12-hour RTO at minimal cost.
3
Select the compute DR mechanism.
Copy the application EC2 AMI to the secondary Region.
Having the AMI available in the secondary Region allows the Auto Scaling group to launch instances from the pre-configured image when failover is initiated, which can be done in minutes.

Anahtar Kavram

Backup and Restore is the most cost-effective disaster recovery strategy for scenarios with flexible RTO (e.g., 12-24 hours) and RPO (e.g., 24 hours), as it avoids ongoing compute and active database replica costs in the secondary region.
Bu soruyu puanla