ITIL 4 Foundation (ITIL4F) — Questions 226–300

By reducing the number of steps in a change approval process, the team is eliminating unnecessary complexity and bureaucracy. This directly aligns with the 'Keep it simple and practical' guiding principle, which advocates for minimizing process overhead to achieve outcomes efficiently. The focus is on streamlining the workflow itself, not on automation or iterative feedback.

Service Configuration Management (C) is the ITIL 4 practice responsible for maintaining the Configuration Management Database (CMDB) and ensuring that Configuration Items (CIs) are accurate, up-to-date, and under controlled management. This practice focuses on defining, recording, and controlling CIs and their relationships, directly supporting the integrity of the CMDB.

Option A is correct because automation, when applied after optimization, reduces manual effort for repetitive tasks, freeing people to focus on complex, value-adding activities like problem-solving and innovation. This aligns with the ITIL 4 guiding principle 'Optimise and automate,' which emphasizes that automation should be applied to optimized processes to maximize efficiency and human potential.

The guiding principle 'Start where you are' emphasizes leveraging existing services, processes, and capabilities to avoid reinventing the wheel. Reusing an existing authentication module aligns with this principle. 'Focus on value' ensures everything contributes to value, but not specifically about reuse. 'Progress iteratively with feedback' is about incremental improvements, not reuse. 'Collaborate and promote visibility' is about working together and transparency.

A pre-approved software installation that follows a standard procedure is a classic service request, not a change or incident. Service request management handles predefined, low-risk requests where the approval and process are already established, such as installing approved software via a self-service catalog. This aligns with the ITIL 4 definition of a service request as a standardized, pre-authorized demand from a user.

ITIL 4 classifies events as informational, warning, or exception.

Option C is correct because organisational culture is explicitly defined within the ITIL 4 Organisations and People dimension, which focuses on how the organisation's structure, culture, and human resources enable value co-creation. This dimension ensures that the culture supports the service management strategy and that people have the right competencies and authority to perform their roles effectively.

Service management is defined as a set of specialized organizational capabilities for enabling value for customers in the form of services.

The primary purpose of Incident Management is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations.

The guiding principle 'Start where you are' recommends leveraging existing services, processes, and capabilities before creating new ones. Option B is correct.

Problem Management includes problem identification, root cause analysis (problem control), and managing known errors (error control). Monitoring services is part of Monitoring and Event Management. Managing changes is part of Change Enablement.

Holistic thinking considers the entire system and interconnections. Changing one component without considering impacts or optimizing a single element in isolation are not holistic. Considering end-to-end service and involving all departments are holistic approaches.

The scenario describes a service designed to deliver desired outcomes while shielding customers from managing specific costs and risks. This directly aligns with the ITIL 4 definition of a service, which is a means of enabling value co-creation by facilitating outcomes customers want to achieve, without the customer having to manage the associated costs and risks. Options like utility, outcome, or warranty are components of value but do not capture the full concept of a service as a delivery mechanism that abstracts away cost and risk management.

Incident Management focuses on restoring normal service operation as quickly as possible after an unplanned interruption or service degradation, minimizing business impact. Problem Management, in contrast, seeks to identify and eliminate the root cause of incidents to prevent recurrence. This fundamental distinction in purpose—restoration versus root cause analysis—is the key difference tested in the ITIL 4 Foundation exam.

Incident management aims to restore normal service operation as quickly as possible and minimize adverse impact.

Standard changes are pre-authorized and follow a defined procedure, making them suitable for routine requests.

Availability Management is the ITIL 4 practice specifically tasked with ensuring that IT services deliver the agreed level of availability to meet business requirements. It involves planning, measuring, and improving the availability of services, components, and supporting infrastructure, directly aligning with the question's focus on delivering agreed availability levels.

Problem Management aims to identify and remove the root causes of incidents to prevent recurrence.

The Monitoring and Event Management practice is specifically designed to observe IT services and infrastructure, detect events (e.g., SNMP traps, syslog messages, performance threshold crossings), and classify them (e.g., informational, warning, exception) so that the appropriate response—such as automated remediation, alerting, or incident creation—can be triggered. This aligns with ITIL 4's definition of the practice as ensuring that events are systematically identified and acted upon to maintain service availability and performance.

