ITIL 4 Foundation (ITIL4F) — Questions 151–225

Utility concerns the functionality offered by a service and whether it enables the customer's required outcomes — "fit for purpose". The customer confirms the service performs ("works well") yet business benefits are absent, so the shortfall lies in utility's outcome contribution, not warranty's assurance of availability, capacity, security or continuity.

This option is correct. The 'output' refers to the tangible deliverable, which is the new software feature itself. Since the feature 'works,' the output is considered good or satisfactory, meeting its technical specifications. However, the 'outcome' represents the actual benefit or result achieved for the stakeholders, such as increased productivity. If the working feature fails to deliver this desired benefit, then the outcome is poor, despite the functionality of the output.

The mobile app itself is a tangible deliverable, directly produced by the IT team's development activity, making it an output. The faster response time, however, represents the benefit or change experienced by customers (stakeholders) as a result of using that app. This improved efficiency and customer experience is the desired outcome, demonstrating the value derived from the output.

The company's use of a big-bang approach directly violated the 'Progress iteratively with feedback' principle. This principle advocates for breaking down work into smaller, manageable iterations, allowing for continuous learning, adaptation, and course correction based on stakeholder feedback at each stage. A big-bang deployment bypasses these crucial feedback loops, significantly increasing the risk of encountering unforeseen issues late in the process, leading to widespread failure when the entire system is launched simultaneously.

Collaborate and promote visibility directly addresses siloed working by mandating shared information across teams and stakeholders. It satisfies the stem's requirement to break down silos and make information visible, since the principle explicitly pairs cross-team collaboration with transparent, accessible communication, ensuring relevant parties can act on the same data.

The Continual Improvement practice is dedicated to aligning an organization's practices and services with changing business needs through the ongoing identification and improvement of all elements involved in the management of products and services. A central component of this practice is the Improvement Register, which serves as a structured database to capture, track, and manage all identified improvement opportunities from across the organization, ensuring they are prioritized, actioned, and reviewed for effectiveness. This register is crucial for maintaining visibility and driving the improvement lifecycle.

Operational Level Agreements (OLAs) are internal agreements between different departments or teams within the same service provider organization. Their primary purpose is to define the specific responsibilities, activities, and performance targets that each internal group must meet to collectively ensure the successful delivery of services and, consequently, the achievement of the customer-facing Service Level Agreements (SLAs). Without robust OLAs, internal coordination can falter, jeopardizing SLA compliance.

The 'Improve' value chain activity is specifically designed to ensure the continual improvement of products, services, and practices across all value chain activities and the four dimensions of service management. Its primary purpose is to identify and manage improvement opportunities, translating them into actionable initiatives to enhance value delivery and optimize organizational performance. This activity drives the ongoing enhancement cycle, making it the correct answer for its direct focus on improvement.

The "Keep it simple and practical" guiding principle directly advises organizations to use the minimum number of steps necessary to achieve a desired outcome, eliminating anything that does not add value. It explicitly states that if a process, service, action, or metric provides no value or produces no useful outcome, it should be removed. This principle directly addresses the avoidance of unnecessary complexity and bureaucracy, advocating for straightforward, pragmatic solutions that are easy to understand and implement.

Utility directly describes the functionality offered by a service, defining what the service *does* and whether it is 'fit for purpose.' It addresses the specific requirements of the consumer, enabling them to perform tasks or achieve desired objectives. This term precisely captures the inherent capabilities and features that allow a service to support a consumer's performance or remove constraints.

A Service Request is a formal request from a user for something standard that is part of normal service delivery, such as information, advice, a standard change, or access to a service. Provisioning a new laptop for a new employee is a classic example of a pre-defined, low-risk, and often automated service request, following established procedures for fulfillment.

In ITIL 4, utility is precisely defined as the functionality provided by a service to address a particular requirement or achieve a specific outcome for the consumer. It describes whether a service is "fit for purpose," meaning it possesses the necessary features and performance capabilities to support the consumer's objectives. This concept focuses on the tangible value derived from the service's core functions, enabling the consumer to perform tasks or achieve goals effectively.

