ITIL-4-Foundation Sample Questions Answers

The second step is to conduct an objective current-state assessment of existing services and service management practices. This should include consideration of the users’ perception of the value being received, along with a review of people’s competencies and skills, the processes and procedures involved, the capabilities of the available technological solutions and the prevailing organizational culture. The success of an improvement initiative depends on a clear and accurate understanding of the starting point and the required impact of the initiative.

For example, an organization can measure the current net promoter score (NPS) from a customer satisfaction survey, conduct a benchmark survey against its competitors or review findings of operational statistics or audit reports to understand its current state. If this step is skipped, the current state will not be understood and there will not be an objective baseline measurement against which improvement can be measured.

https://www.bmc.com/blogs/itil-continual-improvement/

Customers are one of the key stakeholder groups that service providers should cooperate with. Customers are the persons who define the requirements for a service and take responsibility for the outcomes of service consumption1. Customers can be internal or external to the service provider’s organization2. Customers are essential for value co-creation, as they provide feedback, resources, and demand for services3. References: ITIL Foundation - ITIL 4 Edition, page 5; ITIL® 4 – A Pocket Guide, page 18; [ITIL® 4 Practice Guide: Customer Relationship Management], page 7.

This is one of the most important questions for continual improvement. This question helps to define measurable targets for the IT service provider that will help to reach the vision of the company in the long-term. At this stage, we look at the identified key performance indicators from the previous step and determine what values we want to target for each of these indicators. This decision must be made with the business’s vision in mind, but also with a sense of what is practically possible.

https://blog.masterofproject.com/continual-improvement-model/

In ITIL 4, several service consumer roles are defined to clarify how different stakeholders interact with services. These roles include customer, user, and sponsor, all of which fall under the broader term service consumer.

A user is defined as the role that uses services.

A customer is the role that defines the requirements for a service and takes responsibility for the outcomes of service consumption.

A sponsor is the role that authorizes the budget for service consumption.

A service consumer is a generic term for one or more of these roles (customer, user, sponsor).

Because the exact phrase in the question is “the role that uses services”, this matches the ITIL 4 definition of “user”, so:

C. User is the correct answer.

The other options do not match that definition:

A. Service consumer – an umbrella term, not specifically “the role that uses services”.

B. Customer – focuses on requirements and outcomes, not direct use.

D. Sponsor – focuses on funding and authorization, not use of services.

ITIL 4 Foundation: Definitions of service consumer roles – customer, user, sponsor

ITIL 4 Foundation: Key concepts of service relationships and service consumption

Service management is a set of specialized organizational capabilities for enabling value for customers in the form of services. These capabilities include tangible things like capital, people, and equipment, and can also include intangible things like knowledge, management and skills. These capabilities can also include intangible things, like knowledge, management, and skills.

https://www.bmc.com/blogs/itil-key-concepts-service-management/#:~:text=Service%20management%20is%20a%20set,like%20knowledge%2C%20management%20and%20skills.

In ITIL 4, the ‘improve’ value chain activity is part of the service value chain within the service value system. Its official purpose is to ensure continual improvement of products, services, and practices across all value chain activities and the four dimensions of service management.

Option A matches the core wording of this purpose:

“Ensure the continual improvement of practices across all value chain activities.”

Even though the full ITIL statement also mentions products, services, and the four dimensions of service management, this option is the only one that directly reflects the continual improvement focus of the improve activity across the value chain.

Why the other options are not correct:

B. Ensure services continually meet expectations for quality, costs, and time to marketThis is more aligned with design and transition, obtain/build, and deliver and support, which focus on planning, building, and delivering services that meet agreed requirements, costs, and time constraints.

C. Ensure a shared understanding of the improvement direction for services across the organizationThis sounds closer to guiding principles or governance, and to some aspects of service level management and continual improvement planning, but it is not the formal purpose statement of the improve value chain activity.

D. Ensure continual engagement and good relationships with all stakeholdersThis aligns strongly with the engage value chain activity, whose purpose is about understanding stakeholder needs, ensuring transparency, and maintaining relationships.

