Objective 3.4 covers resilience and recovery: staying up when parts fail and coming back quickly when something fails badly, through redundancy, alternate sites, diversity, planning, testing, backups, and power.
Staying up. High availability uses load balancing, which spreads requests across independent servers, or clustering, which makes several servers behave as one system that survives the loss of a member. Platform diversity and multi-cloud systems keep one flaw or outage from becoming your entire outage: redundancy is a spare, and diversity is a spare of a different kind. Power resilience pairs a UPS for immediate, short-term power with a generator for slower-starting, long-term power.
Where and how to recover. Hot, warm, and cold sites differ in equipment and data currency: more readiness means faster recovery and higher cost. Geographic dispersion guards against regional loss. Continuity of operations decides which functions must keep running during a crisis, and capacity planning covers the people, technology, and infrastructure to make that true. Recovery plans are proven by tabletop exercises, simulations, parallel processing, and fail over tests, which trade realism for risk and cost.
Backups. Backups are tested, protected copies kept separate from the original. Choices include onsite or offsite storage, frequency, encryption, snapshots, replication, and journaling. A snapshot on the same storage shares its failures, and replication mirrors damage as well as good data, so neither replaces an independent backup.
Exam scenarios give a recovery requirement and ask which site type, backup method, or test fits; faster recovery generally costs more, so the answer is usually a trade-off.
Written by Knotch · reviewed Nov 15, 2026 · 7 study articles behind this page