"Focus on value" is indeed one of the seven ITIL 4 guiding principles, emphasizing that all activities performed by the organization should directly or indirectly create value for its stakeholders, including customers, users, and the organization itself. This principle encourages understanding the customer's perspective and ensuring that every service management effort contributes to tangible outcomes and perceived benefits. Value can encompass financial, experiential, or strategic benefits.

The user's inability to access services due to a password issue constitutes an unplanned interruption to a service, which is the definition of an incident in ITIL 4. The primary objective of incident management is to restore normal service operation as quickly as possible, minimizing business impact. Logging the incident ensures it is properly tracked, prioritized, and managed through to resolution, aligning with ITIL's incident management practice.

Analyzing the incident from March 15 to identify the root cause of slow transactions aligns directly with ITIL's Problem Management practice. This proactive approach seeks to understand the underlying issues causing performance degradation, rather than just resolving symptoms. By identifying the root cause, the organization can implement permanent solutions, prevent recurrence of slow transactions, and improve overall service quality and user satisfaction.

A service request is a formal request from a user for something that is a normal part of service delivery, typically pre-defined and pre-approved. A password reset is a classic example, as it is a common, routine action with a known procedure and expected outcome, often fulfilled through self-service or standard operating procedures. It falls squarely under the scope of standard service offerings.

Knowledge Management maintains the body of information that supports all practices, including known errors, workarounds, and resolution steps. The agent could quickly apply the workaround because Knowledge Management had captured and made it available. This practice ensures that useful information is created, shared, and kept current across the organization.

A standard change is a low-risk, pre-authorized change that is well-understood, fully documented, and often implemented as a service request. These changes follow a defined procedure, do not require additional authorization each time they are implemented, and are typically initiated to deliver a new or changed service feature or to resolve a common issue. Their pre-approval streamlines the change process for routine activities, ensuring efficiency while maintaining control and predictability within the service environment.

Value co-creation requires the consumer to actively participate in the service relationship rather than passively receive output. This satisfies the stem's focus on co-creation elements, since value emerges through interaction between provider and consumer, not from the provider alone.

Warranty provides assurance that a product or service will meet agreed requirements, describing 'how' the service performs. This includes aspects such as availability, capacity, security, and continuity. When a software vendor provides a cloud-based CRM, they are implicitly or explicitly guaranteeing these non-functional requirements, ensuring the service is 'fit for use' and operates reliably according to specified service levels.

This option is correct because the Partners and Suppliers dimension explicitly addresses the relationships an organization has with other organizations that are involved in the design, development, delivery, support, and improvement of services. When designing a new service, a service provider frequently needs to consider external collaborations, contracts, and the entire supply chain to acquire necessary components, expertise, or capabilities, making this dimension highly relevant.

The 'Plan' value chain activity establishes a shared understanding of the vision, current status, and improvement direction for all four dimensions of service management and all products and services across the organization. Introducing a new monitoring tool necessitates this foundational planning to define its purpose, scope, resource requirements, and how it aligns with overall organizational strategy. This initial activity sets the stage for all subsequent actions, ensuring alignment and effective resource allocation.

The 'Keep it simple and practical' principle advocates for eliminating anything that does not contribute to value creation, focusing on the minimum necessary steps to achieve the desired outcome. Reducing the number of steps in a change process directly aligns with this by removing unnecessary complexity, bureaucracy, and waste, ensuring the process remains efficient, effective, and easy to understand and execute for all stakeholders.

Service Configuration Management is the ITIL practice specifically tasked with ensuring that accurate and reliable information about the configuration of services and the Configuration Items (CIs) that support them is available when and where needed. This practice defines, identifies, controls, records, reports, and verifies all CIs and their relationships within the Configuration Management Database (CMDB). Its core function is to maintain the integrity and accuracy of configuration data throughout the entire service lifecycle, making it directly responsible for the CMDB.

This statement is correct and aligns perfectly with the ITIL guiding principle of "Optimize and automate." By automating repetitive, low-value, or high-volume tasks, organizations can significantly reduce the burden of mundane operational activities on their workforce. This strategic liberation of human resources enables skilled personnel to concentrate on more complex problem-solving, strategic initiatives, innovation, and tasks requiring critical thinking or complex decision-making, thereby increasing overall organizational value and efficiency.

