ITIL-5-Foundation ITIL Foundation (Version 5) Question and Answers

The main purpose of value stream mapping is to identify and prioritize improvement opportunities, which makes option B correct. ITIL presents value stream mapping as a practical way to understand how work actually flows across teams, systems, and organizational boundaries. By visualizing the “as-is” situation, organizations can spot bottlenecks, delays, handoff issues, waste, duplicated effort, and points where value is lost or slowed. This analysis helps them decide where improvements will have the greatest effect. Mapping may also support better collaboration and management practice use, but those are secondary outcomes. It is not mainly about automating monitoring or controlling stakeholders. The real value lies in making the flow of work visible so that improvement efforts can be based on evidence rather than assumptions or isolated local viewpoints.

Transition is the activity that ensures new or changed products are introduced into the live environment in a controlled and seamless way, so option B is correct. In ITIL, transition bridges development and live operation. It includes planning releases, validating readiness, deploying changes, minimizing disruption, and confirming that the new or changed product can operate effectively in its target environment. Build focuses on creating or modifying solution components. Deliver is concerned with providing services to users. Operate is about maintaining and monitoring live products and systems. Transition is essential because even a well-designed and well-built product can fail if it is introduced poorly. ITIL therefore treats transition as a distinct lifecycle activity that protects service quality, reduces risk, and supports smooth adoption of changes by both technical teams and service consumers.

The purpose of the support activity is to assist users and maintain service performance, so option A is correct. In ITIL, support focuses on helping users, managing incidents and issues, minimizing disruption, and sustaining acceptable service quality when problems occur. It works closely with other activities such as operate and deliver, but its emphasis is on responding to needs, restoring service, and reducing impact. Designing service architectures belongs to design. Building solution components belongs to build. Discovering new opportunities belongs to discover. Support is essential in maintaining trust and user confidence because it is often the activity users encounter most directly when something goes wrong or when they need help. Effective support contributes significantly to perceived service quality and the wider experience of service consumption.

The information and technology dimension supports product and service management by enabling the data, information, and technology needed to create, deliver, support, and improve services. That is why option A is correct. ITIL emphasizes that this dimension includes applications, infrastructure, automation, analytics, AI, monitoring, communication tools, and the governance of information assets. It also includes data quality, usability, access, security, and technology capability. These elements help organizations make informed decisions, support workflows, and enable digital products and services. Roles and responsibilities belong primarily to organizations and people. Workflow structure belongs to value streams and processes. External relationships belong to partners and suppliers. Therefore, the dimension focused on the technological and informational foundation of management and service delivery is information and technology.

Digital services are always based on digital products, so option B is correct. In ITIL, a digital product is a combination of an organization’s resources based on digital technology and designed to offer value to consumers. A digital service uses those digital products to facilitate outcomes and support value co-creation. This means the product forms the technological and resource foundation for the service. The relationship does not work the other way around, so digital products are not based on digital services. They also do not exist independently in the context of digital service management, because products and services are integrated through the lifecycle and value system. Finally, digital products are not service actions. Service actions are provider activities, while products are configurations of resources. Therefore, digital services depend on digital products.

ITIL practice guides use a standardized structure to make the guidance easier to understand, compare, and apply across different organizational contexts. That is why option A is correct. A consistent structure helps learners and practitioners quickly locate key areas such as purpose, key concepts, workflows, measures, roles, competencies, information and technology, and capability development. This improves usability without forcing identical implementation. ITIL does not require organizations to implement every practice in the same sequence, nor does it prescribe one mandatory set of tools. In fact, ITIL strongly supports adaptation to context. The standard format provides clarity and coherence while still allowing flexibility. This is especially helpful in product and service management, where many practices interact and need to be understood as part of a broader management system.

Services may have unintended and surprising outcomes, both positive and negative, so option D is correct. ITIL recognizes that services help facilitate desired outcomes, but they do not guarantee them. Outcomes depend on many factors, including the consumer’s context, usage patterns, constraints, and interactions with the provider. Services may optimize costs and risks, but they do not remove them entirely. Likewise, even well-designed services can create unexpected side effects, dependencies, or new forms of risk. Sometimes those effects are beneficial, and sometimes they are harmful. This is why ITIL emphasizes continual improvement, stakeholder feedback, service relationships, and holistic thinking. Understanding that services can create both intended and unintended consequences helps organizations manage expectations realistically and improve how products and services are designed, delivered, and supported over time.

A digital product is a combination of an organization’s resources based on digital technology and designed to offer value to consumers, so option C is correct. ITIL treats products as structured configurations of resources that can include software, infrastructure, data, interfaces, knowledge, and supporting capabilities. These products form the basis for digital services and help enable outcomes for consumers. Option A sounds more like a service offering description. Option B describes access to resources as a form of service relationship. Option D describes service actions. The digital product concept is important because it connects strategic intent, design, build, operation, and service delivery. It is not just a piece of software, but a managed combination of resources created to support value creation through technology-enabled services.

A key success metric for the acquire activity is the quality of the resources and services outsourced from suppliers, so option B is correct. Acquire is concerned with sourcing and allocating the inputs needed for value creation, including third-party services, components, technology, and other resources. Success therefore depends not only on speed and efficiency, but also on whether what is acquired is fit for purpose, reliable, and aligned with needs. Incident counts are more relevant to operate or support. SLA performance is more relevant to live service delivery. Negative impact of changes is more relevant to transition and change-related activities. ITIL views acquisition as a strategic and operational capability that supports the wider lifecycle. Poor-quality acquired resources create downstream problems, so quality is a strong and appropriate success measure.

