ITIL 4 Foundation (ITIL4F) — Questions 76–150

Problem Management includes the error control phase, which manages known errors and workarounds. Incident Management resolves incidents but does not formally manage workarounds for known errors. Change Enablement and Service Level Management are not responsible for workarounds.

Neglecting any dimension can lead to service quality issues or failure.

Shift-left is the correct concept because it refers to moving problem resolution activities earlier in the service lifecycle, specifically to the first point of contact (e.g., service desk). By empowering the service desk with better tools, knowledge, and automation, more incidents can be resolved without escalation, directly improving efficiency and first-contact resolution rates.

Governance is the component of the ITIL Service Value System (SVS) that is directly responsible for defining policies, setting strategic direction, and ensuring that those policies are implemented and enforced across the organization. While other SVS components execute or improve activities, governance provides the oversight and accountability mechanisms to align IT investments with business objectives.

The service desk is responsible for first-level support and resolution.

Data protection regulations like GDPR are legal frameworks that impose obligations on organizations regarding the processing and protection of personal data. In the PESTLE model, 'Legal' covers laws, regulations, and compliance requirements that directly affect IT service management, such as GDPR's requirements for data breach notification, consent management, and data subject rights.

Warranty in ITIL 4 refers to the assurance that a service will meet agreed-upon availability, capacity, continuity, and security requirements. A 99.99% uptime guarantee directly addresses the availability aspect of warranty, ensuring the service is reliable and accessible as promised.

Service Level Management is the ITIL 4 practice responsible for negotiating, agreeing, and monitoring Service Level Agreements (SLAs). It ensures that the agreed service levels are documented, tracked, and reported, aligning IT services with business expectations. This practice directly manages the lifecycle of SLAs, including their creation, review, and improvement.

When using a cloud service, the provider typically takes on risks like hardware failures, so the consumer no longer bears that risk.

Option C is correct because ITIL 4 emphasizes that all four dimensions (Organizations & People, Information & Technology, Partners & Suppliers, Value Streams & Processes) must be considered holistically to ensure a balanced approach. Neglecting any dimension can lead to service failures, such as implementing a new technology without considering the necessary skills (Organizations & People) or supplier dependencies (Partners & Suppliers). This balanced perspective prevents siloed thinking and ensures that services are designed, delivered, and improved effectively.

Standard changes are pre-approved, low-risk, and follow a documented procedure. This description matches a standard change.

IT Asset Management covers the full lifecycle of assets, including financial and contractual aspects.

An output (the system) does not always lead to a positive outcome. The doctors' increased workload is a negative outcome despite the system functioning.

'Collaborate and promote visibility' is shown by breaking silos and sharing information. 'Think and work holistically' is shown by considering the impact on security and the entire system.

The three change types are standard, normal, and emergency.

Service Level Management negotiates, agrees, and monitors SLAs with customers.

PESTLE includes Political, Economic, Social, Technological, Legal, and Environmental factors. Economic factors are external. Option B is correct.

Utility is defined as the functionality of a service to meet the consumer's needs (fit for purpose). Warranty is the assurance that a service meets agreed conditions (fit for use).

A service request is a formal request from a user for something to be provided – for example, for information, advice, or a standard change. In ITIL 4, provisioning a new laptop for a new employee is a pre-defined, low-risk, standard request that follows an approved procedure, making it a service request rather than a change or incident.

Resetting a password is a standard incident resolution activity within the incident management practice, as defined by ITIL 4. The agent is restoring normal service operation (user access) after an unplanned interruption (forgotten or locked password). Documenting the resolution in the ticket is a key step in the incident management process to ensure auditability and closure.

The primary purpose of Incident Management is to restore normal service operation as quickly as possible, minimizing the adverse impact on business operations. Option B is correct.

Warranty is the assurance that a service is 'fit for use', covering availability, capacity, continuity, and security. Utility is 'fit for purpose'.

The first step is to log the incident to initiate the Incident Management process and restore service.

Optimise and automate emphasizes first optimizing processes by removing non-value-adding steps before automating. The team is reviewing and eliminating waste, which is the optimization step.

Standard changes are pre-approved, low-risk, frequent changes that follow a defined procedure.

Problem Management involves root cause analysis and error control. Option B is correct because documenting known errors and workarounds is part of error control. Option A is an incident management activity; Option C is a change enablement activity; Option D is service request management.

The chatbot is a specific technology tool that handles IT service requests, directly aligning with the 'Information and Technology' dimension. This dimension covers the technology architecture, applications, and data used to deliver and manage services. The chatbot represents an application or software component that processes and automates service interactions, making it a clear fit for this dimension.

The primary purpose of Incident Management is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations. This is defined in ITIL 4 as the core objective of the practice, focusing on speed of recovery rather than root cause analysis or change control.

Availability Management ensures that services are available as agreed, managing planned and unplanned downtime.

PESTLE is a strategic analysis framework used in the 'Four Dimensions of IT Service Management' to assess external factors that can impact service management. Technological advancements are explicitly one of the six PESTLE factors (Political, Economic, Social, Technological, Legal, Environmental), making option A correct because it directly corresponds to the 'Technological' dimension of the model.

Capacity and Performance Management ensures that services perform at the required level to meet demand. Availability Management focuses on uptime, not performance.

Warranty is about the assurance that a service will meet agreed requirements, including availability, capacity, security, and continuity. Uptime guarantee is a warranty aspect.

Service Configuration Management is the ITIL 4 practice responsible for maintaining accurate and reliable information about configuration items (CIs) throughout their lifecycle. It ensures the CMDB reflects the current state of CIs, including relationships and attributes, by controlling updates through defined processes and audits. Outdated CI data directly indicates a failure in this practice's core function of configuration control and status accounting.

