ITIL 4 Foundation (ITIL4F) — Questions 376–450

Service Configuration Management is the dedicated practice responsible for maintaining accurate and reliable information about the services and the configuration items (CIs) that support them. This includes planning, identifying, controlling, monitoring, and verifying the versions, baselines, and relationships of all CIs throughout their lifecycle. Its core function is to ensure the integrity of the Configuration Management System (CMS) and the Configuration Management Database (CMDB), providing a foundational understanding of the service landscape for other practices.

This statement accurately describes a standard change. Standard changes are inherently low risk because they are routine, repetitive, and have a proven track record of successful implementation. Their well-understood nature means the steps, potential impacts, and required resources are clearly defined and predictable, allowing for pre-authorization without individual assessment each time.

The Organizations and People dimension specifically addresses the organizational structure, culture, and governance required to manage services effectively. It encompasses the roles, responsibilities, authorities, and communication models within the organization, as well as the necessary skills, competencies, and leadership behaviors of its workforce. This dimension directly focuses on the human element and the organizational context that shapes how work is performed and value is delivered.

This foundational principle dictates that every single activity undertaken by the organization must directly or indirectly contribute to the creation of value for its identified stakeholders. It requires a clear understanding of what constitutes value from the consumer's perspective, ensuring that all efforts, resources, and decisions are aligned with delivering beneficial outcomes. This principle directly answers the question by establishing value as the primary driver for all organizational endeavors.

A service request is a formal request from a user for something that is part of the normal service delivery, typically a pre-defined, low-risk, and repeatable action. These requests are often pre-authorized and follow a standard procedure, frequently managed through a service catalogue. The installation of pre-approved software perfectly aligns with this definition, representing a standard offering that can be fulfilled efficiently without extensive assessment or authorization.

An emergency change is specifically designed for situations requiring immediate action to resolve a high-impact incident, such as a security breach, or to implement a critical fix. These changes bypass some or all of the standard change authorization and assessment processes to expedite implementation, with approval often granted retrospectively or by a dedicated emergency change authority. Their primary purpose is to restore normal service operation or mitigate significant risks as quickly as possible.

Continual improvement is one of the five essential components of the ITIL 4 Service Value System (SVS). This component ensures that an organization's products, services, and practices are consistently aligned with evolving stakeholder needs and business objectives. It drives ongoing efforts to enhance value co-creation across all aspects of service management, making it integral to the SVS's dynamic nature.

An Emergency change is a specific type of change that must be implemented as quickly as possible, typically to resolve an active incident, restore a failed service, or apply a critical security patch. These changes often bypass some of the standard authorization and testing steps due to the extreme urgency and potential severe impact of delay. However, they still require post-implementation review and formal documentation to ensure governance and learning.

This is the stated purpose in ITIL 4.

The ability to export reports is a direct output, representing a specific, tangible deliverable or functionality provided by the new software feature. This option describes a concrete capability that the development team has engineered and released, which users can directly utilize. It is a direct product of the development effort, enabling subsequent outcomes and value for stakeholders.

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

The "Start where you are" principle mandates that an organization should not discard existing resources or processes without first thoroughly assessing their current state and potential utility. This involves evaluating what is already in place, including services, people, partners, processes, and technology, to determine what can be leveraged, improved, or adapted rather than initiating entirely new efforts from scratch. This principle directly applies when a project begins by understanding the current environment.

An exception event is specifically generated when a predefined operational or performance threshold has been violated, indicating a deviation from the expected or acceptable state of a service or component. This type of event signals that a specific metric, such as CPU utilization, memory usage, or response time, has crossed its upper or lower limit. It requires attention because it represents an actual breach, potentially impacting service quality or stability, and often triggers an alert for investigation.

