ITIL 4 Foundation (ITIL4F) — Questions 1–75

Categorization helps balance the need for speed and risk assessment for different types of changes.

Change enablement is the ITIL practice that ensures all changes to the production environment are properly assessed, authorized, and controlled before implementation. By enforcing a standardized change management process—including change requests, approvals, and review boards—this practice directly prevents unauthorized modifications that cause service outages.

Incident Management (D) is the correct ITIL practice because it provides the specific framework for classifying, prioritizing, and handling incidents based on business impact and urgency. This practice defines the lifecycle from detection through resolution, including categorization and prioritization matrices that directly address the scenario's requirement.

Incident Management aims to restore normal service operation as quickly as possible and minimize the adverse impact on business operations.

The SVS includes: Guiding Principles, Governance, Service Value Chain, Practices, and Continual Improvement. Service Catalogue and Known Error Database are not components.

Option B is correct because continual improvement is a core component of the ITIL 4 Service Value System (SVS) and is applied as a guiding principle at all levels, from strategic to operational activities. The ITIL 4 framework explicitly embeds the continual improvement model into the SVS to ensure that all value chain activities, practices, and governance are iteratively optimized, not treated as a one-time project.

The Information and Technology dimension includes data, knowledge, information security, AI, cloud, and tools. Option A (Knowledge management tools) and Option D (Information security policies) are correct. Option B is part of Partners and Suppliers; Option C is part of Organisations and People; Option E is part of Value Streams and Processes.

Capacity management starts with planning, then monitoring, analyzing, forecasting, and implementing improvements.

A service request is a formal request for something to be provided – for example, for a new laptop. An incident is an unplanned service interruption; slowness could be an incident if it's a degradation, but a request for a new device is a service request.

Incidents are unplanned interruptions or degradation of service quality. Service requests are pre-defined, pre-approved, routine requests that do not involve a disruption.

Option A is correct because 'Practices' are a core component of the ITIL 4 Service Value System (SVS). The SVS is defined by the ITIL 4 framework to include the Guiding Principles, Governance, Service Value Chain, Practices, and Continual Improvement. Practices are sets of organizational resources designed for performing work or accomplishing an objective, replacing the ITIL v3 'processes' concept.

Mean Time to Restore Service (MTRS) directly measures the average time taken to fully restore a service after a failure, making it the best metric for assessing how effectively the service desk restores service. ITIL 4 defines MTRS as the elapsed time from when a service fails to when it is fully restored, including diagnosis, repair, and verification. A lower MTRS indicates faster restoration, which is the core objective of incident management.

The Continual Improvement practice uses the 7-step improvement model.

SVS includes Guiding Principles, Governance, Service Value Chain, Practices, and Continual Improvement.

First Contact Resolution (FCR) and Customer Satisfaction (CSAT) are key service desk metrics.

Option D is correct because in ITIL 4, an 'output' is a tangible, direct result of an activity (e.g., fewer server incidents due to the monitoring system), while an 'outcome' is the business value or benefit derived from that output (e.g., improved end-user productivity). The monitoring system directly reduces server incidents (output), which in turn enables end-users to work without interruption, improving their productivity (outcome). This aligns with the ITIL Service Value System's focus on value co-creation through outcomes.

Option B is correct because Problem Management is explicitly tasked with investigating the underlying cause of one or more incidents, aiming to identify the root cause and prevent recurrence. Option D is correct because Incident Management focuses on restoring normal service operation as quickly as possible, often using a workaround to achieve this, which is a key distinction from Problem Management's longer-term analytical focus.

Option A is correct because the Service Value Chain is a core component of the ITIL 4 Service Value System (SVS). It provides an operating model for the creation, delivery, and continual improvement of services through six key activities: plan, improve, engage, design & transition, obtain/build, and deliver & support.

A service request is a formal request from a user for something to be provided – for example, for information, advice, or access to an IT service. Creating a new user account is a standard, pre-defined request that does not involve a change to the service or an unplanned interruption, so it fits the ITIL 4 definition of a service request (option D).

