ITIL-4-Foundation ITIL 4 Foundation Exam Questions and Answers

In ITIL 4, the service level management practice is responsible for:

Setting clear, business-based targets for service performance

Monitoring and reporting on service delivery

Conducting regular reviews with customers and stakeholders

Ensuring that services and service performance meet agreed needs and expectations

Part of this practice explicitly involves reviewing services with customers to validate that the services are still meeting their needs and agreed service levels. These reviews are used to confirm whether the services remain fit for purpose and to identify improvement opportunities.

The other options have different focuses:

Monitoring and event management focuses on observing services and infrastructure, identifying events, and determining their significance.

Change enablement controls risks related to changes and ensures that changes are properly assessed and authorized.

Service desk is the main point of contact between service provider and users, handling incidents and service requests, but it is not primarily responsible for formal reviews of service coverage against customer needs.

Because the described activity—conducting reviews to ensure services cover customer needs—is a core responsibility of service level management, the correct answer is B.

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/

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/

Comprehensive and Detailed Explanation From Exact Extract:

In ITIL 4, the monitoring and event management practice is concerned with the systematic observation of services and service components. Its purpose is described as:

Continuously monitoring services and infrastructure.

Identifying and capturing changes of state in these components.

Classifying certain changes of state as events, which are then recorded, reported, and, where necessary, acted upon.

This practice enables early detection of issues, supports automated responses where appropriate, and helps maintain the normal operation and performance of services.

Option C accurately reflects this purpose, so it is correct.

The other options describe the purposes of different ITIL practices:

A – This is the purpose of incident management (restoring normal service operation quickly to minimize impact).

B – This is the purpose of service request management (handling user-initiated service requests effectively).

D – This is the purpose of change enablement (ensuring successful changes through proper risk assessment and authorization).

Relevant ITIL 4 Foundation references:

Monitoring and event management practice: purpose and key activities.

Purpose statements for incident management, service request management, and change enablement practices (for comparison).

The incident management practice aims to minimize the negative impact of incidents by restoring normal service operation as quickly as possible1. A complex or 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. This may require a temporary team to work together, such as a major incident team or a swarming team3. References: ITIL Foundation - ITIL 4 Edition, page 14; ITIL® 4 – A Pocket Guide, page 32; ITIL® 4 Practice Guide: Incident Management, page 8.

More complex incidents will usually be escalated to a support team for resolution, or even suppliers and partners who offer support for products and services they provide.

This question is testing your understanding of the ITIL 4 guiding principle “Start where you are.”

The essence of this principle is that an organization should not start from scratch when making improvements. Instead, it should first look at and assess what already exists — current services, processes, tools, and methods — before deciding what to keep, change, or replace.

The ITIL 4 Foundation guidance explains that organizations should carefully consider the existing state before designing the future state. It stresses that existing practices, services, and tools may already contain value, and that blindly discarding them can lead to waste, increased risk, or loss of useful knowledge.

In that context, the most accurate word to complete the sentence is:

An organization which is undertaking an improvement initiative should consider the existing methods and services when building for the future.

“Consider” reflects the idea of evaluating and understanding what already exists before making decisions.

The principle does not state that everything must be re-used or improved; some things may be retained, some modified, and some removed. But the key is that they must be considered first.

B. DiscardThis directly contradicts the principle “Start where you are.” ITIL explicitly warns against discarding existing methods and services without first understanding and assessing them.

C. Re-useWhile re-use is often a possible outcome of applying this principle, it is not mandatory that all existing methods and services be re-used. The principle is about assessing and considering them first, then deciding what to keep, change, or retire. Therefore, “re-use” is too narrow for the sentence.

D. ImproveImprovement may be needed, but you cannot decide how to improve something until you have considered and understood its current state. The guiding principle’s wording focuses first on consideration/evaluation of what already exists.

Therefore, the correct choice that best matches the intent and wording of the ITIL 4 guiding principle “Start where you are” is:

A. Consider

References (Aligned with ITIL 4 Foundation Concepts)

ITIL 4 Foundation: Guiding principles – Start where you are (discussion on assessing and considering existing services, processes, and methods before designing the future state)

ITIL 4 Foundation: Emphasis on avoiding starting from scratch and avoiding unnecessary waste by considering the current situation before making changes.

https://assyst.ifs.com/blog/the-7-guiding-principles-of-itil-4-0

Don ' t over-engineer solutions. Think about what you can do now.

Like focus on value, this principle is heavily focused on the prevention of waste. Waste correlates with complexity. Higher complexity means there are more opportunities for waste to creep into a system.

Focus on delivering the desired outcome, not building the most elegant and elaborate solution. Use the minimum number of steps to deliver that outcome, ensuring you are not over-processing (delivering quality above and beyond what is required).

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.

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

The purpose of the service configuration management practice is to ensure that accurate and reliable information about the configuration of IT assets, and the relationships that support them, is available when and where it is needed1. IT assets are any financially valuable components that can contribute to the delivery of an IT product or service2. Configuration items are any component that needs to be managed in order to deliver an IT service3. References: ITIL Foundation - ITIL 4 Edition, page 15; ITIL® 4 – A Pocket Guide, page 36; ITIL® 4 Practice Guide: Service Configuration Management, page 7.

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)

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/

In ITIL 4, guiding principles are defined as recommendations that guide an organization in all circumstances, regardless of changes in goals, strategies, work type, or management structure. They are explicitly intended to support decision-making and actions at all levels of the organization.

The guiding principles help people decide:

How to approach work

How to prioritize activities

How to respond to challenges or opportunities