The 'Start where you are' guiding principle mandates that organizations assess their current state and leverage existing services, processes, tools, and people whenever possible, rather than starting from scratch. For a new mobile banking app, this means identifying and reusing existing components, APIs, security protocols, or even development methodologies already present within the organization. This approach avoids unnecessary duplication of effort, accelerates development, and leverages prior investments, directly promoting the strategic reuse of assets.

The "Collaborate and promote visibility" principle directly addresses the challenge of separate teams and communication silos by advocating for cross-functional cooperation and transparent information sharing. It encourages working together across boundaries, fostering mutual understanding, and ensuring all relevant parties have a clear view of activities and progress. This principle explicitly targets the breakdown of departmental barriers and the improvement of shared context necessary for effective service delivery.

ITIL 4 defines service management as a set of specialized organizational capabilities for enabling value for customers in the form of services. The primary purpose is to facilitate value co-creation, where organizations collaborate with consumers to realize desired outcomes. This involves understanding stakeholder needs and designing, delivering, and improving services that provide utility and warranty, ultimately contributing to mutual value.

This option correctly identifies the output and outcome. The "CRM system" is the tangible output, representing the specific product or service component delivered by the organization's activities. "Faster data access and increased sales" are the desired outcomes, which are the benefits realized by the organization and its customers as a result of utilizing the CRM system. This alignment demonstrates a clear understanding of how delivered outputs enable the achievement of valuable business outcomes, central to the ITIL 4 value co-creation model.

This principle advises against discarding existing resources or processes without first assessing their current utility and potential for reuse. It encourages a thorough examination of the current state, including services, processes, people, partners, and technology, to identify what can be leveraged or improved rather than initiating new efforts from scratch. This approach promotes efficiency and avoids unnecessary waste by building upon established foundations.

Problem identification is a foundational activity within Problem Management, initiating the process by detecting and logging potential or actual problems. This involves analyzing incident trends, reviewing service desk data, and receiving direct input from various stakeholders to proactively identify recurring issues or single, high-impact events that warrant deeper investigation. The goal is to move beyond mere symptom treatment to understand underlying causes.

Engaging all relevant departments, such as development, operations, security, finance, and business units, during the planning phase of a new service exemplifies a truly holistic approach. This comprehensive stakeholder involvement ensures that the service is designed with a full understanding of its requirements, dependencies, potential impacts, and value streams across the entire organization, fostering proactive, cross-functional collaboration from inception to deliver integrated value.

A service is defined in ITIL 4 as a means of enabling value co-creation by facilitating outcomes customers want, without them managing specific costs and risks. This matches the stem's description precisely, making it the correct concept.

Incident Management's primary objective is to restore normal service operation as quickly as possible following an unplanned interruption or reduction in service quality. It focuses on the immediate impact and resolution of service disruptions. In contrast, Problem Management aims to reduce the likelihood and impact of incidents by identifying and eliminating their underlying root causes, often preventing future occurrences of similar issues.

Forecasting future demand for services is a critical activity within capacity and performance management, specifically for proactive capacity planning. By analyzing historical trends, business plans, and anticipated growth, organizations can predict future resource requirements for IT services and their underlying components. This foresight enables the timely acquisition, provisioning, or scaling of infrastructure and applications, ensuring that sufficient capacity is available to meet evolving business needs without costly over-provisioning or detrimental under-provisioning.

Configuration management is fundamentally concerned with understanding how different components of an IT service relate to each other to ensure service integrity and operational efficiency. By defining and tracking Configuration Items (CIs) and their interdependencies within the Configuration Management System (CMS), it provides crucial insights into how changes to one asset (represented as a CI) might impact others. This relational information is vital for effective incident, problem, and change management, ensuring service stability and reliability.

This ITIL practice is specifically responsible for ensuring that services and components are able to perform their agreed function when required, meeting established availability targets. It encompasses designing for resilience, implementing redundancy, proactive monitoring, and establishing recovery mechanisms to maximize service uptime and minimize downtime. Its core purpose is to guarantee the continuous operational capability of services and their underlying components.

