75 of 139 questions · Page 1/2 · Key Concepts of ITIL 4 · Answers revealed
Drag and drop the steps of the capacity and performance management process into the correct order.
Drag or tap steps into the slots.
Why this order
Capacity management starts with planning, then monitoring, analyzing, forecasting, and implementing improvements.
A user calls the service desk to request a new laptop because their current one is slow. According to ITIL 4, how should this be categorized?
A service request is a formal request from a user for something that is a normal part of service delivery, typically pre-defined, pre-approved, and often automated. Requesting a new laptop falls squarely into this category, as it's a standard offering within the service catalog, handled efficiently by the Service Request Management practice. These requests are usually low-risk, frequently occurring, and have a clear, established fulfillment process.
Why this answer
According to ITIL 4, a service request is a user-initiated request for something to be provided, such as information, advice, a standard change, or access to a service. Requesting a new laptop because the current one is slow is a standard request for equipment, not a failure of an existing service. Therefore, it should be categorized as a service request.
Exam trap
ITIL4F often tests the distinction between incident and service request; candidates may incorrectly choose incident because the user reports a problem (slow laptop), but the request is for a new asset, which is a service request.
How to eliminate wrong answers
Option A is wrong because a change request is typically for modifying an existing service or infrastructure, often requiring approval and scheduling; a laptop replacement is a standard service request. Option C is wrong because an incident is an unplanned interruption or reduction in quality of a service; a slow laptop might be an incident if it's a fault, but the user is requesting a new laptop, which is a request for a new asset. Option D is wrong because a problem is the underlying cause of one or more incidents; this scenario is not about root cause analysis but about fulfilling a request.
In value co-creation, which of the following is TRUE about the roles of service provider and service consumer?
This statement accurately defines the core principle of value co-creation within the ITIL framework. Value is not unilaterally delivered by a provider and passively consumed; instead, it emerges from the active, collaborative engagement and interaction between the service provider and the service consumer. Both parties contribute resources, capabilities, and knowledge, influencing the service design, delivery, and consumption to realize mutually beneficial outcomes. This joint participation is essential for tailoring services effectively and maximizing their utility and warranty.
Why this answer
In ITIL 4, value co-creation is a fundamental principle where both the service provider and service consumer actively participate in creating value. The provider supplies resources and manages risks, while the consumer contributes requirements, feedback, and usage context. This joint participation ensures that value is not simply delivered but is realized through the interaction of both parties.
Exam trap
The trap here is that candidates often assume the provider is solely responsible for value creation (Option D) because traditional IT service management focused on delivery, but ITIL 4 explicitly shifts to a co-creation model where the consumer's active role is essential.
How to eliminate wrong answers
Option A is wrong because the provider does not bear all costs and risks; the consumer also bears costs (e.g., subscription fees, internal resources) and risks (e.g., service disruption impact). Option C is wrong because the consumer is not solely responsible for defining all service requirements; requirements are collaboratively defined through ongoing dialogue and feedback between provider and consumer. Option D is wrong because the provider does not create all value while the consumer passively receives it; value is co-created through active consumer involvement, such as using the service, providing feedback, and integrating it into their own processes.
Which THREE of the following are correct about the relationship between utility and warranty?
Warranty assures that a service is 'fit for use,' meaning it meets agreed-upon performance characteristics and non-functional requirements. This includes aspects like service availability, capacity, continuity, and security, ensuring the service performs reliably and consistently as expected by the consumer. It provides confidence that the service will not fail or be unduly interrupted during its operation.
Why this answer
Warranty in ITIL 4 refers to the assurance that a service will meet its agreed requirements, ensuring it is 'fit for use'. This includes aspects like availability, capacity, continuity, and security, which guarantee that the service can be relied upon under defined conditions.
Exam trap
A common misconception is that utility alone can create value, but the trap here is that candidates forget warranty is a mandatory prerequisite for value realization, as per ITIL 4's definition of a service.
Which THREE of the following are key components of the service value chain in ITIL 4?
Deliver & Support is a core activity within the ITIL Service Value Chain (SVC), focusing on ensuring services are delivered according to agreed specifications and support is provided to users. This activity encompasses the operational aspects of service provision, including incident resolution, service request fulfillment, and ongoing service operation, directly contributing to the realization of value for the service consumer.
Why this answer
In ITIL 4, the service value chain consists of six key activities: Plan, Improve, Engage, Design & Transition, Obtain/Build, and Deliver & Support. Option A (Deliver & Support) is correct because it is the activity that ensures services are delivered and supported according to agreed specifications and stakeholders' expectations. Option B (Improve) is correct because it is the activity focused on continual improvement of products, services, and practices across all value chain activities and the four dimensions of service management.
Option C (Plan) is correct because it is the activity that ensures a shared understanding of the vision, current status, and improvement direction for all four dimensions and all products and services across the organization. Option D (Problem resolution) is not a service value chain activity; it is a practice (problem management) within ITIL 4. Option E (Service desk) is also not a value chain activity; it is a practice (service desk) that serves as the entry point for incident and service request handling.
Exam trap
The trap here is that candidates confuse ITIL practices (like problem management) or functions (like the service desk) with the six fixed value chain activities, leading them to select plausible-sounding but incorrect options.
In ITIL 4, what is the definition of a service?
This definition accurately captures the essence of a service in ITIL 4, emphasizing its customer-centric and outcome-focused nature. A service is designed to collaborate with the customer ('value co-creation') to help them achieve their desired results ('outcomes') without the customer needing to manage the specific costs and risks associated with the underlying resources. The service provider takes on the burden, allowing the consumer to focus on their core business objectives and realize value.
Why this answer
In ITIL 4, a service is defined 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. This definition shifts the focus from technology components to the business outcomes and value delivered, aligning with the ITIL 4 guiding principle of 'Focus on Value'.
Exam trap
The trap here is that candidates often confuse the definition of a service with its components (hardware/software), organizational functions, or operational processes, leading them to select options A, B, or C instead of recognizing the ITIL 4 focus on value co-creation and outcomes.
How to eliminate wrong answers
Option A is wrong because it describes a set of IT hardware and software, which is a technology asset or configuration item, not a service; ITIL 4 defines a service in terms of value co-creation, not technology components. Option B is wrong because it refers to a function within the IT organization, such as a service desk or IT operations team, which is an organizational structure, not a service definition. Option C is wrong because it describes a process for managing incidents, which is a specific ITIL practice (incident management), not the definition of a service itself.
A customer subscribes to a cloud storage service. They no longer need to maintain their own servers, reducing their capital expenditure. This reduction is an example of:
Moving to cloud storage eliminates the consumer's server hardware, maintenance and facilities overheads, so those costs disappear entirely from their books. ITIL 4 defines this as costs removed from the consumer, matching the stem's capital expenditure reduction achieved by no longer maintaining own servers.
Why this answer
When a customer subscribes to a cloud storage service, they eliminate the need to purchase and maintain their own physical servers. This directly reduces their capital expenditure (CapEx), which is a cost that is removed from the consumer. In ITIL 4, this is a key example of how cloud services shift financial burdens away from the consumer.
Exam trap
The trap here is that candidates confuse 'costs removed from the consumer' with 'risk transferred to the provider,' but risk transfer specifically involves liability for service failures or data breaches, not the elimination of capital expenses.
How to eliminate wrong answers
Option B is wrong because utility refers to the functionality of the service (e.g., the ability to store and retrieve data on demand), not the financial impact of reduced CapEx. Option C is wrong because warranty assurance covers availability, capacity, continuity, and security of the service, not the removal of capital costs. Option D is wrong because risk transferred to the provider typically involves operational risks like data loss or downtime, not the financial risk of capital investment in hardware.
An IT department decides to implement a new monitoring tool. Before purchasing, they analyse the potential benefits, costs, and risks. This analysis directly supports which ITIL 4 concept?
Value represents the perceived benefits, usefulness, and importance of something to a stakeholder, derived from balancing the benefits, costs, and risks. An IT department decides to implement a new monitoring tool because they anticipate it will deliver greater value, such as improved operational efficiency, enhanced problem detection, or better risk management, which are expected to outweigh the investment and potential challenges. This decision is fundamentally driven by the expectation of creating or realizing this net positive outcome.
Why this answer
ITIL 4 defines value as the perceived benefits, usefulness, and importance of something, co-created through services. Analysing benefits, costs, and risks before purchasing is a value assessment — it weighs what the organisation gains against what it spends and the exposure it accepts. This directly supports the value concept in the ITIL 4 service value system.
Exam trap
ITIL4F often tests the distinction between utility (functionality) and value (perceived benefit) — candidates pick utility because the tool 'does something', missing that the analysis is about benefits versus costs and risks.
How to eliminate wrong answers
Option A is wrong because warranty in ITIL 4 refers to assurance that a service will meet its agreed requirements (availability, capacity, security, continuity), not a cost-benefit-risk analysis. Option C is wrong because utility is about the functionality a service offers — 'what it does' — not the financial and risk evaluation. Option D is wrong because output is a tangible or intangible deliverable of an activity, not a decision-support concept.
Which ITIL 4 concept describes the functionality of a service that makes it fit for purpose?
Utility is the correct ITIL 4 concept that describes the functionality offered by a product or service to meet a particular need. It defines 'what the service does' and determines whether it is 'fit for purpose.' This concept directly addresses the inherent capabilities and features that allow a service to perform its intended functions and support the consumer's tasks.
Why this answer
Utility is the ITIL 4 concept that defines the functionality offered by a service to meet a specific user need, making it 'fit for purpose.' It answers the question 'What does the service do?' and is a core component of service value, distinct from warranty which addresses 'fit for use.'
Exam trap
The trap here is that candidates often confuse 'utility' with 'value' or 'outcome,' mistakenly thinking the service's functionality directly equals its business value, when in ITIL 4 utility is only one component that contributes to value alongside warranty.
How to eliminate wrong answers
Option A is wrong because Warranty refers to the assurance that a service will meet agreed requirements (e.g., availability, capacity, security), not its core functionality. Option B is wrong because Value is the perceived benefits, usefulness, and importance of a service, which is an outcome of both utility and warranty combined, not the functionality itself. Option D is wrong because Outcome is the result of using a service (e.g., a business goal achieved), not the service's inherent functionality or features.
A user calls the service desk to request a new laptop because their current one is slow and outdated. However, the user's manager wants the request handled as an incident because the laptop is affecting productivity. According to ITIL 4, how should this request be classified?
A service request is a formal request from a user for something that is part of normal service delivery, such as information, advice, or a standard change. Requesting a new laptop, especially when it's a standard model and follows a pre-defined fulfillment process, perfectly aligns with the definition of a service request. These requests are typically low-risk, frequently occurring, and follow established procedures for efficient processing.
Why this answer
This request is a service request because the user is asking for a new laptop as a pre-defined, standard item, not reporting a disruption to an existing service. ITIL 4 defines a service request as a formal request for something to be provided, such as access to a new asset. The user's inability to work effectively does not change the classification; the underlying issue is a need for a new asset, not an unplanned interruption.
Exam trap
The trap here is that candidates confuse the user's inability to work (which sounds like an incident) with the actual nature of the request (a standard request for a new asset), leading them to incorrectly choose Option C.
How to eliminate wrong answers
Option A is wrong because a change request is used for modifications to existing services or assets, not for standard, pre-approved requests like ordering a new laptop, which follow a service request process. Option C is wrong because an incident is an unplanned interruption or reduction in quality of an existing service; the user's current laptop is slow but still operational, and the request is for a new asset, not restoration of service. Option D is wrong because a problem is the root cause of one or more incidents, and this request does not involve investigating why the laptop is slow; it is a straightforward request for a replacement.
A company's IT service desk receives multiple calls that users cannot access the CRM system. What should the service desk do FIRST according to ITIL 4?
Logging an incident and working to restore service is the correct initial action. An incident is defined as an unplanned interruption to a service or a reduction in the quality of a service, which perfectly describes multiple user calls about an issue. Incident management's primary objective is to restore normal service operation as quickly as possible, minimizing business impact, making it the most appropriate immediate response.
Why this answer
According to ITIL 4, the primary goal of the service desk is to restore normal service operation as quickly as possible when an incident occurs. Multiple users losing access to the CRM system is a clear incident (an unplanned interruption or reduction in quality of an IT service), so the first action is to log the incident and work to restore service, typically by applying a known workaround or fix. This aligns with the 'incident management' practice, which prioritizes speed of restoration over root cause analysis or permanent changes.
Exam trap
The trap here is that candidates confuse incident management with problem management, thinking that finding the root cause (Option C) should come first, but ITIL 4 mandates restoring service before investigating causes.
How to eliminate wrong answers
Option A is wrong because raising a service request to grant user access assumes the issue is a simple access request, but the scenario describes a systemic failure affecting multiple users, which is an incident, not a pre-approved standard change. Option B is wrong because submitting a change request to modify the CRM system is a premature action; change management requires a RFC (Request for Change) after the incident is resolved, and the first priority is restoration, not modification. Option C is wrong because initiating a problem investigation to find the root cause is part of problem management, which occurs after the incident is resolved or if the incident recurs; ITIL 4 explicitly states that incident management focuses on restoring service first, not investigating root causes.
Which TWO of the following are examples of costs that a service consumer may transfer to a service provider?
This option is correct because a service provider frequently procures, owns, and maintains the necessary hardware infrastructure (e.g., servers, storage, networking equipment, or even end-user devices) required to deliver an IT service. These capital expenditures are then bundled into the service charges, effectively transferring the hardware acquisition and lifecycle management costs from the consumer to the provider. This approach allows the consumer to avoid large upfront investments and focus on outcomes.
Why this answer
Hardware procurement costs are a direct expense that a service consumer can transfer to a service provider through a service agreement, where the provider procures and manages the hardware as part of the service. Option D is correct because software licensing costs included in the service represent a cost that the consumer avoids paying directly, as the provider bundles the license into the service fee. This aligns with ITIL 4's concept of cost transparency, where the consumer shifts capital expenditure (CAPEX) to operational expenditure (OPEX) via the provider.
Exam trap
The trap here is that candidates often confuse 'cost transfer' with 'cost reduction' or 'outsourcing of all costs,' mistakenly selecting employee salaries (Option E) as transferable, when ITIL 4 specifically distinguishes between transferred costs (direct service components) and retained costs (consumer's own operational expenses).
An organization is considering adopting a cloud-based CRM system to replace its on-premise solution. According to ITIL 4, which of the following is a risk that is transferred from the consumer to the service provider?
This option is correct because in a cloud-based CRM (Software as a Service model), the cloud provider is entirely responsible for managing and maintaining the underlying physical infrastructure, including servers, storage arrays, and networking equipment within their data centers. Consequently, the risk associated with hardware component failures, and the subsequent impact on service availability, is transferred from the consuming organization to the cloud service provider. The provider implements redundancy and fault tolerance to mitigate this risk.
Why this answer
When using a cloud service, the provider typically takes on risks like hardware failures, so the consumer no longer bears that risk.
A hospital IT department implements a new patient record system that requires doctors to double-enter data. Although the system works correctly, doctors complain it increases their workload. According to ITIL 4, this is an example of:
This option is correct. An output is a tangible or intangible deliverable of an activity, such as the new patient record system itself. A positive outcome, conversely, represents the achievement of a desired result or benefit for a stakeholder. The system has been delivered (output), but it is not successfully enabling the hospital staff or patients to achieve their objectives or realize value, indicating a lack of beneficial results.
Why this answer
The new patient record system produces an output (the record is created and stored correctly), but doctors must double-enter data, which increases their workload and reduces efficiency. In ITIL 4, a positive outcome requires that the service not only meets functional requirements (utility) but also supports the user's goals without negative side effects. Here, the system fails to deliver a positive outcome because it degrades the user experience and adds unnecessary effort, even though the output is technically correct.
Exam trap
The trap here is that candidates confuse a technically working system (output) with a valuable service (outcome), assuming that if the system functions correctly, the service must be successful, ignoring the negative impact on the user's experience and workload.
How to eliminate wrong answers
Option A is wrong because utility refers to the functionality that the service provides (the system works correctly), but a positive outcome requires both utility and warranty, plus the service must enable users to achieve their goals without adverse effects; increased workload negates a positive outcome. Option C is wrong because warranty covers availability, capacity, continuity, and security—there is no failure in these areas; the system is available and secure, so warranty is not the issue. Option D is wrong because a successful service relationship requires that both the service provider and consumer perceive value; here, the doctors (consumers) are dissatisfied due to the extra workload, so the relationship is not successful.
Which ITIL 4 concept describes the functionality of a service, ensuring it meets the consumer's needs and has the required attributes?
Utility defines what a service does — its functionality — and confirms it meets the consumer's needs with the required attributes, such as performance or capacity. This directly satisfies the stem's demand for the concept describing functionality, distinguishing it from warranty, which covers fitness for use.
Why this answer
Utility is the ITIL 4 concept that describes the functionality offered by a service, specifically ensuring it meets the consumer's needs by providing the required attributes (e.g., performance, features). It answers the question 'What does the service do?' and is one of the two key components of service value, alongside warranty. In ITIL 4, utility is defined as the 'functionality offered by a product or service to meet a particular need,' directly aligning with the question's focus on functionality and required attributes.
Exam trap
The trap here is confusing utility with warranty, as candidates often think 'meeting needs' includes reliability or security, but ITIL 4 strictly separates functionality (utility) from assurance (warranty).
How to eliminate wrong answers
Option A is wrong because warranty describes the assurance that a service will meet agreed-upon requirements (e.g., availability, capacity, continuity, security), not its functionality or attributes. Option B is wrong because output refers to the tangible or intangible deliverables of an activity (e.g., a report or a processed transaction), not the overall service functionality that meets consumer needs. Option C is wrong because outcome is the result of using a service (e.g., increased productivity or reduced risk), not the service's inherent functionality or attributes.
Which ITIL 4 concept describes the assurance that a service meets its agreed availability and capacity requirements?
Warranty, in ITIL 4, refers to the assurance that a service will meet agreed requirements regarding its performance. It specifically addresses how the service performs, covering aspects such as availability, capacity, continuity, and security. Essentially, warranty confirms that the service is "fit for use," ensuring that it can be used reliably and consistently to deliver the desired outcomes without undue interruption or degradation. This concept directly describes the assurance provided by a service.
Why this answer
Warranty is the ITIL 4 concept that focuses on the 'assurance' that a service will meet its agreed-upon availability, capacity, continuity, and security requirements. It represents the operational guarantees that make the service fit for use, directly addressing the question's focus on availability and capacity commitments.
Exam trap
The trap here is that candidates confuse Utility (what the service does) with Warranty (how well it performs), leading them to pick Utility when the question explicitly asks about assurance of availability and capacity requirements.
How to eliminate wrong answers
Option A is wrong because Risk refers to a possible event that could cause harm or loss, not the assurance of meeting availability and capacity requirements. Option C is wrong because Utility describes the functionality of a service—'what it does'—not the assurance of its performance levels. Option D is wrong because Outcome is a result enabled by the service, not the guarantee of service performance metrics like availability or capacity.
A bank is using a cloud-based accounting software. The software provider ensures 99.9% uptime and data encryption. Which ITIL 4 concept is represented by the uptime guarantee?
Warranty refers to the assurance that a product or service will meet agreed requirements, specifically concerning its fitness for use. This includes aspects such as availability, capacity, security, and continuity, ensuring the service performs reliably under specified conditions. Therefore, a guarantee regarding the availability of cloud-based accounting software directly falls under the definition of warranty, as it addresses how the service performs and its reliability.
Why this answer
In ITIL 4, warranty refers to the assurance that a service will meet its agreed requirements — including availability, capacity, security, and continuity. A 99.9% uptime guarantee is a warranty commitment, as it defines the level of assurance the provider offers. Utility, by contrast, is about the functionality the service provides (what it does), while warranty is about how well it performs.
Exam trap
ITIL4F often tests the utility vs. warranty distinction — candidates see 'uptime guarantee' and pick utility because it sounds like a service feature, forgetting that warranty covers assurance of availability, capacity, security, and continuity.
How to eliminate wrong answers
Option A is wrong because a service relationship is the overall interaction between provider and consumer, including service provision, consumption, and relationship management — not the specific uptime guarantee. Option C is wrong because utility describes the functionality offered by a service (fit for purpose), such as the accounting features, not the uptime assurance. Option D is wrong because an outcome is the result enabled by the service for the consumer (e.g., accurate financial reporting), not the availability guarantee itself.
A software company is using ITIL 4 to improve its incident management process. Currently, incidents are resolved but often require significant rework, leading to delays. Which practice should the company focus on to address this issue?
Problem Management is specifically designed to reduce the likelihood and impact of incidents by identifying, analyzing, and resolving the root causes of actual and potential incidents. It proactively prevents recurrence and minimizes the impact of unavoidable incidents through structured analysis, known error identification, and the implementation of permanent solutions. This practice is crucial for improving service stability and reducing future operational overhead.
Why this answer
Problem Management (D) is the correct practice because the issue of recurring rework and delays indicates underlying root causes that are not being addressed. Problem Management focuses on identifying and eliminating the root causes of incidents, which reduces the need for rework and prevents future incidents, directly improving efficiency.
Exam trap
The trap here is that candidates often confuse Incident Management (restoring service quickly) with Problem Management (preventing recurrence), and choose Incident Management because it seems directly related to resolving incidents, missing that the question specifically asks about reducing rework and delays caused by recurring issues.
How to eliminate wrong answers
Option A is wrong because Change Enablement manages the lifecycle of changes to IT services, not the root cause analysis of recurring incidents; it would not address why rework is needed. Option B is wrong because Incident Management focuses on restoring normal service operation as quickly as possible, but it does not prevent the underlying causes that lead to rework and delays. Option C is wrong because the Service Desk provides a single point of contact for users and handles incident logging and initial support, but it does not perform root cause analysis or eliminate the need for rework.
An IT team is designing a new service. They ensure that the service is available during agreed hours and performs within agreed capacity levels. Which aspect of value are they addressing?
Warranty describes how the service performs, specifically its fitness for use, by assuring that the service meets agreed-upon requirements. When designing a new service, an IT team ensures the warranty by guaranteeing specific levels of availability, capacity, continuity, and security. This assurance provides confidence to the service consumer that the service will consistently meet its defined performance criteria and be available when needed, making it reliable for its intended use.
Why this answer
Warranty in ITIL 4 refers to the assurance that a service will meet agreed-upon conditions, such as availability, capacity, continuity, and security. By ensuring the service is available during agreed hours and performs within agreed capacity levels, the team is directly addressing the warranty aspect of value, which provides confidence in the service's operational reliability.
Exam trap
The trap here is that candidates often confuse utility (what the service does) with warranty (how well it performs), mistakenly thinking that ensuring availability and capacity is part of the service's functionality rather than its operational guarantees.
How to eliminate wrong answers
Option A is wrong because cost in ITIL 4 refers to the financial resources expended on a service, not the operational guarantees of availability or capacity. Option B is wrong because risk involves the potential for negative outcomes or uncertainties, whereas the question describes specific, agreed-upon performance assurances that mitigate risk but are not risk itself. Option C is wrong because utility is the functionality or 'fit for purpose' of a service (what it does), not the 'fit for use' guarantees of availability and capacity that warranty covers.
Which TWO of the following are components of value according to ITIL 4?
In ITIL 4, value is co-created and defined by the perception of stakeholders. Outcomes represent the results achieved by a service consumer that enable them to meet their objectives, often facilitated by a service. These desired results directly contribute to the realization of value, as they address the underlying needs and goals of the consumer, making them a fundamental component of value itself.
Why this answer
In ITIL 4, value is defined as the perceived benefits, usefulness, and importance of something. It is explicitly composed of two components: outcomes (the results achieved for stakeholders) and benefits (the positive gains realized from services). Option A is correct because outcomes are the measurable results that directly contribute to value, such as increased customer satisfaction or reduced downtime.
Exam trap
The trap here is that candidates often confuse 'outputs' with 'outcomes' or mistakenly include 'costs' and 'risks' as components of value, when ITIL 4 explicitly limits the definition to outcomes and benefits only.
A company uses an external provider for email services. Which of the following costs is typically removed from the consumer (company) and borne by the provider?
By engaging an external provider for email services, the company effectively transfers the operational burden and capital expenditure associated with the underlying infrastructure. The external provider assumes full responsibility for acquiring, housing, powering, cooling, patching, and maintaining the physical and virtual servers, storage, and network components necessary to deliver the email service. This transfer of infrastructure ownership and management is a primary driver for outsourcing such services.
Why this answer
When a company uses an external provider for email services (SaaS model), the provider is responsible for the underlying infrastructure. The cost of purchasing and maintaining email servers is a capital and operational expense that shifts from the consumer to the provider, as the provider owns and manages the hardware, storage, and server software (e.g., Microsoft Exchange Online or Google Workspace). This aligns with the ITIL 4 concept of utility and warranty, where the provider ensures availability and capacity without the consumer incurring direct hardware costs.
Exam trap
The trap here is that candidates confuse 'costs removed from the consumer' with 'costs that are reduced or shared,' leading them to select options like user support or training, which remain consumer-side responsibilities even in a fully outsourced email service.
How to eliminate wrong answers
Option A is wrong because training employees on how to use email remains a consumer responsibility; the provider delivers the service but does not train end users on client applications (e.g., Outlook or Gmail interface). Option C is wrong because user support for password resets is typically a shared or consumer-side activity, often handled by the consumer's IT service desk or identity management system (e.g., Azure AD self-service password reset), not the email provider. Option D is wrong because internet connectivity is a separate utility cost borne by the consumer to access the provider's service; the provider does not cover the consumer's ISP or network access fees.
Which ITIL 4 concept describes the perceived benefits, usefulness, and importance of a service to stakeholders?
Value, within the ITIL 4 framework, is defined as the perceived benefits, usefulness, and importance of something. It is a subjective concept, co-created through the interaction between service providers and consumers, encompassing both tangible and intangible benefits. Value represents the overall worth or significance that stakeholders attribute to a product, service, or other output, directly addressing the question's focus on "perceived benefits and usefulness."
Why this answer
Value is the core concept in ITIL 4 that defines the perceived benefits, usefulness, and importance of a service to stakeholders. It is co-created through the use of the service and is central to the Service Value System (SVS), where all activities are directed toward delivering value. Utility (fit for purpose) and Warranty (fit for use) are components that contribute to value, but they do not themselves describe the perceived benefits or importance.
Exam trap
The trap here is that candidates often confuse Utility or Warranty with Value, because ITIL 4 defines Utility and Warranty as components that contribute to value, but the question specifically asks for the concept that describes the perceived benefits, usefulness, and importance—which is Value itself.
How to eliminate wrong answers
Option A is wrong because Utility refers specifically to the functionality offered by a service to meet a user's need (fit for purpose), not the perceived benefits or importance to stakeholders. Option C is wrong because an Outcome is a result for a stakeholder enabled by one or more outputs, not the perception of benefits, usefulness, or importance. Option D is wrong because Warranty describes the assurance that a service will meet agreed requirements (fit for use), such as availability, capacity, security, and continuity, not the perceived value.
Which ITIL 4 concept describes the functionality of a service offered to meet a specific need?
Utility describes the functionality offered by a service to meet a particular need, determining whether the service is 'fit for purpose'. It addresses what the service does and whether it supports the performance of a task or the achievement of an objective. This concept directly defines the specific features, functions, and performance characteristics that enable the user to achieve their desired results, making it the direct answer for describing the functionality of a service.
Why this answer
Utility is the ITIL 4 concept that defines the functionality of a service—what the service does to meet a specific customer need. It addresses the 'fit for purpose' aspect, ensuring the service delivers the required features or capabilities to achieve a desired outcome.
Exam trap
Candidates often confuse utility and warranty. Utility addresses 'fit for purpose' (functionality to meet a need), while warranty addresses 'fit for use' (reliability, availability, etc.). The question explicitly asks about functionality, so utility is correct.
How to eliminate wrong answers
Option A is wrong because warranty describes the assurance that a service will meet agreed-upon performance levels (availability, capacity, continuity, security), not its functionality. Option B is wrong because outcome refers to the result or benefit realized by the customer from using the service, not the service's inherent functionality. Option C is wrong because output is a tangible or intangible deliverable produced by a service activity (e.g., a report or processed transaction), not the overall functionality that meets a specific need.
A large hospital has signed a contract with an external IT provider for a new electronic health records (EHR) system. The hospital's clinical staff will use the system daily, the hospital's IT department will manage user access, and the provider will host and maintain the underlying infrastructure. The hospital's CIO is accountable for ensuring the EHR service delivers the required clinical outcomes. Which TWO of the following statements correctly describe the service relationships in this scenario according to ITIL 4? (Choose two.)
In ITIL 4, a user is a role that uses services. Clinical staff interact directly with the EHR system to perform their daily duties, so they fit the definition of users. They are not necessarily the customer who agrees the service level, nor the sponsor who authorizes the budget, but their hands-on interaction makes them users.
Why this answer
Clinical staff use the EHR system daily, making them users. The CIO authorizes budget and is accountable for outcomes, fulfilling the sponsor role. These two roles are distinct from the provider, who hosts and maintains the service.
The hospital's IT department manages access but does not define requirements or authorize budget, so it is not the customer or sponsor here.
Exam trap
The trap here is assuming that any organization touching the service is automatically the provider or customer, when ITIL 4 roles depend on the specific relationship and accountability, not just activity.
An IT service desk analyst receives a call that users cannot access the CRM system. What should they do FIRST?
Logging an incident is the correct action because an incident is defined as an unplanned interruption to a service or a reduction in the quality of a service. The primary objective of incident management is to restore normal service operation as quickly as possible, minimizing business impact. Users being unable to access a service directly represents such an unplanned disruption requiring immediate attention to restore functionality.
Why this answer
In ITIL 4, when users cannot access a service, the first step is to log an incident record to capture the details and initiate the incident management process. The goal of incident management is to restore normal service operation as quickly as possible, so logging the incident is the immediate action before any problem, change, or service request activities.
Exam trap
ITIL4F often tests the distinction between incident, problem, change, and service request — candidates must recognize that a service outage is an incident and the first action is to log it.
How to eliminate wrong answers
Option A is wrong because a problem record is raised for root cause analysis of recurring or significant incidents, not as the first response to a single service disruption. Option C is wrong because a change request is used to implement a modification to the IT infrastructure, which comes after diagnosis and is not the first step. Option D is wrong because a service request is for standard user requests (e.g., access, information), not for reporting a service outage.
During a service review, a customer states that the service 'works well' but they are not achieving the expected business benefits. According to ITIL 4, this indicates a shortfall in which aspect of the service?
Utility concerns the functionality offered by a service and whether it enables the customer's required outcomes — "fit for purpose". The customer confirms the service performs ("works well") yet business benefits are absent, so the shortfall lies in utility's outcome contribution, not warranty's assurance of availability, capacity, security or continuity.
Why this answer
Utility in ITIL 4 refers to the functionality offered by a service to meet a specific need—the 'what it does' that enables desired business outcomes. When the customer says the service 'works well' but fails to deliver expected business benefits, the shortfall is in utility, because the service's features or capabilities are not aligned with or sufficient to achieve the intended outcomes. This is distinct from warranty, which covers availability, capacity, continuity, and security—the 'how it is delivered'.
Exam trap
The trap here is that candidates confuse 'works well' (which implies good warranty) with overall service success, and incorrectly assume the problem must be warranty-related, when ITIL 4 explicitly separates utility (fitness for purpose) from warranty (fitness for use).
How to eliminate wrong answers
Option B (Warranty) is wrong because warranty ensures the service is available, reliable, and secure when needed; the customer already stated the service 'works well', so warranty is not the issue. Option C (Risk) is wrong because risk is an inherent uncertainty that could affect outcomes, but the question explicitly describes a gap in achieving expected benefits, not a risk event or mitigation failure. Option D (Cost) is wrong because cost relates to the financial resources consumed by the service; the customer's complaint is about missing business benefits, not about the service being too expensive or over budget.
Which ITIL 4 term describes the functionality offered by a product or service to meet a particular need?
Utility directly describes the functionality offered by a service, defining what the service *does* and whether it is 'fit for purpose.' It addresses the specific requirements of the consumer, enabling them to perform tasks or achieve desired objectives. This term precisely captures the inherent capabilities and features that allow a service to support a consumer's performance or remove constraints.
Why this answer
Utility is the ITIL 4 term that defines the functionality offered by a product or service to meet a particular need. It directly addresses what the service does for the user—its core capability to solve a problem or enable an outcome. In ITIL 4, utility is often described as 'fit for purpose,' distinguishing it from warranty, which covers 'fit for use.'
Exam trap
The trap here is confusing 'utility' with 'outcome'—candidates often think the functionality directly produces the outcome, but utility is the enabler, while the outcome is the actual result experienced by the user.
How to eliminate wrong answers
Option A is wrong because an outcome is the result achieved by a stakeholder through the use of a service, not the functionality itself. Option C is wrong because an output is a tangible or intangible deliverable produced by an activity (e.g., a report or a processed transaction), not the service's capability to meet a need. Option D is wrong because warranty describes the assurance that a service will meet agreed requirements (availability, capacity, continuity, security), not the functionality it provides.
What is the definition of 'utility' in ITIL 4?
In ITIL 4, utility is precisely defined as the functionality provided by a service to address a particular requirement or achieve a specific outcome for the consumer. It describes whether a service is "fit for purpose," meaning it possesses the necessary features and performance capabilities to support the consumer's objectives. This concept focuses on the tangible value derived from the service's core functions, enabling the consumer to perform tasks or achieve goals effectively.
Why this answer
In ITIL 4, 'utility' is defined as the functionality offered by a service to meet a specific need. It represents the 'what' of the service—the features and capabilities that enable the service to deliver the desired outcome, such as processing a transaction or providing access to data. This is distinct from 'warranty,' which covers how the service is delivered reliably.
Exam trap
The trap here is that candidates often confuse 'utility' with 'warranty' or 'value,' especially when options mention risk removal or assurance, which are related but distinct concepts in ITIL 4's service definition.
How to eliminate wrong answers
Option B is wrong because cost incurred by the service consumer is not part of utility; it relates to the service's value proposition and is considered separately in cost-benefit analysis. Option C is wrong because risks removed from the consumer are a potential benefit of using the service, but utility specifically refers to the functionality that enables risk reduction, not the risk removal itself. Option D is wrong because assurance that a service will perform as agreed is the definition of 'warranty' in ITIL 4, not utility.
A user submits a request to reset their password. The service desk handles this by following a pre-approved standard procedure. According to ITIL 4, this is classified as:
A service request is a formal request from a user for something that is a normal part of service delivery, typically pre-defined and pre-approved. A password reset is a classic example, as it is a common, routine action with a known procedure and expected outcome, often fulfilled through self-service or standard operating procedures. It falls squarely under the scope of standard service offerings.
Why this answer
A password reset is a standard, pre-approved request for a service action that does not involve a change to the service's risk profile or a deviation from normal operations. ITIL 4 defines a service request as a formal request from a user for something to be provided – for example, information, advice, or a standard change. Since the service desk follows a pre-approved procedure without requiring additional authorization, this fits the service request category exactly.
Exam trap
The trap here is that candidates confuse a 'standard change' with a 'service request' because both are pre-approved, but ITIL 4 reserves 'standard change' for modifications to services or infrastructure, while 'service request' is for user-initiated requests for information, advice, or access.
How to eliminate wrong answers
Option B is wrong because a change request involves a modification to a service or configuration item that requires assessment and authorization (e.g., via a change advisory board), whereas a password reset is a pre-approved standard activity with no risk of service disruption. Option C is wrong because an incident is an unplanned interruption or reduction in quality of an IT service, but a password reset is a planned, routine request that does not indicate a service failure. Option D is wrong because a problem is the underlying cause of one or more incidents, not a user-initiated request for a standard action like a password reset.
Which THREE of the following are elements of value co-creation according to ITIL 4?
Value co-creation requires the consumer to actively participate in the service relationship rather than passively receive output. This satisfies the stem's focus on co-creation elements, since value emerges through interaction between provider and consumer, not from the provider alone.
Why this answer
According to ITIL 4, value co-creation requires active collaboration between provider and consumer rather than one-way delivery. Option A is correct because the consumer must actively participate in the service relationship, contributing inputs, feedback, and engagement that shape the service. Option B is correct because value is co-created when the provider and consumer work together, combining their respective resources and capabilities.
Option D is correct because the consumer applies the provider's resources (such as people, information, and technology) to achieve its own desired outcomes, which is the essence of value realization. Option C is incorrect because delivering outputs without consumer involvement contradicts the co-creation principle, which demands participation. Option E is incorrect because value is not simply delivered by the provider to the consumer; it emerges through joint interaction and the consumer's use of the service.
Exam trap
The trap here is that candidates often confuse 'value delivery' (a one-way provider-to-consumer model) with 'value co-creation' (a bidirectional partnership), leading them to select option E as correct when it is actually a misconception from older service management paradigms.
What is the PRIMARY purpose of the ITIL 4 concept 'service management'?
ITIL 4 defines service management as a set of specialized organizational capabilities for enabling value for customers in the form of services. The primary purpose is to facilitate value co-creation, where organizations collaborate with consumers to realize desired outcomes. This involves understanding stakeholder needs and designing, delivering, and improving services that provide utility and warranty, ultimately contributing to mutual value.
Why this answer
The primary purpose of 'service management' in ITIL 4 is to enable value co-creation through services. This is achieved by organizing and managing resources, activities, and processes to deliver outcomes that customers value, while balancing the provider's constraints. ITIL 4 defines service management as a set of specialized organizational capabilities for providing value to customers in the form of services, directly linking it to the Service Value System (SVS) and the guiding principles.
Exam trap
The trap here is that candidates confuse the operational goal of 'managing IT' (Option D) with the strategic purpose of service management, which is explicitly defined in ITIL 4 as enabling value co-creation through services, not just running technology.
How to eliminate wrong answers
Option B is wrong because ensuring compliance with regulations is a specific governance or risk management activity, not the overarching purpose of service management; ITIL 4 treats compliance as one outcome within the broader goal of value co-creation. Option C is wrong because reducing costs of IT operations is a potential benefit or objective of service management, but not its primary purpose; focusing solely on cost reduction ignores value delivery and customer outcomes. Option D is wrong because managing IT infrastructure and applications is a tactical or operational activity (part of service management practices like Service Desk or Technical Management), not the primary purpose; ITIL 4 emphasizes that infrastructure management serves to enable services that co-create value.
An IT service provider is designing a new service. They want to ensure that the service will deliver value to customers by achieving desired outcomes without requiring them to manage specific costs and risks. Which key concept of ITIL 4 does this best describe?
A service is defined in ITIL 4 as a means of enabling value co-creation by facilitating outcomes customers want, without them managing specific costs and risks. This matches the stem's description precisely, making it the correct concept.
Why this answer
The scenario describes a service designed to deliver desired outcomes while shielding customers from managing specific costs and risks. This directly aligns with the ITIL 4 definition of a service, which is a means of enabling value co-creation by facilitating outcomes customers want to achieve, without the customer having to manage the associated costs and risks. Options like utility, outcome, or warranty are components of value but do not capture the full concept of a service as a delivery mechanism that abstracts away cost and risk management.
Exam trap
The trap here is that candidates often confuse 'utility' (the functionality) with the full service definition, forgetting that a service must also include the abstraction of costs and risks, which is a key differentiator in ITIL 4.
How to eliminate wrong answers
Option B (Utility) is wrong because utility refers to the functionality offered by a product or service to meet a specific need, not the abstraction of costs and risks. Option C (Outcome) is wrong because an outcome is a result for a stakeholder enabled by one or more outputs, not the mechanism that delivers value while managing costs and risks. Option D (Warranty) is wrong because warranty focuses on the assurance that a product or service will meet agreed requirements (availability, capacity, continuity, security), not on achieving desired outcomes without customer cost/risk management.
What is the definition of 'warranty' in ITIL 4?
Warranty, in ITIL 4, precisely defines the assurance that a service will consistently meet its agreed-upon specifications and requirements, thereby confirming its 'fitness for use.' This critical aspect ensures the service performs reliably without undue interruption or degradation, providing confidence to the consumer. Specifically, warranty addresses key performance indicators related to availability, capacity, continuity, and security, guaranteeing the service's operational integrity.
Why this answer
In ITIL 4, 'warranty' is defined as the assurance that a service will meet its agreed-upon performance requirements, covering aspects like availability, capacity, continuity, and security. Option C correctly captures this by stating 'the assurance that a service will perform as agreed,' which aligns with the ITIL 4 definition that warranty focuses on the service's reliability and fitness for use under defined conditions.
Exam trap
The trap here is that candidates often confuse 'warranty' with 'utility,' mistakenly selecting Option D because they think warranty is about what the service does (functionality), rather than the assurance of how it will perform under agreed conditions.
How to eliminate wrong answers
Option A is wrong because it describes 'utility,' which is the value created by the service through functionality that meets a specific need, not warranty. Option B is wrong because it refers to 'cost' or 'price,' which is a separate financial consideration and not part of the warranty definition in ITIL 4. Option D is wrong because it defines 'utility' again—the functionality offered by a service to meet a specific need—whereas warranty is about the assurance of performance, not the features themselves.
An IT service provider guarantees 99.9% availability for a critical application. This guarantee is an example of which ITIL 4 concept?
Warranty is the assurance that a service meets agreed requirements, covering availability, capacity, continuity and security. The 99.9% availability guarantee is precisely this assurance, distinguishing it from utility, which describes the functionality the service provides to support the consumer's outcomes.
Why this answer
A 99.9% availability guarantee defines the service's fitness for use in terms of reliability and performance, which aligns directly with the ITIL 4 concept of 'Warranty'. Warranty ensures that the service will meet agreed-upon conditions such as availability, capacity, continuity, and security, making it the correct choice for this scenario.
Exam trap
The trap here is that candidates confuse 'Warranty' (fitness for use, including availability guarantees) with 'Utility' (fitness for purpose, or what the service does), leading them to incorrectly select Utility when the question explicitly states a performance guarantee.
How to eliminate wrong answers
Option B is wrong because Utility refers to the functionality of the service—'what the service does'—such as processing transactions or storing data, not the guaranteed uptime percentage. Option C is wrong because Risk is a potential event that could cause harm or loss, not a guarantee of service performance; the 99.9% availability is a warranty condition, not a risk assessment. Option D is wrong because Output is a tangible or intangible deliverable produced by a process (e.g., a report or a code module), not a measure of service reliability or availability.
Which THREE are roles in the service relationship according to ITIL 4?
The Customer is a key consumer role in the service relationship, representing the organizational entity or individual that defines service requirements and is accountable for the service's value realization. They authorize the service and are typically responsible for its financial aspects, ensuring it aligns with broader organizational objectives and strategic needs. This role focuses on the overall agreement and outcome.
Why this answer
In ITIL 4, the service relationship model defines three core roles: the customer, the sponsor, and the user. The customer is the role that defines the requirements for a service and takes responsibility for the outcomes of service consumption. This role is essential for establishing the service relationship and ensuring that the service meets agreed needs.
Exam trap
The trap here is that candidates often confuse 'supplier' or 'manager' with the official ITIL 4 roles, because in real-world organizations these titles are common, but ITIL 4 specifically limits the service relationship roles to customer, sponsor, and user.
Which TWO of the following are correct statements about value co-creation according to ITIL 4?
This statement is correct. Service providers contribute a variety of resources and capabilities, such as technological infrastructure, specialized knowledge, skilled personnel, and intellectual property, to enable the service consumer to achieve their desired outcomes. These contributions form the essential foundation of the service offering, allowing consumers to leverage these assets effectively.
Why this answer
Option D is correct because in ITIL 4 value co-creation, the service provider brings its own resources—such as infrastructure, tools, technology, and expertise—into the service relationship, and these provider resources are essential inputs to the creation of value. Option E is correct because the consumer is not a passive recipient; the consumer also contributes resources such as information, time, effort, and other assets, and value emerges only through the interaction and integration of both parties' resources. Together, D and E reflect the ITIL 4 principle that value is co-created through the combined contributions of provider and consumer rather than produced unilaterally.
Option A is incorrect because it describes the outdated, one-directional view of value creation, whereas ITIL 4 explicitly rejects the idea that the provider alone creates and delivers value. Option B is incorrect because value in ITIL 4 is not limited to money; it can include outcomes such as improved performance, reduced risk, compliance, and user experience. Option C is incorrect because value co-creation can occur in many forms of service relationship, not only formal contracts, and ITIL 4 does not restrict co-creation to contractual arrangements.
Exam trap
ITIL4F often tests the misconception that value is created solely by the provider, tricking candidates into selecting options that ignore the consumer's role in value co-creation.
A service consumer transfers costs and risks to the provider by using a service. Which of the following is an example of a risk that is removed from the consumer?
This option perfectly illustrates a risk transferred from the consumer to the provider. When a consumer utilizes a service, they rely on the provider's infrastructure and operational capabilities. The risk associated with the provider's own hardware failing and subsequently causing a service outage is entirely borne by the provider, who is responsible for maintaining availability and resolving such incidents according to agreed service levels. The consumer pays for the service's outcome, not the direct management of infrastructure risks.
Why this answer
It describes a risk that is transferred from the consumer to the provider when using a service. The provider's hardware failure causing a service outage is a risk that the consumer no longer bears; instead, the provider is responsible for managing and mitigating this risk through redundancy, SLAs, and incident management processes. This aligns with the ITIL 4 concept of utility and warranty, where warranty ensures the service is available when needed, shifting operational risks to the provider.
Exam trap
The trap here is that candidates often confuse cost transfer (Option B) with risk transfer, or mistakenly think that all operational risks (like employee errors or data loss from internal processes) are automatically assumed by the provider, when in fact only risks explicitly covered by the service warranty and SLA are transferred.
How to eliminate wrong answers
Option A is wrong because employee errors in using the service remain the consumer's responsibility, as the consumer controls user training and access management; the provider does not assume this risk. Option B is wrong because the cost of purchasing and maintaining servers is a financial cost, not a risk; while costs are transferred, the question specifically asks for a risk, and this option confuses cost with risk. Option C is wrong because the risk of data loss due to the consumer's internal processes (e.g., poor backup practices or user mistakes) stays with the consumer, as the provider cannot control the consumer's internal operations or data handling procedures.
An organisation implements a new human resources (HR) system. The project team delivers the system on time and within budget. However, HR staff find the system difficult to use and employee satisfaction with HR services does not improve. According to ITIL 4, which statement describes this situation?
This option accurately reflects the scenario by distinguishing between output and outcome, a core ITIL 4 concept. The output, which is the successful delivery and implementation of the new HR system within specified project constraints (on time, on budget), was achieved. However, the desired outcome, specifically the improvement in employee satisfaction that the system was intended to facilitate, was not realized, highlighting a common challenge in value co-creation.
Why this answer
In ITIL 4, an output is a tangible deliverable (e.g., the HR system delivered on time and within budget), while an outcome is the result for stakeholders (e.g., improved employee satisfaction). The scenario shows the output was successful, but the outcome was not achieved because the system was difficult to use and satisfaction did not improve. Option C correctly identifies this mismatch.
Exam trap
The trap here is confusing 'output' (the system delivery) with 'outcome' (the business result), leading candidates to assume that on-time, on-budget delivery automatically means success, when ITIL 4 emphasizes that value is only realized through positive outcomes.
How to eliminate wrong answers
Option A is wrong because output and outcome are distinct concepts in ITIL 4; output is the deliverable (the system), outcome is the business result (satisfaction), and they are not the same here. Option B is wrong because it claims the outcome (employee satisfaction) was achieved, but the scenario explicitly states satisfaction did not improve, and it incorrectly states the output (delivery) failed, when in fact the system was delivered on time and within budget. Option D is wrong because it claims both output and outcome were achieved, but the outcome (improved satisfaction) was not achieved.
Which of the following BEST describes value co-creation in ITIL 4?
In ITIL 4, value co-creation is a fundamental principle emphasizing that value is not delivered by the provider in isolation but is actively shaped through collaborative interactions. Both the service provider and the consumer contribute resources, capabilities, and context throughout the service relationship. This mutual participation ensures that the service truly enables the consumer's desired outcomes, making value a shared achievement.
Why this answer
ITIL 4 defines value co-creation as a collaborative process where both the service provider and the consumer actively contribute resources and activities to achieve desired outcomes. This is a foundational shift from traditional delivery models, emphasizing that value is not simply handed over but emerges from the interaction and joint effort of both parties.
Exam trap
The trap here is that candidates often default to a traditional 'provider delivers value' mindset (Option B) because it mirrors older service management models, but ITIL 4 explicitly requires recognizing the consumer's active role in value creation.
How to eliminate wrong answers
Option B is wrong because it describes a one-way, product-centric view where the provider creates value in isolation and then delivers it to the consumer, which contradicts the ITIL 4 principle of value co-creation that requires active consumer participation. Option C is wrong because it incorrectly asserts that value is solely defined by the provider based on service features, whereas ITIL 4 states that value is perceived by the consumer and co-created through their needs, constraints, and involvement. Option D is wrong because it reduces value to a narrow financial metric (cost savings), ignoring the broader outcomes, experiences, and utility/warranty considerations that define value in ITIL 4's service value system.
A multinational corporation uses a SaaS-based project management tool. The tool's provider offers a standard set of features, but the corporation's project managers frequently request custom workflows and reports. The provider has a published product roadmap and does not customize the tool for individual customers. According to ITIL 4, which statement best describes the nature of the value proposition in this service relationship?
In ITIL 4, a service's value proposition is about enabling outcomes the consumer wants to achieve. The provider offers a standardized tool that can facilitate project management outcomes, but the consumer must integrate it into its own workflows and processes. Value is co-created through this integration, even without customization. The provider's roadmap and standard features form the basis, and the consumer realizes value by using the service effectively.
Why this answer
The provider offers a standardized SaaS tool, but value is co-created when the consumer integrates it into its workflows to achieve project management outcomes. The provider facilitates outcomes, but the consumer must use the service effectively. Customization is not required for value co-creation; the focus is on enabling outcomes through the service relationship.
Exam trap
The trap here is assuming that value co-creation requires the provider to customize the service for each consumer, when in fact co-creation happens through the consumer's use and integration of the service.
A software development team delivers a new feature to the marketing department. The feature is working but the marketing team reports no increase in campaign effectiveness. Which ITIL 4 distinction does this illustrate?
An output is a tangible deliverable produced by an activity, such as the new software feature itself. An outcome, conversely, is the result or effect achieved for a stakeholder, often enabled by the output, representing the actual value realized. The question describes the delivery of a feature and implies its subsequent impact, directly aligning with this distinction, making it the correct choice for differentiating the deliverable from its benefit.
Why this answer
ITIL 4 distinguishes between 'output' (a tangible deliverable, such as a working software feature) and 'outcome' (the actual business result, such as increased campaign effectiveness). In this scenario, the team delivered the output (the feature works), but the desired outcome (improved marketing performance) was not achieved, illustrating the critical gap between delivering a product and realizing business value.
Exam trap
The trap here is that candidates confuse 'output vs outcome' with 'utility vs warranty' because both involve service value, but utility focuses on functionality fit for purpose, not the business result gap illustrated in this scenario.
How to eliminate wrong answers
Option B is wrong because Incident vs Problem deals with unplanned interruptions (incidents) versus their root causes (problems), not with the difference between delivering a feature and achieving business value. Option C is wrong because Service Request vs Change focuses on pre-defined, low-risk requests (service requests) versus controlled modifications (changes), which does not apply to a delivered feature failing to produce a business result. Option D is wrong because Utility vs Warranty describes functionality (utility) and assurance/availability (warranty) of a service, not the distinction between a deliverable and its business impact.
Which THREE of the following are components of the ITIL 4 Service Value System (SVS)?
The Service Value Chain is one of the five core SVS components, converting inputs into outputs through six activities. It satisfies the stem's requirement by being an explicitly named element of the Service Value System, alongside guiding principles, governance, practices and continual improvement.
Why this answer
The ITIL 4 Service Value System (SVS) is composed of five core components: Guiding Principles, Governance, Service Value Chain, Practices, and Continual Improvement. Option A (Service Value Chain) is correct because it is the central operating model of the SVS, describing the six activities (Plan, Improve, Engage, Design and Transition, Obtain/Build, Deliver and Support) that convert inputs like demand and opportunity into value. Option C (Guiding Principles) is correct because the seven guiding principles (Focus on Value, Start Where You Are, Progress Iteratively with Feedback, Collaborate and Promote Visibility, Think and Work Holistically, Keep It Simple and Practical, Optimize and Automate) are a foundational SVS component that informs decision-making across the organization.
Option E (Practices) is correct because ITIL 4 defines 34 management practices (e.g., Incident Management, Continual Improvement, Change Enablement) that are a formal component of the SVS, providing the resources and capabilities needed to perform work. Option B (Service Portfolio) is not a component of the ITIL 4 SVS; it is a service management concept/tool used to manage services across their lifecycle, not one of the five SVS elements. Option D (ITIL Maturity Model) is also not an SVS component; it is a separate assessment tool used to evaluate an organization's ITIL adoption and capability maturity.
Exam trap
The trap here is that candidates often confuse the components of the SVS with elements of the ITIL framework like the Service Portfolio or Maturity Model, which are related but not part of the SVS structure.
A service provider offers a payroll service that calculates employee salaries and generates payslips. The service is delivered according to a schedule and meets all compliance requirements. Which statement BEST distinguishes utility from warranty in this context?
This option correctly distinguishes between utility and warranty for a payroll service. Utility represents the core functionality that enables the customer to achieve their objective, specifically the accurate calculation of salaries and the generation of payslips, which is the 'fitness for purpose.' Warranty assures that this essential functionality is delivered reliably, meeting agreed-upon performance criteria such as on-schedule delivery and adherence to legal and regulatory compliance standards, which are critical for payroll operations and represent the 'fitness for use.'
Why this answer
Ly distinguishes utility from warranty: utility is the functionality offered by the service (calculating salaries and generating payslips), while warranty is the assurance that the service will meet agreed conditions (delivery on schedule and compliance). In ITIL 4, utility is 'fit for purpose' (what the service does), and warranty is 'fit for use' (how it is delivered reliably).
Exam trap
The trap here is that candidates often confuse utility with warranty by swapping their definitions, especially when both involve time-based or compliance-related aspects, leading them to pick Option C or D.
How to eliminate wrong answers
Option A is wrong because utility is not about cost; cost is a separate consideration in service value, and warranty is not solely about availability but includes capacity, continuity, and security. Option C is wrong because it reverses the definitions: on-time delivery is a warranty aspect, not utility, and salary calculation is utility, not warranty. Option D is wrong because warranty is not focused on functionality; it focuses on the conditions under which functionality is delivered (e.g., performance, reliability).
A company is reviewing its service management practices and identifies that it lacks a consistent approach to handling known errors. Which practice should be improved to manage known errors effectively?
Problem management is the practice responsible for reducing the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors. A known error is a problem that has been analyzed and has a documented root cause and a workaround. Problem management systematically tracks these known errors, facilitating their resolution and preventing recurring incidents.
Why this answer
Known errors are documented in the Known Error Database (KEDB) and are a key output of problem management. Problem management is responsible for identifying the root cause of incidents and documenting workarounds or permanent fixes as known errors, making option D correct.
Exam trap
The trap here is that candidates confuse incident management with problem management, assuming that handling known errors is part of restoring service quickly, but ITIL 4 explicitly assigns known error management to problem management, not incident management.
How to eliminate wrong answers
Option A is wrong because service level management focuses on negotiating and monitoring service level agreements (SLAs), not on documenting or managing known errors. Option B is wrong because incident management handles restoring normal service operation after an incident, but it does not own the process of identifying root causes or maintaining known error records. Option C is wrong because configuration management maintains the configuration management database (CMDB) and tracks configuration items (CIs), but it does not manage the lifecycle of known errors or their workarounds.
What is the definition of 'value' in ITIL 4?
This option accurately reflects the ITIL 4 definition of value. Value is understood as the perceived benefits, usefulness, and importance of something from the perspective of a stakeholder. It is subjective and context-dependent, encompassing both tangible outcomes and intangible benefits that contribute to achieving an organization's objectives, making it a cornerstone of the ITIL 4 service value system.
Why this answer
ITIL 4 defines value as the perceived benefits, usefulness, and importance of something, which is a subjective assessment by stakeholders rather than an objective measure. This definition emphasizes that value is co-created through the use of services and depends on the outcomes and experiences of the service consumer, not just on technical outputs or financial metrics.
Exam trap
The trap here is that candidates often confuse value with tangible metrics like cost savings or outputs, but ITIL 4 deliberately defines value as a subjective perception of benefits and importance, not as an objective financial or production measure.
How to eliminate wrong answers
Option A is wrong because it reduces value to monetary worth, ignoring the subjective and co-created nature of value in ITIL 4, which includes non-financial aspects like user satisfaction and business outcomes. Option C is wrong because cost savings are only one potential benefit of a service, not the definition of value itself; value encompasses both benefits and costs in a holistic manner. Option D is wrong because outputs are the tangible deliverables of a service (e.g., a report), whereas value is about the outcomes and perceived importance that those outputs enable for the customer.
An IT team has redesigned a customer portal, delivering new features on time and within budget. However, customer satisfaction scores have dropped because users find the new interface confusing. Which statement best describes this situation?
Outputs are the deliverables produced; outcomes are the results stakeholders value. Delivering the portal on time and budget satisfies scope and cost, yet the drop in satisfaction shows the intended outcome — usable, clear customer service — was not achieved.
Why this answer
The IT team successfully delivered the redesigned customer portal (the output) on time and within budget, but the drop in customer satisfaction scores indicates that the intended outcome—improved user experience and satisfaction—was not achieved. In ITIL 4, an output is a tangible deliverable (like a new feature or a service), while an outcome is the result or value realized by the customer. Here, the output was delivered, but the outcome failed, making option D correct.
Exam trap
The trap here is that candidates often confuse 'output' with 'outcome' and assume that delivering a feature on time and within budget automatically implies a successful outcome, but ITIL 4 emphasizes that value is only realized when the output leads to the desired outcome.
How to eliminate wrong answers
Option A is wrong because the team did deliver an output (the redesigned portal), so it is not a case of achieving an outcome without an output. Option B is wrong because the planned outcome (improved customer satisfaction) was not achieved, so both output and outcome were not delivered as planned. Option C is wrong because the output (the portal) was delivered, but the outcome was negative, not positive; the statement 'positive outcome' is incorrect.
An IT service provider offers a payroll service with a guaranteed uptime of 99.9%. Which dimension of service value does this guarantee primarily address?
Warranty refers to the assurance that a product or service will meet agreed-upon requirements, specifically addressing aspects like availability, capacity, continuity, and security, ensuring it is "fit for use." An uptime guarantee directly specifies the expected availability of the payroll service, providing confidence to the customer that the service will consistently perform as required. This makes the uptime guarantee a fundamental component of the service's warranty.
Why this answer
The guarantee of 99.9% uptime directly addresses the 'Warranty' dimension of service value, which ensures the service is available, reliable, and secure when needed. In ITIL 4, Warranty focuses on the assurance that the service will meet agreed-upon availability levels, while Utility covers the functionality or 'fit for purpose' of the service. This uptime metric is a classic Warranty attribute, as it quantifies the service's availability guarantee.
Exam trap
A common confusion is between 'Utility' (what the service does) and 'Warranty' (how well it is delivered), leading candidates to incorrectly select Utility because they associate uptime with the service's core function rather than its assurance.
How to eliminate wrong answers
Option A is wrong because 'Outcome' refers to the business result enabled by the service (e.g., employees getting paid on time), not the technical guarantee of uptime. Option B is wrong because 'Utility' describes the service's functionality or 'fit for purpose' (e.g., calculating payroll taxes), not its availability assurance. Option C is wrong because 'Output' is a tangible deliverable (e.g., a pay slip or a transaction record), not the ongoing availability guarantee of the service.
Which ITIL 4 concept describes the assurance that a service will meet its agreed availability, capacity, and security requirements?
Warranty provides the assurance that a service will meet agreed requirements regarding its performance and conditions of use, ensuring it is "fit for use." This encompasses aspects such as availability, capacity, continuity, and security, guaranteeing that the service performs reliably and consistently according to specified service levels and non-functional requirements.
Why this answer
Warranty in ITIL 4 is the concept that directly addresses the assurance that a service will meet its agreed requirements, including availability, capacity, and security. While utility focuses on the functionality or 'what the service does,' warranty covers the 'how well' it performs, ensuring the service is fit for use under defined conditions.
Exam trap
The trap here is that candidates confuse utility (what the service does) with warranty (how well it does it), often picking utility because they think 'assurance' relates to the service's core function, but ITIL 4 specifically separates these concepts to distinguish between functionality and performance guarantees.
How to eliminate wrong answers
Option A is wrong because utility describes the functionality of a service—what it does to meet a user's need—not the assurance of performance levels like availability or security. Option C is wrong because risk is the potential for an event to cause harm or loss, not a guarantee that service requirements will be met; it is managed through controls, not an inherent assurance. Option D is wrong because value is the perceived benefit or worth of a service to stakeholders, which results from a combination of utility and warranty, not the assurance itself.
An organization develops a mobile app for customers to track deliveries. Customers can see real-time updates (utility) and the app is available 99.9% of the time (warranty). Which term describes the improved customer satisfaction from using the app?
Improved customer satisfaction is the direct outcome, representing the desired result or effect achieved by customers through their use of the mobile app. This is the ultimate value proposition, as the app's functionalities enable users to achieve their goals, leading to a positive experience. Outcomes are the actual benefits realized by stakeholders, enabled by the service's outputs.
Why this answer
An outcome is the result of using a service, specifically the improved customer satisfaction or business value derived from the app's functionality and reliability. In ITIL 4, utility (the app's real-time tracking) and warranty (99.9% availability) enable the outcome, but the outcome itself is the positive change in the customer's state—here, enhanced satisfaction from successfully tracking deliveries.
Exam trap
The trap here is confusing the service's functional attributes (utility) or assurance (warranty) with the resulting business outcome, leading candidates to pick 'Utility' or 'Warranty' instead of recognizing that satisfaction is an outcome derived from using the service.
How to eliminate wrong answers
Option A is wrong because an output is a tangible or intangible deliverable of a process, such as a software build or a report, not the customer's perceived benefit or satisfaction. Option B is wrong because warranty is a component of service value that assures availability, capacity, continuity, and security (e.g., 99.9% uptime), not the resulting customer satisfaction. Option D is wrong because utility is the functionality offered by the service (e.g., real-time delivery updates), which is a prerequisite for value but not the improved satisfaction itself.
An e-commerce company experiences a slowdown in its website during a flash sale. The slowdown is not a complete outage. According to ITIL 4, how should this be classified?
An incident is an unplanned interruption to a service or a reduction in the quality of a service. The e-commerce website slowdown directly fits this definition, as it represents a degradation in the expected performance and quality of the service provided to customers. The primary objective of incident management is to restore normal service operation as quickly as possible with minimal business impact.
Why this answer
In ITIL 4, an incident is defined as an unplanned interruption to a service or a reduction in the quality of a service. A website slowdown during a flash sale is a degradation of service quality, not a full outage, so it still qualifies as an incident. The focus of Incident Management is to restore normal service operation as quickly as possible, which applies here even though the service is only partially degraded.
Exam trap
ITIL4F often tests the distinction between incidents and problems, and candidates commonly pick 'problem' whenever a root cause might exist, forgetting that the incident is the service degradation itself and a problem is only raised for the underlying cause.
How to eliminate wrong answers
Option A is wrong because a problem is the underlying cause of one or more incidents, not the degraded service itself; the slowdown is the symptom, and a problem record would only be raised if root cause analysis is needed. Option B is wrong because a service request is a user-initiated request for something standard like information, access, or a minor change, not an unplanned degradation of service. Option D is wrong because a normal change is a planned modification to the environment; adding servers may be a later corrective action, but the slowdown itself is not a change request.
Which THREE of the following are types of service relationships in ITIL 4?
A service offering is a formal and detailed description of one or more services, designed to address the needs of a specific target consumer group. It encompasses the goods, access to resources, and service actions provided, clearly defining the value proposition and the terms under which the service is delivered and consumed, thereby structuring a core aspect of the service relationship.
Why this answer
Service Offering (B) is correct because in ITIL 4, a service offering describes one or more services designed to address the needs of a target consumer group, including goods, access to resources, and service actions. It is a core component of the service relationship model, which defines how value is co-created through service provision and service consumption.
Exam trap
The trap here is that candidates often confuse operational components like the Service Desk or external entities like Partners and Suppliers with the formal relationship types defined in the ITIL 4 service relationship model, which strictly include only service offering, service provision, and service consumption.
An organization has a service desk that handles both incident resolution and service requests. A user contacts the desk because they forgot their password and need a reset. According to ITIL 4, how should this be classified?
A password reset is correctly classified as a service request because it is a predefined, routine request from a user for access to a service. Service requests are typically low-risk, frequently occurring, and often have a known fulfillment procedure, sometimes even automated. This category includes requests for information, advice, standard changes, or access, perfectly aligning with the predictable nature of resetting a forgotten password.
Why this answer
A password reset is a pre-defined, standard request that follows an established procedure with low risk, making it a classic service request under ITIL 4. It is not an incident because the user is not reporting an unplanned interruption or reduction in quality of an IT service; they are simply requesting a routine action. ITIL 4 defines a service request as a formal request from a user for something to be provided – such as information, advice, or a standard change – which aligns perfectly with a password reset.
Exam trap
The trap here is confusing a user's inability to access a system with an incident, when ITIL 4 explicitly classifies standard, pre-approved user requests (like password resets) as service requests, not incidents.
How to eliminate wrong answers
Option A is wrong because a password reset is a standard, pre-approved change that falls under a service request, not a change request; change requests are typically for non-standard, risk-assessed modifications. Option B is wrong because a problem is the root cause of one or more incidents, not a single user request; there is no evidence of a recurring underlying issue with the password policy. Option C is wrong because an incident is an unplanned interruption or reduction in quality of a service, whereas a forgotten password is a planned, routine user action that does not represent a service failure.
Which ITIL 4 concept describes the functionality offered by a product or service to meet a particular need?
Utility refers to the functionality offered by a service, describing what the service *does* and whether it is "fit for purpose." It encompasses the specific features and capabilities that enable a consumer to perform tasks, achieve objectives, or remove constraints. This concept directly addresses the inherent ability of a service to meet a particular need through its provided functionality.
Why this answer
Utility is the ITIL 4 concept that defines the functionality offered by a product or service to meet a particular need. It answers the question 'What does the service do?' and is essential for creating value by enabling desired outcomes.
Exam trap
The trap here is confusing utility with warranty, as candidates often think 'meeting a need' includes reliability or security, but utility strictly refers to functionality, while warranty covers performance guarantees.
How to eliminate wrong answers
Option A is wrong because an outcome is the result of using a service, not the functionality itself; outcomes are enabled by utility but are distinct from it. Option C is wrong because an output is a tangible or intangible deliverable (e.g., a report or a processed transaction), not the functionality that meets a need. Option D is wrong because warranty describes the assurance that a service will meet agreed requirements (availability, capacity, continuity, security), not the functionality offered.
Which TWO of the following are correct about the relationship between outputs and outcomes?
Outputs are the tangible or intangible deliverables produced by an activity or service. Outcomes, conversely, are the results achieved for stakeholders, often involving a change in behavior or performance. Therefore, outputs serve as the direct means or enablers that facilitate the achievement of these desired outcomes, establishing a clear cause-and-effect relationship where the deliverable makes the result possible.
Why this answer
A is correct because outputs are the tangible or intangible deliverables produced by a service or process, and they enable the achievement of outcomes. For example, a software deployment (output) enables improved user productivity (outcome). Without outputs, desired outcomes cannot be realized, as outcomes depend on the effective use of outputs.
Exam trap
The trap here is confusing outputs with outcomes, leading candidates to select 'Outcomes are tangible deliverables' (B) or 'Outcomes are always measurable' (E), when in fact outcomes are results for stakeholders and may be intangible or hard to measure.
During a major incident, the IT team implements a temporary workaround to restore service. Later, a permanent fix is applied. Which ITIL 4 practice is primarily responsible for ensuring the permanent fix is identified and applied?
Problem Management is the practice responsible for reducing the likelihood and impact of incidents by identifying actual and potential causes of incidents and managing workarounds and known errors. It conducts thorough root cause analysis to understand the underlying issues, coordinates the development of permanent solutions, and ensures their implementation to prevent recurrence, making it the correct practice for identifying root causes and coordinating permanent fixes.
Why this answer
Problem Management is the ITIL 4 practice responsible for identifying the root cause of incidents and ensuring permanent fixes are developed and applied. In this scenario, the temporary workaround is an Incident Management action, but the permanent fix requires Problem Management to conduct root cause analysis (RCA) and coordinate the implementation of a known error resolution.
Exam trap
The trap here is that candidates confuse Incident Management's responsibility for restoring service with Problem Management's responsibility for finding the permanent fix, especially when a workaround is involved.
How to eliminate wrong answers
Option A is wrong because Change Management handles the authorization and scheduling of changes, not the identification of permanent fixes; it executes the fix after Problem Management has identified it. Option B is wrong because Service Desk is the single point of contact for users and manages the incident lifecycle, but it does not perform root cause analysis or determine permanent solutions. Option D is wrong because Incident Management focuses on restoring normal service operation as quickly as possible using workarounds, not on identifying or applying permanent fixes.
A user reports they cannot print to a network printer. The service desk analyst suspects a driver issue. Which ITIL 4 concept BEST describes this scenario?
An Incident is defined in ITIL 4 as an unplanned interruption to a service or a reduction in the quality of a service. The user's inability to print to a network printer directly represents such an interruption, preventing them from performing their work as expected. The primary goal of incident management is to restore normal service operation as quickly as possible to minimize business impact. This scenario perfectly fits the definition of an incident requiring immediate attention.
Why this answer
This scenario is an Incident because the user reports an unplanned interruption to a service (printing), and the service desk analyst is working to restore normal service operation as quickly as possible. Even though a driver issue is suspected, the focus is on resolving the immediate failure, not on finding the root cause or implementing a permanent fix, which aligns with the ITIL 4 definition of an Incident.
Exam trap
The trap here is that candidates confuse a suspected root cause (driver issue) with a Problem, but ITIL 4 distinguishes between the immediate service interruption (Incident) and the underlying cause (Problem) — the scenario does not describe any root cause analysis or workaround identification.
How to eliminate wrong answers
Option B (Problem) is wrong because a Problem is the root cause of one or more incidents, and the scenario describes a single user report with a suspected driver issue — not an investigation into the underlying cause. Option C (Change) is wrong because a Change is the addition, modification, or removal of an authorized, planned, or supported service or component; this scenario involves an unplanned failure, not a planned alteration. Option D (Service request) is wrong because a Service request is a pre-defined, low-risk request for information, access, or a standard change (e.g., password reset, printer toner refill), not a report of a service failure.
What is the difference between an output and an outcome in ITIL 4?
In ITIL 4, outputs are precisely defined as the specific deliverables produced by service activities, such as a new application feature, a processed transaction, or a resolved incident. Outcomes, however, represent the actual results or benefits achieved by stakeholders through the consumption or use of these outputs, like improved business efficiency, enhanced customer satisfaction, or increased revenue. This distinction is crucial for understanding how services contribute to value realization.
Why this answer
In ITIL 4, an output is a tangible or intangible deliverable produced by an activity, such as a report or a software build. An outcome is the result achieved by a stakeholder through the use of that output, such as improved efficiency or reduced risk. Option B correctly captures this distinction: outputs are deliverables, while outcomes are the results that matter to stakeholders.
Exam trap
The trap here is that candidates confuse outputs with outcomes because both can be described as 'results,' but ITIL 4 specifically defines outputs as deliverables and outcomes as stakeholder-perceived results, so always check whether the result is a product or a business benefit.
How to eliminate wrong answers
Option A is wrong because it reverses the definitions: outputs are not results (they are deliverables), and outcomes are not activities (they are results achieved by stakeholders). Option C is wrong because the terms are not interchangeable in ITIL 4; they have distinct meanings in the service value system, where outputs lead to outcomes. Option D is wrong because outputs can be intangible (e.g., a decision or approval) and outcomes can be tangible (e.g., a measurable reduction in downtime).
A software development team delivers a new feature (output) but users find it difficult to use, resulting in low adoption. Which statement BEST describes this situation?
This is the correct option because it accurately distinguishes between an output and an outcome, a fundamental concept in ITIL 4. The "new feature" is a clear output, representing a tangible deliverable produced by the development team. However, the mere delivery of an output does not automatically guarantee the achievement of the desired outcome, which refers to the results or value realized by stakeholders, such as increased user satisfaction or improved business processes. The scenario implies that while the feature exists, its intended positive impact has not materialized.
Why this answer
The team successfully produced the new feature (the output), but users found it difficult to use, leading to low adoption. In ITIL 4, an output is a tangible or intangible deliverable, while an outcome is the actual result or value achieved for stakeholders. Here, the output was delivered, but the desired outcome—user adoption and value realization—was not achieved.
Exam trap
The trap here is confusing output with outcome, or misapplying utility vs. warranty—candidates often think a delivered feature automatically provides utility, but ITIL 4 requires that utility must enable the user to achieve a desired outcome, not just produce a technical artifact.
How to eliminate wrong answers
Option A is wrong because an outcome was not delivered; the output was produced, but the outcome (user adoption) was not achieved. Option B is wrong because warranty (assurance of availability, capacity, continuity, and security) is not the issue; the problem is utility (functionality that meets user needs), which is lacking due to poor usability. Option D is wrong because the service lacks utility (the feature is difficult to use), not warranty; warranty concerns are about reliability and performance, not user-friendliness.
A service provider offers a payroll service with guaranteed 99.9% uptime and response times under 2 seconds. Which ITIL 4 concept does this guarantee represent?
Warranty describes the assurance that a product or service will meet agreed requirements, ensuring it is "fit for use." This includes aspects like availability, capacity, security, and continuity, often expressed as service level guarantees such as uptime percentages or maximum response times. Therefore, a "guaranteed" payroll service directly relates to its warranty, as the provider is promising specific performance levels and assurances regarding the service's operation.
Why this answer
The guarantee of 99.9% uptime and response times under 2 seconds represents the 'Warranty' concept in ITIL 4. Warranty focuses on the availability, capacity, continuity, and security of a service—ensuring it is 'fit for use' under agreed conditions. The uptime percentage directly addresses availability, while the response time threshold addresses capacity and performance, both core components of warranty.
Exam trap
The trap here is that candidates confuse 'Utility' (what the service does) with 'Warranty' (how well it performs), leading them to pick Utility because they focus on the payroll function rather than the performance guarantees.
How to eliminate wrong answers
Option A is wrong because an 'Outcome' is the result or benefit delivered to a customer (e.g., employees being paid accurately), not the technical performance guarantees like uptime or response time. Option C is wrong because 'Cost' refers to the financial expenditure incurred by the service provider or customer, not the operational performance metrics of the service. Option D is wrong because 'Utility' describes the functionality or features of a service that make it 'fit for purpose' (e.g., calculating payroll taxes), not the assurance of availability or performance levels.
Which TWO of the following are examples of service relationships?
This is a quintessential example of a service relationship. The cloud service provider acts as the service provider, delivering storage as a defined service, while the company is the service consumer, utilizing this service to achieve its objectives. This arrangement involves the co-creation of value, where the provider manages the infrastructure and the consumer benefits from reliable, scalable data storage without owning the underlying assets.
Why this answer
In ITIL terms, a service relationship is a cooperation between a service provider and a service consumer, encompassing service provision, service consumption, and service relationship management. Option C is correct because a company consuming storage from a cloud service provider is a classic provider-consumer relationship, with the cloud provider supplying the service and the company consuming it under agreed terms. Option D is correct because outsourcing IT support to a third party establishes a formal service relationship in which the external provider delivers IT support services to the consuming organization.
Option A is not a service relationship but a goods/supply contract, since hardware is a product rather than a service being consumed. Option B describes an internal incident report or request to a help desk, which is a support interaction rather than a service relationship between provider and consumer. Option E describes internal collaboration within a department, which is teamwork rather than a provider-consumer service relationship.
Exam trap
The trap here is that candidates often confuse any business interaction (like hardware supply or internal reporting) with a service relationship, but ITIL 4 strictly requires a provider-consumer dynamic with a service offering that delivers value through outcomes, not just goods or internal processes.
A service consumer uses a payroll service. The provider ensures data encryption and backups. Which concept does this primarily support?
Warranty, in ITIL 4, provides assurance that a service will meet agreed requirements regarding availability, capacity, continuity, and security, ensuring the service is "fit for use." For a payroll service, this means the provider guarantees the service will be accessible when employees need their pay, can handle the volume of transactions, is resilient to disruptions, and protects sensitive financial data. This directly addresses the implicit "provider ensures" aspect of the question stem, focusing on the quality and performance attributes.
Why this answer
Warranty in ITIL 4 refers to the assurance that a service will meet agreed-upon conditions such as availability, capacity, continuity, and security. Data encryption and backups directly support the security and continuity aspects of warranty, ensuring the payroll service is protected against data breaches and data loss. This goes beyond mere functionality (utility) to guarantee the service is fit for use under defined conditions.
Exam trap
The trap here is that candidates confuse utility (what the service does) with warranty (how it is assured), mistakenly thinking encryption and backups are part of the service's functionality rather than its assurance guarantees.
How to eliminate wrong answers
Option A is wrong because output refers to the tangible result of an activity (e.g., a processed payroll report), not the protective measures like encryption and backups. Option B is wrong because utility describes the functionality or 'fit for purpose' of a service (e.g., calculating pay), not the assurance of security and data resilience. Option C is wrong because risk is a potential event that could cause harm, whereas encryption and backups are controls that mitigate risk, not the concept of risk itself.
During a service review, the provider demonstrates that the service meets all agreed targets. However, users report that the service does not help them achieve their goals. Which concept is lacking?
"Utility" refers to the functionality offered by a service to meet a particular need, specifically whether the service is "fit for purpose." If, during a service review, it's demonstrated that the service fails to help users achieve their intended goals or support their desired outcomes, then its utility is fundamentally lacking. This indicates the service does not possess the necessary capabilities to enable the consumer to perform their work or achieve their objectives, making it ineffective despite any other performance metrics.
Why this answer
Utility is the functionality offered by a service to meet a specific need. Even if all agreed targets (warranty) are met, the service fails to deliver utility if it does not help users achieve their goals. This gap between technical compliance and business outcome is the core of the question.
Exam trap
The trap here is that candidates confuse meeting agreed targets (warranty) with delivering value (utility), assuming that if all SLAs are satisfied, the service must be successful.
How to eliminate wrong answers
Option B (Risk) is wrong because risk refers to uncertainty that could affect objectives, not the lack of goal-aligned functionality. Option C (Output) is wrong because outputs are the tangible deliverables of a service (e.g., a report), not the outcome or value the service provides. Option D (Warranty) is wrong because warranty ensures the service will meet agreed performance, availability, and capacity targets—which the provider demonstrated—but does not address whether the service actually helps users achieve their goals.
An organisation's IT service desk is receiving a high volume of calls about users being unable to log in to the payroll system following a scheduled maintenance window. According to ITIL 4, what type of record should be raised FIRST?
An unplanned interruption to a live service, affecting multiple payroll users, meets the ITIL 4 incident definition. Incident management restores normal service quickly, so this record type is raised first; problem or change records follow only if investigation warrants them.
Why this answer
An incident is defined as an unplanned interruption to a service or a reduction in its quality. Since users cannot log in after the maintenance window, this is an unplanned service interruption, and ITIL 4 dictates that an incident record should be raised first to restore normal service operation as quickly as possible.
Exam trap
The trap here is that candidates confuse the need for root cause analysis (problem management) with the immediate priority of restoring service (incident management), leading them to select option C instead of B.
How to eliminate wrong answers
Option A is wrong because a service request is for a pre-defined, standard request (e.g., password reset or access grant), not for restoring service after an unplanned failure. Option C is wrong because a problem record aims to identify the root cause of one or more incidents, but it should be raised only after the incident is logged and managed, not as the first action. Option D is wrong because a change request is for planned alterations; reversing the maintenance window changes would be a corrective change, but the immediate priority is to restore service via incident management, not to initiate a change.
A company provides a cloud-based file storage service. Users can store and retrieve files, but the service has no backup or redundancy. Which statement about this service is correct?
This option is correct because the service provides utility by enabling users to successfully store and retrieve their files, fulfilling its core functional purpose. However, it lacks warranty, which encompasses assurances regarding service performance, availability, and continuity. The absence of backup or redundancy means the service cannot guarantee protection against data loss or sustained availability, thus failing to meet the 'fit for use' criteria for warranty.
Why this answer
Utility is the functionality offered by a service to meet a specific user need, and here the service allows users to store and retrieve files, so it has utility. Warranty ensures the service is available, reliable, and secure; since there is no backup or redundancy, the service lacks warranty. Therefore, option D is correct.
Exam trap
The trap here is confusing utility with warranty: candidates often assume that because a service works (utility), it automatically has warranty, but warranty requires explicit assurance mechanisms like backups or redundancy.
How to eliminate wrong answers
Option A is wrong because the service does provide utility (file storage and retrieval), so it cannot be said to have neither utility nor warranty. Option B is wrong because the service lacks warranty due to no backup or redundancy, so it does not have both utility and warranty. Option C is wrong because the service has utility (it works for its intended purpose), not warranty; warranty requires assurance of availability and continuity, which is absent.
Which TWO of the following are true about the relationship between outputs and outcomes?
This option correctly defines the core ITIL 4 concepts. An output refers to a tangible or intangible deliverable produced by an activity, such as a new system or a processed report. Conversely, an outcome represents the actual result or effect achieved for a stakeholder, often expressed as value creation, improved performance, or reduced risk, directly enabled by the consumption or use of one or more outputs.
Why this answer
ITIL 4 defines an output as a tangible or intangible deliverable of an activity, while an outcome is the result for a stakeholder that is enabled by the output. For example, a software deployment (output) leads to improved user productivity (outcome). This distinction is fundamental to value co-creation in service management.
Exam trap
The trap here is that candidates often assume outputs are always tangible and outcomes always intangible, but ITIL 4 explicitly allows both to be either, and the key differentiator is the stakeholder's perspective and context, not physicality.
Which THREE of the following are stakeholders in a service relationship?
A customer is a person or group who defines the requirements for a service and takes responsibility for the outcomes of service consumption. They are a primary stakeholder in a service relationship because they are the recipient of the value created by the service and often fund or authorize its provision. Their satisfaction is a key measure of the service's success.
Why this answer
In ITIL 4, the service relationship is defined by the interactions between a service provider and a service consumer, and the consumer role is further broken down into customer, user, and sponsor. Option B (Customer) is correct because the customer is the role that defines the requirements for a service and takes responsibility for the outcomes of service consumption, making them a core stakeholder in the relationship. Option C (User) is correct because the user is the role that actually uses the service, and their experience and needs directly shape the service relationship.
Option D (Service provider) is correct because the provider is the other party in the relationship, responsible for delivering and managing the services that create value for the consumer. Option A (Regulator) is not a stakeholder in the service relationship itself; regulators impose external constraints but are not one of the defined consumer or provider roles. Option E (Competitor) is not a stakeholder in the service relationship because competitors operate outside the direct provider-consumer interaction and do not participate in the co-creation of value within that relationship.
Exam trap
The trap here is that candidates often mistake external influencers like regulators or competitors as stakeholders in the direct service relationship, but ITIL 4 specifically limits the term to direct participants in the value co-creation process.
A service provider introduces a new service that allows customers to self-report issues. This results in a 30% reduction in call volume to the service desk and faster resolution times. According to ITIL 4, what is the outcome of this service?
A 30% reduction in call volume and faster resolution times are direct outcomes because they represent the tangible, measurable results and improvements experienced by the stakeholders. These metrics directly reflect the value realized from the new service, demonstrating improved efficiency and a better experience for customers. Outcomes describe the actual changes in behavior, performance, or perception that are enabled by the service's outputs.
Why this answer
ITIL 4 defines an outcome as a result for a stakeholder enabled by one or more outputs. In this scenario, the 30% reduction in call volume and faster resolution times are the measurable, value-driven results experienced by the service provider and customers, directly enabled by the self-reporting feature (the output). The outcome is the business impact, not the feature itself or its adoption metrics.
Exam trap
The trap here is that candidates confuse outputs (the feature itself) or intermediate metrics (adoption rate, cost savings) with the actual outcome, which must be a tangible result for stakeholders as defined by ITIL 4's output vs. outcome distinction.
How to eliminate wrong answers
Option A is wrong because the self-reporting feature is an output (a tangible deliverable or capability), not an outcome (the result or benefit achieved from using that output). Option B is wrong because cost savings are a potential benefit or value, but the question specifically asks for the outcome as defined by ITIL 4, which is the direct result (reduced call volume and faster resolution) that leads to such savings, not the savings themselves. Option D is wrong because the number of users who adopted the feature is a metric of adoption or usage, not the outcome; outcomes are the results for stakeholders, not the count of users.
A company launches a new mobile banking app. Customers can transfer money, view balances, and pay bills. The app is available 99.9% of the time during business hours. Which statement about the app's utility and warranty is TRUE?
This option correctly distinguishes between utility and warranty within the context of a mobile banking app. Utility represents the core functionality that enables value, such as the ability for customers to transfer money, directly supporting their objectives. Warranty, on the other hand, provides assurance that the service will meet agreed-upon requirements, with 99.9% availability being a prime example of a performance guarantee. Both aspects are crucial for delivering a valuable and reliable service experience.
Why this answer
In ITIL 4, utility refers to the functionality offered by a service (what it does), while warranty refers to the assurance that the service will meet agreed-upon conditions such as availability, capacity, continuity, and security. The app's ability to transfer money, view balances, and pay bills represents its utility, and the 99.9% availability guarantee during business hours represents its warranty. Therefore, option B correctly pairs utility with functionality and warranty with availability.
Exam trap
The trap here is that candidates often confuse utility with availability or reliability, mistakenly thinking utility is about 'how well' the service works rather than 'what' it does, leading them to reverse the definitions as in option A.
How to eliminate wrong answers
Option A is wrong because it reverses the definitions: utility is the functionality (what the service does), not the availability guarantee, and warranty is the assurance of conditions like availability, not the functionality. Option C is wrong because warranty always applies when a service is delivered; even if the app works, the provider must guarantee conditions like availability, performance, and security. Option D is wrong because utility always applies; the app's functionality (transferring money, viewing balances) is essential to the service, and warranty alone cannot deliver value without utility.
A hospital's IT department is adopting ITIL 4. They want to define the steps needed to create, deliver, and improve their IT services. Which ITIL 4 component should they use to structure these activities?
The Service Value Chain is the central operating model in ITIL 4, outlining six key activities (Plan, Improve, Engage, Design & Transition, Obtain/Build, Deliver & Support) that an organization performs to create value for its consumers. It provides a flexible, end-to-end operational structure, allowing the IT department to define specific value streams by combining these activities in various sequences to deliver different products and services effectively. This model directly addresses the need for structuring service delivery activities.
Why this answer
The Service Value Chain (D) is the correct component because it provides an operating model that outlines the key activities required to respond to demand and facilitate value creation through the creation, delivery, and improvement of services. It consists of six interconnected activities (Plan, Improve, Engage, Design & Transition, Obtain/Build, Deliver & Support) that directly structure the steps needed for service management. The hospital's IT department can use this model to map out the end-to-end processes for developing and enhancing their IT services.
Exam trap
The trap here is that candidates often confuse the Service Value Chain with the Continual Improvement Model, mistakenly thinking that improvement steps alone cover service creation and delivery, whereas the Service Value Chain is the comprehensive operating model that structures all activities from demand to value.
How to eliminate wrong answers
Option A is wrong because the Continual Improvement Model is a structured approach for managing improvement initiatives (e.g., defining vision, assessing current state, implementing improvements), but it does not define the core steps for creating and delivering services; it is a supporting tool rather than the primary operating model. Option B is wrong because the Guiding Principles (e.g., Focus on Value, Start Where You Are) are recommendations that guide decision-making and behavior, not a sequence of activities for service creation and delivery. Option C is wrong because the Four Dimensions of Service Management (Organizations & People, Information & Technology, Partners & Suppliers, Value Streams & Processes) represent holistic perspectives that must be considered, but they do not prescribe the specific steps or workflow for creating, delivering, and improving services.
A company hires a managed service provider to run its email system. Which cost is typically REMOVED from the consumer by using this service?
By engaging a managed service provider for email services, the company transfers the responsibility and financial burden of acquiring, hosting, and maintaining the physical or virtual server infrastructure dedicated to email. This includes capital expenditure for server hardware, software licenses, power, cooling, and the operational costs associated with patching, monitoring, and troubleshooting the email server environment. These direct infrastructure costs are absorbed by the MSP and are no longer borne by the client organization.
Why this answer
When a company hires a managed service provider to run its email system, the provider takes over the operation of the email infrastructure, including the servers, storage, and networking components. This removes the capital expenditure (CapEx) and operational costs associated with purchasing, maintaining, patching, and upgrading email servers (e.g., Microsoft Exchange Server or a dedicated SMTP/IMAP server). The consumer no longer needs to procure hardware, manage RAID arrays, or handle server OS licensing for the email service.
Exam trap
The trap here is that candidates may confuse the removal of capital costs (like servers) with ongoing operational costs (like subscription fees), or incorrectly assume that all IT staff costs are removed when only specific email-related roles might be affected.
How to eliminate wrong answers
Option A is wrong because salaries of internal IT staff not related to email are not removed by outsourcing the email system; those staff remain employed for other systems and tasks. Option C is wrong because subscription fees to the provider are a new cost introduced by the service, not removed from the consumer. Option D is wrong because electricity costs for office computers are unrelated to the email server infrastructure and are still incurred by the consumer for their own desktop and laptop usage.
A company is implementing ITIL 4 and wants to ensure that all changes to IT services are managed in a controlled manner. Which practice should they use to balance the need for change with the need to minimize risk?
Change enablement is the correct practice because it directly addresses the need to manage the lifecycle of all changes, from planning and assessment to authorization and deployment. Its purpose is to maximize the number of successful service and product changes by ensuring that risks are properly assessed, changes are authorized, and their impact on services is minimized. This practice is crucial for introducing new features, fixing errors, or improving performance in a controlled manner.
Why this answer
Change enablement is the correct practice because it specifically governs the lifecycle of changes to IT services, ensuring that all changes are assessed, authorized, and implemented in a controlled manner. This practice balances the need for rapid service evolution with the imperative to minimize risk by using standardized procedures, change models, and authorization policies (e.g., pre-approved standard changes, normal changes requiring CAB approval, emergency changes with expedited review).
Exam trap
The trap here is that candidates confuse 'managing changes' with 'fixing incidents' or 'solving problems,' leading them to select incident management or problem management instead of recognizing that change enablement is the dedicated practice for controlled change implementation and risk balancing.
How to eliminate wrong answers
Option A is wrong because incident management focuses on restoring normal service operation as quickly as possible after an unplanned interruption or degradation, not on proactively controlling planned changes. Option C is wrong because problem management aims to identify and eliminate the root causes of incidents, reducing their recurrence, but does not manage the authorization or implementation of changes. Option D is wrong because the service desk provides a single point of contact for users to report incidents and request services, but it does not own the change authorization or risk-balancing process.
Which of the following is an example of value co-creation?
Value co-creation in ITIL 4 emphasizes that value is not merely delivered by the service provider but is actively created through collaboration between the provider and the consumer. When a consumer uses a cloud service, they gain utility, and their subsequent feedback directly informs service improvements. This iterative process, where consumer experience and input shape the service's evolution, exemplifies how both parties contribute to optimizing the service and realizing greater value.
Why this answer
Value co-creation in ITIL 4 requires active participation from both the service provider and the consumer to jointly realize value. In option A, the consumer uses the cloud service and provides feedback, which the provider uses to make improvements—this is a direct example of collaboration that enhances the service's utility and warranty, aligning with the ITIL 4 guiding principle of 'Focus on Value'.
Exam trap
The trap here is that candidates often mistake any consumer action (like paying) as co-creation, but ITIL 4 requires active, collaborative participation—not passive consumption or financial exchange alone.
How to eliminate wrong answers
Option B is wrong because a provider unilaterally setting service levels without consumer input is a top-down approach that ignores the consumer's needs and feedback, violating the co-creation principle where value is jointly defined. Option C is wrong because paying for a service without using it represents no interaction or contribution from the consumer, so no value is co-created—value requires active engagement, not just financial transaction. Option D is wrong because installing a server without the consumer's input is a provider-only activity that does not involve the consumer in defining or refining the service, missing the collaborative aspect of co-creation.
In ITIL 4, which role is responsible for defining the requirements for a service and ensuring the provider meets them?
The customer is the individual or group who defines the requirements for a service, articulating the desired outcomes and value that the service should deliver to their organization or stakeholders. They are responsible for specifying what the service needs to achieve from a business perspective, ensuring that the service provider understands these needs. The customer's role is critical in driving the service design and ensuring the delivered service aligns with their strategic objectives and operational demands.
Why this answer
In ITIL 4, the customer is the role that defines the requirements for a service and takes responsibility for the outcomes of service consumption. The customer ensures the provider meets those requirements. This is distinct from the user, who actually uses the service.
Exam trap
ITIL4F often tests the distinction between customer, user, and sponsor roles, causing candidates to confuse who defines requirements (customer) with who uses the service (user) or who funds it (sponsor).
How to eliminate wrong answers
Option A (Service provider) is wrong because the provider delivers the service, not defines requirements. Option B (Sponsor) is wrong because the sponsor authorizes the budget for service consumption but does not necessarily define detailed requirements. Option D (User) is wrong because the user uses the service but does not define requirements or ensure they are met.
A small accounting firm decides to subscribe to a cloud-based tax preparation service instead of building and maintaining its own tax software. The firm's partners agree that using this service will reduce the need to hire additional IT staff and lower the risk of software failures during peak tax season. Which ITIL 4 concept does this scenario best illustrate?
ITIL 4 describes that using a service shifts certain costs and risks from the consumer to the provider. The firm avoids hiring IT staff (cost) and reduces the risk of software failures by relying on the cloud provider. This is a classic example of how service consumption removes or transfers costs and risks, allowing the consumer to focus on its core business.
Why this answer
By subscribing to the cloud service, the accounting firm avoids hiring IT staff and reduces the risk of software failures during peak season. This demonstrates the ITIL 4 concept that service consumption transfers certain costs and risks from the consumer to the provider, allowing the consumer to focus on core activities.
Exam trap
The trap here is confusing the transfer of costs and risks with value co-creation; the scenario emphasizes what the consumer avoids, not joint activities.
Which THREE of the following are typical risks that can be transferred from a service consumer to a service provider when using a cloud-based email service?
For an email service, the provider is typically responsible for the physical infrastructure, including the servers, storage, and networking hardware that host the email platform. A hardware failure, such as a disk crash or power supply unit malfunction in an email server, directly impacts service availability and is a primary operational risk that the provider must actively manage through redundancy, monitoring, and maintenance protocols.
Why this answer
When a consumer uses a cloud-based email service, the provider is responsible for the underlying hardware, including servers, storage, and network infrastructure. Any failure of the email servers (e.g., disk crashes, power supply failures) is a risk that the provider must manage through redundancy and maintenance, thus transferring that risk away from the consumer.
Exam trap
The trap here is that candidates mistakenly think all risks are transferred to the cloud provider, but in reality, risks related to the consumer's own environment (internet access, user training) remain with the consumer, while only risks inherent to the provider's infrastructure and platform operations are transferred.
Ready to test yourself?
Try a timed practice session using only Key Concepts of ITIL 4 questions.