This option is correct because ITIL 4's Four Dimensions of Service Management are intrinsically linked, forming a complex and interdependent system. A deficiency or change in one dimension, such as inadequate organizational capabilities, outdated technology, inefficient processes, or unreliable suppliers, will inevitably propagate and negatively affect the others. Neglecting any single dimension compromises the service's ability to create value effectively, leading to operational failures, reduced service quality, and an inability to meet stakeholder expectations.

Documenting a known error and providing a workaround is a critical activity within the 'error control' phase of Problem Management. A known error signifies that the root cause of a problem has been identified, and a workaround is a temporary solution that reduces or eliminates the impact of incidents while awaiting a permanent fix. This enables Incident Management to restore service more quickly and efficiently, minimizing business disruption for users.

In ITIL 4, the Customer is the individual or group who defines the requirements for a service and takes responsibility for the outcomes delivered by that service. They are the primary stakeholders who articulate their needs, desired utility, and warranty expectations, which directly inform the service provider's understanding of value. Their input is crucial for ensuring that services are designed and continually improved to meet specific business objectives and deliver the expected value.

When an organization outsources its email service, it transfers the direct operational control and security responsibility for the underlying infrastructure to the third-party provider. A compromise of the provider's email server by a hacker represents a critical third-party risk, as the organization's email data and service availability become directly dependent on the provider's security posture and incident response capabilities. This risk is a direct consequence of relinquishing internal control over the email infrastructure.

This statement accurately defines the core concepts in ITIL 4. An output is a specific, tangible or intangible deliverable produced by an activity, such as a report, a new system, or a processed request. An outcome, conversely, is the result or effect achieved for a stakeholder, often a benefit or a change in their situation, which is enabled by the consumption or use of one or more outputs.

Focus on value is one of the seven ITIL 4 guiding principles, directly satisfying the stem’s requirement to identify two correct principles from the ITIL 4 framework. This principle ensures that every improvement initiative, service, and process is explicitly linked to delivering measurable outcomes for stakeholders, preventing activity that does not contribute to perceived or realised value.

This is indeed the correct first step in the ITIL 4 Continual Improvement Model, establishing the clear purpose and desired outcome of any improvement initiative. It involves defining the overall direction, understanding stakeholder value, and ensuring alignment with organizational objectives. This foundational step provides the guiding star for all subsequent activities, ensuring that efforts are focused on achieving a meaningful and beneficial future state.

An SLA, or Service Level Agreement, formally establishes the agreed-upon service levels and responsibilities between a service provider and its customer, who consumes the service. Conversely, an OLA, or Operational Level Agreement, is an internal agreement between different teams or departments within the *same* service provider organization. Its purpose is to define the specific support activities and performance targets required to deliver the overall service levels committed in an SLA to the customer.

This is the core purpose of service management in ITIL 4.

A sponsor is a key stakeholder in service consumption, typically an individual or group responsible for authorizing the budget and providing strategic direction for the service. They ensure the service aligns with organizational objectives and often hold the ultimate authority for its funding and continued existence. The sponsor's involvement is crucial for securing resources and maintaining executive support throughout the service lifecycle, making them a distinct and vital role in the consumption process.

Software licensing fees are a common cost incurred by service providers, particularly when delivering services that rely on commercial off-the-shelf software, operating systems, or specialized applications. The provider often manages these licenses centrally, bundling their cost into the overall service offering, such as in Software as a Service (SaaS) models or managed application services. This ensures legal compliance and operational functionality, making it a direct component of the service's total cost.

The ITIL Continual Improvement Model, often referred to as the 7-step model, is the foundational framework for the Continual Improvement practice. This structured approach guides organizations through identifying opportunities, planning improvements, implementing changes, and reviewing outcomes across all services and products. It ensures that improvements are systematically managed and contribute directly to value creation and organizational objectives, making it central to sustained service excellence.

Demand represents the need or desire for products and services from internal or external consumers, acting as a fundamental input to the Service Value System. It directly prompts the SVS to initiate activities across its value chain to create or co-create value in response to these expressed requirements. The SVS is inherently designed to convert this demand into tangible outcomes and value for stakeholders. Consequently, demand is a primary and valid trigger for the SVS.