Finding underlying causes of incidents is the central purpose of Problem Management. This ITIL practice focuses on identifying the root causes of actual or potential incidents, analyzing trends, and developing permanent solutions to prevent recurrence. By moving beyond temporary fixes, Problem Management aims to eliminate known errors and improve the long-term stability and reliability of IT services, thereby reducing the overall number and impact of future incidents.

This statement accurately defines the primary purpose of the Monitoring and Event Management practice. It involves systematically observing services and service components, recording changes of state identified as events, and then classifying these events. This classification is crucial for determining the appropriate response, whether it's an informational alert, a warning requiring further investigation, or an an indicator of an incident that needs immediate action.

The service value chain is a core component of the ITIL 4 Service Value System, representing an operational model that outlines the key activities required to respond to demand and facilitate value co-creation through the creation and management of products and services. It provides a flexible, interconnected set of activities that an organization performs to deliver value, integrating various practices and resources. This component is central to how an organization transforms inputs into outputs.

A warning event, as defined by ITIL 4, indicates that a predefined threshold has been met or exceeded, signaling a potential degradation of service or an impending incident. In this scenario, high server CPU usage reaching a critical level triggers such an event, prompting IT staff to investigate and take proactive measures. The primary objective of a warning event is to enable intervention before the situation escalates into an actual service disruption, thereby maintaining service quality and availability.

Warranty, in ITIL 4, precisely defines the assurance that a service will consistently meet its agreed-upon specifications and requirements, thereby confirming its 'fitness for use.' This critical aspect ensures the service performs reliably without undue interruption or degradation, providing confidence to the consumer. Specifically, warranty addresses key performance indicators related to availability, capacity, continuity, and security, guaranteeing the service's operational integrity.

A password reset is a classic example of a service request in ITIL 4. Service requests are standard, pre-defined, and often automated requests for information, advice, or access to a service, or for a standard change. They are typically low-risk, frequently occurring, and have a known resolution path, making them distinct from incidents or changes. Users expect a quick and predictable fulfillment process for such common requests.

The "Start where you are" guiding principle explicitly advises against starting from scratch without first considering what is already available and functional within the organization or its ecosystem. It encourages organizations to assess existing services, processes, people, partners, and tools to determine if they can be leveraged, adapted, or improved upon, making only the necessary changes to achieve the desired state. This approach minimizes waste, accelerates progress, and builds upon proven capabilities, directly aligning with the idea of reusing existing processes rather than reinventing the wheel.

IT Asset Management covers the full lifecycle of IT assets, including financial, contractual and inventory detail, tracking cost, ownership and compliance. It satisfies the stem's requirement for managing financial and contractual aspects, unlike practices such as Service Configuration Management, which focuses on configuration items and their relationships rather than commercial data.

The 'Keep it simple and practical' guiding principle advises against unnecessary complexity and encourages delivering the minimum necessary to achieve the objective. A monitoring tool that generates an overwhelming number of alerts, many of which are likely non-actionable or redundant, directly violates this principle. Such over-alerting introduces significant complexity, makes the system impractical to use effectively, and obscures critical information, thereby failing to provide a simple, practical, and useful output for the IT department.

Warranty is the assurance that a service meets agreed requirements, covering availability, capacity, continuity and security. The 99.9% availability guarantee is precisely this assurance, distinguishing it from utility, which describes the functionality the service provides to support the consumer's outcomes.

This action directly aligns with the ITIL 4 Guiding Principles of "Focus on value" and "Keep it simple and practical." By systematically identifying and eliminating redundant, unnecessary, or non-value-adding activities within the change management process, an organization can significantly streamline workflows, reduce cycle times, and optimize resource utilization. This simplification enhances efficiency, improves responsiveness, and ensures that every remaining step contributes directly to desired outcomes.

Service Level Management is the dedicated practice responsible for setting clear, business-based targets for service performance and ensuring that the organization meets those targets. This practice explicitly involves negotiating and agreeing upon service level agreements (SLAs) with customers, which define the expected quality, availability, and other performance metrics of a service. It also continuously monitors, reports on, and reviews service performance against these agreed-upon levels to ensure customer satisfaction.

