ITIL ITIL-5-Foundation - ITIL Foundation (Version 5)

A problem is the cause, or potential cause, of one or more incidents, which makes option B correct. ITIL clearly distinguishes problem management from incident management. Incident management focuses on restoring service quickly after an interruption or degradation. Problem management looks more deeply at why incidents happened and how similar incidents can be prevented in the future. This is why the root cause idea is central to the definition of a problem. An unplanned interruption is an incident, not a problem. A user request is a service request. A critical incident is still an incident, even if its impact is high. By separating incidents from problems, ITIL enables organizations to both restore service rapidly and reduce repeat disruption through analysis, learning, and long-term corrective actions.

The guiding principle “optimize and automate” should be applied by optimizing processes before automating them, so option B is correct. ITIL warns against automating poor or unnecessary activities because automation can make waste faster and more expensive instead of improving value. Organizations should first understand the workflow, remove unnecessary complexity, simplify where possible, and confirm that the process supports desired outcomes. Only then should they automate appropriate parts of the work. Automation should complement human capabilities, not blindly replace people in every function. Some activities still require judgment, empathy, creativity, and contextual understanding. This principle reflects ITIL’s broader emphasis on practicality, value, and continual improvement. Optimization ensures the work is worth doing, and automation then helps deliver it more efficiently, consistently, and at scale.

ITIL emphasizes that value stream mapping identifies and visualizes how value flows, while value stream management ensures that the value stream performs effectively over time. That is why option A is correct. Mapping is a diagnostic and analytical activity. It helps organizations understand the current flow of work, information, handoffs, delays, bottlenecks, and opportunities for improvement. Management is broader and continuous. It involves monitoring performance, setting measures, coordinating improvements, adapting to changes, and maintaining the health of the value stream over time. Mapping is therefore one important tool within the larger discipline of management. The other options create false distinctions. ITIL applies both concepts across products and services, and neither one is limited only to reporting, auditing, cost, or risk. The real difference is analysis versus ongoing operational stewardship.

The customer takes responsibility for the outcomes of service consumption, so option C is correct. In ITIL, the customer is the person or organization that defines requirements and is accountable for the outcomes enabled by the service. This is different from the sponsor, who authorizes budget, and different from users, who interact with the service directly. The service provider is responsible for delivering and supporting the service, but it cannot fully control the consumer’s outcomes because those outcomes also depend on how the service is used within the consumer’s environment. This distinction is important in service relationships because value is co-created, not simply delivered one-way. By placing accountability for outcomes with the customer, ITIL reflects the shared nature of value creation and the need for active participation on both sides.