ITIL ITIL-5-Foundation ITIL Foundation (Version 5) Exam Practice Test

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.

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.

A service journey describes the end-to-end interactions between a service provider and a service consumer, which makes option A correct. ITIL uses this concept to help organizations understand the full consumer experience across the stages of discovering, accessing, using, receiving support for, and continuing with a service. It includes visible touchpoints, interactions, perceptions, and moments that shape user experience and value realization. It is not the same as internal workflows, which belong more to value streams and processes. It is also not the same as the product lifecycle or the formal sequence of value chain activities. By understanding the service journey, organizations can improve service design, communication, support, and experience from the consumer perspective rather than only from an internal operational viewpoint.

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 correct answer is partners and suppliers because this ITIL dimension focuses on an organization’s relationships with external parties involved in creating, delivering, supporting, or improving products and services. These may include suppliers, strategic partners, outsourced providers, and other contributors in the wider service ecosystem. ITIL emphasizes that no organization operates alone, so managing agreements, dependencies, expectations, and collaboration with third parties is essential. This dimension also considers sourcing strategies, levels of integration, risk, capability availability, and service coordination across networks. The other dimensions focus on different areas: organizations and people addresses structure, culture, and competencies; information and technology addresses data and enabling technologies; and value streams and processes addresses workflows and how work is organized to create value. Therefore, external relationship management sits within partners and suppliers.

The correct components of the ITIL Value System are guiding principles, governance, value chain, management practices, and continual improvement, so option D is correct. The ITIL Value System provides the overall model for how an organization ensures its products and services create value in a coherent, aligned, and adaptable way. The guiding principles provide universal recommendations for decision-making. Governance ensures direction, evaluation, and monitoring. The value chain defines the high-level activities used across the lifecycle. Management practices provide the capabilities needed to perform work. Continual improvement ensures that the whole system evolves and remains effective over time. The other options list important concepts, but not the formal components of the Value System. ITIL uses this model to integrate governance and management into one practical framework.

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.

The most appropriate metric for assessing the success of the build activity is the quality of the product solutions, so option D is correct. Build is concerned with creating or modifying solution components so they are fit for intended use in later lifecycle stages. Measures for build therefore focus on the quality, completeness, maintainability, and suitability of what is produced. The other options are associated with different activities. Incident resolution within targets is more relevant to support. Customer satisfaction after service delivery is more relevant to deliver and service experience. First-contact fulfillment is also a service delivery or support measure. ITIL encourages organizations to choose metrics that match the purpose of each value chain activity. Since build is about producing sound product components, the quality of those solutions is the clearest measure of success.

ITIL describes the guiding principles as something that should be used collectively and balanced based on the situation, which makes option D correct. They are not a checklist to follow in a rigid order, and they do not replace governance, practices, or other parts of the value system. Instead, they support decision-making and behavior across all circumstances. In one situation, focus on value may be especially important. In another, collaboration, iterative progress, or simplicity may need more emphasis. The point is that they work together. Applying one principle without considering the others can create imbalance or poor outcomes. This flexible approach allows the principles to remain useful across different industries, organizational types, and contexts. Their value lies in judgment, not mechanical sequence.

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.

Value co-creation means that value is created jointly through interactions between service providers and service consumers, so option D is correct. ITIL moved away from the idea that value is simply produced by the provider and handed over to the consumer. Instead, value emerges through the combination of provider offerings, consumer participation, context, usage, and the wider service relationship. A service may offer strong utility and warranty, but the actual value realized depends on how the consumer uses it and what outcomes are achieved. This is why ITIL emphasizes service relationships, shared responsibilities, and stakeholder perspectives. Value is not created independently of those relationships, and it is not defined solely by the provider. Co-creation reflects the dynamic and interactive nature of modern digital product and service management.

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.

The dimension that addresses organizational and cross-organizational workflows is value streams and processes, so option D is correct. ITIL uses this dimension to focus on how work is organized, coordinated, and performed to enable value creation. It includes flows of activities, information, and artifacts within the organization and across organizational boundaries. This dimension is especially important because value is often created through complex interactions among multiple teams, suppliers, and systems. By understanding processes and mapping value streams, organizations can identify delays, bottlenecks, and waste while improving coordination and outcomes. Partners and suppliers focuses on external relationships, organizations and people focuses on structure and skills, and information and technology focuses on enabling systems and data. The workflow dimension is therefore value streams and processes.

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.