Logging each call as an incident is the correct initial action because an incident is defined as an unplanned interruption to a service or a reduction in the quality of a service. Each user call reporting a network issue signifies a service disruption that requires immediate attention and tracking. This ensures proper incident management processes are followed, service level agreements are monitored, and provides crucial data for subsequent problem identification and resolution.

The ITIL Service Value System (SVS) is designed to provide a comprehensive and integrated framework for service management, encompassing all organizational components and activities required to create value. It ensures that guiding principles, governance, the service value chain, practices, and continual improvement all work together cohesively. This holistic approach moves beyond isolated processes to a unified system, optimizing overall service delivery and value realization.

Negotiating and agreeing Service Level Agreements (SLAs) is a fundamental and defining activity of the Service Level Management practice. This involves establishing clear, measurable targets for service performance, availability, capacity, and other critical aspects, ensuring they align with customer expectations and business requirements. By formalizing these agreements, Service Level Management sets the baseline for monitoring, reporting, and continual improvement of service delivery, directly linking IT services to business outcomes.

This dimension encompasses the organizational structure, culture, roles, responsibilities, and the required skills and competencies of all personnel involved in service management. The described issue, where the IT team experiences a skill gap and temporary productivity loss after implementing a new tool, directly highlights a failure to adequately prepare and enable the people within the organization for the change, making this the primary dimension affected.

Incident Management's primary purpose is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible. An unplanned disruption, such as a user being unable to access a critical service, directly aligns with the ITIL definition of an incident. The immediate action taken by the service desk to resolve this access issue is a core activity within the Incident Management practice, aiming for swift resolution and service restoration.

This ITIL practice is precisely designed to reduce the likelihood and impact of incidents by identifying and resolving their underlying causes, known as problems. It proactively analyzes recurring incident patterns, trends, and historical data to diagnose root causes, develop effective workarounds, and recommend permanent solutions. Its goal is to prevent future incidents, thereby enhancing service stability and reliability.

Conducting service reviews with customers is a fundamental activity of Service Level Management, providing a structured forum to discuss service performance, customer satisfaction, and any changes in business requirements. These regular reviews are crucial for ensuring that the agreed service level agreements (SLAs) remain relevant and continue to align with customer needs and business objectives, fostering a collaborative relationship and identifying opportunities for continual improvement.

Implementing a new payroll system profoundly impacts employees, managers, HR, and finance departments, necessitating significant changes in roles, responsibilities, and daily workflows. This dimension focuses on ensuring the organization has the right culture, structure, and capabilities, alongside effective communication and training strategies, to successfully adopt and operate the new system. Effective change management, stakeholder engagement, and clear definition of new roles are critical components addressed by this dimension for project success.

The Customer is a key consumer role in the service relationship, representing the organizational entity or individual that defines service requirements and is accountable for the service's value realization. They authorize the service and are typically responsible for its financial aspects, ensuring it aligns with broader organizational objectives and strategic needs. This role focuses on the overall agreement and outcome.

The SVS explicitly receives demand and opportunities as inputs from stakeholders and the external environment. Opportunities represent options to add value or improve services, while demand represents the need for products and services. The SVS transforms these inputs through the service value chain and practices into value for the organization, its customers, and other stakeholders, enabling true co-creation.

This statement is correct. Service providers contribute a variety of resources and capabilities, such as technological infrastructure, specialized knowledge, skilled personnel, and intellectual property, to enable the service consumer to achieve their desired outcomes. These contributions form the essential foundation of the service offering, allowing consumers to leverage these assets effectively.

An economic recession represents a significant external factor because it originates from broad macroeconomic conditions, such as declining GDP, increased unemployment, and reduced consumer spending, which are entirely beyond an organization's direct control. These conditions directly impact market demand for products and services, influence investment capital availability, and can necessitate strategic adjustments to an organization's financial planning and operational capacity. Consequently, an organization must adapt its service management practices to navigate the challenges posed by a contracting economy.

The "Collaborate and promote visibility" guiding principle is directly applicable here because reducing incident resolution time typically requires input and cooperation from multiple teams, such as the service desk, technical support, and development. This principle emphasizes breaking down organizational silos, fostering cross-functional teamwork, and ensuring all relevant stakeholders share information and progress openly. Such collective effort and transparency are crucial for identifying root causes, implementing effective solutions, and tracking improvements across the entire service value chain.

