A company is designing a disaster recovery (DR) strategy for a non-critical reporting application. The business requires a Recovery Point Objective (RPO) of 24 hours and a Recovery Time Objective (RTO) of 12 hours. The primary objective is to minimize ongoing infrastructure costs.
Which combination of actions should a SysOps administrator take to meet these requirements at the lowest cost? (Select TWO.)
- Configure AWS Backup to perform daily backups of the application resources and copy them to a secondary AWS Region.Cevap
- Store the infrastructure configuration as AWS CloudFormation templates to deploy the resources in a secondary AWS Region only when a disaster occurs.Cevap
- CCreate an Amazon RDS Read Replica in a secondary AWS Region and configure an active-active failover routing policy in Amazon Route 53.
- DSet up Amazon S3 Cross-Region Replication to duplicate application files to a secondary Region while keeping S3 Versioning disabled on the destination bucket.
- EProvision a pilot light environment by running a continuously operating, scaled-down version of the application servers in a secondary AWS Region.
Cevap
To meet the RPO and RTO requirements at the lowest cost, configure AWS Backup to perform daily backups and copy them to a secondary AWS Region, and store infrastructure configurations as AWS CloudFormation templates to deploy resources only when a disaster occurs.
The RPO of 24 hours allows for a daily backup schedule. Configuring AWS Backup to run daily snapshots and copy them to a secondary Region ensures the data is safely replicated within the RPO window. The RTO of 12 hours gives the administrator enough time to spin up resources from scratch. Storing infrastructure configuration as AWS CloudFormation templates allows resources to be deployed only when a disaster occurs, ensuring zero ongoing infrastructure running costs for the secondary Region's compute resources.
Adım Adım Çözüm
Anahtar Kavram
Disaster Recovery strategies and RTO/RPO cost trade-offs