ITIL 4 Foundation (ITIL4F) — Questions 451–525

Option D is correct because it directly applies the ITIL guiding principles of 'Start where you are' (by mapping the startup's existing DevOps processes), 'Collaborate and promote visibility' (via a joint team), and 'Progress iteratively with feedback' (incremental rollout with feedback loops). This approach avoids the resistance and disruption of forced adoption while creating a lightweight integrated process that satisfies both the need for visibility and the startup's agility requirements.

Problem Management is responsible for identifying the root cause of incidents and ensuring permanent fixes are applied. Incident Management focuses on restoring service quickly, often via workarounds.

In ITIL 4, change types are categorized as standard, normal, and emergency. A normal change (B) is a change that is not standard or emergency and must follow the full change management process, including assessment, authorization, and scheduling. This is a core definition in the ITIL 4 framework.

The 'Engage' value chain activity is specifically about understanding stakeholder needs, managing relationships, and ensuring transparency and communication throughout the service lifecycle. It involves interacting with customers, users, and other stakeholders to gather requirements, provide updates, and obtain feedback, which aligns directly with option A.

Options A, B, and D are correct. The six value chain activities are: Plan, Improve, Engage, Design & Transition, Obtain/Build, Deliver & Support. 'Monitor' is a step in the continual improvement model, not a value chain activity. 'Problem Management' is a practice.

An output is a tangible deliverable, while an outcome is the result for the stakeholder. Option A is correct. Option B reverses the definitions; Option C is about utility vs warranty; Option D is incorrect.

An incident is an unplanned interruption to a service or reduction in its quality. The inability to print is an unplanned reduction in service quality.

An output is a tangible deliverable (e.g., a report), while an outcome is the result for a stakeholder (e.g., improved decision-making).

This principle is about working in timeboxed iterations, incorporating feedback, and avoiding big-bang approaches. It does not require full feedback before starting (that would be waterfall), and it does not advocate for small changes without coordination.

The service desk analyst is handling a customer complaint and implementing a workaround for a known error. This aligns with the incident management practice, which focuses on restoring normal service operation as quickly as possible. The workaround is a temporary fix to resolve the incident, not a permanent solution, which is why incident management is the correct practice.

Option B is correct because the 'service desk' practice is explicitly defined in ITIL 4 as the single point of contact (SPOC) between the service provider and users. This ensures that all user interactions, whether for incidents, service requests, or general inquiries, are funneled through a consistent channel, reducing confusion and improving response times.

In the Monitoring and Event Management practice, an event is any change of state that has significance for the management of a service or configuration item. Option C is correct because a server CPU utilization exceeding a threshold is a predefined condition that triggers an event, often an 'alert' or 'warning' event, which is automatically detected by monitoring tools (e.g., SNMP traps, Prometheus alerts) and requires attention or automated response.

Change Enablement involves a Change Authority (who approves changes) and a Change Manager (who oversees the process). The Service Desk Manager is not necessarily involved.

Options A and B are correct. The SVS consists of: Guiding Principles, Governance, Service Value Chain, Practices, and Continual Improvement. 'Service desk' is a function, and 'Configuration management database' is a tool.

Availability Management is responsible for ensuring services are available as agreed in SLAs.

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

The service desk manager is overlooking the 'Focus on value' guiding principle because she is implementing a new knowledge base system without first analyzing incident patterns to ensure the solution addresses the actual root cause of repeat incidents. This principle requires that all improvements directly contribute to value for stakeholders, and skipping pattern analysis risks investing in a solution that may not reduce repeat incidents, thus failing to deliver the intended value.

'Start where you are' advises to assess the current system before building a new one. They should understand what the legacy system does well and what needs improvement.

First Contact Resolution (FCR) is a key performance indicator for service desks, measuring how often issues are resolved during the initial contact without escalation.

The 'Think and work holistically' guiding principle is correct because it explicitly addresses the interconnected nature of services as complex systems. ITIL 4 states that a change in one service component (e.g., a database update) can have cascading effects on other components (e.g., application performance or user experience), requiring a systems-thinking approach to avoid unintended consequences.

Continual Improvement includes defining improvement initiatives, using the improvement register, and applying the ITIL continual improvement model. Options A, B, and D are correct. Option C is part of Service Level Management; Option E is part of Monitoring and Event Management.

The migration changes technology (Information and Technology) and likely involves a new vendor relationship (Partners and Suppliers).

A 99.9% uptime guarantee is a formal commitment to the availability and capacity of the service, which directly aligns with the ITIL 4 concept of 'Warranty'. Warranty ensures the service will be available, secure, and have sufficient capacity to meet agreed terms, often expressed as a Service Level Agreement (SLA) metric. This is distinct from 'Utility', which defines what the service does (its functionality), not how reliably it is delivered.

Capacity and Performance Management is the correct practice because it specifically focuses on ensuring that services achieve agreed and expected performance levels, including during peak demand periods. This practice involves monitoring current usage, forecasting future demand, and planning capacity to meet service level targets, making it directly responsible for performance under load.

First-call resolution (FCR) is the ITIL 4 metric that directly measures the percentage of incidents resolved during the initial contact with the service desk, without escalation or callbacks. Improving FCR reduces operational costs and enhances user satisfaction by eliminating the need for follow-up interactions, which aligns precisely with the company's goal of improving its service desk's first-call resolution rate.

Involving representatives from finance, legal, and operations in planning meetings directly applies the 'Collaborate and promote visibility' guiding principle. This principle emphasizes that cross-functional collaboration and transparent communication are essential for successful service management, especially when implementing a new cloud service that impacts multiple stakeholders. By including these diverse teams early, the IT department ensures that requirements, risks, and constraints are visible to all parties, reducing silos and enabling informed decision-making.

The first step is to log the incident, which captures details and initiates the incident management process.

Warranty is about 'fitness for use'—assurance that the service will meet agreed conditions like availability, capacity, and security.

PESTLE includes Political, Economic, Social, Technological, Legal, Environmental. Option A (Political), Option B (Economic), and Option E (Technological) are correct. Option C (Organizational culture) and Option D (Internal processes) are internal.

Service relationships involve cooperation between provider and consumer. Outsourcing and using a cloud provider are clear examples. Internal team collaboration is not a service relationship per se, and vendor management is a practice, not a relationship.

Problem Management is responsible for managing the lifecycle of all problems, including updating the Known Error Database (KEDB) with workarounds. After a major incident is resolved, the workaround is documented in the KEDB by Problem Management to prevent future incidents and enable faster resolution. This aligns with ITIL 4's definition of Problem Management as the practice that identifies, analyzes, and documents known errors and workarounds.

Partners and Suppliers dimension deals with relationships and contracts with external providers.

The principle 'Progress iteratively with feedback' directly supports increasing release frequency by breaking down the six-month release cycle into smaller, incremental deliveries. Each iteration incorporates feedback from stakeholders and users, allowing the team to adapt and release features more frequently, which is a core Agile practice.

Data encryption and backups are about assurance and protection – key aspects of warranty (fitness for use).

Utility is 'fit for purpose' – does it support the user's goals? If targets are met but users are unsatisfied, the service likely lacks utility. Warranty is about availability etc., which may be fine.

An output is a tangible deliverable (e.g., a report), while an outcome is the result for a stakeholder (e.g., improved decision-making). Option D is correct.

An unplanned interruption to a service is an incident. Even though it occurred after maintenance, users are now unable to access the service, which constitutes a loss of service – the definition of an incident.

The service has utility (users can store/retrieve files) but lacks warranty because there is no backup or redundancy, meaning availability and capacity are not assured.

The SVS includes guiding principles, governance, service value chain, practices, and continual improvement.

The policy for service design that ignores existing services and processes directly contradicts the 'Start where you are' guiding principle. This principle emphasizes leveraging what already exists (current services, processes, and capabilities) as a foundation for improvement, rather than designing from scratch. By disregarding current state, the organization wastes resources and risks losing valuable insights from existing operations.

Outputs are deliverables; outcomes are results achieved by using outputs. The same output can lead to different outcomes for different stakeholders.

Option B is correct because the IT manager should first implement a problem management practice to systematically analyze the recurring authentication failures and slow page load times. This aligns with ITIL 4's guiding principle of 'focus on value' by addressing root causes rather than symptoms, reducing incident volume long-term without additional cost. The 30% incident increase and lack of root cause identification indicate a reactive approach, and problem management directly targets this gap to improve service stability.

Neglecting other dimensions like people or processes can lead to poor adoption and value. Option D identifies a common consequence. The others are less direct.

Service requests are pre-approved, standard requests like password resets. Options C and D are incidents or problems; option B is a change.

Monitoring and Event Management detects events, classifies them (informational, warning, exception), and responds appropriately.

Informational, warning, and exception are the three event types recognized in ITIL 4.

Think and work holistically encourages viewing the organization as a whole system.

IT Asset Management (ITAM) is the correct practice because it is specifically defined in ITIL 4 to manage the lifecycle of all IT assets, including their financial aspects such as procurement, depreciation, and disposal. This practice ensures that assets are accounted for, controlled, and optimized from acquisition to retirement, directly covering financial management of hardware, software, and licenses.

The incident manager is applying the 'Progress iteratively with feedback' guiding principle by conducting a root cause analysis on recurring incidents. This principle emphasizes using feedback loops to improve processes iteratively, rather than attempting a single large-scale fix. By analyzing the root cause, she can implement targeted improvements and monitor their effectiveness over time, aligning with ITIL's iterative approach to continual service improvement.

Neglecting this dimension can lead to poor contract management and supply chain issues. Option B is about people; option E is about technology.

The Service Value System (SVS) is designed to ensure that all four dimensions of service management—organizations and people, information and technology, partners and suppliers, and value streams and processes—are holistically considered for value co-creation. This prevents siloed thinking and aligns every component toward delivering value, which is the primary purpose of the SVS.

The guiding principles are a component that directs behavior and decision-making.

The 'Start where you are' guiding principle advises leveraging existing services, processes, and data rather than rebuilding from scratch. In this scenario, migrating all historical data from the old incident management tool may not deliver proportional value—old data could be incomplete, poorly structured, or irrelevant to current operations. The principle suggests evaluating which data is truly useful for incident analysis, trending, or compliance, and discarding the rest to avoid unnecessary cost and complexity.

Error control, part of Problem Management, manages known errors through their lifecycle.

The 'Start where you are' guiding principle in ITIL 4 directs organizations to leverage existing services, processes, and data rather than building from scratch. It avoids unnecessary complexity by assessing current capabilities and making incremental improvements, which aligns with minimizing waste and rework.

Change Enablement defines three change types: standard, normal, and emergency.

Option B is correct because the 'Start where you are' guiding principle emphasizes leveraging existing investments and capabilities rather than discarding them. It directs organizations to assess current services, processes, and tools to identify what can be reused or improved, avoiding unnecessary rework and reducing risk.

Skills are part of the Organizations and People dimension. Overlooking skills means this dimension was neglected.

Shift-left in the service desk involves empowering front-line staff with better tools, knowledge, and automation to resolve issues at the first point of contact. This directly increases first contact resolution (FCR) rates because technicians can handle more incidents without escalating. Higher FCR reduces the number of incidents that need to be passed to higher-level support, which is the second correct benefit.

Service requests are predefined, pre-approved, and follow a standard process, unlike incidents which are unplanned.

PESTLE stands for Political, Economic, Social, Technological, Legal, Environmental. Economic conditions and new technology trends are external. Internal policies and staff skills are internal.

The monitoring system that sends alerts when CPU usage exceeds 90% directly involves detecting and responding to operational events. This is the core function of the Monitoring and Event Management practice, which defines how events (such as threshold breaches) are captured, analyzed, and acted upon. The alert itself is an 'event' in ITIL 4 terms, making this practice primarily responsible.