This situation shows transfer of goods and service actions, so option C is correct. The printer being delivered to the customer is an example of transfer of goods because a physical item is provided to the consumer. The ongoing maintenance and support are service actions because they involve activities carried out by the supplier to help the customer use the printer successfully and maintain service performance. Access to resources would apply if the customer were mainly using provider-owned resources under agreed terms, such as software access or shared infrastructure. A service journey is broader and refers to the end-to-end experience across interactions. ITIL identifies these interaction patterns to help organizations understand how value is co-created in different service relationships. In this case, both a physical transfer and ongoing provider activity are clearly present.

The main purpose of feedback during improvement iterations is to ensure that actions remain relevant and effective as circumstances change, so option B is correct. ITIL promotes iterative progress because environments, stakeholder needs, risks, and information often change during work. Feedback helps teams learn what is working, what is not, and what should be adjusted before moving further. It is not realistic to expect all stakeholders to fully agree at every point, and feedback does not eliminate the need for future adjustments. Instead, it supports better decisions, earlier correction, and more effective alignment with value. This approach reduces waste and improves adaptability. It is closely connected to the guiding principle “progress iteratively with feedback,” which encourages organizations to move in manageable steps and use learning continuously to refine outcomes.

Access to resources supports value co-creation by allowing consumers to use provider resources under agreed terms, which makes option A correct. In ITIL, not every service interaction requires transfer of ownership or direct provider action every time. Sometimes the value comes from enabling consumers to access applications, data, infrastructure, knowledge bases, or equipment that remain under provider control. The consumer gains the ability to use these resources to achieve outcomes without needing to own and manage all of them directly. This helps optimize costs, risks, and effort. It does not mean transferring responsibility for all resources to the consumer, nor does it imply restricting usage to internal teams. It also does not eliminate service actions entirely, because support and other activities may still be needed. Access to resources is one important form of service relationship.

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.

This is an example of service actions, which makes option B correct. In ITIL, service relationships can involve access to resources, transfer of goods, and service actions. Service actions are activities performed by the provider, or jointly by provider and consumer, to help users achieve outcomes. Assisting a user with configuring a laptop clearly involves active support and direct interaction, so it fits the service actions category. It is not transfer of goods, because the key interaction is not about handing over a physical item. It is not sustainability, which relates to environmental, social, and economic responsibility. It is also not simply access to resources, because the engineer is doing more than just granting access. The assistance itself is the value-creating action in this scenario.

A Service Level Agreement is best described as a documented agreement between a service provider and a customer that identifies the services and their agreed levels, so option B is correct. In ITIL, the SLA is a formal mechanism for creating shared understanding of expected and achieved service quality. It may include metrics related to utility, warranty, sustainability, and user experience, depending on context. It is more than an informal discussion and is not just an internal guideline. It also is not limited to vendor penalty clauses, although contractual elements may exist around it. The purpose of an SLA is to clarify what will be provided, how performance will be measured, and what both parties can reasonably expect. This helps support transparency, accountability, and effective service relationships.

The primary purpose of a product in ITIL is to offer value to consumers through a defined configuration of resources, so option A is correct. A product combines resources such as technology, people, information, processes, and partner capabilities in a way that is designed to create value. Services are often built on products, and products provide the structure and capabilities that services use to facilitate outcomes. Option C describes the purpose of a service more directly than the purpose of a product. Products do not replace service management practices, nor is compliance their primary purpose, even though compliance may be a requirement. ITIL integrates product and service management because products are central to how value is made possible, while services are central to how value is experienced and co-created through relationships.

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.

Information and technology is the dimension that addresses the data and technologies used in digital products and services, so option D is correct. ITIL explains that this dimension includes applications, infrastructure, tools, automation, analytics, AI, monitoring, communication systems, and the management of data, information, and knowledge. It also includes concerns such as data quality, access, governance, security, and technology capability. This dimension is central in digital product and service management because technology not only supports service delivery, but often forms the core of the product itself. Partners and suppliers covers external organizations, organizations and people covers structure and skills, and value streams and processes covers workflows. Therefore, when the focus is specifically on data and technological enablement, the correct ITIL dimension is information and technology.