The ITIL 4 Service Value System (SVS) is a structured framework that includes the service value chain and guiding principles as core components. The service value chain (C) is a set of interconnected activities that an organization performs to deliver value, while guiding principles (E) are universal recommendations that guide decision-making. Both are explicitly defined as components of the SVS in the ITIL 4 Foundation syllabus.

Events are classified as informational, warning, or exception. A warning event occurs when a threshold is exceeded but service is not yet affected. Exception events indicate actual service disruption.

Warranty is 'fit for use' – assurance that a service will meet agreed requirements such as availability, capacity, continuity, and security.

A password reset is a standard, pre-approved request for information or access that follows a defined procedure, which aligns with ITIL 4's definition of a service request. It does not involve restoring a failed service (incident), altering a configuration (change), or investigating an underlying cause (problem).

The principle 'Start where you are' emphasizes leveraging existing services and processes rather than starting from scratch. Adjusting a working process aligns with this principle.

IT Asset Management (ITAM) is the ITIL 4 practice responsible for managing the complete lifecycle of all IT assets, including financial and contractual aspects. It covers planning, acquisition, deployment, maintenance, and disposal, ensuring cost optimization and compliance with vendor contracts. This aligns directly with the question's emphasis on lifecycle management plus financial and contractual oversight.

Option D (Keep it simple and practical) is correct because the monitoring tool is generating alerts for every minor performance fluctuation, which adds unnecessary complexity and noise. This violates the principle of minimizing complexity to achieve outcomes efficiently; a practical approach would filter alerts to only those requiring action, preventing the service desk from being overwhelmed.

Warranty assures that the service will meet agreed conditions like availability, capacity, and security – fitness for use.

Option C is correct because the guiding principle 'Keep it simple and practical' emphasizes eliminating unnecessary complexity. In change management, approval steps that do not add value (e.g., redundant sign-offs for low-risk changes) cause delays without improving quality. By removing such steps, the process becomes more efficient while still maintaining appropriate controls.

The primary purpose of Incident Management is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations. This is defined in ITIL 4 as the core objective of the practice, focusing on speed of resolution rather than root cause analysis or change authorization. Option C directly aligns with this definition.

The ITIL 4 Service Value System (SVS) includes the Guiding Principles, Governance, Service Value Chain, Practices, and Continual Improvement. 'Opportunity, demand, and value' are inputs and outputs, not components.

Governance is a core component of the ITIL 4 Service Value System (SVS). It ensures that the organization's activities and resources are aligned with its objectives through direction, monitoring, and control. Without governance, the SVS would lack the oversight needed to guide decision-making and compliance.

Service requests are for pre-defined, pre-approved items in the service catalogue. Since this request is not in the catalogue, it should be handled as a normal change (or possibly a service request after approval). However, the best answer is a normal change as it requires assessment and approval.

Service Level Management (SLM) is the ITIL practice specifically tasked with negotiating, agreeing, and monitoring service level targets. It defines, documents, and manages Service Level Agreements (SLAs) and Operational Level Agreements (OLAs) to ensure that the delivered service meets agreed performance metrics. This practice is the single point of accountability for service level achievement and continuous improvement against those targets.

Incidents should be logged immediately to restore service; problem management is initiated later to find the root cause.

Option A is correct because the ITIL 4 Service Value System (SVS) is designed to provide a holistic, end-to-end model for service management, integrating all components (guiding principles, governance, service value chain, practices, and continual improvement) to enable value co-creation. It does not replace existing management systems but rather aligns and coordinates them within a unified framework.

Service Level Management involves negotiating, agreeing, and monitoring SLAs, as well as reporting on service performance.

The scenario focuses on technology benefits but neglects the impact on people (training, productivity loss).

Resetting permissions for an unplanned access issue is restoring a failed service, which is Incident Management.

Problem Management (C) is the correct practice because it focuses on identifying the root cause of recurring incidents to prevent future occurrences. The IT team's decision to analyze a recurring incident pattern and find its root cause aligns directly with the proactive and reactive activities of Problem Management, which aims to minimize the impact of incidents and prevent them from happening again.

