220-1102 Question 674
Single answerPurpose of the changeA technician needs to submit a change request to move 20 accounting users to a new shared printer queue after repeated print failures on the current queue. The new queue has already been tested successfully in a lab. During the weekly change advisory meeting, the manager asks the technician to clarify the purpose of the change before approving it. Which statement BEST describes the purpose of the change?
- A
To document why the change is being made, including the business need and expected outcome
- B
To list every possible future IT project that might be related to printing services
- C
To identify which technician should be blamed if the printer migration fails
- D
To avoid having to create a rollback plan because the new queue worked in testing
Show answer and explanation
Correct answer: A
Explanation
The purpose of the change in a change-management request is to clearly state why the change is needed and what outcome it is intended to achieve. In practical IT environments, this typically includes the issue being resolved, the business justification, and the expected improvement to service. For A+ Core 2, candidates should recognize that change management is not just about technical steps; it also includes communicating business impact, obtaining approval, documenting risk, and preparing rollback procedures. Best practices commonly reflected in IT service management guidance, such as ITIL-style change enablement, emphasize documenting the reason for the change, expected benefits, impact, risk, implementation plan, and backout plan.
- A. Correct.
Correct. In change management, the purpose of the change explains the reason for the proposed change, the problem it addresses, and the intended benefit or business outcome. In this scenario, that would include resolving repeated print failures and improving reliability for accounting users.
- B. Incorrect.
Incorrect. A change request should be focused on the specific proposed change, not unrelated or speculative future projects. While related dependencies may be documented, the purpose section is not meant to become a long-range project roadmap.
- C. Incorrect.
Incorrect. Change management is intended to reduce risk, improve communication, and support controlled implementation, not assign blame. Accountability and implementation roles may be documented elsewhere, but the purpose of the change is not to identify fault.
- D. Incorrect.
Incorrect. Even if testing was successful, standard change management still requires risk assessment and a rollback plan. The purpose of the change explains why the change should happen, not why process safeguards can be skipped.