ITIL 4 Foundation (ITIL4F) — Questions 301–375

Incident Management restores service, Problem Management finds root cause, and Change Enablement implements the permanent fix.

The scenario describes a release broken into small, timeboxed iterations with frequent stakeholder reviews. This directly aligns with the 'Progress iteratively with feedback' guiding principle, which emphasizes delivering value incrementally and using feedback loops to adjust direction. In ITIL 4, this principle is about breaking work into manageable steps and validating each step with stakeholders to reduce risk and improve outcomes.

The 'Organisations and People' dimension addresses culture, roles, skills, authorities, and communication. The other options refer to the other three dimensions.

The first action for any incident, including a CRM system outage, is to log the incident in the ITSM tool. This ensures a formal record is created with details such as user impact, timestamp, and symptoms, which is the foundation for all subsequent incident management activities per ITIL 4. Without logging, there is no auditable trail or basis for prioritization, escalation, or problem management.

Incident Management is defined as restoring normal service ASAP. Option A is correct. Problem Management (B) finds root causes; Change Enablement (C) controls changes; Service Request Management (D) handles pre-defined requests.

Option D is correct because 'Manage risk at all times' is not one of the seven ITIL 4 guiding principles. The seven principles are: Focus on value, Start where you are, Progress iteratively with feedback, Collaborate and promote visibility, Think and work holistically, Keep it simple and practical, and Optimize and automate. Risk management is a practice within ITIL 4, not a guiding principle.

Option C is correct because Problem management in ITIL 4 is explicitly focused on identifying the root cause of incidents to prevent recurrence, aligning with the 'find root cause' activity. Option D is correct because Incident management's primary objective is to restore normal service operation as quickly as possible, minimizing business impact.

Option C is correct because ITIL 4 explicitly states that the four dimensions (Organizations & People, Information & Technology, Partners & Suppliers, Value Streams & Processes) must be applied to every service and every service management activity to ensure a holistic approach. This prevents siloed thinking and ensures that all aspects of service delivery are considered, from design through operation. Ignoring a dimension for any activity can lead to service failures, such as neglecting the 'Partners & Suppliers' dimension when managing a cloud-based service.

A service consumer is a generic role that includes customers (who authorize), users (who use), and sponsors (who fund).

Incident Management focuses on restoring service quickly, often with a workaround, while Problem Management identifies and resolves the root cause to prevent recurrence.

Iterative progress involves small, timeboxed cycles with feedback loops.

The service desk acts as a single point of contact for users to report issues, request services, and get support.

Availability management begins with defining requirements, then designing, monitoring, analyzing, and improving.

Keep it simple and practical emphasizes eliminating unnecessary complexity.

Option C is correct because, according to ITIL 4, a service request is a formal request from a user for something to be provided – for example, a new laptop. This is a standard, pre-approved change that follows a defined procedure, not an unplanned interruption or a failure. The user is not reporting an incident (the laptop is slow but still operational) or a problem; they are asking for a new asset as part of normal service delivery.

The change manager is reviewing the entire service value system (SVS) to understand how the change affects all components, which directly applies the 'Think and work holistically' guiding principle. This principle emphasizes considering the whole system—including all processes, technology, partners, and value streams—rather than focusing on isolated parts. By examining the SVS as a whole, the manager ensures that interdependencies and downstream impacts are identified before implementation.

According to ITIL 4, the first action for a service desk analyst when receiving a user-reported outage is to log the incident and categorize it. This ensures the incident is formally recorded, prioritized, and routed to the appropriate support team for resolution. Skipping this step would violate the incident management process, which mandates logging as the initial activity to maintain an accurate audit trail and enable proper escalation.

The service desk manager is considering the entire value chain—balancing speed (password reset automation) with security (password complexity policy)—rather than optimizing a single component. This aligns with 'Think and work holistically' because the decision integrates the security team's requirements, the service desk's efficiency goals, and the overall service value. By rejecting a tool that fails security compliance, the manager avoids suboptimizing the system for one stakeholder.