The correct answer is A because the project team focused on technology and processes but neglected the 'Organizations and People' dimension by not involving the HR department in defining service outcomes. ITIL 4 emphasizes that all four dimensions must be balanced; ignoring the people and organizational aspects, such as stakeholder engagement and culture, leads to misaligned services that fail to deliver value, regardless of how efficient the technology or processes are.

Service consumers include customers, users, and sponsors. In this context, customers and users are direct consumers.

They have identified the problem and are controlling it by finding a workaround; this is the 'Problem Control' phase.

The SVS components are: Guiding principles, Governance, Service value chain, Practices, and Continual improvement.

Value is co-created through active participation of both provider and consumer. Providers contribute resources, while consumers contribute their own resources and needs. Value is not solely created by the provider, nor is it always monetary.

Events include informational, warning, and exception types. A printer running low on toner is a warning event; a server reaching 100% CPU usage is an exception event.

Political factors (e.g., trade sanctions), Economic factors (e.g., recession), and Legal factors (e.g., regulations) are PESTLE categories. Culture and technology are internal or part of other dimensions.

The cross-functional team including developers, operations, and support staff directly applies the 'Collaborate and promote visibility' guiding principle. By breaking down silos and sharing knowledge across roles, the team gains a complete view of the incident lifecycle, enabling faster root cause analysis and resolution. This principle emphasizes that collaboration and transparency are essential for effective service improvement, especially when reducing incident resolution time.

Skills and competencies are part of the Organisations and People dimension.

Deliver & support includes monitoring and managing services in operation, so adding monitoring tools directly affects this activity.

FCR (First Contact Resolution) and CSAT (Customer Satisfaction) are common service desk metrics.

The Service Desk provides a single point of contact (SPOC) for users to report incidents, submit service requests, and get assistance, ensuring effective communication.

In ITIL 4, an exception event indicates that something has occurred that deviates from normal operation, often requiring immediate attention. A high-priority alert triggered by a monitoring tool automatically detecting and classifying events fits this definition, as it signals a significant anomaly that may impact services.

Implementing a self-service password reset tool automates a repetitive manual process (password reset requests), which directly aligns with the ITIL guiding principle 'Optimise and automate'. The team is not just making the process simpler; they are replacing human intervention with technology to reduce incident volume and improve efficiency.

According to ITIL 4, the first action for any reported service disruption is to log the incident and categorize it appropriately. This ensures the incident is formally recorded, prioritized, and routed for resolution. Without logging, no structured response or escalation can occur, and the incident cannot be tracked or measured.

Opportunities and demand are the two main triggers that start value streams.

The guiding principle 'Start where you are' emphasizes using existing documentation, workflows, and processes as a baseline before making changes. By reviewing current incident management documentation and workflows, the team ensures they understand the current state, avoiding unnecessary rework and leveraging what already works. This aligns with ITIL 4's recommendation to assess and build upon existing practices rather than starting from scratch.

Option C is correct because the 'Progress iteratively with feedback' principle breaks work into smaller, manageable increments, allowing teams to detect and correct issues early. This iterative approach prevents the accumulation of errors that could lead to large-scale failures, as each increment is validated before proceeding, reducing the overall risk.

The ITIL Continual Improvement Model has 7 steps: What is the vision?; Where are we now?; Where do we want to be?; How do we get there?; Take action; Did we get there?; How do we keep the momentum going?

Data protection regulations are legal requirements, so this is the Legal factor.

The Service Desk practice in ITIL 4 serves as the single point of contact between the service provider and users. Its primary purpose is to capture, manage, and progress all service requests and incidents, ensuring they are logged, categorized, prioritized, and routed to the appropriate resolution teams. This aligns with the ITIL 4 definition that the Service Desk is the entry point for all user interactions, not a specialized technical function.

The Information and Technology dimension is the correct focus because it directly addresses the technical architecture required to meet the business requirements for uptime, security, and scalability. This dimension includes the specific technologies, such as load balancers for scalability, firewalls and encryption for security, and redundant infrastructure for uptime, ensuring the e-commerce platform's technology stack is aligned with business goals.

Start where you are is applied by using existing systems. Think and work holistically might be overlooked if they ignore how the new tool affects other systems.