ITIL-4-Foundation ITIL 4 Foundation Exam Free Practice Exam Questions (2025 Updated)

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.

The ITIL SVS describes how all the components and activities of the organization work together as a system to enable value creation.

The SVS is made up of specific inputs, elements, and outputs relevant to service management. The key inputs to the SVS are opportunity and demand. The output of the SVS is value delivered by products and services.

Opportunity refers to options or possibilities to add value for stakeholders or otherwise improve the organization.

Demand refers to need or desire for products and services among internal and external consumers.

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

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.

Taking a holistic approach to service management includes establishing an understanding of how all the parts of an organization work together in an integrated way (remember the four dimensions of service management?), including having an end-to-end visibility of how demand is captured and translated into outcomes. In a complex system, the alteration of one element can impact others and, where possible, these impacts need to be identified, analysed and planned for.

To apply this principle successfully, consider this advice:

Recognize the complexity of the systems

Collaboration is key to thinking and working holistically

Where possible, look for patterns in the needs of and interactions between system elements

Automation can facilitate working holistically

https://www.bmc.com/blogs/itil-guiding-principles/

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

When focusing on value, the first step is to know who are the customers and key stakeholders being served. Next, it is important to have an understanding of what consitutes value from the consumer’s perspective.

https://www.bmc.com/blogs/itil-guiding-principles/#:~:text=When%20focusing%20on%20value%2C%20the,value%20from%20the%20consumer 's%20perspective.

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 problem management practice is to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents and managing workarounds and known errors1. Workarounds are temporary solutions that reduce or eliminate the impact of an incident or problem for which a full resolution is not yet available2. Known errors are problems that have a documented root cause and a workaround3. References: ITIL Foundation - ITIL 4 Edition, page 15; ITIL® 4 – A Pocket Guide, page 35; ITIL® 4 Practice Guide: Problem Management, page 7.

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.

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.

A service request is defined as a request from a user or a user’s authorized representative that initiates a service action which has been agreed as a normal part of service delivery.

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/

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.

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.

A known error is a problem that has been analysed but not resolved1. This means that the root cause of the problem has been identified, but a permanent solution has not been implemented yet2. A known error can be recorded in a known error database (KEDB) and linked to related incidents and problems3. References: ITIL Foundation - ITIL 4 Edition, page 15; ITIL® 4 – A Pocket Guide, page 35; ITIL® 4 Practice Guide: Problem Management, page 8.

A service level agreement (SLA) is a documented agreement between a service provider and a customer that identifies both services required and the expected level of service1. A necessity to a successful SLA is that the language and terms used in the SLA should be commonly understood by all parties, to avoid ambiguity, confusion, and disputes2. The other statements are not true because:

Base the SLA on system-based metrics that are useful to the service provider: The SLA should be based on customer-based metrics that are meaningful to the customer and reflect the value of the service2.

In order to promote consistent service, they should be carried forward, unchanged, from one year to the next: The SLA should be reviewed and updated regularly to reflect changing business needs, customer expectations, and service performance2.

Vague targets, such as those related to user experience should be avoided: The SLA should include both quantitative and qualitative targets, such as those related to user experience, satisfaction, and perception, as well as availability, reliability, and security2. References: ITIL Foundation - ITIL 4 Edition, page 16; ITIL® 4 – A Pocket Guide, page 37; ITIL® 4 Practice Guide: Service Level Management, page 8.