A change record states: "The change request has been approved by the CAB."
What is a CAB in IT change management?
The Change Advisory Board (CAB) is an ITIL construct: a cross-functional group (IT operations, business, security, architects) that reviews the risk, impact, rollback plan, and scheduling of normal and major changes before authorising them.
Change type
CAB required?
Description
Standard change
No — pre-approved
Low-risk, routine, well-documented procedure
Normal change
Yes — full CAB review
Non-routine change, scheduled through the change process
Emergency change
ECAB — reduced group
Critical production fix, expedited approval process
Key vocabulary: RFC (Request For Change), change record, CAB approval.
2 / 9
A new engineer asks about the difference between change types in the ITIL process.
What is an "emergency change" in ITIL change management, and how does it differ from a "standard change"?
Both standard and emergency changes bypass full CAB review, but for different reasons: standard changes are pre-approved because they are routine and low-risk; emergency changes are expedited because a production incident demands it.
Concept
Standard change
Emergency change
Why expedited
Pre-approved — known low risk, documented procedure
Critical production incident — time-sensitive
Approval body
None required — pre-authorised
ECAB (Emergency CAB) — smaller, faster group
Example
Routine monthly patch deployment
P1 incident hotfix outside maintenance window
3 / 9
An operations manager says: "The team is operating under a change freeze from 15 December to 5 January."
What does a change freeze mean for deployments?
A change freeze (or change moratorium) is a temporary suspension of all non-emergency changes. Production is considered too risky to change during peak business periods. Emergency changes can still be approved via ECAB with justification.
Term
Meaning
change moratorium
Temporary halt on all non-emergency production changes
freeze window
The specific date range during which the freeze applies
emergency change exception
A critical change approved during a freeze to resolve a production incident
freeze communication
Notifying all teams of the freeze dates and exception process well in advance
4 / 9
A change manager rejects a change record saying: "The rollback plan is insufficient."
What must a rollback plan include to be considered complete in an ITIL change record?
A rollback plan must be: specific (exact commands/steps, not "restore from backup"), accountable (named owner), timely (maximum rollback window defined), and verifiable (success criteria stated).
Component
Requirement
Backout procedure
Numbered step-by-step instructions with exact commands
Rollback owner
A named engineer responsible for executing the rollback
RTO for rollback
Maximum acceptable time to complete the rollback (e.g. ≤15 minutes)
Rollback success criteria
Observable evidence that the rollback completed successfully
5 / 9
A change item reads: "Post-implementation review (PIR) for this change is scheduled 48 hours after deployment."
What is the purpose of a PIR in change management?
The Post-Implementation Review (PIR) closes the feedback loop. Questions addressed: did the change achieve its stated objective? Were there unexpected impacts? What should be improved in the change process? Results feed change management KPIs.
PIR topic
Question addressed
Objective achievement
Did the change accomplish what the RFC stated?
Unexpected impacts
Did the change cause any unintended side effects?
Lessons learned
What can be improved in the change procedure next time?
Change quality KPI
Change success rate, unplanned changes ratio — fed by PIR outcomes
6 / 9
Alex (Senior Developer) comments on a PR: 'This change introduces a significant API modification. Have you considered the potential impact on downstream services? We should document this thoroughly.' What is Alex primarily concerned about regarding the proposed change?
Alex is worried about compatibility issues. While code quality (option A) and performance (option D) are important, the core concern here is ensuring that the new API change won't break existing systems or integrations – a key aspect of risk assessment in change management. It highlights the need for thorough impact analysis before deployment.
7 / 9
Sarah (Change Manager) sends a Slack message to the team: 'Just a reminder – we're entering a formal change freeze on Friday for the database migration. No deployments are permitted until January 15th.' What is the primary purpose of this 'change freeze'?
A 'change freeze' is a deliberate restriction on deploying modifications. It's implemented to minimize risk and allow sufficient time for thorough testing and validation before releasing changes into a live production environment – a fundamental control in change management processes. The other options represent secondary considerations or potential activities *after* the freeze.
8 / 9
David (Lead DevOps) sends a message: 'The automated deployment pipeline is failing with a 'rollback required' error. We need to quickly revert to the previous stable version to minimize disruption.' What does 'rollback required' typically indicate within the change management process?
'Rollback required' signifies an unplanned failure during a deployment. This triggers a formal change – reverting to a stable version – as a priority action to mitigate service disruption. It's distinct from planned maintenance or code debugging; it's directly related to restoring functionality after a failed attempt.
9 / 9
Maria (Developer) writes in a PR description: 'This update modifies the authentication flow. We've added comprehensive unit tests, but we need to ensure compatibility with our legacy systems before deploying.' What aspect of change management is Maria primarily addressing?
Maria's comment highlights the importance of considering compatibility and potential impact when modifying critical systems like authentication flows. Change management isn't just about *what* is changed; it's also about *how* that change affects other parts of the system and its dependencies – a core principle of risk assessment.
What will I practice in "Change Management Vocabulary Exercises"?
This is a Release Management exercise set. It walks through 9 scenario-based multiple-choice questions built around real usage of release management terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 9 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the release management vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Release Management exercises?
See the Release Management exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — release management vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.