Domain 7 · Objective reference 7.9 · Chapter 51 of 62
Govern normal and emergency changes
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: Emergency means faster governance not absent governance.
Explore the anchors
Record purpose impact and proposed modification.
Concept matching activity
Match this task or description to its concept:
Approve testing rollback and implementation.
Choose a concept before checking the explanation.
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
Concepts and mechanisms
Change management evaluates, approves, schedules, implements and verifies modifications to a service. Include purpose, scope, impact, dependencies, testing, authority and recovery. Configuration records preserve the resulting state. Normal, standard or emergency routes can differ, but none should mean that consequential changes become unowned or undocumented.
Design, evidence and tradeoffs
Coordinate with business, security, operations and suppliers. A rollback plan must address data and schema compatibility as well as an earlier binary. Verify intended business behavior, access, monitoring and removal of temporary privileges after deployment. Retrospective emergency review should examine appropriateness and lessons, not fabricate an earlier approval. Reassess assurance after material changes.
Worked example
A release changes a database schema, so recovery planning evaluates compatibility of the earlier application with transformed data.
Check your understanding
Why is storing the previous executable not a complete rollback strategy?
Show explanation
It does not establish that state, schema, dependencies and external effects can be safely restored or used by that executable.
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.