Service Configuration Management manages CIs and configuration baselines to support control and auditing.

Service desk handling begins with logging, then categorization, support, updating, and confirmation.

Option A is correct because the ITIL 4 definition of a change authority explicitly states it is a person or group responsible for authorizing a change. This aligns with the change enablement practice, which assigns authorization based on the change type and organizational policies, not on a single role like the CAB.

Value co-creation is a joint activity between the provider and consumer. Both parties contribute resources and activities to create value.

The Configuration Management Database (CMDB) is the central repository for storing and managing configuration records (CIs) and their relationships. This is the core responsibility of the Service Configuration Management practice, which ensures that accurate and reliable information about CIs is available to support other service management processes.

Utility is 'fit for purpose' (functionality), warranty is 'fit for use' (assurance). Both are necessary for a service to create value. Warranty covers availability, capacity, continuity, and security.

D is correct because a Standard change is pre-authorized by default and follows a low-risk, standardized procedure, such as applying a routine security patch or provisioning a new user account. This aligns with ITIL 4's definition of a Standard change as one that is well-understood, fully documented, and can be implemented without requiring additional approval each time.

The ITIL 4 Service Value System (SVS) is designed as a flexible operating model that enables organizations to co-create value consistently. It integrates all components and activities of the organization into a unified system, allowing adaptation to changing business needs without prescribing rigid processes. This flexibility is its primary purpose, distinguishing it from a fixed hierarchy or standardization framework.

Option C is correct because the 'Focus on value' guiding principle in ITIL 4 explicitly states that everything the organization does must map directly to value for stakeholders, starting with a clear understanding of who the consumer is and what they value. This principle ensures that service design, delivery, and improvement are driven by outcomes that matter to the customer, not by internal processes or technology.

Option A is correct because it directly applies the ITIL 4 guiding principle 'Focus on Value' by prioritizing a permanent fix based on business impact, and 'Progress Iteratively with Feedback' by using Problem Management to identify the root cause of the intermittent outages. This approach ensures a long-term solution that minimizes business impact and prevents recurrence, aligning with the company's limited budget by avoiding a complete system overhaul.

The service value chain consists of six activities: Plan, Improve, Engage, Design & Transition, Obtain/Build, and Deliver & Support.

ITIL 4 defines a service as a means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.

Incident Management is responsible for restoring service using workarounds; Problem Management identifies the workaround but does not execute it.

Utility is 'fit for purpose' — the functionality offered by a product or service to meet a specific need. Option A is correct.

The 'Focus on value' guiding principle emphasizes that all activities and services should be directly linked to delivering value to stakeholders, starting with understanding the customer's desired outcomes. In ITIL 4, this means defining the service's utility (fit for purpose) and warranty (fit for use) based on what the customer actually needs, rather than assuming technical requirements. This principle ensures that service design is driven by value co-creation, not by internal capabilities or assumptions.

D is correct because a service request in ITIL 4 is defined as a formal request from a user for something to be provided – for example, information, advice, access to a service, or a pre-approved standard change. Since the software installation is pre-approved and follows a standard procedure, it fits the definition of a service request, not an incident or problem.

The ITIL 4 Continual Improvement Model is a 7-step process that guides improvement initiatives.

Standard changes are pre-approved and low-risk, often implemented via a service request.

The primary purpose of Incident Management is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations.

The service provider takes on the costs of infrastructure, removing those costs from the consumer.

Value is defined as the perceived benefits, usefulness, and importance of something. Assessing benefits, costs, and risks is key to determining value.

First Call Resolution (FCR) is a key metric for the Service Desk practice because it measures the percentage of incidents resolved during the first interaction with the user, without the need for escalation or follow-up. A high FCR directly indicates the efficiency and effectiveness of the Service Desk in resolving issues promptly, reducing user downtime and operational costs. This metric is critical for assessing the quality of first-level support and the knowledge base's adequacy.

