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

Obtain/build is one of the six activities of the service value chain, which is a set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization1. Obtain/build activity relates with buying new products, as well as designing, developing, and testing new or changed service components2. This activity ensures that service components are available when and where they are needed and meet agreed specifications3. References: ITIL Foundation - ITIL 4 Edition, page 10; ITIL® 4 – A Pocket Guide, page 21; ITIL® 4 Practice Guide: Service Value Chain, page 9.

An outcome is a result for a stakeholder enabled by one or more outputs1. Outputs are tangible or intangible deliverables of an activity1. For example, a service provider may produce a report (output) that helps a customer make a decision (outcome)2. References: ITIL Foundation - ITIL 4 Edition, page 3; ITIL® 4 – A Pocket Guide, page 13.

Emergency changes. These are changes that must be implemented as soon as possible; for example, to resolve an incident or implement a security patch. Emergency changes are not typically included in a change schedule, and the process for assessment and authorization is expedited to ensure they can be implemented quickly. As far as possible, emergency changes should be subject to the same testing, assessment, and authorization as normal changes, but it may be acceptable to defer some documentation until after the change has been implemented, and sometimes it will be necessary to implement the change with less testing due to time constraints. There may also be a separate change authority for emergency changes, typically including a small number of senior managers who understand the business risks involved.”

https://itsm.tools/why-what-change-management/#:~:text=Emergency%20changes. &text=Emergency%20changes%20are%20not%20typically,they%20can%20be%20implemented%20quickly.

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-enablem ent/#:~:text=The%20change%20schedule%20is%20used,problem%20management%2C%20and%20improvement%20planning.

A change is defined as the addition, modification, or removal of anything that could have a direct or indirect effect on services

https://www.bmc.com/blogs/itil-change-enablement/#:~:text=A%20change%20is%20defined%20as,or%20indirect%20effect%20on%20services.

Effective incident management often requires a high level of collaboration within and between teams as this can facilitate information-sharing and learning, as well as helping to solve the incident more efficiently and effectively. There may also be a need for good collaboration tools so that people working on an incident can work together effectively. One technique that takes advantage of collaboration is termed swarming. This brings many different stakeholders together to work on the issue. Management of incidents may require frequent interaction with third party suppliers, and routine management of this aspect of supplier contracts is often part of the incident management practice.

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

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.

Utility is the term used to describe the functionality of a service, or how well it meets the needs and expectations of the customers and users. Utility can be expressed as ‘what the service does’ or 'the functionality offered by a product or service to meet a particular need’1. Utility is one of the two elements of service value, along with warranty2. References: ITIL Foundation - ITIL 4 Edition, page 4; ITIL® 4 – A Pocket Guide, page 14.

The purpose of the service level management 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 targets1. This practice conducts reviews to validate that services are covering the needs of the customer and to identify areas for improvement2. References: ITIL Foundation - ITIL 4 Edition, page 16; ITIL® 4 – A Pocket Guide, page 37; ITIL® 4 Practice Guide: Service Level 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 .