220-1102 Operational Procedures Practice Question
A change advisory board (CAB) has approved a standard change to update the firmware on a network switch. Before implementing the change, the technician creates a backup of the current configuration and prepares a rollback plan. After successfully applying the firmware update, what should the technician do NEXT according to change management best practices?
⚠ Common exam trap
Candidates often confuse the documentation step for standard changes with the post-implementation report requirement that applies only to major or emergency changes, leading candidates to incorrectly select Option C.
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
✓
Document the change in the change request with the results
After implementing a standard change, the technician must document the actual results—including success, failure, or any deviations—in the change request. This closes the change management lifecycle, provides an audit trail, and ensures the CAB and other stakeholders have a record of what was done. Without this documentation, the change cannot be formally verified or used for future reference.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Notify all users of potential downtime
Why it's wrong here
User communication for a standard change is performed during the planning phase, prior to implementation, to set expectations and provide workaround instructions if needed. Sending notifications after the change has succeeded defeats the purpose and can cause confusion if the change involved a service interruption. Even for a standard change, the notification timeline is defined in the change procedure and must occur before the execution window, not as a follow-up activity.
- ✓
Document the change in the change request with the results
Why this is correct
Recording the actual outcome, including verification steps, any encountered issues, and rollback actions, is a mandatory part of the close-out process for any change. This documentation creates an audit trail and becomes a reference for future changes, helping to identify recurring problems and improve the standard change process. It is the primary deliverable expected by the change manager after implementation, and it formally updates the change record from 'implemented' to 'reviewed' until final closure.
- ✗
Submit a post-implementation report to the CAB
Why it's wrong here
A standard change is pre-authorized by the CAB based on a low-risk template, so it does not require a formal post-implementation report; that reporting requirement is reserved for emergency or major changes with higher risk or broader impact. Instead, the results are captured within the change request itself for administrative review. Forcing a standard change through a post-implementation CAB report creates unnecessary overhead and delays the change closure, contradicting the streamlined intent of standard changes.
- ✗
Close the change request immediately
Why it's wrong here
Closing a change request without first documenting the results leaves no evidence that the change was verified and successful, which exposes the organization to audit violations and makes later troubleshooting impossible. The change management policy typically requires that the change record be updated with actual results, and only then can the change be set to 'closed' status. Immediate closure also skips the opportunity to signal any hidden issues that would require a back-out plan, undermining the governance the CAB approval process is meant to enforce.
Go deeper
Related to this question
Learn chapter
Cloud Backup Solutions
Key term
Audit
An audit is a systematic, independent review of IT systems, processes, and controls to verify compliance with policies, standards, and regulations.
Key term
Change management
Change management is the structured process of planning, approving, implementing, and reviewing changes to IT systems to minimize risk and disruption.
About these practice questions
This 220-1102 question is part of Courseiva's 925-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.