Incident Management restores service with a workaround; Problem Management identifies root cause; Change Enablement implements the fix. Option D is correct. Option A lacks Problem Management; Option B lacks Incident Management; Option C is incorrect.

An output is a tangible, deliverable result produced by an activity or process. A monthly financial report is a concrete, physical or electronic artifact that can be handed over, stored, and verified, making it a clear example of an output in ITIL 4.

Option A is correct because Service Level Management (SLM) practice includes monitoring actual service performance against agreed targets in Service Level Agreements (SLAs) and reporting on compliance. This ensures that service delivery meets the defined quality levels and provides transparency to both the service provider and the customer.

Value co-creation means value is created jointly by the provider and consumer through their interaction. The provider delivers resources, and the consumer uses them to achieve outcomes.

Value is the perceived benefits, usefulness, and importance of something. Here, the service enables outcomes (reduced time) that are valued by stakeholders.

Partners and Suppliers dimension includes contracts, sourcing strategy, and supplier management. The other dimensions focus on internal aspects.

Option A is correct because the 'Organization and People' dimension of ITIL 4 focuses on the human and structural aspects of service management, including clearly defining roles, responsibilities, and authority levels for service management activities. This ensures accountability and effective decision-making across the service value chain.

These are fundamental ITIL 4 definitions.

First call resolution rate is a key performance indicator for the Service Desk. Option A is correct. Options B, C, and D are not directly measured by FCR.

Standard changes are low-risk, pre-approved, and have a defined procedure. Normal changes require approval via change advisory board; emergency changes require urgent approval.

The 'Organizations and People' dimension focuses on roles, responsibilities, competencies, and culture. By defining workflows without assessing staff skills, the project team neglects the human factor required to operate the new CRM system effectively, risking adoption failure and operational inefficiency.

First Contact Resolution (FCR) and Customer Satisfaction Score (CSAT) are typical service desk metrics. Options B and C are correct. Option A is for Incident Management; Option D is for Availability Management; Option E is for Capacity Management.

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 achieved through a structured lifecycle that includes logging, categorization, prioritization, escalation, and resolution of incidents. The focus is on speed of recovery, not root cause analysis, which belongs to Problem Management.

Opportunity and demand are the external triggers that initiate the service value chain activities. The ITIL 4 Service Value System (SVS) defines these as the primary inputs that flow into the service value chain, prompting the creation, modification, or retirement of services to meet stakeholder needs.

In the ITIL 4 Four Dimensions model, the Information and Technology dimension specifically addresses the management of technology infrastructure, applications, and data. Information security is a key consideration here because it governs how data is protected, stored, and transmitted across systems, directly impacting the availability, confidentiality, and integrity of services. Without robust security controls, the technology dimension cannot ensure reliable service delivery.

The first step in incident management is to log and classify the incident to restore service as soon as possible. Root cause analysis belongs to problem management, which is initiated later if needed.

Warranty covers availability, capacity, continuity, and security. A backup system is part of continuity (warranty). Utility is about functionality.

In ITIL 4, an incident is defined as an unplanned interruption or reduction in quality of an IT service, while a problem is the underlying cause of one or more incidents. Option A correctly captures this distinction: incidents are the visible disruptions, and problems are the root causes that need to be identified and resolved to prevent recurrence.

A data protection regulation (e.g., GDPR) is a Legal factor in PESTLE. The other options are not PESTLE factors or are too generic.

Utility is 'fit for purpose' (does the service meet the required function?), while warranty is 'fit for use' (is the service available, secure, and reliable?).

The correct principles are 'Focus on value' and 'Optimise and automate'. 'Plan and implement' and 'Measure and improve' are not ITIL guiding principles.

Service Request Management uses the service catalogue to offer standardized, pre-approved requests.

C is correct because a standard change in ITIL 4 is a pre-authorized, low-risk, and frequently repeated change that follows a defined procedure. Deploying minor bug fixes that have been pre-authorized fits this definition, as the change is already approved and can be implemented without additional authorization.

Service request management starts with receipt, then categorization, fulfillment, verification, and closure.

The Organisations and People dimension addresses culture, roles, skills, authorities, and communication.

