220-1102 Operational Procedures Practice Question
A technician is implementing a change to deploy new accounting software to 20 workstations. The change has been approved by the Change Advisory Board (CAB). During the deployment, the technician discovers that three workstations have incompatible hardware. According to change management best practices, what should the technician do FIRST?
⚠ Common exam trap
Many exam-takers assume they can pragmatically skip or modify the deployment for the incompatible workstations without formal approval, but CompTIA tests the strict adherence to the change management process where any unapproved deviation—even a logical one—is a violation of policy.
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
✓
Halt the deployment and notify the CAB.
According to change management best practices, when an approved change encounters an unexpected issue—such as incompatible hardware—the technician must halt the deployment and notify the Change Advisory Board (CAB). The CAB must reassess the change request, evaluate the impact of the incompatibility, and decide whether to modify, roll back, or proceed with the change. Proceeding without CAB approval violates the change management process and could introduce unapproved risks or configuration drift.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Proceed with the change on the remaining 17 workstations.
Why it's wrong here
Proceeding with the remaining 17 workstations would sidestep the known compatibility issue on the other three without revisiting the approved change plan. Because the change request was approved for 20 systems, implementing a partial deployment changes the scope of the change, which requires change advisory board (CAB) authorization. The technician also leaves three machines unmodified, creating an inconsistent environment and potential security or compliance gaps that the CAB has not yet assessed.
- ✓
Halt the deployment and notify the CAB.
Why this is correct
Halting the deployment immediately and notifying the CAB is the correct response because the technician has discovered a condition that invalidates an assumption in the approved change plan. The CAB is the only body authorized to re-evaluate the change, approve a revised approach, issue an emergency change, or authorize a rollback. Continuing without escalation would violate change management policy and expose the organization to unplanned risk on the three incompatible workstations. This action also preserves an auditable trail of the decision-making process.
- ✗
Continue the deployment but skip the three incompatible workstations.
Why it's wrong here
Continuing the deployment but simply skipping the three incompatible workstations is an unapproved change of scope, even though the other 17 may be ready. The change request technically covers all 20 machines, and the technician has no authority to exclude any of them without CAB approval. In addition, the skipped workstations remain without the mandated accounting software, which can lead to inconsistencies in financial data and audit findings. The only valid path is to stop work and request an updated or emergency change that explicitly removes or modifies those three systems.
- ✗
Modify the change request to exclude the three workstations and proceed.
Why it's wrong here
Modifying the change request to exclude the three workstations and then proceeding is an unauthorized alteration of a formal control document. In a mature change management process, no one except the CAB or another designated authority may change the approved scope, classification, or implementation details. By editing the request themselves, the technician bypasses governance controls and removes the compatibility issue from review, making the problem invisible to stakeholders. The correct action is to submit a new change request or request a CAB emergency meeting, not to rewrite the existing request.
Go deeper
Related to this question
Learn chapter
Change Management Process
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.
Key term
Configuration drift
Configuration drift is the gradual, unplanned change in a system's configuration settings over time, causing it to deviate from its original or desired state.
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.