This is one of the ITIL guiding principles.

This is the precise ITIL 4 definition of an outcome. An outcome signifies the achievement or change in state that a stakeholder desires, which is made possible through the consumption and utilization of service outputs. It represents the actual value realized, distinct from the tangible deliverables (outputs) or the service's inherent utility, focusing on the ultimate impact for the consumer.

The core objective of the incident management practice is to minimize the negative impact of incidents by restoring normal service operation as swiftly as possible. This often involves implementing temporary workarounds to enable users to continue working, rather than immediately seeking a permanent fix. Rapid restoration ensures business continuity and reduces disruption to service consumers.

The ITIL guiding principles are a set of seven universal and enduring recommendations that guide an organization in all circumstances, regardless of changes in its objectives, strategies, or type of work. These principles, such as 'Focus on value' and 'Collaborate and promote visibility,' encourage good practices and sound decision-making across all levels and activities within the service value system. They serve as a foundational element, ensuring a consistent and effective approach to service management.

Defining the vision and direction is the correct first step in the ITIL Continual Improvement Model, corresponding to "What is the vision?". This foundational activity involves articulating a clear, high-level understanding of what the organization intends to achieve through its improvement efforts. Establishing this strategic context ensures that all subsequent improvement activities are aligned with organizational objectives, providing a guiding purpose before delving into current states, desired outcomes, or specific actions.

Problem identification is the crucial initial phase of Problem Management, focusing on detecting and logging problems. This activity involves proactively identifying potential issues through trend analysis of recurring incidents, analyzing significant single incidents that indicate an underlying flaw, or recognizing patterns from monitoring data, all with the goal of understanding the root causes of service disruption or degradation. It sets the foundation for subsequent investigation and resolution efforts.

Warranty includes availability, capacity, and performance.

"A monthly performance report generated by the IT system" is a clear example of an output. This report is a tangible artifact and a direct deliverable produced by an IT activity (report generation). It is a specific product that can be consumed or used by stakeholders, providing information, even though its ultimate purpose is to enable better decision-making (an outcome).

The Social factor in PESTLE analysis examines the demographic characteristics, cultural trends, and societal values of the population relevant to an organization's operations. This includes aspects like population growth rates, age distribution, health consciousness, lifestyle changes, and attitudes towards work and leisure. Understanding these external social dynamics is crucial for tailoring services, marketing strategies, and human resource policies effectively.

This is the core purpose of Service Level Management.

This principle directly advises that before any improvement initiative begins, the organization must thoroughly assess its current services, processes, and tools. It emphasizes understanding what is already in place, what works well, and what needs improvement, preventing unnecessary disruption and ensuring that valuable existing components are leveraged rather than discarded.

This statement identifies a specific functional capability that the system provides, enabling the automation of billing processes. In ITIL 4, utility refers to the functionality offered by a service, determining whether it is 'fit for purpose' by supporting the performance of tasks or the achievement of desired outcomes for the consumer. Providing automated billing directly contributes to the value derived from the service's core capabilities.

The Service Desk is the SPOC for users.

Products and services are the tangible or intangible offerings that result directly from the successful execution of activities within the service value chain. They are the primary outputs designed and delivered by the organization to meet consumer demand and enable value co-creation. These offerings embody the transformed inputs and efforts of the entire value chain, making them the quintessential output.

Neglecting the human element, including inadequate training, poor communication, and insufficient support during transitions, inevitably leads to poor user adoption of new systems. Without proper change management and engagement, users will struggle to understand the value, functionality, or necessity of new tools, resulting in underutilization or outright rejection. This directly hinders the realization of intended benefits and return on investment for technological advancements.

Service requests are for standard, pre-approved items like access requests.

