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

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 team is applying the guiding principle “progress iteratively with feedback,” so option C is correct. ITIL recommends moving in manageable steps rather than attempting to deliver everything in one large release. By releasing a small set of features first, the team reduces risk, gets faster learning, and avoids investing heavily in assumptions that may prove incorrect. Gathering user feedback allows them to refine priorities and make the next release more valuable and relevant. This principle is especially useful in complex or uncertain environments where needs may evolve and outcomes cannot be perfectly predicted in advance. While focus on value and collaboration are also important here, the clearest principle illustrated is iterative progress supported by feedback. It helps improve adaptability, responsiveness, and overall service quality.

The principle “think and work holistically” emphasizes considering all components of the service value system and their relationships when making decisions, so option A is correct. ITIL teaches that products and services are created and managed through interconnected people, technologies, partners, workflows, governance mechanisms, and practices. Focusing on one part in isolation can create local optimization but system-wide problems. A change that improves one team’s efficiency, for example, may create delays or risks elsewhere. This principle encourages organizations to view the full system, including dependencies, handoffs, stakeholders, and outcomes. While value creation is important, that idea is broader and more closely linked to “focus on value.” Automation belongs to another principle. Holistic thinking ensures that improvements support the whole organization and the overall flow of value.

Value streams and processes are important because they show how activities are coordinated to create and deliver value, so option B is correct. In ITIL, the value streams and processes dimension focuses on how work flows through the organization and across organizational boundaries. It helps explain the sequence of activities, dependencies, handoffs, and interactions that transform demand into useful outcomes for stakeholders. This is essential because value creation is rarely achieved by one team or one isolated activity. Tools, reporting lines, and contracts may support management, but they are not the main concern of this dimension. ITIL stresses that actual work as performed should be understood, mapped, analyzed, and improved. Value streams make the flow of value visible, while processes provide structured guidance for recurring activities that support that flow.

The governing body is accountable at the highest level for the organization’s performance and compliance, so option A is correct. In ITIL, governance ensures that the organization is directed and controlled in a way that aligns with stakeholder expectations, legal and regulatory obligations, and strategic objectives. The governing body does not usually perform day-to-day operations or manage technical product details directly. Instead, it evaluates the environment and stakeholder needs, directs priorities and policies, and monitors performance and conformance. Financial reporting may be one concern, but governance is much broader and includes value creation, risk, compliance, ethics, and strategic oversight. This high-level accountability is essential because it connects leadership intent with responsible management and assures stakeholders that the organization is being guided appropriately.

The organizations and people aspect of an Official ITIL Practice Guide describes the roles, competencies, and responsibilities needed for a specific practice, so option C is correct. This reflects the Four Dimensions model, where organizations and people focuses on leadership, structure, culture, roles, skills, and communication. In a practice guide, this aspect helps organizations understand what human capabilities and accountabilities are necessary to apply the practice effectively. Capability assessment and development is more about measuring and improving maturity or capability over time. General information provides overview content. Partners and suppliers focuses on external relationships and contributions. Since the question asks specifically about roles, competencies, and responsibilities, the organizations and people section is the most accurate answer. ITIL uses this structure to keep practice guidance holistic and practical.

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 primary purpose of the acquire activity is to secure and allocate the necessary resources efficiently, so option B is correct. In ITIL, value creation depends on having the right people, technologies, suppliers, components, information, and services available when needed. The acquire activity supports this by sourcing, obtaining, and allocating resources in line with strategy, architecture, and operational demand. It may involve procurement, supplier coordination, access arrangements, or other forms of resource acquisition. Incident recovery belongs more to support. User onboarding belongs to deliver. Creating prototypes belongs to design. Acquire is important because value streams cannot perform effectively if critical resources are missing, delayed, poor in quality, or misaligned with requirements. It helps ensure that the organization has the inputs needed to build, operate, and improve products and services.

