ITIL 4 Foundation (ITIL4F) — Questions 1–75

This is the correct explanation. ITIL 4 categorizes changes to strategically balance the need for rapid service delivery with the imperative for thorough risk assessment. Standard changes are pre-authorized and low-risk, allowing for speed and efficiency. Normal changes undergo detailed assessment and authorization to manage significant risks effectively. Emergency changes prioritize speed for critical fixes, accepting a higher initial risk for rapid resolution, with formal review often occurring post-implementation to ensure governance. This approach ensures appropriate governance for each change type.

Service Level Management handles SLAs and monitoring of service levels.

This is the precise and primary purpose of the Incident Management practice according to ITIL 4. Its objective is to ensure that any unplanned interruption or reduction in the quality of an IT service is resolved swiftly, restoring functionality to an agreed-upon service level. By focusing on rapid restoration, Incident Management minimizes the negative impact on business operations, user productivity, and overall service value.

The Service Value Chain is a central element of the SVS.

Tools are part of this dimension.

A service request is a formal request from a user for something that is a normal part of service delivery, typically pre-defined, pre-approved, and often automated. Requesting a new laptop falls squarely into this category, as it's a standard offering within the service catalog, handled efficiently by the Service Request Management practice. These requests are usually low-risk, frequently occurring, and have a clear, established fulfillment process.

Practices are a component of the SVS.

A normal change is any change that is not standard or emergency, requiring a full assessment, authorization, and scheduling process. This type of change typically involves a structured workflow, including planning, risk and impact analysis, approval by a change authority (such as a Change Advisory Board or CAB), and careful coordination. Replacing a critical server, given its potential impact and the need for careful planning and approval, perfectly aligns with the characteristics and rigor of a normal change.

Continual Improvement is the ITIL 4 practice explicitly dedicated to aligning an organization's practices and services with changing business needs through ongoing, iterative improvement. It directly utilizes the ITIL Continual Improvement Model, which is a seven-step framework guiding all improvement initiatives from defining the vision to sustaining momentum. This model provides a structured approach for identifying, planning, implementing, and reviewing improvements across the entire service value system.

Guiding Principles are universal recommendations that guide an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure. They promote good decision-making and behavior across the entire service management ecosystem, ensuring a consistent approach to value creation. These principles are fundamental to how an organization approaches service management and value co-creation.

First Contact Resolution (FCR) is a crucial service desk metric that measures the percentage of requests or incidents resolved entirely during the initial interaction, directly reflecting efficiency and user convenience. Customer Satisfaction (CSAT) gauges how pleased users are with the service received, often collected immediately after resolution. For a password reset, successfully resolving it on the first contact and ensuring the user is satisfied are primary indicators of effective service desk performance and value delivery.

Managing supplier contracts is a fundamental and integral activity within the Supplier Management practice. This involves the entire lifecycle of contracts, from negotiation and establishment to ongoing administration, amendment, and eventual termination. Effective contract management ensures that terms, conditions, and service expectations are clearly defined, legally binding, and consistently met by external providers, safeguarding the organization's interests and service delivery.

One of the five SVS components.

A service request is a pre-defined, pre-approved request from a user for information, advice, or a standard change, such as the provision of a new user account. These requests are typically low-risk, routine, and often fulfilled through automated processes or simple, well-documented procedures. Creating a new user account perfectly aligns with the definition of a standard service offering.

Standard changes are pre-approved and low risk.

Warranty assures that a service is 'fit for use,' meaning it meets agreed-upon performance characteristics and non-functional requirements. This includes aspects like service availability, capacity, continuity, and security, ensuring the service performs reliably and consistently as expected by the consumer. It provides confidence that the service will not fail or be unduly interrupted during its operation.

Standard changes are pre-authorized and have a low risk.

The SVS provides a holistic model for value creation.

The core purpose of a Service Level Agreement (SLA) is to formally document the mutually agreed-upon service targets and responsibilities between a service provider and its customer. This includes critical metrics such as availability, performance thresholds, incident response times, and problem resolution targets, establishing clear expectations and providing a basis for measuring service quality and accountability from the customer's perspective.

Problem Management is the ITIL practice dedicated to reducing the likelihood and impact of incidents by identifying and resolving their underlying causes. Investigating recurring network outages directly aligns with its objectives, which include performing root cause analysis, managing known errors, and implementing permanent solutions. This proactive approach aims to prevent future incidents and improve overall service stability, making it the correct practice for this scenario.

