Pass the ITIL ITIL 4 ITIL-4-Foundation Questions and answers with CertsForce

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 .

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.

You need to use all of your resources as effectively and efficiently as you can. This means that you should automate wherever you can, and use people only for tasks that can’t be automated. It also means that you need to think carefully about what you can automate and about the circumstances where only a person will do; and about simplifying those processes you do decide to automate to eliminate wasteful or inefficient steps.

You should always optimize the work BEFORE you automate it, as automating something that is inefficient or ineffective may just result in you doing the wrong thing faster!

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

The service desk practice provides a single point of contact for users and customers to report issues, make requests, or seek guidance1. This practice guarantees that users have a range of access channels to choose from to report problems, such as phone, email, web portal, chatbot, or self-service2. This helps to improve user satisfaction, reduce frustration, and increase efficiency3. References: ITIL Foundation - ITIL 4 Edition, page 14; ITIL® 4 – A Pocket Guide, page 32; ITIL® 4 Practice Guide: Service Desk, page 7.

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. Change authorization is the activity of verifying that a proposed change is desirable, viable, and achievable before committing to its implementation2. The change type (standard, normal, or emergency) and model (a predefined approach for handling a specific type of change) is the basis for assigning the change authority (the role that can authorize a change)2. The other statements are incorrect because:

A standard change is a low-risk, pre-authorized change that follows an agreed procedure and does not require authorization at the point of implementation2.

An emergency change is a high-priority change that must be implemented as soon as possible to resolve an incident or implement a security patch2. An emergency change must be authorized by an emergency change authority (ECA), which is usually a subset of the normal change authority (CAB)2.

Ensuring that changes are authorized before their deployment is done by the change enabler (the role that coordinates all aspects of a change)2. References: ITIL Foundation - ITIL 4 Edition, page 16; ITIL® 4 – A Pocket Guide, page 39; ITIL® 4 Practice Guide: Change Enablement, page 7.

ITIL® defines a problem as a cause, or potential cause, of one or more incidents. A known error is a problem that has been analyzed but not resolved.

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