Domain 7 · Objective reference 7.10 · Chapter 52 of 62
Choose backup, recovery-site and resilience strategies
About 5 minutes · Current ISC2 outline effective 15 April 2024; the announced 15 April 2027 replacement requires separate mapping
Session only. Enable saving or download a backup from this course’s hub.
Completion is self-reported and does not certify understanding.
See it · Try it · Recall it
Picture the topic
Remember this: A backup is useful only if it can be restored in time.
Explore the anchors
Define recovery time and data-loss tolerances.
Concept matching activity
Match this task or description to its concept:
Choose backup site and dependency arrangements.
Choose a concept before checking the explanation.
Recovery timeline sandbox
Illustrative targets: service RTO 4 hours, data RPO 2 hours. Restoration and validation are sequential in this exercise. Change the durations and backup age.
Service ready after 5h: RTO missed. Data age 4h: RPO missed.
The bars show task duration on a fixed 16-hour scale. A restore can meet RTO and miss RPO. Real acceptance also checks integrity, dependencies and business functionality.
A quick way to study this topic
- Hide the explanation and redraw these three anchors from memory.
- Explain the difference between the anchors in your own words.
- Apply the distinction to the worked example below. Check the full lesson for assumptions and exceptions.
- Recall it again tomorrow, then after a few days. A memory hint is a retrieval cue, not a replacement for understanding.
Original academy illustrations and fictional exercises. These are learning simulations, not a real virtual machine, network assessment or measure of job readiness. Activities reset when you leave or reload; they do not change quiz scores.
What this chapter explains
- Concepts and mechanisms
- Design, evidence and tradeoffs
- Recovery choices and availability limits
Concepts and mechanisms
Recovery strategies combine data, technology, facilities, staff and suppliers. Onsite, offsite and cloud backups have different access, location and dependency considerations. Cold sites require more preparation before use; hotter arrangements provide more ready capacity but cost more and can share configuration or compromise risk. High availability and fault tolerance address selected service failures, not every data-loss or security scenario.
Design, evidence and tradeoffs
Choose the strategy from business impact, recovery time, recovery point, capacity and credible failure conditions. Replication can copy corruption, and backup isolation can fail at the identity or key dependency. Quality of service can support prioritized communications but does not replace recovery. Validate that actual staff, credentials, connectivity and business transactions work under the intended conditions.
Recovery choices and availability limits
A hot recovery site offers more ready capability than a cold site but introduces cost and synchronization dependencies. Capacity agreements need credible activation assumptions. Onsite, offsite and cloud backups differ in location, access and common failure exposure; test restoration and protect recovery credentials. High availability and fault tolerance address selected failures and do not replace recoverable data copies. Quality of service prioritizes traffic under policy and cannot recreate lost data. Compare strategies against recovery-time and recovery-point objectives with dependencies and reconciliation included.
Worked example
A standby service is technically ready, but the recovery exercise finds that its identity provider is the same unavailable production dependency.
Check your understanding
Why can replication be insufficient as the only recovery protection?
Show explanation
It may reproduce deletion, corruption or malicious changes and may share failure dependencies with the original service.
Source and study boundary
Official syllabus source. The reference identifies the topic being taught. Explanations and examples are original academy material; a topic link does not establish independent approval or sufficient exam mastery.