Resetting a user's password is a classic example of a standard change because it is a routine, frequently occurring, and low-risk activity with a well-defined and proven procedure. This type of request is typically pre-authorized, allowing service desk staff to execute it immediately without requiring additional approvals, thereby ensuring efficient and rapid resolution for common user issues.

This is a key activity of Service Level Management.

This sequence accurately reflects the logical and controlled flow of activities within the ITIL 4 change enablement practice. It begins with a formal "Request," followed by a thorough "Assess" phase to understand impact and risk. "Authorize" grants permission, "Plan" details the execution, "Implement" performs the change, and "Review" confirms success and captures lessons learned, ensuring a structured and effective change process.

This is the foundational first step in the ITIL Continual Improvement Model. It establishes the overall direction and purpose for any improvement initiative, clearly articulating the desired future state and the value it aims to deliver. Without a clear vision, subsequent improvement efforts lack focus and a measurable target, making it impossible to align activities or assess success effectively. This initial step ensures all stakeholders understand the ultimate goal.

Capacity and Performance Management is the ITIL practice specifically designed to ensure that services and service components can meet current and future demand in a cost-effective way. It proactively plans, monitors, and optimizes the utilization of resources, including infrastructure, applications, and people, to guarantee that services consistently achieve their agreed-upon performance targets and user experience requirements. This practice involves understanding demand patterns, forecasting future needs, and making informed decisions about scaling or optimizing resources.

Correct. This dimension includes roles, responsibilities, and governance.

Problem management is the ITIL practice specifically designed to reduce the likelihood and impact of incidents by identifying and managing their underlying causes. When an organization repeatedly faces incidents from a recurring issue, problem management initiates root cause analysis to diagnose the systemic flaw. It then works to eliminate the problem or, failing that, establish effective workarounds and known errors to minimize future disruption.

The service value chain is a core component of the SVS.

Suppliers are stakeholders.

This activity is the second step of the ITIL Continual Improvement Model, focusing on establishing a clear understanding of the current state. It involves baselining existing services, processes, and practices to measure current performance and identify areas requiring improvement. This critical assessment provides the factual basis for setting realistic targets and tracking progress effectively throughout the improvement journey.

This principle directly advocates for identifying and eliminating anything that does not produce value or is not required to achieve the desired outcome. Removing unnecessary approval steps perfectly aligns with this, as it simplifies the process, reduces waste, and makes the service delivery more efficient and practical. It encourages using the minimum number of steps necessary to achieve the desired outcome effectively and efficiently.

The 'Start where you are' principle mandates that organizations assess their current state and leverage existing services, processes, people, and technology rather than attempting to create everything anew. It promotes a pragmatic approach, recognizing that current solutions often have value and can be improved incrementally. Understanding the current landscape prevents unnecessary disruption and ensures improvements are built upon a solid foundation.

One of the five components.

A service request is a formal request from a user for something standard that is part of normal service delivery, often pre-defined and pre-approved within a service catalogue. Requesting a new software installation, especially if it's a standard offering, perfectly aligns with this definition. These requests are typically low-risk, frequently occurring, and follow a standardized process for fulfillment.

Availability Management ensures that services and components deliver their agreed-upon availability targets, meeting the current and future needs of the organization and its customers. This practice involves planning, designing, implementing, measuring, and improving the availability of services, components, and IT infrastructure. It focuses on maximizing service uptime, reliability, maintainability, and serviceability to ensure services are accessible whenever required by users.

A Service Level Agreement (SLA) is a formal, documented agreement between a service provider and a customer that precisely defines the services to be provided and the specific, measurable level of service expected. It outlines key performance indicators (KPIs), availability targets, responsibilities of both parties, and often includes remedies or penalties for non-compliance. This document directly addresses the question by establishing the mutually agreed-upon service quality and performance benchmarks.

When a consumer utilizes an external service, the direct financial burden associated with the underlying infrastructure, such as purchasing, maintaining, powering, and housing servers, is typically absorbed by the service provider. This represents a cost that is effectively transferred from the consumer, who would otherwise incur these expenditures directly, to the provider. The consumer pays for the utility and warranty of the service, not the individual components, thereby offloading the operational and capital costs of infrastructure management.