Utility is defined as the functionality offered by a product or service to meet a particular need, i.e., fit for purpose. Warranty is assurance that the service will perform as agreed (fit for use).

The ITIL 4 Service Value System (SVS) is a structured framework that defines how all components and activities of an organization work together to facilitate value creation. The Guiding Principles (B) are a core component, providing universal recommendations that guide an organization in all its work, and the Service Value Chain (C) is the central operating model for creating, delivering, and improving services. Both are explicitly listed as key components of the SVS in the ITIL 4 Foundation syllabus.

A request for a new laptop is a pre-approved, standard change (service request), even if the user is dissatisfied. Slow performance is not an unplanned disruption.

The first step in incident management is to log the incident, capturing key details, before proceeding with investigation or escalation.

Mean Time to Resolve (MTTR) measures how quickly incidents are resolved, reflecting efficiency.

The first step in Incident Management is to log the incident and attempt to restore service. The analyst should create an incident record.

The ITIL 4 Service Value System (SVS) is a holistic framework that includes several core components: the Guiding Principles, Governance, the Service Value Chain, Practices, and Continual Improvement. The seven guiding principles (e.g., 'Focus on Value', 'Start Where You Are') are explicitly defined as a standalone component of the SVS, not a subset of any other component. Therefore, option B is correct because the guiding principles are their own distinct element within the SVS structure.

Option D is correct because it aligns with the ITIL guiding principles of 'Start where you are' and 'Progress iteratively with feedback'. By optimizing the most critical database queries and adding caching, the company addresses the root cause of the performance issue (inefficient queries) with minimal cost and downtime, avoiding the high risk and expense of a full system rewrite or database replacement.

According to ITIL 4, when users cannot access a service like a CRM system, the first action is to log an incident record and attempt to restore service as quickly as possible. This aligns with the incident management practice, which prioritizes minimizing downtime over root cause analysis or procedural changes. The analyst must capture details, categorize the incident, and apply a workaround or fix to restore normal service operation.

The Information and Technology dimension is one of the four dimensions of service management in ITIL 4. It covers the technologies, tools, and data used to manage and deliver services, including specific systems like ITSM platforms, monitoring tools, and databases. This dimension ensures that technology aligns with service strategy and operational requirements.

Problem Management includes problem identification, problem control (root cause analysis), and error control (managing known errors). Logging incidents and fulfilling requests belong to other practices.

The SVS includes Guiding Principles, Governance, Service Value Chain, Practices, and Continual Improvement.

Governance includes evaluating, directing, and monitoring. Setting objectives and assigning targets is part of directing.

The primary purpose of Incident Management is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations. This ensures that service availability and quality are maintained, aligning with the ITIL 4 guiding principle of 'Focus on Value' by prioritizing rapid recovery over root cause analysis.

The Service Desk practice is defined in ITIL 4 as the entry point and single point of contact for users seeking support, reporting incidents, or requesting services. Its primary focus is on capturing, managing, and resolving user interactions, not on technical infrastructure monitoring or asset lifecycle management.

Problem management starts with detection and logging, then categorization, root cause analysis, solution identification, and closure.

The first step is to log an incident to restore service as quickly as possible. Root cause analysis (problem management) comes later.

Option D is correct because the Value Streams and Processes dimension focuses on workflows, activities, and how work is done.

Service Level Management is the practice of negotiating, agreeing, and monitoring service level agreements (SLAs) with customers, and ensuring that services meet those targets.

Capacity and Performance Management ensures that services have the necessary resources to meet agreed performance and demand levels.

Incident Management aims to restore normal service operation as quickly as possible and minimize adverse impact on business operations. Option C is correct.

In a service relationship, the consumer can transfer direct costs (like hardware procurement) and personnel costs (like hiring IT staff) to the provider. Licensing costs are often part of the service. Office rent is typically not transferred.