First Call Resolution (FCR) is a key metric for the Service Desk because it directly measures the percentage of incidents resolved during the first contact with the user, without the need for escalation or a callback. A high FCR indicates an efficient and knowledgeable Service Desk, reducing user downtime and operational costs. This metric is central to ITIL's focus on delivering value and minimizing disruption to business activities.

A new laptop for a new employee is typically a pre-approved, standard request that follows a defined procedure. This qualifies as a Service Request, not an Incident.

Information and Technology includes data, security, and compliance aspects. Regulatory requirements for data protection are addressed in this dimension. Option B is correct.

The Service Desk provides a single point of contact for users to report issues, ask questions, and request services.

The guiding principle 'Start where you are' focuses on understanding the current state and leveraging existing successes before making changes. Option A is correct.

The SVS includes the service value chain, guiding principles, governance, practices, and continual improvement. The two correct ones are service value chain and guiding principles.

The principle 'Start where you are' advises leveraging existing assets, processes, and capabilities rather than building from scratch. By reusing an existing process for the new service, the team avoids unnecessary rework and reduces risk, directly applying this principle to optimize resource use.

The Partners and suppliers dimension is correct because the outage originated from a third-party data center and network provider, which are external dependencies. ITIL 4 emphasizes managing relationships, contracts, and performance of external partners to ensure service continuity. Focusing on this dimension allows the provider to enforce SLAs, conduct joint risk assessments, and implement redundancy measures with suppliers.

The feature is an output (deliverable). The lack of increased effectiveness shows that the desired outcome was not achieved.

Option B is correct because the root cause is inefficient database queries, not insufficient hardware. Optimizing queries directly addresses the high CPU load by reducing the processing required per query, aligning with the ITIL guiding principle of 'Focus on Value' by solving the actual problem without unnecessary expenditure. This approach also respects the limited budget, as query optimization typically requires only DBA time rather than costly infrastructure upgrades.

Warranty relates to the service being 'fit for use', which includes availability and capacity. Utility (fit for purpose) includes functional requirements like quick search results.

Incident Management focuses on restoring service; Problem Management focuses on finding root causes. Problem Management may use workarounds from known errors.

The change order was approved based on the original scope, which did not include a reboot. The discovery that a reboot is required introduces a new risk (application outage) that was not assessed during the initial approval. The IT manager, as the change authority, must be informed and make a decision on whether to proceed with the change under the new circumstances, in line with the ITIL 4 'change enablement' practice of managing risk and ensuring authorized decisions.

The SVS consists of: Guiding Principles, Governance, Service Value Chain, Practices, and Continual Improvement. The other options are not components.

Service relationships include service provision, service consumption, and service relationship management. Options A and D are correct.

Option A is correct because identifying and documenting configuration items (CIs) is a foundational activity of Service Configuration Management. It ensures that all components of the IT infrastructure, including hardware, software, and documentation, are uniquely identified and recorded in the configuration management database (CMDB) to support control and traceability.

The 'Start where you are' guiding principle emphasizes using existing processes, services, and capabilities as a baseline before making improvements. By documenting the current service desk process and identifying what works well, the team avoids reinventing the wheel and leverages proven practices, which is the core of this principle.

Change enablement is the correct practice because it provides a structured process for assessing, authorizing, and implementing changes to IT infrastructure, directly addressing unauthorized changes that cause service outages. By enforcing a formal change model with defined roles (e.g., Change Manager) and approval gates, it ensures that only authorized, risk-assessed modifications are deployed, preventing the root cause of the outages.

Option B is correct because the problem management team should first implement a workaround to restore service and minimize business impact while the permanent fix is being developed. Restarting the application server every hour during peak times directly addresses the memory leak symptom by freeing accumulated memory, preventing CPU saturation at 95% and avoiding timeouts. This aligns with ITIL 4's guidance to apply a workaround as an interim measure when a known error exists and a fix is pending.

The Service Desk practice is explicitly defined in ITIL 4 as the single point of contact (SPOC) between the service provider and all users. Its primary purpose is to capture, manage, and resolve service requests and incidents, ensuring users have a consistent entry point for all interactions with IT services.