The service desk acts as the SPOC for all user interactions.

The Service Configuration Management practice is precisely responsible for maintaining accurate information about Configuration Items (CIs) throughout their entire lifecycle. This includes identifying, controlling, recording, reporting, and verifying CIs, their attributes, and their relationships. It ensures that the organization has a clear understanding of its service components and their interdependencies, supporting effective service delivery and change management through baselines.

Focus on value is one of the guiding principles.

An emergency change is a high-priority change that must be implemented as soon as possible, typically to resolve an incident or implement a security fix that has an immediate and significant impact on services. These changes bypass some standard steps of the normal change process due to their urgency, often requiring a separate, expedited authorization process to minimize service disruption. Their primary goal is to restore service operation or prevent a major business impact.

Guiding principles are a core component of the SVS.

Governance is a fundamental component of the ITIL 4 Service Value System, providing the means by which an organization is directed and controlled. It encompasses the framework of authority and decision-making, ensuring that the service value chain and all ITIL practices are aligned with the organization's strategic objectives and stakeholder requirements. Effective governance is essential for achieving value co-creation.

Correct: Emergency changes are for urgent issues.

Neglecting proper security practices, such as regular vulnerability assessments, patch management, and access control reviews, directly leads to unaddressed weaknesses in systems and applications. This oversight significantly increases the likelihood of successful cyberattacks, unauthorized data access, and subsequent data breaches, compromising confidentiality, integrity, and availability of information assets.

This statement accurately distinguishes between a Service Level Agreement (SLA) and an Operational Level Agreement (OLA) according to ITIL 4 principles. An SLA is a documented agreement between a service provider and a customer that specifies the service to be provided, the agreed service levels, and the responsibilities of both parties. An OLA, on the other hand, is an internal agreement between different functional units or teams within the service provider organization, outlining their commitments and responsibilities to each other to ensure the delivery of the agreed service levels to the customer.

A warning event indicates a condition that, if left unaddressed, has the potential to escalate into a significant problem or service disruption. It serves as an early indicator, prompting proactive investigation or intervention before a critical threshold is breached. A server's disk usage reaching 80% precisely fits this category, as it signals a need for attention and potential action to prevent the disk from becoming full, which would then become a more severe issue.

Roles and responsibilities are a fundamental component of the "Organizations and People" dimension, defining the specific tasks, authorities, and accountabilities assigned to individuals and teams within the service organization. Clearly delineated roles ensure that all necessary activities for service delivery and support are covered, preventing gaps or overlaps and fostering efficient collaboration among personnel. This directly addresses the human element and organizational structure required for effective service management.

A monthly performance report is a concrete, tangible deliverable produced by a service or process, such as a reporting function. It is a specific artifact that can be physically or digitally handed over, reviewed, and stored. This report serves as a direct product of an activity, providing data and insights, and is therefore a clear example of an an output in ITIL 4, distinct from the value or benefits it might subsequently enable.

This principle advocates for breaking down large initiatives into smaller, manageable iterations, each with defined objectives and deliverables. Crucially, it emphasizes incorporating feedback loops at the end of each iteration to learn, adapt, and make necessary adjustments. This approach significantly reduces the risk of major disruption by allowing for course correction and ensuring that improvements align closely with evolving requirements and stakeholder needs.

Warranty, in ITIL 4, refers to the assurance that a service will meet agreed-upon requirements regarding its performance and fitness for use. This specifically includes aspects like availability (e.g., 99% uptime), capacity (ability to handle expected load), continuity (resilience to disruptions), and security (protection against unauthorized access). It answers the question "how well does the service perform?" and is typically defined in Service Level Agreements (SLAs) or other contractual terms.

The output (system) was delivered, but the outcome (improved efficiency) was not realized.