Therefore, A is the correct option because it directly reflects the official purpose of the ‘improve’ value chain activity in ITIL 4.

References (ITIL 4 Foundation):

ITIL® Foundation: ITIL 4 Edition – Service Value System, Service Value Chain – Improve activity (purpose)

ITIL® Foundation: ITIL 4 Edition – Overview of service value chain activities

Continual improvement encompasses all elements of the ITIL SVS. It involves aligning an organization’s practices and services with changing business needs, through the ongoing assessment and improvement of each element involved in the management of products and services. Continual improvement applies to the SVS in its entirety, as well as to all of the organization’s products, services, service components, and relationships, and is the responsibility of every individual involved in service management.

https://www.bmc.com/blogs/itil-continual-improvement/

Comprehensive and Detailed Explanation From Exact Extract:

In ITIL 4, problem management focuses on identifying and managing the underlying causes of incidents. Its purpose is described as reducing both the likelihood and impact of incidents by:

Identifying actual and potential causes of incidents (problems).

Managing workarounds and known errors so that the impact of incidents is minimized until a permanent solution can be implemented.

A workaround is a way of reducing or eliminating the impact of an incident or problem when a full resolution is not yet available. A known error is a problem that has a documented cause and either a workaround or a permanent solution identified.

Therefore, the missing word in the sentence is “workarounds”, making D the correct answer.

Why the other options are incorrect:

Events are handled primarily by the monitoring and event management practice.

Changes are controlled through the change enablement practice.

Configuration items are managed by the service configuration management practice.

Relevant ITIL 4 Foundation references:

Problem management practice: purpose, definitions of problem, workaround, and known error.

In ITIL 4 terminology, a problem is defined as the cause, or potential cause, of one or more incidents. Incident management deals with restoring service as quickly as possible, while problem management focuses on finding and addressing the underlying causes so that incidents do not recur.

A problem is therefore directly associated with the cause behind one or more incidents, matching the wording in the sentence.

A known error is a problem that has been analyzed and has a documented root cause and workaround; it is not simply “the cause or potential cause” but a further state of a problem.

A change is the addition, modification, or removal of anything that could have a direct or indirect effect on services, not specifically the cause of incidents.

An event is any change of state that has significance for the management of a service or other configuration item; again, not defined as the cause of incidents.

Because ITIL 4 explicitly associates the phrase “cause, or potential cause, of one or more incidents” with problem, the correct answer is D.

Each activity contributes to the value chain by transforming specific inputs into outputs. The inputs could be demand from outside the value chain, or outputs of other activities, while the transformation is facilitated by ITIL practices, undertaken using internal or third-party resources, processes, skills, and competencies.

https://www.bmc.com/blogs/itil-service-value-chain/

When a supplier modifies the contract they offer to your organization, this represents a change that can affect services, service components, costs, risks, and agreed service levels.

In ITIL 4, the purpose of the change enablement practice is to maximize the number of successful service and product changes by ensuring that risks are properly assessed, authorizing changes to proceed, and managing the change schedule. This includes changes that arise from external parties such as suppliers, not just technical changes inside IT.

A contract modification by a supplier can:

alter delivery terms or service performance

introduce new risks (financial, operational, compliance)

require changes to service design, support, or architecture

Because of this, it should go through change enablement, where:

the risk to services is assessed

the impact on existing services and customers is evaluated

a decision is made whether to approve, reject, or modify the proposed change

coordination with other practices (like supplier management and service level management) may occur, but the formal risk assessment and authorization of the change are part of change enablement.

Why the other options are less appropriate:

A. Incident management

Focuses on restoring normal service operation as quickly as possible after an unplanned interruption or reduction in quality.

It reacts to incidents; it does not manage contractual changes or assess risks from supplier contract modifications.

B. Service level management

Ensures SLAs and service targets are defined, agreed, and monitored with customers.

While it may be involved in understanding how a supplier change affects SLAs, it is not the primary practice responsible for overall risk assessment and authorization of such changes.

C. Service request management

Deals with predefined, user-initiated requests, such as password resets or standard access requests.

