ITIL 4 Foundation (ITIL4F) — Questions 76–150

Cloud computing platforms are fundamental technological infrastructures that provide scalable and on-demand computing resources, including servers, storage, databases, networking, software, analytics, and intelligence, over the internet. These platforms are integral to the Information and Technology dimension because they represent the actual technology components and services utilized to deliver and support IT services, enabling flexible and efficient operations.

'Improve' is a service value chain activity focused on continual improvement.

Guiding principles are a key component of the SVS.

Applying a critical security patch to a production server to fix a vulnerability is a prime example of an emergency change. Such a situation involves an immediate, severe threat to the security, availability, or integrity of a live service, demanding urgent action to prevent significant business impact or data compromise. The critical nature of the vulnerability necessitates an expedited assessment and authorization process, bypassing the typical, longer change schedule to mitigate the risk as quickly as possible.

"To define the vision and direction for the organization" is the correct primary purpose of the "Plan" value chain activity. This activity ensures a shared understanding of the organization's vision, mission, and strategic objectives, providing clear direction for all products, services, and relationships. It establishes the overarching guidance for all other service value chain activities, aligning them with organizational goals.

Reporting service performance is a critical activity within Service Level Management, ensuring transparency and accountability. This involves systematically collecting, analyzing, and presenting data on how well services are meeting their agreed-upon targets to relevant stakeholders, including customers and internal management. Regular performance reports highlight achievements, identify deviations, and provide insights necessary for continuous service improvement and informed decision-making regarding service levels.

A server's CPU usage exceeding 95% and requiring immediate attention is a clear example of an exception event. This critical threshold signifies an abnormal and potentially service-impacting situation that demands urgent, often reactive, intervention to prevent performance degradation or system failure. It represents a severe deviation from expected operational norms that cannot be ignored without significant consequences for service delivery.

Warranty describes how the service performs, specifically its fitness for use, by assuring that the service meets agreed-upon requirements. When designing a new service, an IT team ensures the warranty by guaranteeing specific levels of availability, capacity, continuity, and security. This assurance provides confidence to the service consumer that the service will consistently meet its defined performance criteria and be available when needed, making it reliable for its intended use.

A standard change is a low-risk, pre-authorized change that follows a well-established, documented procedure. Updating a firewall rule, if it's a routine, templated modification (e.g., opening a specific port for a new application following a pre-approved template), perfectly aligns with this definition. Such changes are implemented without needing additional authorization each time, enabling efficient and consistent delivery of common infrastructure modifications.

Logging an incident is the correct first step as it formally records an unplanned interruption to a service, or a reduction in the quality of a service. The primary objective of incident management is to restore normal service operation as quickly as possible, minimizing business impact. Attempting service restoration directly aligns with this core principle.

In ITIL 4, value is co-created and defined by the perception of stakeholders. Outcomes represent the results achieved by a service consumer that enable them to meet their objectives, often facilitated by a service. These desired results directly contribute to the realization of value, as they address the underlying needs and goals of the consumer, making them a fundamental component of value itself.

The 'Plan' activity is foundational, establishing a unified strategic direction across the organization for all products and services. It ensures that all stakeholders share a common understanding of the organizational vision, the current state of services, and the overarching direction for future improvements. This activity provides the necessary guidance and constraints for all other service value chain activities, aligning efforts towards value co-creation.

Problem management's primary purpose is indeed to eliminate or reduce the likelihood and impact of incidents by identifying and resolving their underlying root causes. This involves both reactive analysis of existing incidents and proactive trend analysis to prevent future occurrences, often leading to the creation of known errors and permanent solutions or effective workarounds.

IT Asset Management is the practice of planning, acquiring, deploying, managing, and retiring IT assets, including servers, throughout their entire lifecycle. This comprehensive approach encompasses tracking financial aspects like depreciation, contractual details, physical location, and operational status from procurement through to disposal. It directly addresses the organization's need to understand and manage the full journey and value of its servers.

Governance evaluates, directs, and monitors the organization.

The Legal factor in PESTLE analysis encompasses the laws, regulations, and legal frameworks that impact an organization's operations and services. This includes consumer protection laws, data privacy regulations like GDPR, employment laws, and industry-specific compliance requirements. Understanding these legal obligations is critical for ensuring service compliance, mitigating risks, and avoiding penalties, directly influencing how services are designed and delivered.

Outcome is the result for a stakeholder. The feature (output) did not lead to improved productivity, so the intended outcome was not achieved.