Incident Management is the practice responsible for minimizing the negative impact of incidents by restoring normal service operation as quickly as possible. Its core objective is rapid service restoration, which frequently involves applying pre-identified workarounds or temporary fixes to mitigate the immediate disruption. Therefore, applying a workaround to restore service after a major incident is a direct and critical function of Incident Management, ensuring business continuity.

Utility, in ITIL 4, precisely defines whether a service is "fit for purpose." This means the service provides the required functionality and performs as specified to support the consumer's objectives. It addresses the "what" the service does, delivering the specific outcomes and value that the consumer needs to achieve their goals. Without adequate utility, a service cannot truly meet the consumer's fundamental requirements.

A Standard change is pre-authorised and follows a defined, low-risk procedure, satisfying the stem’s constraint that no formal change request is needed. This contrasts with a Normal change, which always requires a formal request and approval, and an Emergency change, which demands urgent authorisation. The axis of difference is the pre-approval status: Standard changes are approved in advance by the change authority, enabling implementation without a new request each time.

This is indeed the primary purpose of the Incident Management practice. Its core objective is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible, thereby ensuring business continuity and maintaining user productivity. This involves rapid diagnosis, workaround implementation, and resolution to return services to their agreed-upon functional state.

This option correctly differentiates between an incident and a service request according to ITIL 4 principles. A password reset is a common, pre-defined user request for a standard service, accurately categorized as a service request. Reporting that the email system is down, however, signifies an unplanned interruption to a critical service, which is precisely what defines an an incident requiring prompt resolution to restore functionality.

The consumer no longer bears the cost of owning and maintaining servers.

Value represents the perceived benefits, usefulness, and importance of something to a stakeholder, derived from balancing the benefits, costs, and risks. An IT department decides to implement a new monitoring tool because they anticipate it will deliver greater value, such as improved operational efficiency, enhanced problem detection, or better risk management, which are expected to outweigh the investment and potential challenges. This decision is fundamentally driven by the expectation of creating or realizing this net positive outcome.

FCR measures the percentage of issues resolved on the first call.

Utility is the correct ITIL 4 concept that describes the functionality offered by a product or service to meet a particular need. It defines 'what the service does' and determines whether it is 'fit for purpose.' This concept directly addresses the inherent capabilities and features that allow a service to perform its intended functions and support the consumer's tasks.

Guiding principles are a component of the SVS.

Logging the incident is the foundational first step in the Incident Management practice. It ensures that the service disruption is formally recorded, assigned a unique identifier, and tracked through its entire lifecycle. Capturing relevant details like user contact, symptoms, and impact is crucial for effective diagnosis, communication, and eventual resolution, aligning with the practice's objective of restoring normal service operation as quickly as possible.

The shift-left strategy aims to empower the lowest possible support tier, typically the service desk or first-line support, to resolve a higher percentage of incidents and service requests. By providing these teams with enhanced knowledge, tools, and training, issues are addressed at the initial point of contact. This reduces the need for costly and time-consuming escalations to specialized second or third-line support, improving efficiency and customer satisfaction.

Incident Management's primary objective is to restore normal service operation as quickly as possible, minimizing business impact. Conversely, Problem Management focuses on identifying and understanding the root causes of incidents to prevent their recurrence or minimize their impact. This clear division ensures both immediate recovery and long-term service stability by addressing symptoms and underlying issues respectively.

Correct. This is one of the four dimensions.

Root cause analysis is part of problem control.

Directing involves setting direction, objectives, and decision-making authority.

This is the correct answer as the Service Desk practice is explicitly designed to be the single point of contact (SPOC) between the service provider and its users. Its primary function is to handle all user interactions, including incidents, service requests, and inquiries, ensuring efficient communication and coordination. By centralizing these interactions, the Service Desk facilitates prompt resolution and maintains user satisfaction, acting as the crucial interface for all service-related matters.

An Underpinning Contract (UC) is a formal agreement between the service provider and a third-party supplier, such as a data centre operator, that specifies required availability levels, performance targets, and remedies for non-compliance. This document directly satisfies the stem’s constraint of defining measurable availability requirements for an externally hosted facility, ensuring the provider can enforce service levels contractually rather than relying on informal expectations.

IT Asset Management manages the complete lifecycle of assets.

