[Feb 25, 2026] Pass ITIL ITIL-4-Foundation Exam Info and Free Practice Test [Q21-Q40]

Reference: https://www.bmc.com/blogs/itil-problem-management/

Reference: https://www.knowledgehut.com/tutorials/itil4-tutorial/it-service-management-concepts

A set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization
https://www.bmc.com/blogs/itil-service-value-system/#:~:text=The%20key%20inputs%20to%20the,or%20other

A user is a person who uses services on a day-to-day basis. Users are distinct from customers, as some customers do not use the service directly1. Users are one of the key stakeholders in service management2. Reference: ITIL Foundation – ITIL 4 Edition, page 5; ITIL\ 4 – A Pocket Guide, page 18.

The service request management practice supports the agreed quality of a service by handling all pre-defined, user-initiated service requests in an effective and user-friendly manner1. A service request is a request from a user or a user’s authorized representative that initiates a service action that has been agreed as a normal part of service delivery2. A user wanting to know how to create a report is an example of a service request that can be handled by the service request management practice3. The other statements are not true because:
* Incident management: The incident management practice restores normal service operation as quickly as possible after an interruption or reduction in quality of an IT service1. A user wanting to know how to create a report is not an incident, as it does not affect the availability or performance of a service2.
* Service level management: The service level management practice sets clear business-based targets for service performance, so that the delivery of a service can be properly assessed, monitored, and managed against these targets1. This practice does not directly handle user requests, but it may define the service level agreements (SLAs) and service level objectives (SLOs) that apply to them2.
* Change enablement: The change enablement practice maximizes the number of successful service and product changes by ensuring that risks have been properly assessed, authorized, and managed within a schedule1. A change is the addition, modification, or removal of anything that could have a direct or indirect effect on IT services2. A user wanting to know how to create a report is not a change, as it does not alter the configuration or functionality of a service component2. References: ITIL Foundation – ITIL 4 Edition, page 16; ITIL4 – A Pocket Guide, page 37; ITIL4 Practice Guide: Service Request Management, page 7.

Nonrepudiation provides an assurance that the sender of data is provided with proof of delivery and the recipient is provided with proof of the sender’s identity, so neither can later deny having processed the data. Further, this concept can apply to any activity, not just the sending and receiving of data; in a more general sense, it is a mechanism to prove that an activity was performed and by whom. Nonrepudiation is typically comprised of authentication, auditing/logging, and cryptography services.
https://www.sciencedirect.com/topics/computer-science/nonrepudiation

The purpose of ‘obtain/build’ value chain activity is “to ensure that service components are available when and where they are needed, and meet agreed specifications.” Service components for ‘deliver and support’ and service components for design and transition are key outputs of ‘obtain/build’ value chain activity.

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/

Explanation
The purpose of the release management practice is to make new and changed services and features available for use.
Release: A version of a service or other configuration item, or a collection of configuration items, that is made available for use.
https://wiki.process-symphony.com.au/framework/lifecycle/process/release-management-itil-4/