220-1102 Operational Procedures Practice Question
A technician is preparing a change request to upgrade the operating system on a file server. Which element is MOST important to include in the change request to minimize the impact on users?
⚠ Common exam trap
Many exam-takers choose Option B (exact start time and expected duration) because they focus on scheduling and communication to minimize user disruption, but they overlook that a rollback plan is the only option that directly addresses failure recovery, which is the primary risk in any change management 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
✓
A detailed rollback plan in case the upgrade fails
A detailed rollback plan is the most critical element to include in a change request for an OS upgrade on a file server. If the upgrade fails or introduces critical issues, the rollback plan provides step-by-step procedures to restore the server to its previous working state, directly minimizing user downtime and data loss. Without a rollback plan, a failed upgrade could leave users unable to access files for an extended period while troubleshooting occurs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The technician's name and contact information
Why it's wrong here
While identifying the technician responsible for the upgrade is important for accountability and coordination, it does nothing to reduce the risk of data loss or downtime if the upgrade encounters a critical failure. The change request's primary purpose is to enable a safe, reversible operation; without a documented rollback procedure, the technician's presence alone cannot restore the previous OS environment or recover user data. Therefore, it is a secondary administrative detail, not the key element for minimizing user impact.
- ✗
The exact start time and expected duration of the upgrade
Why it's wrong here
Specifying when the upgrade will occur and how long it is expected to take helps stakeholders plan for brief unavailability and is a required part of a change schedule. However, the actual duration is an estimate; if the upgrade fails midway, the support team may need to troubleshoot, and without a rollback plan the system could remain offline for hours or days. A rollback plan is what bounds the recovery time by providing a deterministic path back to the pre-upgrade state, whereas start time/duration only communicates the intended outage window without addressing failure recovery. Thus, while useful for notification, it does not minimize the impact of a failed upgrade.
- ✓
A detailed rollback plan in case the upgrade fails
Why this is correct
A detailed rollback plan is the single most critical component because it directly mitigates the worst-case scenario of an OS upgrade failure leaving the system in an unbootable or unstable state. It should include validated backup images, pre-upgrade system state snapshots, specific commands or restore procedures, and acceptance criteria to confirm the system returns to its prior configuration. Without this plan, technicians are forced to troubleshoot reactively, which can lead to prolonged downtime and permanent data loss for users. The primary goal of change management is reducing business disruption, and a rollback plan is the definitive safety net that accomplishes that objective.
- ✗
The total cost of any new hardware or software licenses
Why it's wrong here
While budgeting for new hardware or licenses is a legitimate part of the change proposal for approval, the cost figure is a financial metric that does not affect the technical execution or the capability to recover from an upgrade failure. Even if the upgrade is fully funded, a failed deployment can still leave users without access until the issue is resolved, and cost data provides no procedure for restoring the previous OS. The change request's focus for minimizing user impact is on operational resilience—rollback, testing, and communication—not on financial justification, which is a separate approval consideration. Therefore, cost is irrelevant to the immediate mitigation of user disruption.
Go deeper
Related to this question
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.