Free ITIL-5-FOUNDATION Practice Test Questions and Answers (2026)

The 'think and work holistically' guiding principle advises that no service, practice, process, department, or supplier stands alone. To achieve desired outcomes and work as intended, outputs must be integrated. This principle emphasizes understanding the complete service value system (SVS) and how all its components, such as the guiding principles, governance, service value chain, practices, and continual improvement, work together. Decisions must be made with an understanding of their impact on the wider system, not just on a local part, to ensure end-to-end visibility and value delivery.

B. This describes siloed working, which is the opposite of a holistic approach. Holistic thinking encourages collaboration across teams.

C. This is the primary focus of the 'focus on value' guiding principle, although all principles ultimately support value creation.

D. This is the primary focus of the 'optimize and automate' guiding principle, which advises using technology to its fullest extent.

AXELOS. (2019). ITIL® Foundation, ITIL 4 edition. TSO (The Stationery Office). Section 4.3.2, "Think and work holistically," pp. 48-49.

AXELOS. (2020). ITIL® 4: High-velocity IT. TSO (The Stationery Office). Section 3.2.2, "Think and work holistically," discusses the application of this principle in detail.

The ITIL 4 practice guides are designed with a consistent, standardized structure to help organizations use them effectively. This common format ensures that practitioners can easily navigate different guides, locate relevant information (such as processes, value streams, metrics, and roles), and understand how different practices relate to each other. This consistency simplifies the process of adopting and adapting multiple practices, promoting a more holistic and integrated approach to service management across the organization without being overly prescriptive.

B. The standardized structure does not dictate an implementation sequence; ITIL 4 emphasizes a flexible, iterative approach to adoption.

C. ITIL is a framework of best practices and is explicitly tool-agnostic; it does not enforce specific technology choices.

D. The goal of the structure is to increase flexibility and ease of adoption, not to limit it.

1. AXELOS. (2019). ITIL® 4 Foundation, ITIL 4 Edition. TSO (The Stationery Office). Section 5.1, "ITIL management practices," introduces the practices as a set of resources. The consistent structure of the detailed practice guides is a deliberate design choice to make these resources accessible and easy to apply in a consistent manner.

2. AXELOS. (2020). ITIL® 4 Practice Guides. TSO (The Stationery Office). The introduction common to all 34 practice guides explains their purpose and structure, highlighting the goal of providing a practical and consistent set of resources for organizations.

Value is co-created through the combination of utility and warranty. Utility is the functionality offered by a product or service to meet a particular need, often summarized as what the service does ('fit for purpose'). Warranty is the assurance that a product or service will meet agreed requirements, addressing areas like availability, capacity, continuity, and security. This is often summarized as how the service performs ('fit for use'). For a service to provide value, it must have both; it must do what the consumer needs it to do and perform reliably and securely.

A. While cost and risk are components of value, this is not the primary definition of utility and warranty.

B. Utility and warranty are fundamental concepts that apply to both products and services within the ITIL framework.

C. This statement incorrectly reverses the definitions. 'Fit for use' is warranty, and 'fit for purpose' is utility.

AXELOS. (2019). ITIL® Foundation, ITIL 4 edition. TSO (The Stationery Office). Section 2.5.2, "Utility and warranty," pp. 25-26.

AXELOS. (2020). ITIL® 4: A Pocket Guide. Van Haren Publishing. Chapter 3, "Key concepts of service management," explains utility and warranty.

ITIL distinguishes between 'value stream mapping' as an analytical technique and 'value stream management' as an ongoing practice. Mapping is the activity of visualizing the series of steps required to create and deliver value, identifying waste, and highlighting opportunities for improvement. Management, on the other hand, is the broader, continuous discipline of governing, monitoring, and optimizing these value streams to ensure they perform effectively and efficiently over time. Mapping is a tool used within the practice of management.

B. Mapping is for analysis and improvement, not just reporting. Management is a holistic practice of optimization, not solely an auditing function.

C. Both mapping and management apply to the flow of value, regardless of whether it results in a product, a service, or a combination.

D. Both concepts consider a wide range of factors including cost, risk, quality, and lead time, not just cost control or risk avoidance.

- Axelos. (2020). ITIL® 4: Create, Deliver and Support. TSO (The Stationery Office). Section 3.1.1, "Value stream mapping," describes it as a method to "visualize the stream, analyse it, and identify activities that do not create value."

- Axelos. (2019). ITIL® Foundation, ITIL 4 edition. TSO (The Stationery Office). Section 4.5.1, "Value streams and processes," defines a value stream as the series of steps to create and deliver value, implying an ongoing flow to be managed.

The key difference between continuous delivery and continuous deployment lies in the final step of releasing to the production environment. In continuous delivery, any change that passes all automated tests is automatically prepared and made ready for release, but the final deployment to production requires a manual approval step. Continuous deployment extends this process by automatically deploying every passed change directly to production without any human intervention. This makes continuous deployment a more advanced and automated practice.

A. Continuous deployment enables, rather than prevents, more frequent releases by automating the entire pipeline.

B. Both practices rely on automated code integration through Continuous Integration (CI), not manual integration.

D. Both practices depend heavily on comprehensive, automated testing to ensure changes are safe to release; they do not eliminate testing.

1. AXELOS. (2020). ITIL® 4: High-velocity IT. TSO (The Stationery Office). Section 4.3.5 discusses the CI/CD pipeline, explaining that continuous deployment is the fully automated progression of code to the live environment.

