Free ITIL ITIL-4-Foundation Practice Exam with Questions & Answers

A help desk is considered to be focused on break-fix (what ITIL calls incident management), whereas a service desk is there to assist with not only break-fix but also with service requests (requests for new services) and requests for information (such as “how do I do X?”).

https://www.atlassian.com/itsm/service-request-management/help-desk-vs-service-desk-vs-itsm#:~:tex t=A%20help%20desk%20is%20considered,I%20do%20X%3F%E2%80%9D).

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 ‘progress iteratively with feedback’ guiding principle encourages organizations to break down complex initiatives into smaller, simpler, and more manageable units of work1. This principle also recommends seeking and acting on feedback from stakeholders, avoiding big-bang approaches, and adapting plans based on new information2. However, this principle does not advise prohibiting changes to plans, analysing the whole situation in detail, or reducing the number of steps that produce tangible results, as these would be contrary to the iterative and adaptive nature of this principle3. References: ITIL Foundation - ITIL 4 Edition, page 7; ITIL® 4 – A Pocket Guide, page 27; ITIL® 4 Practice Guide: Progress Iteratively with Feedback, page 9.

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/

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

The problem management practice follows a three-phase approach to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents and managing workarounds and known errors1. The three phases are:

Problem identification: the process of finding problems that are the cause or potential cause of one or more incidents2.

Problem control: the process of analysing the root cause and impact of a problem and developing a workaround or a permanent solution2.

Error control: the process of managing known errors throughout their lifecycle, from recording to removal2. References: ITIL Foundation - ITIL 4 Edition, page 15; ITIL® 4 – A Pocket Guide, page 35; ITIL® 4 Practice Guide: Problem Management, page 9.

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.