A digital service enables value through the use of digital products, so option A is correct. ITIL explains that digital services largely or fully rely on digital products, which are combinations of an organization’s resources based on digital technology and designed to offer value. The service is what facilitates outcomes for consumers, while the product provides the underlying capabilities, technology, interfaces, data, and resources that make that possible. A digital product does not replace the need for services because service management is still required to support delivery, operation, support, and improvement. A digital service is not limited to internal IT systems, since it can serve internal or external consumers. It is also not independent of a digital product, because the product typically underpins the service relationship and service experience.

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.

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 typically used to establish a shared understanding of expected and achieved service quality, so option B is correct. ITIL explains that service quality is often translated into service level metrics and documented through agreements between provider and customer. An SLA identifies the services covered, the agreed service levels, and how those levels will be measured and reviewed. This creates clarity around utility, warranty, sustainability, and experience expectations. A product specification describes product requirements, while service level requirements are usually inputs used to shape a future agreement rather than the formal shared understanding itself. Roadmaps show future direction and planning. Therefore, the SLA is the most appropriate mechanism for defining, communicating, and monitoring the agreed quality of a service relationship.

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.

A digital service is a service that fully or largely relies on digital products, which makes option A correct. ITIL distinguishes between digital products and digital services while showing that they are closely connected. The digital product is the combination of digital resources designed to offer value. The digital service is the means by which value is co-created with consumers using those products. Option B is closer to the definition of a digital product. Option C describes one type of service interaction, not the general definition of a digital service. Option D refers to a catalogue or representation of available services rather than the service itself. The digital service concept reflects ITIL’s focus on technology-enabled value creation through outcomes, service relationships, and managed access to capabilities.

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.

Service quality is most concerned with how well a service meets agreed requirements and expectations, so option A is correct. ITIL defines service quality as the sum of the characteristics of a service that are relevant to its ability to satisfy stated and implied needs. This means quality is broader than speed of incident resolution alone. It includes utility, warranty, sustainability, and user experience, depending on the context of the service relationship. Social responsibility may be part of sustainability, but it does not on its own define overall service quality. Likewise, rapid development does not guarantee quality. ITIL encourages organizations to translate expectations into service level metrics and manage the service accordingly. Therefore, service quality is fundamentally about meeting what has been agreed and what stakeholders genuinely need.

A service is perceived as valuable when its positive effects outweigh its negative effects for the consumer. That is why option C is correct. In ITIL, value is not defined only by what the provider delivers. It depends on the consumer’s perception of benefits, usefulness, and importance. Consumers evaluate whether the service helps them achieve desired outcomes while optimizing associated costs and risks. Even a technically strong service may be seen as low value if it is hard to use, unreliable, expensive, or creates unwanted effort. Conversely, a service with well-balanced utility, warranty, sustainability, and experience may be seen as highly valuable. Provider investment or internal efficiency alone does not determine value. ITIL places emphasis on outcomes and stakeholder perception, which is why consumer judgment about net positive effect is central.

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 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.

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.

The main purpose of the discover activity is to align product capabilities with consumer needs and organizational strategy, so option C is correct. Discover is concerned with understanding the market, stakeholders, opportunities, constraints, and strategic direction before design and build work begins. It helps the organization identify what should be created or improved and why that matters. This includes gathering insights, understanding service consumers, exploring demand, and confirming relevance. Developing and testing products belongs more to build and related activities. Securing resources belongs to acquire. Maintaining and monitoring products belongs to operate. Discover is valuable because it reduces the risk of building the wrong thing and helps ensure that product and service decisions are grounded in value, context, and strategic fit rather than assumptions alone.

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 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.

An event is best described as any change of state that has significance for the management of a service, so option C is correct. In ITIL, events are not automatically negative. They may indicate normal operations, warnings, thresholds being crossed, or conditions that require attention. Event management helps organizations observe and respond appropriately to what is happening in live systems. A user request is a service request, not an event. A sudden damaging occurrence may be an incident or disaster, depending on context. The addition or removal of something affecting services relates more to a change or configuration item context. By defining events broadly as significant state changes, ITIL enables organizations to monitor services proactively and respond before issues become major service interruptions.