It is operational and transactional and not concerned with supplier contract changes or service risk assessment.

D. Change enablement

Specifically designed to assess, authorize, and manage changes to services and service components, including those triggered by changes in supplier contracts.

Therefore, it is the MOST appropriate practice for assessing the risk to services in this scenario.

So, the practice that would be most involved in assessing the risk to services when a supplier modifies their contract is D. Change enablement.

AXELOS – ITIL Foundation: ITIL 4 Edition, Change Enablement practice purpose and description

AXELOS – ITIL 4 Practice Guides (Change Enablement, Service Level Management, Incident Management, Service Request Management)

The incident management practice aims to minimize the negative impact of incidents by restoring normal service operation as quickly as possible1. A major incident is an incident that has a significant impact or urgency for the business and requires a high level of coordination and resources to resolve2. The most likely way of resolving major incidents is by forming a temporary team working together to identify a resolution, such as a major incident team or a swarming team3. The other statements are not true because:

Users establishing a resolution using self-help: Self-help is an option for users to resolve their own incidents with minimal or no assistance from the service provider, but it is not suitable for major incidents that require urgent and expert attention3.

The service desk identifying the cause and a resolution: The service desk is responsible for logging, categorizing, prioritizing, and escalating incidents, but it may not have the skills or authority to identify the cause and a resolution for major incidents that involve multiple teams or suppliers3.

A support team following detailed procedures for investigating the incident: A support team may follow detailed procedures for investigating the incident, but it may not be able to resolve major incidents that require cross-functional collaboration or escalation3. References: ITIL Foundation - ITIL 4 Edition, page 14; ITIL® 4 – A Pocket Guide, page 32; ITIL® 4 Practice Guide: Incident Management, page 8.

In ITIL 4, the purpose of the relationship management practice is to:

Establish and nurture the links between the organization and its stakeholders

Identify, analyze, monitor, and continually improve relationships with stakeholders at strategic and tactical levels

Option C closely reflects this wording: “Identifying, analyzing, monitoring, and the continual improvement of relationships with stakeholders.” This matches the official purpose description, so C is correct.

The other options actually describe other practices:

A. Creating collaborative relationships with key suppliers… – This aligns with supplier management, which focuses on obtaining value from suppliers and managing supplier relationships.

B. Setting clear business-based targets so that the delivery of a service can be properly assessed – This is the purpose of service level management, not relationship management.

D. Handling all pre-defined, user-initiated service requests in an effective and user-friendly manner – This describes service request management.

Therefore, the option that correctly reflects the purpose of the relationship management practice is C.

Don’t start from scratch and build something new without considering what you already have. It’s almost always better to improve what you currently have than to throw it all away and start again, although you must also be able to recognise when a complete replacement is, in fact, needed.

Not only is this approach less wasteful than starting from scratch – because it preserves value that you already have – but it also helps you to keep your people on board. They’re much more likely to support the changes you need if their previous contributions have been appropriately valued.

Don’t rely on metrics and reports to tell you what the current situation is. When you carry out an assessment you should observe what is happening for yourself, and just use the metrics to support your observations.

https://www.sysaid.com/blog/itil/the-7-guiding-principles-of-itil-4-practical-advice-to-help-you-make-decisions

In order to be aligned to customer outcomes and expectations, SLM requires focus and effort to engage and listen to the requirements, issues, concerns, and daily needs of customers:

Engagement is needed to understand and confirm the actual ongoing needs and requirements of customers, not simply what is interpreted by the service provider or has been agreed several years before. ITIL4 refers to value as being co-created, since it needs the input and validation of customers.

Listening is important as a relationship-building and trust-building activity, to show customers that they are valued and understood. This helps to move the provider away from always being in ‘solution mode’ and to build new, more constructive partnerships. Each customer is unique, and the service provider must not have a one-size-fits-all approach.

The activities of engaging and listening provide a great opportunity to build improved relationships and to focus on what really needs to be delivered. They also give service delivery staff an experience-based understanding of the day-to-day work that is done with their technology, enabling them to deliver a more business-focused service. When the customer is engaged and listened to, they feel valued and their perception of the service and service management activities improves.

