Domain 4 · Objective reference 4A4 · Chapter 27 of 35
Plan technology recovery around service objectives
About 5 minutes · Detailed public baseline effective 2022; the replacement exam starts 3 November 2026 and its exact revised topic/task mapping remains unverified
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: Restoring a server is not the same as restoring a service.
Explore the anchors
Map required systems data and suppliers.
Concept matching activity
Match this task or description to its concept:
Restore in an agreed sequence.
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
- Management concept and decision mechanism
- Define and test recovery expectations
Management concept and decision mechanism
Disaster recovery restores technology and data required by the business. Define recovery time, recovery point, dependencies, access, keys, backup strategy, facilities and responsible staff. A backup product’s successful job is not proof of a usable restore. Replication can copy corruption, and isolated backups can still depend on compromised identity or key services. Test the full recovery path under meaningful failure conditions. Restoration should include validation of business data and service behavior, monitoring and an authorized return-to-service decision.
Define and test recovery expectations
A recovery time objective describes a target time to restore an activity or resource. A recovery point objective describes the point to which data must be restored, commonly expressed as a tolerable period of data loss. Both need business agreement and a feasible supporting capability.
A nightly backup does not guarantee that an end-to-end service can be restored within its target. Check restoration speed, data integrity, credentials, supplier availability, and dependencies. Prioritize realistic recovery tests and record constraints and failures.
Worked example
A restore test demonstrates that the newest usable backup is older than the service’s data-loss tolerance even though the restore finishes within its time target.
Check your understanding
Can recovery time be met while recovery point is missed?
Show explanation
Yes. Fast restoration and acceptable data loss are distinct objectives and require separate evidence.
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.