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 file server. The patch requires a reboot, and a maintenance window of 2:00 AM to 3:00 AM has been scheduled. The technician successfully installs the patch, reboots the server, and verifies that the server is functioning normally. According to change management best practices, what should the technician do NEXT?
⚠ Common exam trap
A common mix-up: candidates assume a successful implementation means the job is done, but CompTIA emphasizes that documentation and stakeholder communication are mandatory steps before closure, not optional follow-ups.
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 outcome and inform stakeholders.
After a change is implemented and verified, change management best practices require the technician to document the outcome (including any deviations, issues, or successful verification) and inform stakeholders. This closes the communication loop, ensures the change record is complete for audit trails, and allows the CAB or affected users to confirm the system is stable. Simply closing the request or moving on without documentation violates the standard change management process defined in ITIL and CompTIA objectives.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Close the change request immediately.
Why it's wrong here
Closing the change request immediately is premature because the change management process requires verification and documentation before closure. The technician must first confirm that the patch was applied successfully, record the implementation details and any deviations, and then formally close the request. Failing to document the outcome leaves no audit trail and can lead to compliance violations or difficulty troubleshooting future issues.
- ✓
Document the outcome and inform stakeholders.
Why this is correct
Documenting the outcome and informing stakeholders is the correct next step after applying the patch. The technician should update the change request with the actual implementation results, verification steps taken, and any anomalies encountered. Then, notify all affected parties per the change communication plan, as this ensures transparency and allows stakeholders to address any unexpected impacts. Only after this documentation and communication is the change ready for formal closure.
- ✗
Proceed to the next scheduled maintenance task.
Why it's wrong here
Proceeding directly to the next scheduled maintenance task neglects the necessary closure activities for the current change. Each change must have its outcome documented and stakeholders informed before moving on, otherwise the change record remains incomplete and the change cannot be verified as successful. This also breaks the audit trail, making it impossible to demonstrate compliance with change management policies or to perform a post-implementation review if needed.
- ✗
Update the asset inventory with the patch version.
Why it's wrong here
Updating the asset inventory with the patch version is an important supplementary action, but it is not the primary next step. The change request itself must first be updated with the outcome and stakeholders notified, as required by the change management workflow. Inventory updates are part of the broader documentation process but should occur after or in parallel with the official change record update, not instead of it.
Go deeper
Related to this question
Learn chapter
Browser Security Settings and Add-ons
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
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 →
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) approved a standard change to update antivirus definitions on all servers. The technician completes the update on a file server and verifies the server is functioning normally. According to change management best practices, what documentation should the technician complete?
medium- A.Send an email summary to all CAB members
- ✓ B.Update the change log with implementation details and results
- C.Create a backout plan in case the change fails
- D.Submit a post-implementation review report
Why B: Change management best practices require that after implementing an approved change, the technician must document the implementation details and results in the change log. This ensures a complete audit trail, supports rollback decisions, and provides evidence that the change was executed as approved by the CAB. Simply updating antivirus definitions is a standard change, but the closure documentation is still mandatory for compliance and 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.