https://www.bmc.com/blogs/itil-service-level-management/

The organizations and people dimension sets out the people aspects of service management to be considered when designing, operating and changing service offerings. People include employees, managers, executives, customers, supplier employees, or anybody else who is involved in the creation or consumption of services.

https://assyst.ifs.com/blog/what-are-the-four-dimensions-of-itil-4

Comprehensive and Detailed Explanation From Exact Extract (Aligned with ITIL 4 Foundation Study Guide)

In ITIL 4, improvement work is performed using iterative cycles, supported by continuous feedback. This idea comes from the ITIL Guiding Principle: “Progress iteratively with feedback.”

A feedback loop ensures that each iteration remains aligned with stakeholder needs, performance data, and contextual changes.

Why Feedback Loop is Correct:

Feedback loops provide information about:

the performance of activities

the needs and expectations of stakeholders

whether the current approach is still suitable

issues or improvements identified during the iteration

This continuous flow of information allows the team to adjust the iteration early, ensuring improvement activities remain relevant even when circumstances change.

Why the other options are incorrect:

A. Analysis paralysis: ITIL specifically warns against over-analysis that prevents progress.

B. Direct observation: Helpful for understanding work but does not keep iteration aligned with changing circumstances.

C. Minimum viable product: Useful for early delivery but not for continuous alignment during iterations.

Therefore, the concept that keeps improvement iteration activities appropriate under changing conditions is the feedback loop.

References (Aligned With ITIL 4 Foundation Publications — No URLs)

ITIL 4 Foundation: Guiding Principle “Progress iteratively with feedback”

ITIL 4 Foundation: Continual Improvement concepts

ITIL 4 Foundation: Service Value System emphasis on feedback mechanisms for adaptation

Comprehensive and Detailed Explanation From Exact Extract:

ITIL 4 defines four dimensions of service management that are critical for the effective and efficient co-creation of value:

Organizations and people

Information and technology

Partners and suppliers

Value streams and processes

The “Organizations and people” dimension addresses:

Organizational structure – how the organization is arranged.

Roles and responsibilities – who does what and who is accountable.

Systems of authority and communication – how decisions are made and communicated.

Culture and competencies – behaviors, skills, and capabilities of people involved in service management.

Because this dimension specifically covers roles, responsibilities, and systems of authority, the correct answer is A. Organizations and people.

The other dimensions focus on different aspects:

Information and technology – data, information, and technological solutions used in service management.

Partners and suppliers – relationships and agreements with third parties that support service delivery.

Value streams and processes – how activities and processes are organized to create and deliver value.

Relevant ITIL 4 Foundation references:

The four dimensions of service management chapter.

Detailed description of the “Organizations and people” dimension (structure, roles, responsibilities, authority).

An outcome is a result for a stakeholder enabled by one or more outputs1. Outputs are tangible or intangible deliverables of an activity1. For example, a service provider may produce a report (output) that helps a customer make a decision (outcome)2. References: ITIL Foundation - ITIL 4 Edition, page 3; ITIL® 4 – A Pocket Guide, page 13.

Service management is the term used to describe how organizations manage their services to deliver value to their customers and other stakeholders. Service management requires a set of specialized organizational capabilities, such as processes, roles, tools, and competencies, that enable the effective and efficient delivery of services1. Service management is also a professional practice supported by an extensive body of knowledge, experience, and skills3. References: ITIL Foundation - ITIL 4 Edition, page 2; ITIL® 4 – A Pocket Guide, page 11.

The purpose of the service request management practice is to support the agreed quality of a service by handling all pre-defined, user-initiated service requests in an effective and user-friendly manner. Service request management is dependent upon well-designed processes and procedures, which are operationalized through tracking and automation tools to maximize the efficiency of the practice. To be handled optimally, service request management should follow these guidelines:

Service requests and their fulfilment should be standardized and automated to the greatest degree possible.

Policies should define which service requests will be fulfilled with limited or even no additional approvals so that fulfilment can be streamlined.