A service request represents a formal request from a user for something that is a normal part of service delivery, typically a pre-defined and pre-approved offering from the service catalog. Requesting a new laptop, especially when it's a standard model provided by the organization, falls squarely into this category. These requests are usually low-risk, frequently occurring, and follow established workflows for fulfillment, often with automated or semi-automated processes.

IT Asset Management (ITAM) is responsible for tracking the financial and contractual aspects of IT assets throughout their lifecycle, including acquisition cost, depreciation, warranty information, and end-of-life dates. This crucial financial and lifecycle data is then integrated with Configuration Items (CIs) within the Configuration Management Database (CMDB). This integration enriches the CMDB's technical view with vital business context, enabling better decision-making regarding asset utilization and investment.

Capacity and availability management is the best answer because it addresses capacity, which is the core requirement of the question. Note that the exact ITIL 4 practice name is Capacity and performance management, but among the options, this is the most appropriate.

Root cause analysis (RCA) is a fundamental activity within problem management, specifically falling under the 'problem control' phase. Its purpose is to systematically investigate and determine the underlying causes of one or more incidents, preventing their recurrence. By identifying the true origin of issues, problem management can develop effective workarounds and permanent solutions, thereby reducing the impact and frequency of future service disruptions. This proactive approach is crucial for improving service stability and reliability.

Continual Improvement is a component of the SVS, representing the ongoing improvement of services.

Outsourcing IT support directly and fundamentally impacts the 'Partners and Suppliers' dimension, as it involves establishing or modifying relationships with external organizations that contribute to the design, development, delivery, support, and continual improvement of services. This dimension specifically addresses the interactions and agreements with third parties, making it the most relevant consideration when an organization decides to engage an external provider for service delivery. The very act of outsourcing is a decision rooted in this dimension.

Warning events indicate a threshold is approaching.

Incident Management's core objective is to minimize disruption to business operations by restoring affected services to their agreed-upon operational state as swiftly as possible. This practice focuses on the immediate impact of unplanned interruptions or reductions in service quality, aiming for quick fixes or workarounds to ensure continuity rather than deep root cause analysis. Its success is measured by how rapidly normal service is resumed and the extent to which business productivity is preserved.

Monitoring and Event Management is the ITIL 4 practice specifically designed to systematically observe services and service components, recording and reporting selected changes of state identified as events. A fundamental activity within this practice is the classification of these events into meaningful categories, such as informational (no action needed), warning (potential issue), or exception (requires action), to enable appropriate automated or manual responses.

ITIL 4 emphasizes that neglecting any of the Four Dimensions of Service Management can severely compromise an organization's ability to create value and deliver effective services. For instance, overlooking 'Organizations and People' can lead to skill gaps, while ignoring 'Information and Technology' can result in unreliable systems. A deficiency in 'Partners and Suppliers' might cause supply chain disruptions, and inefficient 'Value Streams and Processes' will hinder service delivery, ultimately leading to service failure, increased costs, or a significant reduction in efficiency.

Roles and skills are fundamental components of the "Organizations and People" dimension, as they define the necessary competencies and responsibilities required within an organization to effectively manage services. Establishing clear roles ensures accountability and efficient workflow, while developing appropriate skills empowers individuals to perform their tasks and contribute to value co-creation. This dimension emphasizes the human element and organizational structure essential for service delivery.

Service Level Management is the practice of setting clear business-based targets for service performance, and ensuring that delivery of services is properly assessed, monitored, and managed against these targets. This practice explicitly involves negotiating service level agreements (SLAs) with customers to define measurable service outcomes, agreeing upon these targets, and then continuously monitoring and reporting on actual service performance against the agreed levels to ensure value co-creation and customer satisfaction.

The Service Desk serves as the crucial single point of contact (SPOC) between the service provider and its users. This means users have one consistent channel for logging incidents, requesting services, and making inquiries, streamlining communication and improving user experience. By centralizing these interactions, the Service Desk ensures efficient routing, tracking, and resolution of all user-initiated contacts, embodying its core ITIL 4 purpose.

Demand represents the need or desire for products and services from consumers, acting as a fundamental trigger for the Service Value System (SVS). Organizations exist to create value by addressing these needs, prompting the SVS to design, deliver, and improve services that fulfill this demand. This proactive response ensures that resources are aligned to meet market requirements effectively, leading to value co-creation.

