Which ITIL 4 concept describes the deliverable produced by an activity, while the result for the stakeholder is described by a different concept?
An output is a tangible or intangible deliverable produced by an activity, such as a new system component, a processed transaction, or a report. It is a direct result of work performed, but not necessarily the desired end-state or benefit. An outcome, conversely, is the result achieved for a stakeholder, enabled by one or more outputs, and represents the actual value or business impact realized. This concept directly addresses the question's focus on "deliverable produced."
Why this answer
In ITIL 4, an 'output' is the tangible or intangible deliverable produced directly by an activity (e.g., a completed service request form), while an 'outcome' is the result for the stakeholder, such as restored business functionality or improved user satisfaction. Option A correctly distinguishes these two concepts, which is a core distinction in service value system design.
Exam trap
The trap here is that candidates confuse 'output' with 'outcome' because both are results of processes, but ITIL 4 explicitly separates them to emphasize that delivering an output does not guarantee a positive stakeholder outcome.
How to eliminate wrong answers
Option B is wrong because 'Service Request vs. Change' describes different types of service management actions, not the relationship between a deliverable and its stakeholder result. Option C is wrong because 'Incident vs.
Problem' distinguishes between an unplanned interruption (incident) and its underlying cause (problem), not between an activity's output and its outcome. Option D is wrong because 'Utility vs. Warranty' describes service functionality (fitness for purpose) and assurance (fitness for use), not the deliverable-result distinction.