The expectations of users regarding fulfilment times and costs should be clearly set, based on what the organization can realistically deliver.

Opportunities for improvement should be identified and implemented to produce faster fulfilment times and take advantage of automation.

https://www.bmc.com/blogs/itil-service-request-management/

ITIL 4 defines a service as:

A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.

The key phrase in the question is “facilitates outcomes that customers want to achieve”, which is directly part of the definition of a service in ITIL 4.

Therefore, the correct answer is A. Service.

Why the other options are incorrect:

B. WarrantyWarranty is one of the two aspects of value (warranty and utility). It relates to how the service performs (availability, capacity, continuity, security), but warranty alone does not ‘facilitate outcomes’ – it describes assurance about performance.

C. OrganizationAn organization is a person or group of people with functions and responsibilities, authorities and relationships. Organizations provide and consume services, but the concept that “facilitates outcomes” is specifically the service.

D. IT assetIT assets (hardware, software, etc.) are components that support services and are financially valuable, but on their own they do not “facilitate outcomes that customers want to achieve” – that is done through services built from these assets.

References (Aligned with ITIL 4 Foundation concepts)

ITIL 4 Foundation: Definition of service

ITIL 4 Foundation: Key concepts of value, outputs, outcomes, utility, and warranty

Organizations maximize co-creation of value with their customers by facilitating the outcomes they want to achieve. The four dimensions of service management have shown that a holistic approach is the best way for an organization to:

Achieve its goals in delivering quality and cost effective services

Meet the needs of its customers

Satisfy the requirements of its stakeholders

https://www.bmc.com/blogs/itil-service-value-system/

In ITIL 4, the continual improvement practice uses a continual improvement register (CIR) as a key tool to record, prioritize, track, and manage improvement opportunities.

The CIR is used to:

Log improvement ideas from any source

Track these ideas from initial identification through assessment, prioritization, and implementation

Provide visibility of the status and progress of each improvement

Support decision-making about which improvements to pursue and when

This matches option C: “Used to track and manage improvement ideas from identification through to final action.”

Why the other options are incorrect:

A. Used to help plan changes, assist in communication, avoid conflicts, and assign resourcesThis describes aspects of change enablement and change schedule / change calendar, not the continual improvement register.

B. Used to select the right method, model or technique for identifying improvementsMethods and models (such as SWOT, balanced scorecard, etc.) support improvement activities, but the CIR is not about choosing methods; it is about recording and managing improvement opportunities.

D. Used to provide a formal description of one or more services, designed to address the needs of a target consumer groupThis describes a service catalogue entry or service offering, not a continual improvement register.

So, the CIR is specifically a tracking and management tool for improvement ideas, making C the correct answer.

References (Aligned with ITIL 4 Foundation concepts)

ITIL 4 Foundation: Continual improvement practice – use of a continual improvement register to log and manage improvements across their lifecycle

ITIL 4 Foundation: Service management practices overview – distinction between change enablement, service catalogue management, and continual improvement

A change that must be implemented as soon as possible without strictly following the standard process e.g. to resolve an incident or implement a security patch.

The process for assessment and authorization is expedited to ensure quick implementation, so scheduling and documentation is not a priority.

The change authority may be separate from what is standard or normal practice, typically smaller in number but with greater capacity to expedite approval.

https://www.bmc.com/blogs/itil-change-enablement/

The purpose of the SLM practice is to set clear business-based targets for service performance, so that the delivery of a service can be properly assessed, monitored, and managed against these targets. SLM involves service level activities, including:

Defining service levels

Documenting

Actively managing them

https://www.bmc.com/blogs/itil-service-level-management/

Think and work holistically

No service, practice, process, department, or supplier stands alone. The outputs that the organization delivers to itself, its customers, and other stakeholders will suffer unless it works in an integrated way to handle its activities as a whole, rather than as separate parts.

https://www.bmc.com/blogs/itil-guiding-principles/#:~:text=5.,rather%20than%20as%20separate%20parts.