Service Level Management (SLM) is the practice of setting clear, business-focused targets for service performance, including availability, and then monitoring and reporting against those targets. It involves negotiating Service Level Agreements (SLAs) with customers, ensuring that services meet agreed expectations, and managing customer perceptions of service quality. This practice directly ensures that IT services achieve agreed availability levels from the customer's perspective by formalizing commitments.

This practice is precisely responsible for ensuring that services and service components can meet current and future performance and demand requirements in a cost-effective way. It involves understanding the demand for services, monitoring the performance and utilization of resources, and planning for necessary adjustments or investments to maintain agreed service levels. By proactively managing resources, it prevents performance bottlenecks and ensures the service remains capable of handling expected workloads.

The primary purpose of the Incident Management practice is to restore normal service operation as quickly as possible, thereby minimizing the negative business impact of service disruptions. This involves swift diagnosis and resolution of service interruptions or degradations, ensuring users can resume their work efficiently. The focus is on immediate restoration and returning to an agreed service level, not necessarily a permanent fix, which distinguishes it from Problem Management.

This option is correct because a service provider frequently procures, owns, and maintains the necessary hardware infrastructure (e.g., servers, storage, networking equipment, or even end-user devices) required to deliver an IT service. These capital expenditures are then bundled into the service charges, effectively transferring the hardware acquisition and lifecycle management costs from the consumer to the provider. This approach allows the consumer to avoid large upfront investments and focus on outcomes.

Problem Management is the ITIL practice responsible for reducing the likelihood and impact of incidents by identifying and resolving their root causes. When a temporary workaround is implemented during a major incident, Problem Management formally documents this solution, often within a Known Error Record, making it accessible for future incident resolution. This practice ensures that temporary fixes are tracked and systematically addressed for permanent resolution, preventing recurrence.

The primary reason for a service provider to design a new service according to ITIL principles is to avoid unbalanced service management, which frequently leads to operational failures and an inability to deliver expected value. ITIL 4's four dimensions of service management—Organizations and People, Information and Technology, Partners and Suppliers, and Value Streams and Processes—must be considered and integrated holistically. Neglecting any dimension creates weaknesses that can undermine the service's effectiveness, increase risks, and prevent successful value co-creation.

Correct: Shift-left aims to resolve issues at the first contact.

The service desk handles initial user contact and first-level resolution.

Normal changes are non-pre-approved changes that must follow a full, structured change process, including assessment, authorization, and scheduling, to ensure minimal risk and impact. These changes typically require a change authority's approval based on a thorough evaluation of their potential effects on services and infrastructure. They are scheduled and implemented according to a defined change calendar, balancing speed with stability. This category encompasses most significant service improvements or infrastructure modifications.

Warranty assures that a service will meet agreed requirements, ensuring it is 'fit for use'. This includes aspects such as availability, capacity, continuity, and security. A cloud service provider's guarantee of 99.99% uptime directly specifies the availability component of the service, promising a certain level of performance and reliability. This commitment directly addresses whether the service will consistently perform as expected, making it a clear example of warranty.

The Service Level Management practice is central to defining, negotiating, agreeing, and monitoring service level agreements (SLAs) with customers. It ensures that services consistently meet agreed-upon performance targets and customer expectations. This practice involves regular reviews of service performance against these agreements, driving improvement initiatives where necessary to maintain value.

This option is correct because in a cloud-based CRM (Software as a Service model), the cloud provider is entirely responsible for managing and maintaining the underlying physical infrastructure, including servers, storage arrays, and networking equipment within their data centers. Consequently, the risk associated with hardware component failures, and the subsequent impact on service availability, is transferred from the consuming organization to the cloud service provider. The provider implements redundancy and fault tolerance to mitigate this risk.

Standard changes are low risk, pre-approved, and follow a procedure.

IT Asset Management (ITAM) is the practice responsible for planning, acquiring, deploying, managing, and disposing of IT assets throughout their entire lifecycle. This comprehensive approach includes managing financial, contractual, and inventory aspects to maximize value, control costs, and mitigate risks associated with IT assets. ITAM ensures that assets are effectively utilized, maintained, and retired in alignment with organizational objectives and regulatory requirements, directly addressing the management of an asset's full lifecycle.

Normal changes are the most common type of change, requiring full assessment, authorization, and scheduling. They follow a defined process, which typically includes peer review, impact analysis, risk assessment, and formal approval, often by a Change Advisory Board (CAB), before implementation. This structured approach is crucial for managing significant service modifications, new deployments, or complex updates that are not pre-approved or driven by an immediate emergency, ensuring thorough risk mitigation.

