An organization is designing a disaster recovery (DR) strategy for an internal reporting application. The application is non-critical, and the business has set both the Recovery Time Objective (RTO) and the Recovery Point Objective (RPO) to 24 hours. The primary objective of the design is to minimize ongoing running costs. Which disaster recovery strategy should the solutions architect recommend to meet these requirements?
- AMulti-Site Active-Active strategy by running full-capacity environments in two regions with continuous bidirectional database replication.
- BWarm Standby strategy by running a scaled-down duplicate of the application and database in a secondary region to allow rapid failover.
- Backup and Restore strategy by taking daily snapshots of the database and application data, storing them in Amazon S3, and recreating the resources only when a disaster occurs.Answer
- DPilot Light strategy by keeping a minimal copy of the database replication instance running continuously in a secondary region while keeping application servers turned off.
Answer
Backup and Restore strategy by taking daily snapshots of the database and application data, storing them in Amazon S3, and recreating the resources only when a disaster occurs.
A Backup and Restore strategy is the most cost-effective option because it does not require running active infrastructure in a secondary region under normal operations. Backups can be scheduled daily to satisfy the 24-hour RPO, and the infrastructure can be provisioned on-demand (e.g., using CloudFormation or Terraform) to restore the application within the 24-hour RTO limit.
Step-by-Step Solution
Key Concept
Disaster Recovery strategies trade off RTO/RPO against cost, where Backup & Restore has the lowest cost and highest RTO/RPO.
Estimated Time:45s