In ITIL 4, the service value chain is the central component of the Service Value System. It describes the set of interconnected activities an organization performs to create value in the form of products and services. The service value chain is explicitly defined as the model that outlines the key activities required to co-create value with customers and other stakeholders.

That is exactly what the question is asking: “the activities needed by an organization to help it co-create value” – which directly matches the role of the service value chain, so A is correct.

Why the other options are not correct in this context:

B. Continual improvement is a practice and a component of the Service Value System that ensures services, practices, and all components are continually improved, but it is not the central model of value-creating activities.

C. Guiding principle refers to recommendations that guide decisions and actions across all circumstances, not the activities themselves.

D. Practices are sets of organizational resources designed for performing work or accomplishing an objective; they support value creation, but they are not the component that models the end-to-end set of activities for co-creating value.

Therefore, the component focused on the activities needed to co-create value is the service value chain, making A the correct answer.

In ITIL 4, a service request is defined as a user request for information, advice, or a standard change, or for access to a service.

A user asking, “How do I create a report?” and contacting the service desk is:

Requesting information/advice

A normal, expected interaction with the service

Not reporting a service failure or interruption

Handling such requests is the purpose of the service request management practice, which ensures that:

Service requests are handled efficiently and user-friendly

Users receive help, information, or access according to agreed procedures

Requests follow pre-defined workflows where possible

Therefore, the practice most likely to help in solving this issue is C. Service request management.

Why the other options are incorrect:

A. Incident managementIncident management deals with unplanned interruptions, reductions in service quality, or failures. Here, the service is working; the user just needs guidance, not restoration of service.

B. Service level managementThis focuses on defining, negotiating, and managing service level agreements (SLAs) and overall service performance, not answering “how to” questions.

D. Change enablementThis practice manages changes to services and components, reducing risk. A user asking how to create a report is not requesting a change to the service.

References (Aligned with ITIL 4 Foundation concepts)

ITIL 4 Foundation: Definition of service request and service request management

ITIL 4 Foundation: Distinction between incidents and service requests

Organizations and people is one of the four dimensions of service management that influence the effectiveness and efficiency of service delivery1. This dimension focuses on the roles, responsibilities, and systems of authority that are needed to deliver and support services2. This dimension also covers the culture, skills, competencies, and collaboration of the people involved in service management3. References: ITIL Foundation - ITIL 4 Edition, page 8; ITIL® 4 – A Pocket Guide, page 19; ITIL® 4 Practice Guide: Organizational Change Management, page 7.

In ITIL 4, service relationships involve shared risks between service provider and service consumer. Both parties contribute to risk management.

Service consumers help mitigate risk by:

Clearly understanding and communicating their requirements

Being explicit about constraints, acceptable levels of performance, and critical outcomes

Ensuring that the provider knows what is truly needed, so services can be designed and delivered appropriately

Option C: “By being fully aware of their own requirements for the service” aligns with this: when consumers understand and clearly state their requirements, ambiguity and misalignment are reduced, which directly reduces risk in the service relationship.

Why the other options are incorrect:

A. Through the provision of services according to predefined needsProvision of services is the role of the service provider, not the consumer.

B. By ensuring that the service provider has configured correctly its resourcesResource configuration is the provider’s responsibility. The consumer may give feedback, but they don’t “ensure” correct configuration.

D. By controlling the specific level of risk on the service provider’s behalfThe provider manages its own risks. Risks are shared, but the consumer does not control the provider’s internal risk levels. The consumer contributes by clarifying requirements and using services as agreed.

References (Aligned with ITIL 4 Foundation concepts)

ITIL 4 Foundation: Service relationships – shared responsibility and shared risks between provider and consumer

ITIL 4 Foundation: Importance of clear requirements and expectations in reducing risks and enabling value co-creation

IT asset is any financially valuable component that can contribute to the delivery of an IT product or service. The scope of IT asset management typically includes all software, hardware, networking, cloud services, and client devices

https://wiki.process-symphony.com.au/framework/lifecycle/process/it-asset-management-itil-4/#:~:text=IT%20asset%20is%20any%20financially,cloud%20services%2C%20and%20client%20devices.