220-1102 Question 675
Single answerScope of the changeA technician is preparing a change request to remove a deprecated browser plug-in from 40 shared Windows workstations in the accounting department. The plug-in has caused repeated security alerts, but a small legacy payroll application may still depend on it. The IT manager asks the technician to define the scope of the change before approval. Which action BEST addresses the scope of the change?
- A
Identify which users, systems, applications, and business processes will be affected, and document the departments and devices included in the rollout
- B
Schedule the removal for after business hours so users are less likely to notice the change
- C
Create a backout plan in case the payroll application fails after the plug-in is removed
- D
Send an email to all employees informing them that the plug-in will be removed next week
Show answer and explanation
Correct answer: A
Explanation
In A+ Core 2 change-management objectives, 'scope of the change' refers to the boundaries and impact of the proposed change: what systems are included, who is affected, what applications or services depend on the change, and which business units or processes may be impacted. In this scenario, the technician must verify whether the change affects only the accounting department's shared PCs or also a legacy payroll workflow. This helps avoid unintended outages and supports proper approval, testing, scheduling, communication, and rollback planning. Best practices from standard IT change-management processes emphasize documenting affected assets, users, dependencies, and business impact before implementation.
- A. Correct.
Correct. Defining the scope of the change means determining exactly what is included and impacted by the change: which devices, users, applications, locations, and business functions are affected. In this scenario, the technician must identify whether only the 40 accounting workstations are included and whether the legacy payroll application or related users depend on the plug-in. This is the core purpose of scoping in change management.
- B. Incorrect.
Incorrect. Scheduling is an important part of change planning, but it does not define scope. A change can be well scheduled and still poorly scoped if the technician has not identified all affected systems, users, and dependencies.
- C. Incorrect.
Incorrect. A backout or rollback plan is a required best practice in change management, especially when a business-critical application may break. However, a backout plan addresses recovery if the change fails, not the scope of what the change includes and affects.
- D. Incorrect.
Incorrect. User communication is also an important change-management step, but notification does not establish the scope. Informing everyone may even be inappropriate if only one department is affected. Scope should be defined first so communication can be targeted and accurate.