Select backup/restore, pilot light, warm standby, or multi-site patterns from explicit RTO, RPO, cost, and complexity constraints.
1.RTO 24 hours, RPO 12 hours, lowest steady-state cost
2.RTO 20 minutes with a scaled-down complete environment
3.Core data services run in recovery Region, application capacity launches during recovery
4.Near-zero RTO and traffic served from both Regions
5.Maximum acceptable data loss is 15 minutes
6.Maximum acceptable recovery time is one hour
7.Protect against accidental deletion replicated immediately
8.A design claims cross-Region recovery but has never been tested
9.DNS fails over, but the target database is stale
10.Moderate budget, RTO several hours, infrastructure recreated from code
Objectifs
- Translate RTO and RPO into architecture implications.
- Select the lowest-complexity strategy that meets the objectives.
- Score at least 80%.
Indices