2. Humble, J., & Farley, D. (2010). Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Addison-Wesley Professional. Chapter 1 provides the foundational definitions distinguishing continuous delivery (manual release trigger) from continuous deployment (automated release). While not an ITIL publication, this is a seminal academic and professional text whose principles are incorporated into ITIL 4.

The primary purpose of using feedback is to ensure that improvement initiatives remain aligned with stakeholder expectations and deliver value in a changing environment. The ITIL guiding principle 'Progress iteratively with feedback' emphasizes that each iteration should be re-evaluated against feedback to allow for course correction. This ensures that the final outcome is fit for purpose and relevant, even if circumstances change during the improvement cycle. This approach prevents wasted effort by confirming progress and adjusting direction as needed.

A. Feedback is for understanding perspectives, not forcing agreement. Valuable insights can come from differing opinions, which help in making better-informed decisions.

C. The iterative approach, which relies on feedback, inherently accepts that adjustments will be needed. Feedback is a mechanism to enable adjustments, not prevent them.

D. Feedback may reveal that priorities need to change to better achieve the desired value. Avoiding priority changes in the face of new information is counterproductive.

- Axelos. (2019). ITIL® Foundation, ITIL 4 edition. TSO (The Stationery Office). Section 4.3.3, "Progress iteratively with feedback," pp. 49-50. This section states, "Using feedback before, throughout, and after each iteration ensures that actions are focused and appropriate, even in changing circumstances."

Value is the perceived benefits, usefulness, and importance of something, and it is always determined by the service consumer. The perception of value is a subjective assessment based on whether the service helps the consumer achieve their objectives (utility) and performs as expected (warranty). This is fundamentally a trade-off; a service is perceived as valuable when its positive effects (achieved outcomes, removed costs, reduced risks) are greater than its negative effects (costs incurred, new risks introduced). The consumer's unique needs, preferences, and circumstances heavily influence this perception.

A. The service provider's ability to minimize their operational costs: This is a provider-centric view. While cost-efficiency can influence price, it does not directly determine the consumer's perception of value.

B. The number of providers delivering the service to the consumer: The number of providers is irrelevant; value is based on the consumer's experience with the specific service they are using.

D. The amount of money the service provider invests in resources: Investment in resources does not guarantee value. A service is only valuable if it effectively facilitates the consumer's desired outcomes.

- AXELOS. (2019). ITIL® Foundation, ITIL 4 edition. TSO (The Stationery Office). Section 2.2, "Value and value co-creation," p. 11. This section states, "Value is the perceived benefits, usefulness, and importance of something."

The governing body is the entity accountable at the highest level for the performance and compliance of the organization. According to ITIL 4, governance is the means by which an organization is directed and controlled. The governing body is responsible for evaluating, directing, and monitoring the organization's activities to ensure that performance aligns with strategic objectives and that all actions are compliant with relevant policies and external regulations. This role is distinct from day-to-day management, which is responsible for operational activities.

B. Day-to-day operations are the responsibility of management, not the high-level governing body which focuses on direction and control.

C. Direct management of technical details is an operational or technical management function, far below the strategic scope of a governing body.

D. While financial performance is a key concern, a governing body's scope is much broader, encompassing overall strategy, risk, and compliance.

- AXELOS. (2019). ITIL® Foundation, ITIL 4 edition. TSO (The Stationery Office). Section 3.1, "Governance". This section defines governance as the system by which an organization is directed and controlled, with the governing body being accountable for this.

- AXELOS. (2019). ITIL® Foundation, ITIL 4 edition. TSO (The Stationery Office). Section 3.1.1, "Governing body and management". This section explicitly distinguishes the accountability of the governing body from the responsibility of management for day-to-day operations.

The activity described involves the ongoing management and oversight of live digital products and their underlying infrastructure. While not a formal ITIL 4 value chain activity name, 'Operate' best encapsulates the day-to-day actions of maintaining system health, monitoring performance, and ensuring availability. These operational tasks are a core component of the 'Deliver and Support' value chain activity, which focuses on ensuring services meet stakeholder expectations once they are live. This includes the execution of routine maintenance and monitoring procedures to prevent disruptions and manage performance.

A. Deliver: This focuses on making services available to users, which is a distinct phase before the ongoing maintenance and monitoring activity begins.

B. Support: This is primarily a reactive function focused on resolving user-reported incidents, queries, and service requests, rather than proactive system maintenance.

D. Transition: This activity pertains to moving new or changed services and features into the live environment, not their ongoing, day-to-day management.

- AXELOS. (2019). ITIL® Foundation, ITIL 4 edition. TSO (The Stationery Office). Section 4.5.6, "Deliver and support," describes the operational tasks, including monitoring, that are necessary for the ongoing management of services in the live environment.

The official ITIL 4 definition of an incident is an unplanned interruption to a service or a reduction in the quality of a service. This definition focuses on the negative impact on the user or business operations as experienced through the service. The primary goal of incident management is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations, ensuring that the best possible levels of service quality and availability are maintained.

A. This is the definition of an 'event,' which is any change of state that has significance for the management of a configuration item or IT service.

C. This is the definition of a 'problem,' which is a cause, or potential cause, of one or more incidents.

D. This describes a vulnerability or a 'known error,' which is a problem that has a documented root cause and a workaround.

1. AXELOS. (2019). ITIL® 4 Foundation, ITIL 4 Edition. TSO (The Stationery Office). Glossary, p. 221. The definition is explicitly stated as "An unplanned interruption to a service, or reduction in the quality of a service."

2. AXELOS. (2020). ITIL® 4 Practice Guide: Incident Management. TSO (The Stationery Office). Section 2.1, "Purpose and description," reiterates this core definition.