ITIL · Question #182
Which of the following would be used to communicate a high level description of a major change that involved significant cost and risk to the organization?
The correct answer is A. Change proposal. A change proposal is the formal ITIL artifact used to present a high-level description, business justification, costs, and risks of a major change to senior stakeholders for authorization.
Question
Which of the following would be used to communicate a high level description of a major change that involved significant cost and risk to the organization?
Options
- AChange proposal
- BChange policy
- CService request
- DRisk register
How the community answered
(55 responses)- A91% (50)
- B2% (1)
- C2% (1)
- D5% (3)
Why each option
A change proposal is the formal ITIL artifact used to present a high-level description, business justification, costs, and risks of a major change to senior stakeholders for authorization.
In ITIL change management, a change proposal is specifically created for significant or major changes that carry substantial cost and risk, providing decision-makers with a high-level overview before detailed planning begins. It differs from a request for change in that it is submitted earlier in the process to secure high-level approval and funding commitment, ensuring that only justified major changes proceed to full planning.
A change policy is a governance document that defines the rules and criteria for managing changes broadly, not a communication artifact for a specific change instance.
A service request covers routine, pre-approved, low-risk activities such as password resets or standard software installs, not high-cost major changes.
A risk register is a repository used to log and track risks across the organization and is not used to communicate the scope or description of an individual change.
Concept tested: ITIL change proposal for major organizational changes
Source: https://www.axelos.com/certifications/itil-service-management/itil-4-foundation
Topics
Community Discussion
No community discussion yet for this question.