The sponsor is the role that authorizes the budget for a service, so option C is correct. In ITIL, different stakeholders in a service relationship have different responsibilities. The customer defines requirements and is accountable for the outcomes of service consumption. Users are the people who actually use the service. The sponsor is the person or group that authorizes funding and provides financial support for the service. This role is important because value co-creation depends not only on usage and outcomes, but also on the commitment of resources needed to obtain and sustain the service. A product vendor may provide or support a product, but that does not automatically make them the budget authority in the consumer organization. Therefore, the sponsor is the role most clearly linked to budget authorization.

The step being performed is “What is the vision?” so option A is correct. In the ITIL continual improvement model, this step establishes the desired direction and ensures that improvement work aligns with organizational goals and objectives. It answers the question of why the improvement matters and what strategic or stakeholder value it is meant to support. Without this first step, later activities may become disconnected from business priorities. “Where are we now?” assesses the current state. “Where do we want to be?” defines the target state more specifically. “Take action” is about implementation. Because the company is ensuring a clear link to goals and objectives before moving ahead, it is working at the vision stage. This creates alignment and gives improvement efforts a clear purpose and justification.

ITIL practice guides benefit organizations by supporting the development of product and service management capabilities, so option C is correct. The guides provide practical, structured guidance for specific management areas and help organizations understand how to perform work effectively in context. They do not prescribe one mandatory technology stack or force all organizations into a single maturity target. ITIL also does not separate product and service management as isolated disciplines; instead, it integrates them through the lifecycle model and the value system. The practice guides help teams understand workflows, roles, measures, interfaces with other practices, and considerations across the Four Dimensions. This makes them useful for building real organizational capability, not just passing exams. Their value lies in practical adaptation and capability improvement across a wide range of management areas.

A product specification is the detailed document that outlines the requirements and characteristics of a product, which makes option D correct. In ITIL, the specification helps create a shared understanding of what the product is expected to do, how it should behave, what constraints apply, and what quality or acceptance criteria must be met. It serves as a reference point for design, build, testing, transition, and later improvement. A prototype is different because it is an early model used to explore or validate ideas. A change request is a formal proposal for a change, and a service request is a user request for a standard service action or access. By clearly documenting requirements and critical characteristics, the product specification supports consistency, communication, and effective lifecycle management.

This commitment represents sustainability, so option D is correct. ITIL includes sustainability as one of the important categories of service level and service quality consideration. It refers to the assurance that a product or service meets requirements related to environmental stewardship, social progress, and economic growth. Examples include responsible sourcing, low carbon footprint, use of recycled or recyclable materials, clean energy, ethical employment practices, and transparent supply chains. Utility is about what the service does. Warranty is about how well it performs. User experience is about how the user perceives interactions with the service and provider. Since the scenario specifically mentions recyclable components, emissions reduction, and supply chain transparency, it clearly reflects sustainability as defined in ITIL 5.

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.

The continual improvement model begins by defining the vision to ensure that improvement efforts align with organizational objectives, so option B is correct. Without a clear understanding of the desired direction, teams may improve the wrong things, optimize locally, or invest effort in changes that do not support strategy or stakeholder value. The vision acts as the anchor for later questions such as where the organization is now, where it wants to be, how it will get there, and how progress will be measured. ITIL emphasizes that improvement should not be random or isolated. It should support the wider purpose, priorities, and desired outcomes of the organization. Current performance metrics and actions matter, but they come after the vision has clarified what success actually means in context.

An incident is defined in ITIL as an unplanned interruption to a service or a reduction in the quality of a service. That is why option B is correct. The key idea is that an incident affects normal service performance and requires timely attention to restore expected service levels. Option A describes an event, which is any change of state that has significance for service management. Option C describes a problem, which is the cause or potential cause of one or more incidents. Option D refers more closely to a known error, defect, or vulnerability. ITIL separates these terms carefully because each one supports a different management activity. Incident management is focused on restoring service quickly, while problem management seeks deeper root causes and longer-term prevention.

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.

The best metric for evaluating the transition activity is the success rate of releases deployed into the live environment, so option A is correct. Transition is responsible for introducing new or changed products and services into live use with minimal disruption and adequate readiness. A strong success measure is therefore how often releases enter production successfully and perform as intended. The number of ideas generated is more relevant to discover or innovation. Average cost per service request relates more to deliver or service management efficiency. Percentage of value streams mapped is a measurement of analysis maturity, not transition performance. ITIL encourages organizations to select metrics that reflect the actual purpose of each activity. Since transition is about controlled introduction into live environments, release success is a direct and meaningful indicator.

The organizations and people dimension is directly influenced by leadership commitment to psychological safety and continual learning, so option D is correct. ITIL explains that culture, leadership, skills, communication, structure, and behavior all sit within this dimension. A psychologically safe environment allows people to speak up about risks, learn from mistakes, ask for help, and contribute ideas without fear. Continual learning strengthens competence, adaptability, and improvement. These factors shape how teams work together and how effectively they can support value creation. While all dimensions can be affected indirectly by leadership, this one is most directly concerned with the human and cultural side of management. Partners and suppliers focuses on external relationships, information and technology on technical enablement, and value streams and processes on workflow design and coordination.

Service performance against agreed SLA targets is not a success metric of the discover activity, so option C is correct. Discover is concerned with understanding stakeholder needs, market context, strategic direction, opportunities, and the relevance of product and service offerings. Suitable success measures therefore include strategic fit, market relevance, and stakeholder satisfaction with offerings. SLA performance, however, is typically associated with live service delivery and service quality management, especially within deliver, operate, and service level management. It measures how well an existing service performs against agreed targets, not how effectively the organization is exploring needs and opportunities. ITIL separates these concerns so that organizations can evaluate discovery work based on alignment and insight rather than operational results that happen later in the lifecycle.