220-1102 Operational Procedures Practice Question
A technician has received approval from the Change Advisory Board (CAB) to apply a critical security patch to a production database server. The patch requires a reboot and will cause a 15-minute outage during the approved maintenance window. The technician has successfully installed the patch and rebooted the server. The server is back online and appears to be functioning normally. According to change management best practices, what should the technician do NEXT?
⚠ Common exam trap
Watch out — candidates often confuse the operational task of informing users with the formal change management requirement to document the change, leading them to select the seemingly helpful but procedurally incorrect 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 post-implementation report and update the change record.
After a change is implemented and verified, change management best practices require the technician to document the outcome in a post-implementation report and update the change record. This ensures a complete audit trail, captures any deviations from the plan, and provides feedback for future changes. Simply closing the ticket or informing users without updating the record violates the formal change management process.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Document the change in the post-implementation report and update the change record.
Why this is correct
The post-implementation report and change record serve as the authoritative documentation of what was actually performed, including any deviations from the approved change plan. Once the maintenance is complete, the technician must record outcomes, any rollback actions taken, and lessons learned, then update the change record's status (e.g., to 'Reviewed' or 'Closed'). This ensures the CAB has visibility for audit and future change decisions, and satisfies change management's requirement for a formal post-implementation review.
- ✗
Close the change request ticket immediately.
Why it's wrong here
Closing the change request ticket immediately skips the required verification that the implementation achieved its intended result and that the system is stable. Standard change management practice requires the change record to remain open until documentation is complete, acceptance is confirmed, and any post-implementation findings are recorded. Immediate closure can hide incomplete or failed changes, break the audit trail, and corrupt metrics used to assess change success.
- ✗
Inform all affected users that the maintenance is complete.
Why it's wrong here
Notifying affected users that maintenance is complete is a courtesy communication, but it is not the formal next action required by the change management process. Before any user communication occurs, the change outcome must be documented in the post-implementation report and the change record updated to capture the actual results. Informing users without written documentation leaves the change without evidence if a problem or a CAB review follows.
- ✗
Perform a full system backup of the server.
Why it's wrong here
Performing a full system backup is a rollback-preparation activity that must happen before the change is implemented, not after it. A post-change backup would capture the modified state, so it cannot support rollback to the original configuration. The immediately required next step is updating the change record and post-implementation report; a backup after the change is neither the defined cascade action nor a substitute for documentation.
Go deeper
Related to this question
Learn chapter
Browser Security Settings and Add-ons
Key term
Audit trail
An audit trail is a chronological record of events, changes, or activities in a system that provides evidence of who did what, when, and from where.
Key term
Audit
An audit is a systematic, independent review of IT systems, processes, and controls to verify compliance with policies, standards, and regulations.
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 →
Same concept, more angles
1 more way this is tested on 220-1102
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. 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?
medium- A.Notify all users of potential downtime
- ✓ B.Document the change in the change request with the results
- C.Submit a post-implementation report to the CAB
- D.Close the change request immediately
Why B: 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.
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.