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

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.

Utility and warranty together support value co-creation because utility makes the service fit for purpose and warranty makes it fit for use, so option D is correct. Utility answers the question, “What does the service do?” It refers to the functionality that helps consumers meet a need or remove a constraint. Warranty answers, “How well does the service perform?” It covers assurance such as availability, capacity, continuity, and security. A service may offer useful functionality, but if it is unreliable or unavailable, it will still fail to create value. Likewise, a stable service with no useful functionality does not help consumers achieve outcomes. ITIL uses both ideas together to explain service quality and service levels. Combined, they help ensure that services are both useful and dependable in real-world use.

The design activity is focused on creating prototypes and specifications, so option A is correct. In the ITIL product and service lifecycle, design translates ideas, needs, and requirements into structured solution concepts that can be built, tested, and transitioned. This includes defining product characteristics, user interactions, architectural approaches, acceptance criteria, and service quality considerations. Prototypes may be created to explore concepts, reduce uncertainty, and validate assumptions before larger investment. Specifications provide the documented requirements and characteristics that guide development and later lifecycle activities. Deliver and support happen later and focus on providing and assisting services in use. Transition is concerned with introducing new or changed products and services into the live environment. Therefore, the lifecycle activity most closely associated with prototypes and specifications is design.

A basic relationship is the correct answer because in ITIL 5 it usually involves a more standardized form of interaction between provider and consumer. The focus is on delivering agreed services efficiently, reliably, and with clear expectations, rather than on deep joint planning or shared governance. In a basic relationship, the service provider typically defines much of the service structure, and the consumer uses the service according to agreed terms. This model works well when services are repeatable, predictable, and designed for scale. By contrast, cooperative and collaborative relationships involve greater interaction, shared decision-making, and more active coordination between the organizations. Therefore, when the goal is support and efficiency through standardized services, the relationship type that best matches that ITIL description is the basic relationship.

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.

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.

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.

Continuous deployment is distinct from continuous delivery because it automatically moves validated changes into the live production environment. That is why option C is correct. In continuous delivery, changes are integrated, tested, and made ready for release, but a deliberate business or operational decision may still be required before deployment to production. In continuous deployment, that final manual release decision is removed, and successful changes flow directly into use. This requires strong automation, testing discipline, monitoring, and confidence in the deployment pipeline. Option B is incorrect because continuous delivery does not require manual code integration; integration is normally frequent and automated. Option D is also wrong because testing becomes more important, not less. ITIL aligns these practices with modern value stream optimization and reliable change flow.

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.

A management practice is best described as a set of organizational resources and capabilities designed to perform work or accomplish an objective, which makes option B correct. In ITIL, a practice is broader than a process. It includes not only activities and workflows, but also roles, competencies, information, technology, partners, and other resources needed to perform effectively. This reflects the Four Dimensions and ITIL’s holistic approach. Option A and D describe value streams or processes more closely, depending on interpretation. Option C refers more to a model or visualization of value co-creation rather than a practice. Practices such as incident management, service level management, architecture management, and supplier management enable the organization to perform specific types of work consistently and effectively within the wider value system.

Value chain activities support an organization’s purpose by translating that purpose into activities that create value, so option A is correct. Purpose explains why the organization exists and what it seeks to provide for consumers and other stakeholders. The value chain then expresses how the organization acts at a high level across the lifecycle of products and services to make that purpose real. Activities such as discover, design, build, transition, operate, deliver, support, and acquire work together to turn intent into outcomes. Governance and compliance frameworks are important, but they are not the main role of value chain activities. Likewise, the value chain does not prescribe specific tools. ITIL positions the value chain as the central operational expression of the value system, helping organizations convert strategic intent into coordinated value-creating action.

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

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.

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.

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 guiding principle “collaborate and promote visibility” should be applied by involving stakeholders and sharing information with them, so option A is correct. ITIL stresses that good decisions and effective work depend on people understanding what is happening, why it matters, and how they can contribute. Collaboration helps bring together different perspectives, knowledge, and responsibilities. Visibility ensures that work, progress, risks, and priorities are transparent enough for informed participation and trust. Limiting communication to management weakens collaboration. Reusing existing processes relates more to “start where you are.” Capturing feedback after each iteration relates more closely to “progress iteratively with feedback.” This principle helps organizations reduce silos, improve coordination, and create a more shared understanding of how value is being created across the service relationship.

An organization’s purpose describes what it does for its consumers and other stakeholders and why it exists, so option D is correct. In ITIL, purpose provides the fundamental reason for the organization’s existence and connects its activities to value creation. It explains the broader intent behind products, services, and relationships. A value stream is a series of steps used to create and deliver value in a specific context. A value chain is the set of high-level lifecycle activities that enables value through products and services. An operating model shows how the organization arranges its capabilities, workflows, and resources to fulfill its purpose. Purpose is therefore the most foundational concept among these. It defines the “why,” while the other concepts describe how value is organized, managed, and delivered in practice.

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.

Support is the activity focused on minimizing the impact of incidents and disasters when they occur, so option C is correct. In ITIL, support includes helping users, restoring normal service, handling incidents, and responding to issues that affect service quality or continuity. Its purpose is not only to react, but to reduce disruption to users and customers as much as possible. Operate maintains live products and supporting systems, while support deals more directly with service interruptions and the human-facing aspects of restoring service. Transition introduces changed products into the live environment, and design defines solutions before they are built. By placing emphasis on rapid assistance, recovery, and user impact reduction, the support activity plays a crucial role in service resilience and in maintaining confidence during service failures or disruptions.

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.