Service Level Management is the dedicated practice responsible for setting clear, business-focused targets for service performance and ensuring that the organization meets these agreed-upon levels. It involves defining, documenting, agreeing, monitoring, analyzing, and reviewing service level agreements (SLAs) with customers, ensuring that services are delivered according to expectations and value is co-created. This practice directly addresses the negotiation and definition of customer-facing service commitments.

Economic conditions, such as inflation rates, interest rates, employment levels, and market growth, are quintessential external factors that significantly impact an organization's ability to deliver and consume services. These elements are beyond the direct control of any single organization and are a key component of the PESTLE (Political, Economic, Social, Technological, Legal, Environmental) analysis framework. They can influence budget availability, customer demand, supplier costs, and overall market viability for IT services.

The Service Desk serves as the crucial single point of contact (SPOC) between the service provider and its users. This central role ensures that users have one clear channel for reporting incidents, making service requests, and seeking information, thereby streamlining communication and improving user experience. By acting as the SPOC, the Service Desk facilitates efficient logging, initial assessment, and routing of all user interactions to the appropriate support teams or practices.

Utility is the functionality offered by a service to meet a need.

Service requests are for routine, pre-approved items.

Trend analysis of incident records is a crucial activity for problem identification, as it involves systematically reviewing historical incident data to detect recurring patterns or increasing frequencies of specific incident types over time. By observing these trends, IT teams can proactively identify emerging problems that might otherwise go unnoticed, signaling a need for deeper investigation into an underlying cause. This proactive approach helps prevent future service disruptions.

Warranty, in ITIL 4, refers to the assurance that a service will meet agreed requirements regarding its performance. It specifically addresses how the service performs, covering aspects such as availability, capacity, continuity, and security. Essentially, warranty confirms that the service is "fit for use," ensuring that it can be used reliably and consistently to deliver the desired outcomes without undue interruption or degradation. This concept directly describes the assurance provided by a service.

Logging an incident record and attempting to restore service is the correct immediate action, aligning with the primary objective of ITIL's Incident Management practice. An incident is defined as an unplanned interruption to a service or a reduction in the quality of a service. The service desk's role is to capture this event, track it, and initiate steps to restore service functionality to users as quickly as possible, minimizing business impact.

The team is optimizing (removing non-value steps) before automating, which directly reflects this principle.

Documenting known errors and workarounds in the Known Error Database is a critical activity within the Error Control phase of Problem Management. Once a problem's root cause has been identified and a temporary solution developed, recording this information allows for quicker incident resolution in the future and prevents recurrence. This database serves as a vital knowledge base, enabling efficient incident diagnosis and providing interim solutions until a permanent fix is implemented.

This dimension encompasses the information and knowledge necessary for service management, along with the technologies and applications required to deliver and support services. A service designed with "excellent functionality" but still problematic often indicates a gap in the underlying information architecture, data availability, or the technological infrastructure needed to effectively realize or deliver that functionality. The superb design might be hindered by inadequate systems, tools, or data processing capabilities.

Technology includes AI and tools like chatbots.

Restoring normal service operation as quickly as possible directly satisfies the Incident Management practice’s primary constraint of minimising business disruption, as defined in the ITIL 4 service value system. This objective prioritises speed of recovery over root-cause analysis, which distinguishes it from the Problem Management practice’s focus on permanent resolution.

Capacity and Performance Management is the ITIL practice specifically designed to ensure that services and service components are able to meet agreed performance targets and demand, both current and future. It involves understanding the current capacity and performance of resources, forecasting future demand, and planning for necessary adjustments to maintain optimal service delivery and user experience. This practice proactively balances the cost of capacity with the need for performance and availability.

Warranty refers to the assurance that a product or service will meet agreed requirements, specifically concerning its fitness for use. This includes aspects such as availability, capacity, security, and continuity, ensuring the service performs reliably under specified conditions. Therefore, a guarantee regarding the availability of cloud-based accounting software directly falls under the definition of warranty, as it addresses how the service performs and its reliability.

Incidents are logged to restore normal service operation.

A standard change is a pre-authorized change that is low-risk, well-understood, and has a documented procedure for implementation. These changes are typically routine, frequently performed, and do not require additional authorization each time they are executed, as the risk has been assessed and approved beforehand. This classification perfectly aligns with following a pre-defined, low-risk procedure, making it efficient for common modifications.