ITIL considers outcomes, costs, and risks together because value is created when desired outcomes are achieved while associated costs and risks are optimized, so option A is correct. A service does not create value simply because it exists or because it provides functionality. Consumers evaluate value based on whether the service helps them achieve meaningful results and whether the effort, expense, constraints, and uncertainty involved are acceptable. If a service enables outcomes but introduces excessive risk or cost, value may be low. Likewise, minimizing risk without enabling outcomes does not create much value. This balanced view is central to ITIL’s definition of service value. It explains why service relationships must consider utility, warranty, experience, sustainability, and the wider context of service consumption rather than focusing on one factor alone.
Question # 25
What is continuous integration?
Options:
A.
Automatically releasing every code change into production
B.
Regularly merging code into a central repository with automated builds and tests
C.
The ability to track and evaluate service value
D.
A method of ensuring ultra-scalable systems through operations engineering
Continuous integration is the practice of regularly merging code into a central repository, typically supported by automated builds and tests, so option B is correct. Its purpose is to detect integration issues early, improve quality, and support a smoother flow of changes through the build and transition activities. By integrating frequently, teams reduce the risk and complexity that arise when many changes are combined late. Automated testing and validation are essential because they provide fast feedback and confidence that the new code still works as expected. Option A describes continuous deployment rather than continuous integration. Options C and D do not match the ITIL or software delivery meaning of the term. Continuous integration supports value stream performance by making change safer, faster, and easier to manage.
Question # 26
How does an enabling value stream contribute to value creation?
Options:
A.
By supporting the effective operation of core value streams
B.
By replacing the need for core value streams
C.
By defining customer outcomes and service expectations
D.
By acting as the primary interface with service consumers
An enabling value stream contributes to value creation by supporting the operation and performance of core value streams. That is why option A is correct. Core value streams directly create or deliver value for service consumers, while enabling value streams provide the capabilities, resources, coordination, or support needed for those core streams to function effectively. Examples may include procurement, onboarding, internal platform management, or knowledge management processes that do not directly serve the customer at the final interaction point but are essential for smooth service creation and delivery. ITIL takes a holistic view of value creation and recognizes that many important workflows are indirect. These supporting streams do not replace core value streams, but they strengthen them by improving reliability, speed, quality, and consistency across the wider operating model.
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.