How to adapt service management practices to the organization’s context

The other options are important ITIL concepts, but they do not primarily exist to guide decisions in every situation:

Four dimensions of service management give a holistic view of what must be considered, but do not themselves provide decision rules.

Service value chain describes core activities that create value, not a decision framework.

Practices describe how specific types of work are organized, not general decision guidance.

Therefore, the ITIL concept that helps an organization make good decisions in all circumstances is the guiding principles.

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

The purpose of the monitoring and event management practice is to systematically observe services and service components and record and report selected changes of state identified as events1. This practice helps to identify and prioritize any issues or opportunities for improvement in the delivery or support of services2. The other statements describe the purposes of different practices: incident management (A), service request management (B), and change enablement (D)3. References: ITIL Foundation - ITIL 4 Edition, page 14; ITIL® 4 – A Pocket Guide, page 31; ITIL® 4 Practice Guide: Monitoring and Event Management, page 7.

The change schedule is used to help plan changes, assist in communication, avoid conflicts, and assign resources. It can also be used after changes have been deployed to provide information needed for incident management, problem management, and improvement planning

https://www.bmc.com/blogs/itil-change-enablement/#:~:text=The%20change%20schedule%20is%20used,problem%20management%2C%20and%20improvement%20planning.

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/

In ITIL 4, service request management is one of the 7 practices described in more detail.

A service request is defined as a user request for something to be provided – for example:

access to an application or file

information or advice

a standard change that is preapproved

a new or replacement item of equipment

The key idea is:

A service request is a formal request from a user for something they are entitled to receive as part of a service.

Looking at each option:

This describes an incident.

An incident is an unplanned interruption to a service or reduction in its quality.

A request to restore normal service operation after something has gone wrong is handled by the incident management practice, not by service request management.

So this is not a service request.

This normally relates to a change.

Implementing a patch modifies the live environment.

This is usually handled through the change enablement practice (and then deployment management), often as a normal change or standard change, depending on the organization’s policies.

Although some standard changes can be triggered via service requests, ITIL Foundation typically uses clearer examples (such as access requests). This option is not the best example.

This is a classic example of a service request:

A user is asking for access (permission) to something as part of an existing service.

It is not fixing something broken, it is asking for something to be provided.

ITIL 4 explicitly lists access requests (for example, to applications, services, or data) as a common type of service request within the service request management practice.

Therefore, C is the correct answer.

This describes problem management:

When we investigate the root cause of one or more incidents, we are using the problem management practice.

The aim is to understand and remove the underlying cause, not to provide a standard service action requested by a user.

So this is not a service request.

This aligns with ITIL 4 Foundation descriptions of:

Service request – a user request for something to be provided.

Service request management practice – managing all types of service requests in a user-friendly and efficient way.

Incident management – restoring normal service operation as quickly as possible.

Problem management – identifying and managing the causes of incidents.

Change enablement – ensuring that changes are evaluated, authorized, and managed.

That is why “a request for access to a file” is the correct example of a service request.

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/

The purpose of the service configuration management practice is to ensure that accurate and reliable information about the configuration of services, and the CIs that support them, is available when and where it is needed. This includes information on how CIs are configured and the relationships between them.

https://wiki.process-symphony.com.au/framework/lifecycle/process/service-configuration-management-itil-4/

The ITIL guiding principle ‘focus on value’ states that everything an organization does should link back, directly or indirectly, to value for itself, its customers, and other stakeholders1. A good way to apply this principle is to understand why services are used by service consumers, what outcomes they enable, and how they contribute to value creation2. This helps to align the service provider’s activities and resources with the needs and preferences of the service consumers3. References: ITIL Foundation - ITIL 4 Edition, page 6; ITIL® 4 – A Pocket Guide, page 24; ITIL® 4 Practice Guide: Focus on Value, page 9.

To protect the information needed by the organization to conduct its business. This includes understanding and managing risks to the confidentiality, integrity, and availability of information, as well as other aspects of information security such as authentication and non-repudiation.

https://www.bmc.com/blogs/itil-management-practices/

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

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

The purpose of the improve value chain activity is to ensure continual improvement of products, services, and practices across all value chain activities and the four dimensions of service management.

https://wiki.process-symphony.com.au/framework/lifecycle/service-value-systemitil-4/#:~:text=The%20purpose%20of%20the%20improve,four%20dimensions%20of%20service%20management.

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.

Individual metrics without a specified service context are unhelpful. They should relate to defined outcomes and not simply operational metrics. This can be achieved with balanced bundles of metrics, such as customer satisfaction and key business outcomes.

https://www.bmc.com/blogs/itil-service-level-management/#:~:text=Service%20Level%20Agreements%20(SLAs) & text=Individual%20metrics%20without%20a%20specified,satisfaction%20and%20key%20business%20outcomes.

The purpose of the continual improvement practice is to align the organization’s practices and services with changing business needs through the ongoing identification and improvement of services, service components, practices, or any element involved in the efficient and effective management of products and services1. This practice needs the right culture to be embedded across the entire organization, as it requires a shared vision, commitment, empowerment, collaboration, learning, and measurement2. References: ITIL Foundation - ITIL 4 Edition, page 15; ITIL® 4 – A Pocket Guide, page 34; ITIL® 4 Practice Guide: Continual Improvement, page 7.

Incident management is typically closely aligned with the service desk, which is the single point of contact for all users communicating with IT. When a service is disrupted or fails to deliver the promised performance during normal service hours, it is essential to restore the service to normal operation as quickly as possible.

https://www.bmc.com/blogs/itil-v3-incident-management/