When service design focuses exclusively on technology, it critically overlooks the "Organizations and People" dimension of service management. This dimension addresses the necessary skills, competencies, roles, and responsibilities required for effective service operation and support. Without considering the human element, there is a high probability that staff will not possess the requisite knowledge or training to competently operate, maintain, or support the new service, leading to operational inefficiencies and service quality issues.

The 'Partners and Suppliers' dimension specifically addresses the relationships an organization has with external entities that are involved in the design, development, delivery, support, or improvement of services. Outsourcing a data center operation directly involves establishing, managing, and governing new or existing supplier agreements and partnerships, making this the most directly and primarily impacted dimension as it dictates how external resources contribute to value creation.

Warranty, in ITIL 4, refers to the assurance that a service will meet agreed-upon requirements. This specifically includes aspects like availability (the service being accessible when needed), capacity (its ability to handle the required workload), continuity (its resilience to disruptions), and security (protection against unauthorized access). These elements collectively ensure the service is 'fit for use' and performs reliably.

Service requests handle predefined, routine requests like new equipment.

Political factors represent external influences stemming from government policies, political stability, and international relations that can significantly impact an organization's operations and service strategy. These factors include changes in trade regulations, taxation policies, or government spending priorities, which are entirely outside an organization's direct control but necessitate strategic adaptation. Consequently, an organization must monitor these shifts to ensure compliance and maintain business viability.

The Service Value Chain (SVC) is a core operational model within the ITIL Service Value System, outlining the six key activities an organization undertakes to create value. It describes how demand is translated into value through a sequence of interconnected steps: Plan, Engage, Design & Transition, Obtain/Build, Deliver & Support, and Improve. The SVC is central to understanding how an organization delivers services and manages its value streams.

Warranty (availability) is good; utility (functionality) is poor due to slow speed and small attachment limit.

This option correctly identifies that the implemented new feature itself constitutes an "output"—a tangible deliverable resulting from an activity. However, if this feature failed to achieve its intended purpose, such as reducing customer complaints or improving efficiency, then the desired "outcome"—the benefit or result for stakeholders—was not realized. ITIL 4 emphasizes that value is co-created through outcomes, not merely by producing outputs.

Logging an incident is the correct action because an incident is defined as an unplanned interruption to a service or a reduction in the quality of a service. The primary objective of incident management is to restore normal service operation as quickly as possible, minimizing business impact. Users being unable to access a service directly represents such an unplanned disruption requiring immediate attention to restore functionality.

Utility is about functionality; if expected benefits are not achieved, the service may lack necessary functionality.

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.

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.

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, often pre-defined, pre-approved, and fulfilled through a standard process. Providing a new laptop for a new employee is a classic example of a standard, repeatable service offering that fits within established workflows and policies. This type of request is typically handled efficiently through automated or semi-automated fulfillment processes.

The Service Value Chain (SVC) is a central component of the ITIL Service Value System, representing an operational model that outlines the key activities required to respond to demand and facilitate value creation through the creation and management of products and services. It comprises six interconnected activities: Plan, Improve, Engage, Design & Transition, Obtain/Build, and Deliver & Support, which are combined in various ways to form different value streams. This flexible chain transforms inputs like demand and opportunities into valuable outputs for stakeholders.

Active participation is key to co-creation.

Mean Time to Restore Service (MTTR) is the most appropriate metric for measuring the effectiveness of service restoration. It quantifies the average time taken from the start of an incident to the full restoration of the affected service to its normal operational state. MTTR directly reflects the efficiency of the incident management process, encompassing detection, diagnosis, repair, and verification, thereby providing a clear indicator of how quickly an organization can recover from service disruptions.

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.

This is the correct definition of Incident Management's purpose.

Core purpose of incident management.

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.

Service is the correct term; it enables value co-creation by facilitating outcomes customers want to achieve.

This is the fundamental purpose of the Incident Management practice within ITIL 4. Its objective is to minimize the negative impact of incidents by restoring normal service operation as swiftly as possible. This involves rapid diagnosis, workaround implementation, and resolution to ensure business continuity and maintain agreed service levels, thereby reducing disruption to users and the organization.

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.

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.

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.

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

Warranty provides assurance that the service is fit for use.

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.

The Guiding Principles are a core component of the SVS.

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.

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.

Users are the ones who actually use the service.

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.

Guiding principles are a fundamental component of the ITIL 4 Service Value System (SVS), providing universal recommendations that can guide an organization in all circumstances. These principles, such as 'Focus on value' and 'Collaborate and promote visibility,' help shape decisions and actions across all levels and activities within service management. They ensure a consistent and effective approach to creating, delivering, and improving services.