Resilience for Cloud Architects
Cloud resilience is the ability of a system to keep working or recover after failures. High availability spreads components across availability zones and removes single points of failure, while backup and disaster recovery define recovery time and recovery point objectives and the strategy, from backup-restore to multi-region active-active.
Stage: Resilient and Performant · Part of the Cloud Architect roadmap · Last reviewed 19 November 2026
What to learn in Resilience
- Deploy an application across multiple availability zones behind a load balancer
- Define recovery time objective and recovery point objective for a system
- Compare backup and restore, pilot light, warm standby and active-active
- Test failover and restore procedures regularly
- Design health checks and automatic replacement of failed instances
Resilience interview questions
What is the difference between RTO and RPO?
Recovery time objective is how long the business can tolerate a service being down. Recovery point objective is how much data loss, measured in time, is acceptable. Tighter targets need more replication and cost more.
Why is a backup you have never restored not trustworthy?
Backups can be incomplete, corrupted, encrypted with a lost key or too slow to restore within the objective. Only regular restore tests prove that data is recoverable and that the documented procedure works under time pressure.
Where Resilience fits in the Cloud Architect roadmap
Resilience belongs to the Resilient and Performant stage (advanced level), which takes about 38 hours. Build for scale and failure.
Other units in this stage
Back to the full Cloud Architect roadmap