Standard changes are routine, pre-approved changes that follow a defined procedure and have low risk, such as password resets or adding a user to a group.

Cloud computing platforms (A) are a core component of the 'Information and Technology' dimension, which covers the technical infrastructure, applications, and data management used to deliver services. This dimension includes hardware, software, networks, and cloud services that enable service delivery and support.

Utility is about fit for purpose (what the service does), while warranty is about fit for use (how it performs). The app works but is not usable, which is a warranty issue.

The ITIL 4 SVS includes guiding principles, governance, service value chain, practices, and continual improvement. Outputs and SLAs are not components of the SVS.

According to ITIL 4, the first action when a service disruption is reported is to log an incident record and attempt to restore service as quickly as possible. This aligns with the incident management practice, which prioritizes minimizing business impact over root cause analysis. The analyst should immediately create an incident ticket and apply a workaround or fix to restore CRM access.

Problem Management (D) is the correct practice because the issue of recurring rework and delays indicates underlying root causes that are not being addressed. Problem Management focuses on identifying and eliminating the root causes of incidents, which reduces the need for rework and prevents future incidents, directly improving efficiency.

Emergency changes are for urgent situations like security patches; they follow a faster authorization process.

Governance evaluates, directs, and monitors the organization's activities to align with strategy.

First Contact Resolution (FCR) measures the percentage of incidents resolved on the first contact with the service desk.

The Plan activity ensures that vision, objectives, and strategies are defined and aligned with organizational goals.

Option C is correct because ITIL 4 defines an incident as an unplanned interruption to a service, and the analyst's first priority is to restore normal service operation as quickly as possible. Logging an incident record ensures the issue is tracked, prioritized, and escalated if needed, while attempting to restore service (e.g., by reverting a configuration or applying a workaround) aligns with the 'Focus on value' and 'Progress iteratively with feedback' guiding principles. This immediate action minimizes business impact before any root cause analysis or change management is initiated.

Service Level Management involves negotiating SLAs, monitoring service performance, and reporting results. Defining service metrics is part of service design, not a direct activity of SLA management.

Warranty covers availability, capacity, continuity, and security. Utility covers functionality.

The ITIL 4 Service Value System (SVS) is designed as a holistic model to facilitate value co-creation through IT-enabled services. It integrates all components and activities of an organization—such as guiding principles, governance, service value chain, practices, and continual improvement—to work together in a coordinated way, ensuring that every element contributes to creating value for stakeholders. This is the primary purpose, as the SVS is not about defining every process or replacing practices, but about enabling the flexible and effective co-creation of value.

The Service Value System (SVS) is the core architectural model in ITIL 4 that describes how all components and activities of an organization work together to facilitate value co-creation through service management. It provides a holistic, flexible framework that integrates the guiding principles, governance, service value chain, practices, and continual improvement to enable the creation, delivery, and improvement of services that generate value for stakeholders.

An informational event is used to notify that a predefined threshold has been reached but does not require immediate action. In this case, 85% disk usage is a standard monitoring threshold that indicates a normal operational state, not a failure or critical condition. ITIL 4 defines informational events as those that provide awareness of a situation that is within normal operating parameters.

The first step is to log an incident to document the service interruption. Investigating the cause (problem) or planning a change comes later.

ITIL 4 defines value as perceived benefits, usefulness, and importance. Costs and risks are factors that affect value, but they are not components; value is about benefits and outcomes.

The 'Plan' activity ensures a shared understanding of the vision, current status, and improvement direction for all services and products.

Problem management aims to identify the root causes of incidents and prevent recurrence or reduce impact. Restoring service is the purpose of incident management.

Option B is correct because 'Organizations and People' is explicitly defined in ITIL 4 as one of the four dimensions of service management. These four dimensions—Organizations and People, Information and Technology, Partners and Suppliers, and Value Streams and Processes—ensure a holistic approach to service management by covering all aspects of service delivery. Without the Organizations and People dimension, the human and cultural factors critical to effective service management would be overlooked.

Collaborate and promote visibility directly addresses breaking silos and making information accessible. Think and work holistically is also relevant because it encourages understanding how changes in one area affect the whole. The other principles are less directly related.

The ITIL continual improvement model is a structured seven-step process (What is the vision?, Where are we now?, Where do we want to be?, How do we get there?, Take action, Did we get there?, How do we keep the momentum going?) that is explicitly defined within the Continual Improvement practice. This practice is the owner of the model, providing the framework for identifying and executing improvements across all other ITIL practices.

IT Asset Management manages the lifecycle of assets, including hardware such as servers.

Option B is correct because a service request in ITIL 4 is a standardized, pre-defined request from a user for information, advice, access, or a change that does not require urgent or root-cause analysis. A new laptop for a new hire is a typical example of a standard change that is pre-approved and follows a predefined workflow, aligning with the ITIL 4 definition of a service request as a low-risk, routine request that is handled through a request fulfillment process.

Governance is the component of the ITIL 4 Service Value System (SVS) that evaluates, directs, and monitors the organization's activities. It provides the framework for decision-making and ensures that the organization's efforts are aligned with its strategic objectives and stakeholder needs. Without governance, there would be no authoritative guidance on how to prioritize or steer service management activities.

A service request is a formal request for something to be provided – for example, a request for information, advice, or access to a service. Standard changes are also pre-approved, but service requests are typically for low-risk, routine tasks that are well-understood and pre-authorized.

PESTLE stands for Political, Economic, Social, Technological, Legal, Environmental.

Option C is correct because outcome is the result for stakeholders, and here users are not experiencing the intended benefit. Output is the deliverable (the feature), but without a positive outcome the service is not successful. Utility and warranty are about functionality and assurance, not specifically the value realisation.