220-1102 Operational Procedures Practice Question
A change advisory board (CAB) approves an emergency change to apply a critical security patch to a critical server. After the patch is applied and the server is verified operational, the technician completes the documentation. According to change management best practices, what post-implementation step is unique to emergency changes?
⚠ Common exam trap
It's easy for candidates to confuse the standard change management step of 'notifying users' or 'reverting if not approved' with the unique emergency change requirement, failing to recognize that the post-implementation review within 30 days is the specific compensating control for the expedited approval process.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Schedule a post-implementation review within 30 days
Per change management best practices (ITIL), emergency changes bypass the normal CAB approval process and require a post-implementation review (PIR) within 30 days to validate the change, assess any unplanned impacts, and ensure proper documentation. This step is unique to emergency changes as it compensates for the lack of pre-approval by formally confirming the change's success and capturing lessons learned.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Schedule a post-implementation review within 30 days
Why this is correct
Emergency changes bypass normal CAB approval, so a post-implementation review within 30 days is mandated to verify the change achieved its intended outcome, assess any unintended impacts, and ensure all documentation, testing, and rollback details are retroactively completed and properly recorded.
- ✗
Notify all users about the change
Why it's wrong here
While user communication may be appropriate for service-affecting changes, it is not a CAB-specific requirement nor unique to emergency changes; the CAB's focus is on risk assessment and review, not broadcast notifications, which are typically handled by change management or communications teams.
- ✗
Revert the change if not approved later
Why it's wrong here
Emergency changes are pre-approved by the CAB or an authorized representative, so there is no later approval step that would trigger a mandatory revert; reverting might be necessary if the change fails, but it is not a CAB-imposed condition tied to retrospective approval.
- ✗
Obtain verbal approval from the CEO
Why it's wrong here
Emergency change approval typically comes from the CAB chair or designated emergency change approver, not necessarily the CEO; involving the CEO is not a standard requirement and would introduce unnecessary delay and bureaucracy in time-sensitive situations, contradicting the purpose of the emergency process.
Go deeper
Related to this question
Learn chapter
Audit Logging and Review
Key term
POST
Power-On Self-Test (POST) is a diagnostic process that a computer runs when it first powers on to check that essential hardware components are working correctly before loading the operating system.
Key term
Lessons learned
Lessons learned is the process of capturing, analyzing, and documenting knowledge gained from past incidents or projects to improve future security operations and prevent recurrence of problems.
About these practice questions
One of 925 original 220-1102 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1102 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1102 exam.