The 'Organisations and People' dimension specifically addresses the human element of service management, encompassing the organizational structure, culture, roles, responsibilities, and the necessary skills and competencies of all personnel. It ensures that individuals possess the required expertise, are adequately trained, and are motivated to perform service management activities effectively. This dimension is crucial for fostering a culture of collaboration, continuous learning, and aligning human capabilities with organizational goals to deliver value.

The 'Deliver & support' activity is precisely where services are delivered and supported according to agreed specifications and expectations, making it the most direct source for identifying operational issues. This activity encompasses incident management, problem management, and service request fulfillment, meaning it is where service failures, performance degradation, and user-reported issues are first encountered, logged, and managed. An IT manager reviewing this activity would directly observe the symptoms and causes of service problems.

The "Start where you are" guiding principle explicitly advises against discarding existing resources and starting from scratch without first considering what is already available. When an IT team is redesigning a process, reviewing the current state is a direct application of this principle, as it involves understanding the baseline, identifying what works well, and recognizing what needs improvement, thereby leveraging existing foundations rather than reinventing solutions.

Customer Satisfaction (CSAT) is a pivotal metric for any service, directly measuring how satisfied customers are with a service or specific interaction, such as with the service desk. It typically involves direct feedback from users, often through surveys, providing invaluable insight into their perception of service quality, responsiveness, and overall value. High CSAT scores indicate that the service is meeting or exceeding customer expectations, making it a fundamental indicator of service success and customer-centricity.

The fundamental purpose of the Service Desk practice is to establish and maintain a single point of contact (SPOC) between the service provider and its users. This crucial role ensures that users have a consistent, accessible, and reliable channel for all IT-related inquiries, incident reporting, service requests, and information needs, thereby streamlining communication and enhancing user experience and satisfaction.

An exception event signifies an abnormal situation where a service or component is operating outside its established baseline or expected parameters, often indicating a failure or a critical degradation. These events trigger immediate investigation and resolution efforts to prevent service disruption or restore normal operations, aligning with the core purpose of event management to detect and respond to deviations.

This option perfectly illustrates a risk transferred from the consumer to the provider. When a consumer utilizes a service, they rely on the provider's infrastructure and operational capabilities. The risk associated with the provider's own hardware failing and subsequently causing a service outage is entirely borne by the provider, who is responsible for maintaining availability and resolving such incidents according to agreed service levels. The consumer pays for the service's outcome, not the direct management of infrastructure risks.

Automating password resets removes repetitive manual effort from the service desk, streamlining the workflow so agents focus on higher-value work. This embodies Optimise and automate, which urges organisations to use technology to eliminate waste rather than simply doing the same manual task faster.

Problem management fundamentally includes root cause analysis (RCA) as a core activity to systematically investigate and identify the underlying causes of incidents. This analytical process goes beyond merely restoring service, aiming to understand why incidents occur. By uncovering the true source of issues, problem management enables the development of effective solutions that prevent future recurrences, thereby improving service stability and reliability.

An opportunity serves as a significant trigger by presenting a potential for improvement, innovation, or the creation of new value for stakeholders. Recognizing an unmet market need, a technological advancement, or a chance to enhance efficiency can initiate the development of new services, features, or processes. These opportunities drive strategic initiatives aimed at capitalizing on potential benefits and expanding the organization's capabilities or market reach.

The "Start where you are" guiding principle mandates that an organization should not discard existing resources or processes without first understanding their current state and value. For an IT team redesigning incident management, this means assessing the current process, identifying what works, what doesn't, and what can be reused or improved, rather than attempting to build an entirely new process from a blank slate. This foundational assessment prevents wasted effort and ensures continuity.

By delivering value in small, manageable increments, the risk associated with large-scale failures is significantly mitigated. Each iteration allows for early detection of defects or misalignments with requirements, confining potential issues to a smaller scope. This approach prevents minor problems from escalating into catastrophic project failures, as corrections can be made frequently and with less overall impact.