ITIL 4 Foundation ITIL4F Questions 226–300 | Page 4/11

226

Multi-Selectmedium

Which TWO of the following are phases of the Continual Improvement Model in ITIL 4?

Select 2 answers

A.Escalate to management

B.Take action

C.Where are we now?

D.Perform root cause analysis

E.Define the problem statement

AnswersB, C

The 'Take action' phase is the fifth step in the ITIL 4 Continual Improvement Model, directly following the 'How do we get there?' phase. In this critical stage, the planned improvements and solutions are implemented, executed, and put into operation. This involves making the necessary changes to services, products, or practices, ensuring the designed improvements are actively deployed and integrated.

Why this answer

In ITIL 4, the Continual Improvement Model consists of seven steps, and option B ("Take action") is one of them — it is the step where the improvement plan is executed, making it a correct phase. Option C ("Where are we now?") is also a correct phase; it is the first step of the model, used to establish the current baseline before deciding where the organization wants to be. The remaining options are not phases of the ITIL 4 Continual Improvement Model: "Escalate to management" (A) is an incident management activity, "Perform root cause analysis" (D) belongs to problem management, and "Define the problem statement" (E) is a general problem-solving technique rather than a named step in the model.

Exam trap

The trap here is that candidates confuse common problem-solving steps (like root cause analysis or escalation) with the specific, named phases of the ITIL 4 Continual Improvement Model, leading them to select options that are not part of the official model.

Full explanation →

227

MCQmedium

Which PESTLE factor is being considered when an organization reviews new data protection regulations before launching a service?

A.Technological

B.Political

C.Legal

D.Economic

AnswerC

The Legal factor specifically addresses the laws, regulations, and legal frameworks that govern how an organization operates, including industry-specific compliance requirements, data protection laws (e.g., GDPR), consumer protection acts, and employment legislation. This factor directly concerns the mandatory rules and standards an organization must follow to avoid penalties and ensure lawful conduct, making it the correct consideration for regulatory adherence.

Why this answer

Data protection regulations, such as GDPR or HIPAA, are legal frameworks that mandate how personal data must be handled, stored, and protected. When an organization reviews these regulations before launching a service, it is directly assessing the Legal and regulatory PESTLE factor to ensure compliance and avoid penalties. This is distinct from Political factors, which involve government stability or policy directions, and Technological factors, which focus on infrastructure or software capabilities.

Exam trap

The trap here is that candidates confuse 'Political' with 'Legal' because both involve government actions, but Political refers to broader policy and stability, while Legal specifically addresses enacted laws and regulations like data protection rules.

How to eliminate wrong answers

Option A is wrong because Technological factors cover hardware, software, and automation capabilities, not compliance with data protection laws. Option B is wrong because Political factors relate to government stability, trade policies, or lobbying, not specific regulatory requirements like data protection. Option D is wrong because Economic factors involve market trends, inflation, or funding, not legal obligations such as data privacy regulations.

Full explanation →

228

Multi-Selecthard

Which THREE of the following are characteristics of a service request?

Select 3 answers

A.Unplanned

B.Low risk

C.Pre-approved

D.Require approval from the Change Advisory Board

E.Predefined and standardized

AnswersB, C, E

Service requests are characterized by their low inherent risk because they involve well-established, routine procedures with predictable outcomes. The potential for negative impact on IT services, users, or the business is minimal, as these requests typically concern standard offerings and have been thoroughly vetted. This low-risk profile allows for streamlined processing and often automated fulfillment without extensive scrutiny.

Why this answer

Option B (Low risk) is correct because service requests are routine, well-understood interactions that carry minimal risk to the environment, unlike changes that may disrupt services. Option C (Pre-approved) is correct because service requests are typically pre-authorized within the service catalog, allowing fulfillment teams to act without seeking separate change approval. Option E (Predefined and standardized) is correct because service requests follow documented, repeatable procedures and are offered as standardized catalog items, ensuring consistent delivery.

Option A (Unplanned) does not belong because service requests are planned, expected interactions initiated by users through normal channels, not unplanned events. Option D (Require approval from the Change Advisory Board) does not belong because CAB approval is associated with normal changes, whereas service requests are pre-approved and do not require CAB review.

Exam trap

ITIL4F often tests the confusion between service requests and changes; candidates may incorrectly think service requests require CAB approval or are unplanned.

Full explanation →

229

MCQeasy

What is the PRIMARY purpose of the Service Desk practice in ITIL 4?

A.To manage the lifecycle of all IT assets

B.To capture and manage all service requests and incidents

C.To analyze root causes of recurring incidents

D.To monitor the performance of IT services

AnswerB

The Service Desk serves as the crucial Single Point of Contact (SPOC) between the service provider and its users, primarily responsible for handling all user interactions. Its core purpose is to capture, log, categorize, prioritize, and manage both incidents (unplanned interruptions to a service) and service requests (a formal request from a user for something standard). This ensures prompt restoration of normal service operation and efficient fulfillment of user needs.

Why this answer

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.

Exam trap

The trap here is that candidates confuse the Service Desk's role as a communication hub with the specialized practices of Problem Management (root cause analysis) or Monitoring and Event Management (performance tracking), leading them to select options that describe those separate ITIL practices.

How to eliminate wrong answers

Option A is wrong because managing the lifecycle of all IT assets is the primary purpose of the IT Asset Management (ITAM) practice, not the Service Desk. Option C is wrong because analyzing root causes of recurring incidents is the responsibility of the Problem Management practice, which uses techniques like 5 Whys or Kepner-Tregoe analysis. Option D is wrong because monitoring the performance of IT services is the core function of the Monitoring and Event Management practice, which uses tools like SNMP traps or synthetic transactions to track service health.

Full explanation →

230

MCQeasy

A retail company is launching a new e-commerce platform. The IT team must ensure the platform's uptime, security, and scalability. Which dimension of IT service management should the team primarily focus on to align technology with business requirements?

A.Organizations and People

B.Information and Technology

C.Partners and Suppliers

D.Value Streams and Processes

AnswerB

This dimension is precisely concerned with the information and knowledge managed by the organization, alongside the technologies and applications that facilitate services. For a new e-commerce platform, considerations like ensuring high uptime through resilient architecture, implementing robust security controls to protect customer data, and designing for scalability to handle fluctuating demand are all direct concerns of this dimension, encompassing infrastructure, software, and data management.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse 'Information and Technology' with 'Value Streams and Processes' because they think processes like incident management for uptime are the primary focus, but the question specifically asks about aligning technology with business requirements, which is the core of the Information and Technology dimension.

How to eliminate wrong answers

Option A is wrong because 'Organizations and People' focuses on roles, culture, and skills, not on the technical alignment of the platform's uptime, security, and scalability. Option C is wrong because 'Partners and Suppliers' deals with external dependencies like third-party vendors or cloud providers, but the primary alignment of technology with business requirements for a new platform starts with the internal technology architecture, not external relationships. Option D is wrong because 'Value Streams and Processes' concerns workflows and procedures for delivering services, not the direct technical configuration of the platform's uptime, security, and scalability.

Full explanation →

231

MCQhard

An IT team is implementing a new monitoring tool. They choose to integrate it with the existing ticketing system rather than building a new one from scratch. Which principle is applied, and which principle might be overlooked if they don’t consider the impact on other tools?

A.Keep it simple is applied; Focus on value might be overlooked

B.Collaborate is applied; Start where you are might be overlooked

C.Start where you are is applied; Think and work holistically might be overlooked

D.Progress iteratively is applied; Optimise and automate might be overlooked

AnswerC

When implementing a new monitoring tool, an IT team will almost certainly leverage existing infrastructure, data sources, and operational processes, which directly aligns with the "Start where you are" principle. However, the focused task of tool implementation can inadvertently lead to overlooking the wider implications across the entire service value system, including impacts on other services, processes, partners, and technology components, thereby potentially neglecting the "Think and work holistically" principle.

Why this answer

The team is reusing the existing ticketing system rather than building a new one, which directly applies the 'Start where you are' principle by leveraging current investments and processes. However, if they fail to assess how the new monitoring tool will interact with other tools (e.g., CMDB, notification services, or reporting dashboards), they overlook 'Think and work holistically,' risking integration failures, data silos, or performance degradation across the service value chain.

Exam trap

The trap here is that candidates confuse 'Start where you are' (reusing existing systems) with 'Keep it simple' or 'Progress iteratively,' and fail to recognize that the overlooked principle is 'Think and work holistically' because the question specifically warns about not considering the impact on other tools.

How to eliminate wrong answers

Option A is wrong because 'Keep it simple' focuses on minimizing complexity, but the scenario describes reuse of an existing system, not simplification of a process or design; 'Focus on value' is not overlooked here since integrating with an existing system can deliver value, but the primary risk is missing holistic impacts. Option B is wrong because 'Collaborate' involves cross-team cooperation, which is not the core principle demonstrated by reusing an existing system; 'Start where you are' is actually applied, not overlooked. Option D is wrong because 'Progress iteratively' involves incremental improvements, not the direct reuse of an existing system; 'Optimise and automate' might be relevant to the monitoring tool itself, but the overlooked principle in this context is holistic thinking, not automation.

Full explanation →

232

MCQmedium

An organization monitors IT systems and detects an event indicating that a disk is 80% full. According to ITIL 4, what type of event is this?

A.Informational event

B.Warning event

C.Exception event

D.Error event

AnswerB

A warning event indicates a condition that is deviating from normal operational parameters but has not yet caused a service disruption or degradation. It serves as an early alert, signaling a potential future problem if left unaddressed, such as a disk approaching full capacity or high CPU utilization. Proactive intervention based on a warning event can prevent an actual incident, making it a critical classification for effective event management. The detection of an event that requires attention but isn't yet an incident aligns perfectly with a warning.

Why this answer

In ITIL 4, a warning event is an event that indicates a threshold has been reached or a condition that could lead to an incident if not addressed. A disk being 80% full is a typical example of a warning event because it signals a potential issue that requires attention but is not yet a failure. It is not an error or exception because the system is still operational.

Exam trap

ITIL4F often tests the distinction between warning and exception events, causing candidates to misclassify threshold-based alerts as exceptions when they are actually warnings.

How to eliminate wrong answers

Option A is wrong because an informational event is a normal operational event that does not require action, such as a user logging in or a backup completing successfully; an 80% full disk is not merely informational as it may require proactive action. Option C is wrong because an exception event indicates that a service or component is operating outside normal parameters, often resulting in a breach of service level or a failure; an 80% full disk is a threshold warning, not an exception. Option D is wrong because an error event indicates a failure or fault that has occurred, such as a disk full error or a service crash; at 80% full, no error has occurred yet.

Full explanation →

233

MCQmedium

During a major incident, a workaround is applied by the service desk. Later, Problem Management identifies the root cause and implements a permanent fix through a normal change. Which sequence of practices is being followed?

A.Service Request Management → Incident Management → Change Enablement

B.Problem Management → Incident Management → Change Enablement

C.Change Enablement → Incident Management → Problem Management

D.Incident Management → Problem Management → Change Enablement

AnswerD

This sequence accurately reflects the ITIL 4 approach to managing service disruptions and their underlying causes. Incident Management prioritizes restoring service functionality, often via a workaround, during a major incident. Subsequently, Problem Management investigates the root cause to prevent recurrence. Finally, if a permanent solution requires a modification to a service or component, Change Enablement ensures that this change is planned, approved, and implemented in a controlled manner.

Why this answer

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

Full explanation →

234

MCQmedium

A release is broken down into small, timeboxed iterations with frequent reviews from stakeholders. Which guiding principle is primarily being applied?

A.Progress iteratively with feedback

B.Collaborate and promote visibility

C.Optimise and automate

D.Focus on value

AnswerA

The question describes a release broken into 'small timeboxed iterations,' which is the essence of iterative progress. This approach inherently requires continuous feedback loops at each stage to review outcomes, learn from experiences, and adapt subsequent iterations. By delivering in increments and gathering feedback, organizations can ensure that services evolve effectively and align with changing requirements, minimizing risk and maximizing responsiveness.

Why this answer

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.

Exam trap

PeopleCert often tests the distinction between 'Progress iteratively with feedback' and 'Collaborate and promote visibility' by presenting scenarios where stakeholder involvement is present but the key differentiator is the iterative, feedback-driven nature of the work, not just the act of collaboration.

How to eliminate wrong answers

Option B is wrong because 'Collaborate and promote visibility' focuses on involving stakeholders and making work transparent, but the question specifically highlights iterative progress and feedback, not just collaboration or visibility. Option C is wrong because 'Optimise and automate' is about improving efficiency and reducing manual effort through automation, which is not the primary focus of timeboxed iterations with reviews. Option D is wrong because 'Focus on value' centers on delivering outcomes that matter to stakeholders, but the question's emphasis on iterative development and feedback loops is a better match for the 'Progress iteratively with feedback' principle.

Full explanation →

235

MCQeasy

Which dimension of ITIL 4 focuses on the culture, roles, and communication within an organisation?

A.Value Streams and Processes

B.Partners and Suppliers

C.Organisations and People

D.Information and Technology

AnswerC

The "Organisations and People" dimension is the correct answer because it explicitly addresses the organizational structure, culture, roles, and responsibilities necessary for effective service management. This dimension ensures that an organization has the appropriate leadership, communication, and human resources with the required competencies to design, deliver, and improve services. It directly encompasses the cultural aspects and the definition of roles that are fundamental to successful service delivery, aligning perfectly with the question's focus.

Why this answer

The 'Organisations and People' dimension of ITIL 4 focuses on the human aspects of service management, including culture, roles, responsibilities, and communication. This dimension ensures that the organizational structure and team competencies align with the service value system, enabling effective collaboration and decision-making.

Exam trap

The trap here is that candidates often confuse 'Organisations and People' with 'Value Streams and Processes' because both involve roles, but the former focuses on culture and communication while the latter focuses on the sequence of activities and workflows.

How to eliminate wrong answers

Option A is wrong because 'Value Streams and Processes' focuses on the workflow, activities, and procedures required to create and deliver value, not on culture or roles. Option B is wrong because 'Partners and Suppliers' addresses external relationships, contracts, and dependencies with third parties, not internal organizational culture or communication. Option D is wrong because 'Information and Technology' covers data, applications, and infrastructure, not the human elements of roles and communication.

Full explanation →

236

MCQmedium

An IT service desk analyst receives a call that users cannot access the CRM system. What should the analyst do FIRST?

A.Search the known error database for a workaround

B.Inform the user that a problem has been raised

C.Escalate the call to Level 2 support

D.Log the incident in the ITSM tool

AnswerD

Logging the incident in the ITSM tool is the foundational first step in the incident management process. This action creates a formal record of the service interruption, enabling tracking, prioritization, and communication throughout its lifecycle until resolution. Proper logging ensures accountability, facilitates adherence to service level agreements, and provides valuable data for future analysis and problem identification.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse the urgency of restoring service with the procedural necessity of logging, leading them to jump to escalation or workaround steps before creating the formal record.

How to eliminate wrong answers

Option A is wrong because searching the known error database for a workaround is a secondary step that occurs after the incident is logged and categorized, not the first action. Option B is wrong because informing the user that a problem has been raised is premature and incorrect; a problem is only raised after multiple related incidents are analyzed, and the analyst should first log the incident and provide initial communication. Option C is wrong because escalating to Level 2 support should only happen after the incident is logged, assessed, and determined to be beyond the analyst's capability to resolve; skipping logging violates the incident management process.

Full explanation →

237

MCQhard

An organisation implements a new human resources (HR) system. The project team delivers the system on time and within budget. However, HR staff find the system difficult to use and employee satisfaction with HR services does not improve. According to ITIL 4, which statement describes this situation?

A.The output and outcome are the same in this context

B.The outcome (employee satisfaction) was achieved, but the output (delivery) failed

C.The output (system delivery) was successful, but the outcome (improved satisfaction) was not achieved

D.The output and outcome were both achieved

AnswerC

This option accurately reflects the scenario by distinguishing between output and outcome, a core ITIL 4 concept. The output, which is the successful delivery and implementation of the new HR system within specified project constraints (on time, on budget), was achieved. However, the desired outcome, specifically the improvement in employee satisfaction that the system was intended to facilitate, was not realized, highlighting a common challenge in value co-creation.

Why this answer

In ITIL 4, an output is a tangible deliverable (e.g., the HR system delivered on time and within budget), while an outcome is the result for stakeholders (e.g., improved employee satisfaction). The scenario shows the output was successful, but the outcome was not achieved because the system was difficult to use and satisfaction did not improve. Option C correctly identifies this mismatch.

Exam trap

The trap here is confusing 'output' (the system delivery) with 'outcome' (the business result), leading candidates to assume that on-time, on-budget delivery automatically means success, when ITIL 4 emphasizes that value is only realized through positive outcomes.

How to eliminate wrong answers

Option A is wrong because output and outcome are distinct concepts in ITIL 4; output is the deliverable (the system), outcome is the business result (satisfaction), and they are not the same here. Option B is wrong because it claims the outcome (employee satisfaction) was achieved, but the scenario explicitly states satisfaction did not improve, and it incorrectly states the output (delivery) failed, when in fact the system was delivered on time and within budget. Option D is wrong because it claims both output and outcome were achieved, but the outcome (improved satisfaction) was not achieved.

Full explanation →

238

MCQeasy

Which ITIL 4 practice has the PRIMARY purpose of restoring normal service operation as quickly as possible and minimizing the adverse impact on business operations?

A.Problem Management

B.Service Request Management

C.Incident Management

D.Change Enablement

AnswerC

Incident Management is the correct practice because its primary purpose is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible. An incident is defined as an unplanned interruption to a service or a reduction in the quality of a service. This practice focuses on rapid diagnosis, workaround implementation, and resolution to ensure business continuity and user productivity are maintained.

Why this answer

Incident Management's primary purpose in ITIL 4 is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations, making it the correct answer. It focuses on the 'here and now' — diagnosing and resolving the immediate disruption rather than investigating underlying causes. This urgency-driven practice is distinct from Problem Management, which seeks root causes.

Exam trap

ITIL4F often tests the boundary between Incident and Problem Management, and candidates frequently select Problem Management because they conflate 'fixing the issue permanently' with 'restoring service quickly.'

How to eliminate wrong answers

Option A is wrong because Problem Management focuses on identifying the root cause of incidents and managing workarounds and known errors, not on rapid restoration of service. Option B is wrong because Service Request Management handles routine user requests (e.g., password resets, software installs) rather than unplanned disruptions. Option D is wrong because Change Enablement authorizes and schedules changes to IT services, ensuring risk is assessed — it does not restore service during an outage.

Full explanation →

239

MCQeasy

Refer to the exhibit. The ITIL Foundation training materials list the seven guiding principles. Which option is NOT among them?

A.Focus on value

B.Keep it simple and practical

C.Optimize and automate

D.Manage risk at all times

AnswerD

"Manage risk at all times" is not explicitly listed as one of the seven ITIL guiding principles. While risk management is an integral and crucial aspect of IT service management, embedded within various ITIL practices and processes, it does not stand alone as a distinct guiding principle in the ITIL 4 framework. Therefore, this option correctly identifies an item that is not an ITIL guiding principle.

Why this answer

'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.

Exam trap

The trap here is that candidates confuse the ITIL 4 guiding principles with the ITIL practices or general management concepts, such as risk management, which is a common practice but not a principle, leading them to incorrectly select 'Manage risk at all times' as a valid principle.

How to eliminate wrong answers

Option A is wrong because 'Focus on value' is explicitly the first guiding principle in ITIL 4, emphasizing that all activities should directly or indirectly contribute to value creation for stakeholders. Option B is wrong because 'Keep it simple and practical' is the sixth guiding principle, advocating for minimizing complexity and ensuring outcomes are achievable without unnecessary overhead. Option C is wrong because 'Optimize and automate' is the seventh guiding principle, focusing on improving processes and leveraging automation to increase efficiency and reduce human error.

Full explanation →

240

Multi-Selectmedium

Which TWO of the following are correctly matched pairs in ITIL 4?

Select 2 answers

A.Change management – record user complaints

B.Service request – unplanned disruption

C.Problem management – find root cause

D.Incident management – restore service

E.Continual improvement – one-time project

AnswersC, D

Problem management is the practice of reducing the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors. A core objective of problem management is indeed to find the root cause of recurring incidents or potential issues, thereby preventing future occurrences and improving service stability. This proactive approach distinguishes it from incident management's reactive focus.

Why this answer

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.

Exam trap

The trap here is confusing the definitions of Incident, Problem, Service request, and Change — candidates often misidentify Service request as an unplanned disruption or mistake Problem management for simple incident logging, when ITIL 4 strictly separates these processes by their purpose and activities.

Full explanation →

241

MCQhard

An IT service provider is implementing a new monitoring tool. According to the ITIL 4 guiding principle 'Focus on value', what should the provider do FIRST?

A.Identify existing monitoring tools and use them if possible

B.Identify the stakeholders and understand what value means to them

C.Define the required metrics and reports from the tool

D.Select the tool with the most features to ensure maximum functionality

AnswerB

This option directly embodies the ITIL 4 guiding principle of 'Focus on value,' which is paramount for any service initiative. Before any technical or functional considerations, it is essential to identify all relevant stakeholders—including users, customers, and service owners—and thoroughly understand their specific needs, desired outcomes, and how they perceive value from the new monitoring tool. This foundational understanding ensures that subsequent design and implementation efforts are aligned with delivering tangible benefits and meeting business objectives.

Why this answer

According to the ITIL 4 guiding principle 'Focus on value', the first step is to identify stakeholders and understand what value means to them. For a monitoring tool, this means engaging with service owners, operations teams, and customers to define what success looks like (e.g., reduced MTTR, improved availability) before selecting or configuring any technology. Without this value definition, the tool risks being implemented with irrelevant metrics or features that do not align with business outcomes.

Exam trap

The trap here is that candidates often jump to technical activities (like defining metrics or selecting tools) because they are familiar with implementation steps, but ITIL 4's 'Focus on value' demands a stakeholder-first approach before any technical decision.

How to eliminate wrong answers

Option A is wrong because identifying existing tools is a 'Start where you are' activity, not the first step under 'Focus on value'; reusing tools without first understanding stakeholder value may perpetuate misaligned monitoring. Option C is wrong because defining metrics and reports presupposes that value has already been defined; doing this first risks creating technical KPIs that do not reflect actual business value. Option D is wrong because selecting the tool with the most features violates 'Focus on value' by prioritizing functionality over stakeholder needs, leading to over-engineering and wasted investment.

Full explanation →

242

MCQhard

A user requests new software that is already pre-approved in the service catalogue. The service desk team handles this request following a defined, automated workflow. According to ITIL 4, what type of record should be created?

A.Problem record

B.Normal change record

C.Service request record

D.Incident record

AnswerC

A service request record is the appropriate choice for a user requesting new software that is already pre-approved, as it represents a formal request for a standard, pre-defined service offering. These requests typically follow established, automated workflows and do not require additional assessment or authorization beyond the initial submission. ITIL 4 emphasizes that service requests are low-risk, frequently occurring events, making this the ideal mechanism for fulfilling such a pre-approved software provision.

Why this answer

A service request record should be created for a user request for pre-approved software that follows a defined workflow. In ITIL 4, service requests are a normal part of service delivery, handled through the service request management practice, and are distinct from incidents and changes. Since the software is pre-approved and the workflow is automated, it qualifies as a service request.

Exam trap

ITIL4F often tests the confusion between service requests and incidents or changes, where candidates may incorrectly choose incident or change record for a routine request, especially when the request is pre-approved.

How to eliminate wrong answers

Option A is wrong because a problem record is created to investigate the root cause of one or more incidents, not for a routine service request. Option B is wrong because a normal change record is required for changes that need assessment and authorization; pre-approved software in the service catalogue does not require a change record. Option D is wrong because an incident record is for unplanned interruptions or degradations of service, not for requesting new software.

Full explanation →

243

MCQmedium

Which of the following describes a key difference between Incident Management and Problem Management in ITIL 4?

A.Incident Management aims to restore normal service as soon as possible; Problem Management aims to prevent incidents from happening or recurring

B.Incident Management is reactive; Problem Management is always proactive

C.Incident Management is only for major incidents; Problem Management is for minor issues

D.Incident Management always resolves the root cause; Problem Management only applies workarounds

AnswerA

Incident Management's primary objective is the swift restoration of normal service operation, minimizing business impact and returning users to productivity as quickly as possible. In contrast, Problem Management focuses on identifying and understanding the underlying causes of incidents, aiming to prevent their recurrence or to mitigate their impact if they cannot be entirely avoided. This clear distinction highlights their different but complementary roles in maintaining service stability and quality.

Why this answer

Incident Management focuses on restoring normal service operation as quickly as possible to minimize business impact, while Problem Management seeks to identify and eliminate the underlying root causes of incidents to prevent recurrence or reduce their impact. This distinction is fundamental in ITIL 4: Incident Management is about speed of recovery, Problem Management about long-term stability.

Exam trap

The trap here is confusing the reactive nature of Incident Management with the misconception that Problem Management is always proactive, when in fact Problem Management includes both reactive and proactive activities.

How to eliminate wrong answers

Option B is wrong because Problem Management can be both proactive (identifying potential causes before incidents occur) and reactive (analyzing incidents that have already happened), so it is not 'always proactive'. Option C is wrong because Incident Management handles all incidents, not just major ones, and Problem Management addresses both major and minor underlying issues. Option D is wrong because Incident Management does not resolve root causes—it restores service via workarounds or fixes—while Problem Management may apply workarounds as a temporary measure while seeking a permanent root cause resolution.

Full explanation →

244

Multi-Selectmedium

Which TWO of the following are examples of applying the 'Progress iteratively with feedback' principle?

Select 2 answers

A.Implementing a change in phases and gathering user feedback after each phase

B.Rolling out a new system to all users at once to avoid confusion

C.Skipping testing to speed up delivery

D.Using two-week sprints with daily stand-ups and sprint reviews

E.Releasing a major update once a year after extensive testing

AnswersA, D

This approach directly exemplifies the 'Progress iteratively with feedback' guiding principle. Implementing a change in smaller, manageable phases allows for focused development and deployment of increments. Crucially, gathering user feedback after each phase provides essential data and insights, enabling the team to learn, adapt, and refine subsequent phases based on real-world usage and stakeholder input, thereby reducing risk and improving value.

Why this answer

Option A is correct because implementing a change in phases and gathering user feedback after each phase embodies the 'Progress iteratively with feedback' principle: work is broken into smaller increments, and feedback from each phase informs the next, reducing risk and enabling course correction. Option D is correct because two-week sprints with daily stand-ups and sprint reviews are a concrete agile implementation of iterative progress with continuous feedback loops, where each sprint delivers a usable increment and reviews capture stakeholder input. Option B is not correct because a big-bang rollout to all users at once is a waterfall-style, non-iterative approach that delays feedback until after full deployment.

Option C is not correct because skipping testing removes the feedback and quality-control mechanisms that iterative delivery depends on. Option E is not correct because a single annual release with extensive testing is a long-cycle, non-iterative approach that provides no incremental feedback during the year.

Exam trap

The trap here is that candidates may confuse 'big bang' deployments (Option B) or annual releases (Option E) with iterative progress, failing to recognize that true iteration requires frequent, small increments with built-in feedback mechanisms.

Full explanation →

245

MCQeasy

What is the primary role of a service desk?

A.To negotiate SLAs with customers

B.To act as a single point of contact (SPOC) for users

C.To manage the lifecycle of all IT assets

D.To perform root cause analysis

AnswerB

The primary role of the Service Desk is to function as the single point of contact (SPOC) between the service provider and its users. This ensures that users have one consistent and recognizable channel for all service-related interactions, including requesting services, reporting incidents, and seeking information. By centralizing communication, the Service Desk streamlines support, improves user experience, and facilitates efficient incident resolution and service request fulfillment.

Why this answer

The primary role of a service desk is to act as a single point of contact (SPOC) for users, ensuring all incidents, service requests, and inquiries are logged, tracked, and resolved or escalated efficiently. This aligns with ITIL 4's guiding principle of 'focus on value' by providing a clear, accessible entry point for users to interact with IT services.

Exam trap

The trap here is that candidates often confuse the service desk's operational SPOC role with other ITIL practices like service level management (SLA negotiation), IT asset management (lifecycle tracking), or problem management (root cause analysis), leading them to select a plausible but incorrect option.

How to eliminate wrong answers

Option A is wrong because negotiating SLAs is a strategic activity performed by service level management, not the service desk, which focuses on operational incident and request handling. Option C is wrong because managing the lifecycle of IT assets is the responsibility of IT asset management (ITAM), which tracks hardware and software from acquisition to disposal, not the service desk's daily support role. Option D is wrong because root cause analysis is a key activity of problem management, which investigates underlying causes of incidents after they occur, whereas the service desk handles initial incident logging and resolution.

Full explanation →

246

Drag & Dropmedium

Drag and drop the steps of the availability management process into the correct order.

Drag or tap steps into the slots.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

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

Full explanation →

247

MCQeasy

According to ITIL 4, which guiding principle advises that ‘if in doubt, leave it out’?

A.Optimise and automate

B.Focus on value

C.Keep it simple and practical

D.Start where you are

AnswerC

This guiding principle directly advocates for identifying and eliminating any steps, processes, services, or metrics that do not produce value or contribute to the desired outcome. It encourages using the minimum number of steps necessary to achieve a result, ensuring that solutions are easy to understand, implement, and maintain. The core message is to prioritize simplicity and practicality, actively advising against unnecessary complexity and the retention of non-essential elements that add no real benefit.

Why this answer

The guiding principle 'Keep it simple and practical' directly advises that if a process, service, or improvement step adds unnecessary complexity without clear value, it should be omitted. The phrase 'if in doubt, leave it out' is a well-known ITIL 4 mantra for this principle, emphasizing that simplicity reduces waste, risk, and overhead in service management.

Exam trap

The ITIL 4 Foundation exam often tests this principle by pairing it with 'Start where you are' or 'Focus on value', leading candidates to confuse the directive to simplify with the idea of reusing existing assets or maximizing stakeholder benefit, but the specific phrase 'if in doubt, leave it out' is unique to 'Keep it simple and practical'.

How to eliminate wrong answers

Option A is wrong because 'Optimise and automate' focuses on improving efficiency through automation and streamlining, not on deciding whether to include or exclude elements based on doubt. Option B is wrong because 'Focus on value' directs attention to delivering outcomes that matter to stakeholders, but it does not specifically address the removal of uncertain or non-essential components. Option D is wrong because 'Start where you are' advises leveraging existing processes and measurements rather than building from scratch, and it does not provide guidance on omitting elements when uncertain.

Full explanation →

248

MCQeasy

A software development team is working on a new feature for an internal application. The team lead insists that the team should not spend time creating detailed plans for the entire project. Instead, the team should deliver the feature in small increments, demonstrate each increment to the product owner, and adjust based on feedback. Which ITIL guiding principle does this approach best illustrate?

A.Keep it simple and practical

B.Progress iteratively with feedback

C.Collaborate and promote visibility

D.Think and work holistically

AnswerB

Progress iteratively with feedback means organizing work into small, manageable iterations and using feedback to improve. The team delivers in increments, demonstrates each to the product owner, and adjusts based on feedback. This directly matches the principle's emphasis on iterative delivery and continuous feedback to ensure the work remains aligned with stakeholder needs.

Why this answer

The team's approach of delivering the feature in small increments, demonstrating each increment, and adjusting based on feedback exemplifies the guiding principle 'Progress iteratively with feedback'. This principle encourages breaking work into smaller iterations and using feedback to ensure the work remains aligned with stakeholder needs. It helps manage complexity and reduces the risk of delivering something that does not meet expectations.

Exam trap

The trap here is confusing iterative delivery with simplicity or collaboration, when the defining characteristic is the use of small increments and feedback loops to guide progress.

Full explanation →

249

MCQmedium

A service desk analyst receives a call from a user requesting a new laptop because their current one is slow. According to ITIL 4, how should this request be classified?

A.Incident, because the user is experiencing a slow laptop

B.Change request, because a new laptop requires changes to the asset register

C.Service request, because the user is asking for a new device, which is a standard request

D.Problem, because the slow performance may be a recurring issue

AnswerC

A service request is a formal request from a user for something standard that is part of normal service delivery, such as a request for information, advice, a standard change, or access to a service. Requesting a new device, especially when it aligns with predefined organizational policies for hardware provision (e.g., for new hires or scheduled refreshes), perfectly fits this definition. These requests are typically low-risk, frequently occurring, and often have established, sometimes automated, fulfillment procedures.

Why this answer

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.

Exam trap

The trap here is that candidates confuse a user's request for a new device with an incident or problem because the current device is slow, but ITIL 4 clearly separates service requests (standard, pre-approved asks) from incidents (service interruptions) and problems (root cause analysis).

How to eliminate wrong answers

Option A is wrong because an incident is an unplanned interruption or reduction in quality of an IT service; a slow laptop that is still usable is not necessarily a service interruption, and the user is explicitly requesting a new device, not reporting a failure. Option B is wrong because a change request is for a modification to a service or configuration item that is not pre-approved; a new laptop from a standard catalog is a pre-approved service request, not a change requiring formal change management. Option D is wrong because a problem is the root cause of one or more incidents; the user's request is for a new device, not an investigation into why the laptop is slow, and there is no evidence of a recurring underlying cause.

Full explanation →

250

MCQhard

A company is implementing a major change to its IT infrastructure. The change manager insists on reviewing the entire service value system to understand how the change will affect all components. Which guiding principle is being applied?

A.Collaborate and promote visibility

B.Think and work holistically

C.Optimise and automate

D.Focus on value

AnswerB

This guiding principle is directly applicable to a major infrastructure change because it mandates considering all components of a service or system, including its people, processes, partners, and information and technology. It ensures that the organization understands how the change will impact the entire value system, identifying interdependencies and potential risks across the full service value chain before implementation, thereby preventing unforeseen issues.

Why this answer

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.

Exam trap

The trap here is that candidates confuse 'Think and work holistically' with 'Collaborate and promote visibility' because both involve broad engagement, but the holistic principle specifically requires analyzing the entire system's structure and interdependencies, not just improving communication.

How to eliminate wrong answers

Option A is wrong because 'Collaborate and promote visibility' focuses on stakeholder communication and transparency, not on analyzing the entire system's structure and interdependencies. Option C is wrong because 'Optimise and automate' is about improving efficiency through automation and resource optimization, not about understanding how a change affects all SVS components. Option D is wrong because 'Focus on value' prioritizes delivering outcomes that matter to stakeholders, but it does not require a comprehensive review of the entire service value system to assess cross-component impacts.

Full explanation →

251

MCQmedium

An IT service desk analyst receives a call that users cannot access the CRM system. According to ITIL 4, what should the analyst do FIRST?

A.Log the incident and categorize it

B.Reboot the server immediately

C.Inform the change manager about a potential emergency change

D.Start a problem investigation to find the root cause

AnswerA

Logging the incident is the foundational first step in the Incident Management practice, ensuring that all service disruptions are formally recorded and tracked. Categorization, which includes assigning impact and urgency, allows for proper prioritization and routing to the appropriate support teams. This systematic approach is crucial for effective incident resolution, service restoration, and subsequent analysis of service performance.

Why this answer

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.

Exam trap

The trap here is that candidates may confuse incident management with problem management or change management, and incorrectly assume that immediate technical action (like rebooting) or root cause analysis is the first priority, rather than following the prescribed process of logging and categorization.

How to eliminate wrong answers

Option B is wrong because rebooting the server immediately bypasses the required logging and categorization step, and could disrupt other services or mask the root cause without proper authorization. Option C is wrong because informing the change manager about a potential emergency change is premature; the incident must first be logged and assessed to determine if a change is actually needed. Option D is wrong because starting a problem investigation to find the root cause is a problem management activity that occurs after the incident is resolved, not the first step in incident management.

Full explanation →

252

MCQhard

During a major incident, the IT team implements a workaround to restore service. Later, they discover the root cause and submit a permanent fix as an emergency change. Which ITIL 4 practices are primarily involved in this sequence?

A.Incident Management, Problem Management, and Change Enablement

B.Incident Management and Problem Management only

C.Problem Management and Change Enablement only

D.Incident Management and Change Enablement only

AnswerA

Incident Management is crucial for detecting and managing the major incident, focusing on restoring service as quickly as possible. Problem Management then identifies the underlying cause and develops a workaround to mitigate the incident's impact. Finally, if implementing this workaround requires any modification to the live environment, even temporarily, Change Enablement ensures the change is properly assessed, authorized, and managed to minimize risk and prevent further disruption.

Why this answer

The sequence involves Incident Management (restoring service via workaround), Problem Management (finding root cause and submitting permanent fix), and Change Enablement (emergency change to implement the fix). All three practices are involved.

Exam trap

The trap is forgetting that Change Enablement is involved even for emergency changes, or assuming that Problem Management alone handles the fix without formal change control.

How to eliminate wrong answers

Option B is wrong because it omits Change Enablement, which is necessary for the emergency change. Option C is wrong because it omits Incident Management, which handled the initial workaround. Option D is wrong because it omits Problem Management, which identified the root cause and proposed the fix.

Full explanation →

253

MCQeasy

Which of the following is an example of an output?

A.Increased customer satisfaction

B.Improved employee morale

C.A monthly financial report

D.Reduced time to market

AnswerC

A monthly financial report is a clear example of an output because it is a tangible, discrete deliverable produced by a specific activity or process. This report is a direct product of work, such as data collection and analysis, and can be physically or digitally handed over to a stakeholder. Outputs are the visible, measurable results of performing tasks, representing the 'what' that is produced, making this a quintessential output.

Why this answer

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.

Exam trap

The trap here is that candidates confuse outcomes (like satisfaction or time savings) with outputs, because ITIL 4 emphasizes value and outcomes, but the question specifically asks for a tangible deliverable, not a result or benefit.

How to eliminate wrong answers

Option A is wrong because increased customer satisfaction is an outcome—a perceived benefit or value realization from the service, not a tangible deliverable. Option B is wrong because improved employee morale is also an outcome, reflecting a change in state or feeling, not a direct product of a process. Option D is wrong because reduced time to market is a performance metric or outcome that measures efficiency gains, not a specific, countable output from an activity.

Full explanation →

254

MCQmedium

Which of the following BEST describes value co-creation in ITIL 4?

A.Value is created through the active participation of both the provider and the consumer

B.The provider creates value independently and delivers it to the consumer

C.Value is solely defined by the provider based on service features

D.Value is determined by the cost savings achieved by the consumer

AnswerA

In ITIL 4, value co-creation is a fundamental principle emphasizing that value is not delivered by the provider in isolation but is actively shaped through collaborative interactions. Both the service provider and the consumer contribute resources, capabilities, and context throughout the service relationship. This mutual participation ensures that the service truly enables the consumer's desired outcomes, making value a shared achievement.

Why this answer

ITIL 4 defines value co-creation as a collaborative process where both the service provider and the consumer actively contribute resources and activities to achieve desired outcomes. This is a foundational shift from traditional delivery models, emphasizing that value is not simply handed over but emerges from the interaction and joint effort of both parties.

Exam trap

The trap here is that candidates often default to a traditional 'provider delivers value' mindset (Option B) because it mirrors older service management models, but ITIL 4 explicitly requires recognizing the consumer's active role in value creation.

How to eliminate wrong answers

Option B is wrong because it describes a one-way, product-centric view where the provider creates value in isolation and then delivers it to the consumer, which contradicts the ITIL 4 principle of value co-creation that requires active consumer participation. Option C is wrong because it incorrectly asserts that value is solely defined by the provider based on service features, whereas ITIL 4 states that value is perceived by the consumer and co-created through their needs, constraints, and involvement. Option D is wrong because it reduces value to a narrow financial metric (cost savings), ignoring the broader outcomes, experiences, and utility/warranty considerations that define value in ITIL 4's service value system.

Full explanation →

255

MCQmedium

An organization is considering outsourcing its IT support. Which dimension is primarily concerned with managing this relationship?

A.Partners and Suppliers

B.Organizations and People

C.Information and Technology

D.Value Streams and Processes

AnswerA

When an organization considers outsourcing its IT support, it is engaging with external entities that will provide services. This directly falls under the "Partners and Suppliers" dimension, which describes the relationships an organization has with other organizations that are involved in the design, development, delivery, support, and continual improvement of services. This dimension ensures effective collaboration and management of third-party contributions to value creation.

Why this answer

The Partners and Suppliers dimension focuses on the relationships an organization has with external entities that provide services or support. When outsourcing IT support, the primary concern is managing the contract, performance, and collaboration with the external service provider, which falls directly under this dimension.

Exam trap

The trap here is that candidates may confuse the 'Organizations and People' dimension with managing external staff, but ITIL 4 explicitly separates internal people management from external partner and supplier relationships.

How to eliminate wrong answers

Option B (Organizations and People) is wrong because it deals with internal roles, culture, and competencies, not the management of external outsourcing relationships. Option C (Information and Technology) is wrong because it covers the data, applications, and infrastructure used to deliver services, not the governance of third-party providers. Option D (Value Streams and Processes) is wrong because it focuses on the workflows and activities that create value, not the contractual and relational management of external partners.

Full explanation →

256

MCQmedium

During a major incident review, the team identifies that communication between the network and application teams was poor. Which guiding principle would most directly address this issue?

A.Collaborate and promote visibility

B.Focus on value

C.Think and work holistically

D.Progress iteratively with feedback

AnswerA

This ITIL guiding principle directly addresses the challenge of organizational silos and poor communication by advocating for cross-functional teamwork and transparent information sharing. It emphasizes the importance of working together across boundaries, fostering a shared understanding of goals, and making work progress visible to all relevant stakeholders. By breaking down barriers and improving communication channels, teams can resolve major incidents more efficiently and effectively.

Why this answer

The guiding principle 'Collaborate and promote visibility' directly addresses the communication breakdown between the network and application teams during a major incident. By fostering cross-team collaboration and making incident data (e.g., network latency metrics, application error logs) visible to all stakeholders, this principle ensures that silos are broken down and root cause analysis is more effective. In contrast, other principles like 'Focus on value' or 'Think and work holistically' are too broad or do not specifically target the interpersonal and information-sharing gap identified in the review.

Exam trap

The trap here is that candidates often choose 'Think and work holistically' because it sounds like it covers system-wide coordination, but they miss that 'Collaborate and promote visibility' is the specific principle designed to address communication and information-sharing failures between teams.

How to eliminate wrong answers

Option B (Focus on value) is wrong because it emphasizes delivering outcomes that matter to customers, not the internal communication failure between teams; it does not address the root cause of poor coordination. Option C (Think and work holistically) is wrong because while it encourages considering the entire system, it does not prescribe the specific action of improving cross-team communication and visibility; it is a mindset, not a direct remedy for siloed behavior. Option D (Progress iteratively with feedback) is wrong because it focuses on incremental improvements and feedback loops over time, which is not the immediate fix for a communication breakdown during a major incident review; it addresses process evolution rather than the current lack of collaboration.

Full explanation →

257

MCQmedium

An organization wants to improve its first call resolution rate. Which practice is most directly responsible for this metric?

A.Incident Management

B.Problem Management

C.Change Enablement

D.Service Desk

AnswerD

The Service Desk serves as the single point of contact between the service provider and its users, handling incidents, service requests, and providing information. A primary objective of the Service Desk is to resolve as many incidents and service requests as possible during the user's initial contact, directly contributing to enhanced user satisfaction and operational efficiency. First Call Resolution (FCR) is a critical and fundamental metric for evaluating the effectiveness and efficiency of Service Desk operations, as it directly quantifies their ability to resolve issues without escalation.

Why this answer

The Service Desk is the single point of contact between the service provider and users, and it is directly responsible for handling user incidents and service requests on first contact. First call resolution (FCR) measures the percentage of incidents resolved during the initial interaction without escalation or callback, which is a core Service Desk responsibility. While Incident Management oversees the overall incident lifecycle, the Service Desk practice is the one that actually resolves incidents at the first point of contact, making it the most directly accountable for FCR.

Exam trap

ITIL4F often tests the distinction between the Service Desk practice and Incident Management, as candidates may confuse the broader incident lifecycle with the specific first-contact resolution responsibility.

How to eliminate wrong answers

Option A is wrong because Incident Management is a broader practice that focuses on managing the lifecycle of all incidents to restore normal service operation, but it does not directly own the first-contact resolution metric—that is delegated to the Service Desk. Option B is wrong because Problem Management aims to identify root causes of recurring incidents and prevent future occurrences, which affects resolution times and volume but not the immediate first-call resolution rate. Option C is wrong because Change Enablement governs changes to services, ensuring risks are assessed and authorized; it has no direct role in resolving user incidents on first contact.

Full explanation →

258

MCQhard

A multinational corporation uses a SaaS-based project management tool. The tool's provider offers a standard set of features, but the corporation's project managers frequently request custom workflows and reports. The provider has a published product roadmap and does not customize the tool for individual customers. According to ITIL 4, which statement best describes the nature of the value proposition in this service relationship?

A.The provider should customize the tool for each customer to ensure value co-creation.

B.The value proposition is based on the provider's ability to facilitate the consumer's desired outcomes while the consumer integrates the service into its own workflows.

C.The provider must change its roadmap to include all requested custom features to fulfill the value proposition.

D.The value proposition is defined solely by the provider's features, and the consumer has no role in value creation.

AnswerB

In ITIL 4, a service's value proposition is about enabling outcomes the consumer wants to achieve. The provider offers a standardized tool that can facilitate project management outcomes, but the consumer must integrate it into its own workflows and processes. Value is co-created through this integration, even without customization. The provider's roadmap and standard features form the basis, and the consumer realizes value by using the service effectively.

Why this answer

The provider offers a standardized SaaS tool, but value is co-created when the consumer integrates it into its workflows to achieve project management outcomes. The provider facilitates outcomes, but the consumer must use the service effectively. Customization is not required for value co-creation; the focus is on enabling outcomes through the service relationship.

Exam trap

The trap here is assuming that value co-creation requires the provider to customize the service for each consumer, when in fact co-creation happens through the consumer's use and integration of the service.

Full explanation →

259

MCQmedium

A company is implementing a new CRM system. The project team has defined the workflows and activities but has not considered the skills required for staff to use the system. Which dimension of ITIL 4 is being neglected?

A.Organizations and People

B.Partners and Suppliers

C.Information and Technology

D.Value Streams and Processes

AnswerA

This dimension specifically addresses the organizational structure, culture, required skills, competencies, and roles necessary for effective service management. Implementing a new CRM system fundamentally changes how people work, necessitating adequate user training and skill development to operate it efficiently and realize its intended benefits. Neglecting to plan for user training and skill development directly indicates a critical gap in addressing the "Organizations and People" dimension, which is paramount for successful adoption and value co-creation from the new system.

Why this answer

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.

Exam trap

PeopleCert often tests the Four Dimensions by presenting a scenario where processes are defined but people are overlooked, tempting candidates to choose 'Value Streams and Processes' because they see 'workflows and activities' mentioned, missing that the dimension of people is the neglected one.

How to eliminate wrong answers

Option B (Partners and Suppliers) is wrong because the question does not mention external vendors, contracts, or third-party dependencies; the oversight is internal staff skills. Option C (Information and Technology) is wrong because the team has defined workflows and activities, which involve technology and information flows, but the missing element is the human capability to use that technology. Option D (Value Streams and Processes) is wrong because the team has already defined the workflows and activities (processes); the gap is in the organizational readiness, not the process design itself.

Full explanation →

260

Multi-Selecthard

Which THREE of the following are ITIL 4 guiding principles?

Select 3 answers

A.Collaborate and promote visibility

B.Process orientation

C.Customer satisfaction

D.Focus on value

E.Optimize and automate

AnswersA, D, E

The "Collaborate and promote visibility" guiding principle emphasizes working across organizational boundaries and with all relevant stakeholders to achieve shared objectives. It advocates for transparent communication and information sharing, ensuring that work, progress, and potential issues are visible to everyone involved. This approach fosters better decision-making, reduces silos, and improves overall service delivery effectiveness by leveraging collective knowledge and effort.

Why this answer

The ITIL 4 guiding principles are universal, enduring recommendations that guide an organization in all circumstances, and three of them appear here. Option A, 'Collaborate and promote visibility,' is correct because working across silos and making work and information transparent is one of the seven ITIL 4 guiding principles. Option D, 'Focus on value,' is correct because everything the organization does must map directly to value for the customer and other stakeholders, making it a core guiding principle.

Option E, 'Optimize and automate,' is correct because ITIL 4 explicitly recommends optimizing human effort and technology before automating, and this is one of the seven principles. Option B, 'Process orientation,' is not a guiding principle; it reflects earlier ITIL v3 thinking about managing by processes rather than a principle in ITIL 4. Option C, 'Customer satisfaction,' is a desirable outcome and a key concept, but it is not one of the seven ITIL 4 guiding principles (the closest principle is 'Focus on value').

Exam trap

The trap here is that candidates often confuse ITIL 4 guiding principles with older ITIL v3 concepts like 'Process orientation' or generic business terms like 'Customer satisfaction', but the exam expects precise recall of the seven specific principles listed in the ITIL 4 Foundation syllabus.

Full explanation →

261

MCQmedium

Which of the following is a key consideration in the Information and Technology dimension?

A.Information security

B.Organizational culture

C.Supplier contracts

D.Process workflows

AnswerA

Information security is a paramount consideration within the 'Information and Technology' dimension, which specifically addresses the information and knowledge required to manage services, as well as the technologies supporting them. It encompasses the practices, policies, and controls necessary to protect the confidentiality, integrity, and availability of data and digital assets throughout their lifecycle. Ensuring robust information security is fundamental for maintaining the reliability, trustworthiness, and compliance of services and the underlying technological infrastructure, directly impacting an organization's ability to deliver value securely.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse the Information and Technology dimension with the Value Streams and Processes dimension, mistakenly selecting process workflows because they think 'technology' includes all operational activities, but ITIL 4 explicitly separates process design from technology management.

How to eliminate wrong answers

Option B is wrong because organizational culture is a key consideration of the Partners and Suppliers dimension, not the Information and Technology dimension. Option C is wrong because supplier contracts are a key consideration of the Partners and Suppliers dimension, focusing on external relationships and agreements. Option D is wrong because process workflows are a key consideration of the Value Streams and Processes dimension, which deals with how activities are coordinated and executed.

Full explanation →

262

MCQmedium

An organization's IT service desk is receiving a high volume of calls about users being unable to log in to the payroll system following a scheduled maintenance window. According to ITIL 4, what type of record should be raised?

A.A change request, to reverse the changes made during the maintenance window

B.A problem record, to investigate the root cause of the login failure

C.A service request, to fulfil the users' need to access the payroll system

D.An incident record, as users are experiencing an unplanned service interruption

AnswerD

An incident is defined as an unplanned interruption to a service or a reduction in the quality of a service. The scenario explicitly describes users experiencing an unplanned inability to access the payroll system, which constitutes a clear service interruption. The primary objective of incident management is to restore normal service operation as quickly as possible, minimizing the negative business impact, making an incident record the appropriate initial response.

Why this answer

An unplanned interruption to a service is classified as an incident. The users' inability to log in to the payroll system after maintenance constitutes a service disruption, so an incident record should be raised to manage the restoration of normal service. Option A is incorrect because a change request is used to plan and control changes, not to record service failures.

Option B is incorrect because a problem record seeks to identify the root cause of incidents, but the immediate need is to log the disruption as an incident first. Option C is incorrect because a service request is for pre-approved, routine requests (e.g., password resets), not for reporting unexpected service outages.

Full explanation →

263

MCQhard

A service provider is designing a new cloud storage service. The service is fast and secure, but it does not have a backup system. Which aspect of service is missing?

A.Output

B.Outcome

C.Utility

D.Warranty

AnswerD

Warranty provides assurance that a service will meet agreed requirements, addressing 'how the service performs' or its fitness for use. This includes non-functional requirements such as availability, capacity, security, and continuity for the cloud storage service. Designing a robust warranty ensures the service is reliable, secure, and performs consistently, directly contributing to stakeholder confidence and overall service value.

Why this answer

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

Full explanation →

264

MCQhard

Which of the following BEST distinguishes an incident from a problem in ITIL 4?

A.Incidents are unplanned service disruptions, while problems are the root causes of incidents

B.Incidents are always reported by users, while problems are identified by technical staff

C.Incidents have a defined resolution time in the SLA, while problems do not

D.Incidents are managed by the service desk, while problems are managed by problem management

AnswerA

This option correctly distinguishes incidents from problems based on their fundamental nature. An incident represents an unplanned interruption to a service or a reduction in its quality, directly impacting users. Conversely, a problem is defined as the cause, or potential cause, of one or more incidents, focusing on the underlying issue rather than the immediate disruption.

Why this answer

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.

Exam trap

The trap here is that candidates confuse the roles or reporting sources (options B and D) or SLA applicability (option C) with the fundamental definitional difference, which is that an incident is the symptom and a problem is the cause.

How to eliminate wrong answers

Option B is wrong because incidents can be identified by technical staff through monitoring tools (e.g., SNMP traps, synthetic transactions) and are not exclusively reported by users; problems can also be reported by users or identified proactively. Option C is wrong because both incidents and problems can have defined resolution times in SLAs (e.g., a problem may have a target for root cause analysis completion), and the presence or absence of an SLA target does not distinguish the two concepts. Option D is wrong because while the service desk typically handles incident logging and initial support, problem management is a separate process that may involve the service desk in coordination, but the distinction is not about who manages them—it is about the nature of the work (restoring service vs. finding root cause).

Full explanation →

265

MCQhard

Which of the following is an example of a PESTLE factor that could affect the Four Dimensions of IT Service Management?

A.A change in organisational culture

B.A new version of the IT service management tool

C.An internal process improvement initiative

D.A new data protection regulation

AnswerD

A new data protection regulation is a quintessential example of a "Legal" factor within the PESTLE framework. Such regulations are external, government-mandated requirements that organizations must comply with, directly impacting their data handling practices, compliance costs, and risk management strategies. This external legal development significantly influences how an organization operates and delivers services, making it a critical PESTLE consideration.

Why this answer

A new data protection regulation (e.g., GDPR) is a classic PESTLE factor under the 'Legal' category. PESTLE factors are external influences (Political, Economic, Social, Technological, Legal, Environmental) that can impact all Four Dimensions of IT Service Management (Organizations & People, Information & Technology, Partners & Suppliers, Value Streams & Processes). A regulation like GDPR forces changes in how data is stored, processed, and protected, affecting technology choices, supplier contracts, and process design across the service value system.

Exam trap

The trap here is confusing internal operational changes (like culture, tools, or process improvements) with external PESTLE factors, leading candidates to select an option that is actually a component of one of the Four Dimensions rather than an external influence that affects them.

How to eliminate wrong answers

Option A is wrong because a change in organisational culture is an internal factor, not an external PESTLE factor; it falls under the 'Organizations & People' dimension. Option B is wrong because a new version of the IT service management tool is a technological change internal to the organization, not an external PESTLE factor; it is part of the 'Information & Technology' dimension. Option C is wrong because an internal process improvement initiative is an internal operational change, not an external PESTLE factor; it belongs to the 'Value Streams & Processes' dimension.

Full explanation →

266

MCQeasy

Which practice involves the use of a service catalogue for predefined offerings?

A.Service Request Management

B.Change Enablement

C.Problem Management

D.Incident Management

AnswerA

Service Request Management is the practice of supporting the agreed quality of a service by handling all pre-defined, user-initiated requests. These requests are typically standardized, often automated, and are prominently featured in a service catalogue, which acts as the primary interface for users to browse and order available services and their associated requests. The catalogue provides clear descriptions, fulfillment times, and costs, making it integral to the efficient processing of service requests.

Why this answer

Service Request Management is the practice that involves the use of a service catalogue for predefined offerings. The service catalogue lists available services and service requests, enabling users to request standard services efficiently. This practice ensures that requests are handled consistently and in a user-friendly manner.

Exam trap

The trap is confusing Service Request Management with Incident Management or Change Enablement, as all involve handling user interactions but serve different purposes.

How to eliminate wrong answers

Option B is wrong because Change Enablement focuses on managing changes to IT services, not on service requests. Option C is wrong because Problem Management aims to identify and manage the root causes of incidents, not to fulfill service requests. Option D is wrong because Incident Management focuses on restoring normal service operation as quickly as possible, not on predefined service offerings.

Full explanation →

267

MCQhard

A software development team frequently deploys minor bug fixes that have been pre-authorized. According to ITIL 4, what type of change is this?

A.Normal change

B.Service request

C.Standard change

D.Emergency change

AnswerC

Standard changes are low-risk, pre-authorized changes that are well-understood, fully documented, and can be implemented without additional authorization. They follow a defined procedure, are often automated, and have a known, predictable outcome. "Frequently deploys minor bug fix" perfectly aligns with the characteristics of a standard change, enabling efficient and rapid deployment of routine, low-impact updates.

Why this answer

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.

Exam trap

The trap here is confusing a pre-authorized standard change with a normal change, as candidates may think any code deployment requires formal approval, missing the key distinction that standard changes are pre-approved based on low risk and repeatability.

How to eliminate wrong answers

Option A is wrong because a normal change requires formal assessment and authorization through the change authority, which is not the case for pre-authorized minor bug fixes. Option B is wrong because a service request is a formal request from a user for something to be provided (e.g., information, access), not a change to an existing service or software. Option D is wrong because an emergency change is applied to resolve an incident or problem urgently, often bypassing normal procedures, whereas these bug fixes are pre-authorized and not urgent.

Full explanation →

268

Drag & Dropmedium

Drag and drop the steps of the service request management process into the correct order.

Drag or tap steps into the slots.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

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

Full explanation →

269

MCQeasy

Which dimension of ITIL 4 focuses on culture, roles, and communication?

A.Organisations and People

B.Information and Technology

C.Partners and Suppliers

D.Value Streams and Processes

AnswerA

Organisations and People covers culture, roles, responsibilities, communication and staffing structures. It directly matches the stem's focus, unlike the Value Streams and Processes, Information and Technology, or Partners and Suppliers dimensions, which address workflow, tooling and external relationships.

Why this answer

The Organisations and People dimension of ITIL 4 focuses on the human aspects of service management, including culture, roles, responsibilities, and communication. This dimension ensures that the organizational structure and team dynamics support the delivery and improvement of IT services, aligning with the ITIL guiding principle of 'Collaborate and Promote Visibility'.

Exam trap

The trap here is that candidates often confuse the Organisations and People dimension with Value Streams and Processes, mistakenly thinking that process documentation alone addresses roles and communication, but ITIL 4 explicitly separates human factors from procedural workflows.

How to eliminate wrong answers

Option B is wrong because Information and Technology focuses on the data, applications, and infrastructure required to deliver services, not on human factors like culture or communication. Option C is wrong because Partners and Suppliers deals with external relationships, contracts, and third-party dependencies, not internal organizational culture or roles. Option D is wrong because Value Streams and Processes concentrates on the workflows, activities, and procedures that create value, not on the people and communication aspects.

Full explanation →

270

MCQeasy

Which of the following is a key metric for measuring the performance of the Service Desk?

A.Number of changes implemented

B.First Call Resolution (FCR)

C.Mean Time to Restore Service (MTTR)

D.Percentage of projects on time

AnswerB

First Call Resolution (FCR) is a critical Service Desk metric that quantifies the percentage of incidents or service requests resolved completely during the initial contact with the user, without requiring further escalation or follow-up. A high FCR rate directly indicates the Service Desk's efficiency and the competence of its agents, significantly enhancing customer satisfaction by minimizing disruption and reducing the need for multiple interactions. It is a primary indicator of the Service Desk's ability to provide immediate value and effective front-line support.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse FCR with MTTR, assuming both measure speed of resolution, but MTTR applies to the entire incident lifecycle and technical restoration, while FCR specifically measures the Service Desk's ability to resolve at first touch without escalation.

How to eliminate wrong answers

Option A is wrong because the number of changes implemented is a metric for Change Enablement, not the Service Desk, which focuses on incident and request management. Option C is wrong because Mean Time to Restore Service (MTTR) is a metric for Incident Management and technical resolution teams, measuring the time to fix a service after a failure, not the Service Desk's first-contact performance. Option D is wrong because the percentage of projects on time is a metric for Project Management or Portfolio Management, not the operational, reactive nature of the Service Desk.

Full explanation →

271

MCQmedium

A user requests a new laptop as part of their onboarding. According to ITIL 4, what type of request is this?

A.Problem

B.Incident

C.Service Request

D.Change Request

AnswerC

A Service Request, according to ITIL 4, is a formal request from a user for information, advice, a standard change, or access to a service. These requests are typically pre-defined, low-risk, and frequently occurring, often fulfilled through automated processes or with minimal approval. Providing a new laptop as part of an employee's onboarding process is a classic example of a standard, pre-approved service offering, making it the correct classification for a service request.

Why this answer

A request for a new laptop during onboarding is a pre-defined, standardized request for a new service or service action, which ITIL 4 defines as a Service Request. This is not an unplanned interruption (Incident), a root cause analysis (Problem), or a modification to an existing service (Change Request). The user is requesting a standard asset as part of a normal business process.

Exam trap

The trap here is that candidates confuse a Service Request with a Change Request, but ITIL 4 explicitly distinguishes them: a Service Request is for a standard, pre-approved service action (like a new laptop), while a Change Request is for altering a service or CI, which requires formal evaluation and authorization.

How to eliminate wrong answers

Option A is wrong because a Problem is the root cause of one or more Incidents, not a request for a new asset. Option B is wrong because an Incident is an unplanned interruption or reduction in quality of an IT service, whereas a new laptop request is a planned, standard action. Option D is wrong because a Change Request is for altering a service or configuration item, not for fulfilling a standard pre-approved request like a new laptop.

Full explanation →

272

MCQeasy

What is the PRIMARY purpose of the Service Desk practice?

A.To manage the lifecycle of all incidents

B.To monitor and manage IT services proactively

C.To analyze root causes of incidents

D.To provide a single point of contact for users

AnswerD

The primary purpose of the Service Desk practice is to establish and maintain a single point of contact (SPOC) between the service provider and its users. This ensures that users have one consistent, identifiable channel for all service-related interactions, including logging incidents, requesting services, making inquiries, and receiving communication. This centralized approach streamlines user experience and facilitates efficient communication flow within the service organization.

Why this answer

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

Full explanation →

273

MCQmedium

An IT team is designing a new service. They decide to reuse an existing process rather than creating a new one. Which ITIL guiding principle is being applied?

A.Focus on value

B.Start where you are

C.Collaborate and promote visibility

D.Progress iteratively with feedback

AnswerB

'Start where you are' means reusing what already exists rather than building anew, so adopting an existing process instead of creating one applies this principle directly. It satisfies the stem's constraint of designing a service through reuse.

Why this answer

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.

Exam trap

The trap here is that candidates confuse 'Start where you are' with 'Focus on value' because both involve efficiency, but the former specifically targets leveraging existing assets rather than creating new value propositions.

How to eliminate wrong answers

Option A is wrong because 'Focus on value' prioritizes delivering outcomes that matter to stakeholders, not the reuse of existing components. Option C is wrong because 'Collaborate and promote visibility' emphasizes teamwork and transparency, not the reuse of processes. Option D is wrong because 'Progress iteratively with feedback' advocates for incremental improvements and continuous feedback loops, not the direct reuse of existing processes.

Full explanation →

274

MCQhard

A cloud service provider uses third-party data centers and network providers. Recently, a network outage at one data center caused a major service disruption. Which dimension should the provider focus on to prevent recurrence?

A.Information and technology

B.Organizations and people

C.Partners and suppliers

D.Value streams and processes

AnswerC

The Partners and Suppliers dimension is explicitly concerned with the relationships an organization has with other entities involved in the design, development, delivery, support, and continual improvement of services. When a cloud service provider relies on third-party data centers, managing the performance, reliability, and contractual obligations, such as Service Level Agreements, of these external partners is paramount. A disruption originating from a third-party data center's network directly falls under the scope of managing these critical external dependencies.

Why this answer

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.

Exam trap

The trap here is that candidates confuse an external network outage with an internal technology failure, leading them to choose Information and technology instead of recognizing the dependency on third-party suppliers.

How to eliminate wrong answers

Option A is wrong because the Information and technology dimension covers the technical infrastructure (e.g., servers, storage, network devices) and data management, but the root cause here is an external network provider's outage, not an internal technology failure. Option B is wrong because the Organizations and people dimension deals with roles, skills, and culture within the provider's own organization, not the management of third-party vendors. Option D is wrong because the Value streams and processes dimension focuses on workflows and procedures for delivering services, but the recurrence prevention requires supplier governance rather than process redesign.

Full explanation →

275

MCQmedium

A software development team delivers a new feature to the marketing department. The feature is working but the marketing team reports no increase in campaign effectiveness. Which ITIL 4 distinction does this illustrate?

A.Output vs Outcome

B.Incident vs Problem

C.Service Request vs Change

D.Utility vs Warranty

AnswerA

An output is a tangible deliverable produced by an activity, such as the new software feature itself. An outcome, conversely, is the result or effect achieved for a stakeholder, often enabled by the output, representing the actual value realized. The question describes the delivery of a feature and implies its subsequent impact, directly aligning with this distinction, making it the correct choice for differentiating the deliverable from its benefit.

Why this answer

ITIL 4 distinguishes between 'output' (a tangible deliverable, such as a working software feature) and 'outcome' (the actual business result, such as increased campaign effectiveness). In this scenario, the team delivered the output (the feature works), but the desired outcome (improved marketing performance) was not achieved, illustrating the critical gap between delivering a product and realizing business value.

Exam trap

The trap here is that candidates confuse 'output vs outcome' with 'utility vs warranty' because both involve service value, but utility focuses on functionality fit for purpose, not the business result gap illustrated in this scenario.

How to eliminate wrong answers

Option B is wrong because Incident vs Problem deals with unplanned interruptions (incidents) versus their root causes (problems), not with the difference between delivering a feature and achieving business value. Option C is wrong because Service Request vs Change focuses on pre-defined, low-risk requests (service requests) versus controlled modifications (changes), which does not apply to a delivered feature failing to produce a business result. Option D is wrong because Utility vs Warranty describes functionality (utility) and assurance/availability (warranty) of a service, not the distinction between a deliverable and its business impact.

Full explanation →

276

MCQhard

A large e-commerce company is experiencing slow response times on its website during peak shopping hours. The IT team has identified that the database server is under high CPU load. They have tried scaling up the server resources, but the issue persists. The team suspects that inefficient database queries are the cause. The service owner wants to implement a solution that aligns with the ITIL guiding principles. The company has a limited budget for this initiative. Which course of action should the team take to address the problem most effectively?

A.Upgrade to a more powerful database server with more CPUs.

B.Analyze and optimize the slow database queries identified by the database administrator.

C.Implement a caching layer to reduce database load.

D.Hire a database consultant to review the entire database architecture.

AnswerB

This option directly targets the identified root cause: inefficient database queries. By analyzing query execution plans, creating appropriate indexes, or rewriting suboptimal SQL statements, performance improvements are achieved at the source. This aligns perfectly with ITIL's 'Focus on value' by delivering tangible performance gains and 'Optimize and automate' by improving the efficiency of existing resources, offering a sustainable and cost-effective solution without unnecessary expenditure.

Why this answer

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.

Exam trap

The trap here is that candidates assume scaling up hardware (Option A) is always the answer to performance issues, but ITIL emphasizes solving the root cause first, and the question explicitly states that scaling up has already failed.

How to eliminate wrong answers

Option A is wrong because scaling up the server has already been tried and failed, indicating that the bottleneck is not CPU capacity but rather how queries are executed; adding more CPUs would only mask the symptom without fixing the inefficient queries. Option C is wrong because implementing a caching layer would reduce read load but does not address the CPU-intensive queries themselves, which may still cause high load on cache misses or for write operations; it also introduces additional complexity and cost. Option D is wrong because hiring a consultant is an expensive, open-ended engagement that may not yield a timely fix, and the problem has already been localized to specific slow queries, making a full architectural review excessive and misaligned with the limited budget.

Full explanation →

277

Multi-Selectmedium

Which TWO of the following are examples of 'warranty' aspects of a service?

Select 2 answers

A.The service includes a user-friendly interface

B.The service can handle 10,000 concurrent users

C.The service provides a search function

D.The service is available 99.9% of the time

E.The service returns search results in under 1 second

AnswersB, D

Capacity is a warranty aspect.

Why this answer

Warranty in ITIL 4 refers to the assurance that a service will meet its agreed-upon performance and capacity requirements. The ability to handle 10,000 concurrent users is a measurable capacity guarantee, ensuring the service can support the expected workload without degradation, which is a core warranty aspect.

Exam trap

The trap here is that candidates often confuse performance metrics (like response time) or features (like search function) with warranty, but ITIL 4 strictly limits warranty to availability, capacity, continuity, and security, not functional capabilities or speed guarantees.

Full explanation →

278

MCQhard

Refer to the exhibit. A change order to patch a security vulnerability on WebServer01 has been approved. The IT manager is the change authority. During implementation, it is discovered that the patch requires a reboot, which will cause an outage for the OrderApp application. What is the MOST appropriate action?

A.Inform the IT manager and ask for a decision on whether to proceed.

B.Escalate to the change advisory board (CAB) for a new approval.

C.Proceed with the change as planned, since the change is already approved.

D.Cancel the change and request a new one with updated information.

AnswerA

When new information, such as an unexpected mandatory reboot causing an outage, emerges after a change has been approved but before its implementation, the designated change authority must be informed. The IT manager, acting as the change authority, is empowered to re-evaluate the change's risk, impact, and schedule based on this updated information. This ensures that decisions are made with the most current data, aligning with ITIL's principle of 'Progress Iteratively with Feedback' and maintaining service stability.

Why this answer

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.

Exam trap

The trap here is that candidates assume a change approval is final and irrevocable, but ITIL 4 requires that any new risk discovered during implementation must be communicated to the change authority for a fresh decision, not blindly executed or automatically escalated to a CAB.

How to eliminate wrong answers

Option B is wrong because the change advisory board (CAB) is typically used for higher-risk or standard changes, not for an operational decision on an already-approved change where the change authority (IT manager) is already identified and available. Option C is wrong because proceeding without informing the change authority of the newly discovered outage risk violates the principle of risk-based decision-making and could lead to unauthorized service disruption. Option D is wrong because canceling the change outright is premature; the change authority should first be consulted to decide if the change can proceed with the new risk or if it should be re-planned.

Full explanation →

279

MCQeasy

What is the PRIMARY purpose of the Problem Management practice?

A.To restore normal service operation as quickly as possible

B.To fulfil service requests from users

C.To manage the lifecycle of all changes

D.To identify the root cause of incidents and prevent recurrence

AnswerD

This option accurately defines the primary purpose of Problem Management, which is to reduce the likelihood and impact of incidents by identifying and resolving their underlying causes. The practice involves thorough root cause analysis to understand why incidents occur and then implementing solutions to prevent their recurrence. By addressing the fundamental issues, Problem Management significantly improves service stability and reduces the overall volume of incidents.

Why this answer

The primary purpose of Problem Management is to identify the root cause of incidents and prevent their recurrence or minimize their impact. This is achieved through root cause analysis (RCA) and the creation of known error records, which directly support service stability and continuous improvement. Unlike Incident Management, which focuses on restoring service quickly, Problem Management addresses the underlying cause to reduce future incidents.

Exam trap

The trap here is that candidates often confuse the reactive, fast-restore focus of Incident Management (Option A) with the proactive, root-cause-elimination focus of Problem Management, especially when both practices deal with incidents.

How to eliminate wrong answers

Option A is wrong because it describes the primary purpose of Incident Management, not Problem Management; Incident Management aims to restore normal service operation as quickly as possible, often through a workaround. Option B is wrong because fulfilling service requests from users is the purpose of Service Request Management, which handles pre-defined, low-risk requests like password resets or information requests. Option C is wrong because managing the lifecycle of all changes is the purpose of Change Enablement (formerly Change Management), which controls the introduction of changes to minimize risk and disruption.

Full explanation →

280

Multi-Selecthard

Which THREE of the following are components of the ITIL 4 Service Value System (SVS)?

Select 3 answers

A.Service Value Chain

B.Service Portfolio

C.Guiding Principles

D.ITIL Maturity Model

E.Practices

AnswersA, C, E

The Service Value Chain is one of the five core SVS components, converting inputs into outputs through six activities. It satisfies the stem's requirement by being an explicitly named element of the Service Value System, alongside guiding principles, governance, practices and continual improvement.

Why this answer

The ITIL 4 Service Value System (SVS) is composed of five core components: Guiding Principles, Governance, Service Value Chain, Practices, and Continual Improvement. Option A (Service Value Chain) is correct because it is the central operating model of the SVS, describing the six activities (Plan, Improve, Engage, Design and Transition, Obtain/Build, Deliver and Support) that convert inputs like demand and opportunity into value. Option C (Guiding Principles) is correct because the seven guiding principles (Focus on Value, Start Where You Are, Progress Iteratively with Feedback, Collaborate and Promote Visibility, Think and Work Holistically, Keep It Simple and Practical, Optimize and Automate) are a foundational SVS component that informs decision-making across the organization.

Option E (Practices) is correct because ITIL 4 defines 34 management practices (e.g., Incident Management, Continual Improvement, Change Enablement) that are a formal component of the SVS, providing the resources and capabilities needed to perform work. Option B (Service Portfolio) is not a component of the ITIL 4 SVS; it is a service management concept/tool used to manage services across their lifecycle, not one of the five SVS elements. Option D (ITIL Maturity Model) is also not an SVS component; it is a separate assessment tool used to evaluate an organization's ITIL adoption and capability maturity.

Exam trap

The trap here is that candidates often confuse the components of the SVS with elements of the ITIL framework like the Service Portfolio or Maturity Model, which are related but not part of the SVS structure.

Full explanation →

281

Multi-Selecthard

Which THREE of the following are key activities of Service Configuration Management?

Select 3 answers

A.Identifying and documenting configuration items (CIs)

B.Authorizing and scheduling changes to CIs

C.Maintaining the configuration management database (CMDB)

D.Verifying and auditing configuration records against actual state

E.Defining service level targets with customers

AnswersA, C, D

Identifying and documenting CIs is a core activity of Service Configuration Management.

Why this answer

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.

Exam trap

The trap here is confusing the activities of Service Configuration Management with those of Change Management or Service Level Management, as ITIL 4F often tests the precise boundaries between practices by listing overlapping but distinct responsibilities.

Full explanation →

282

MCQmedium

An IT team is tasked with redesigning a service desk process. They decide to first document the current process and identify what works well before making changes. Which guiding principle are they applying?

A.Focus on value

B.Progress iteratively with feedback

C.Start where you are

D.Think and work holistically

AnswerC

The "Start where you are" guiding principle mandates that organizations assess the current state of services and processes before initiating any improvement or redesign efforts. By documenting and leveraging existing practices within the service desk, the IT team is directly adhering to this principle, ensuring that valuable elements are retained and unnecessary reinvention is avoided. This foundational understanding prevents wasted effort and builds upon established strengths.

Why this answer

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.

Exam trap

The trap here is that candidates confuse 'Start where you are' with 'Progress iteratively with feedback' because both involve analysis, but the former focuses on the initial baseline assessment while the latter is about the cycle of incremental changes and reviews.

How to eliminate wrong answers

Option A is wrong because 'Focus on value' directs efforts toward delivering outcomes that matter to stakeholders, not on analyzing the current state. Option B is wrong because 'Progress iteratively with feedback' involves making small, incremental improvements with continuous feedback loops, not documenting the current process as a starting point. Option D is wrong because 'Think and work holistically' means considering the entire system and its interdependencies, not specifically analyzing the existing process before changes.

Full explanation →

283

MCQmedium

An IT department is experiencing frequent service outages due to unauthorized changes. They need to implement controls to manage changes effectively. Which ITIL practice should be prioritized to address this issue?

A.Incident management

B.Change enablement

C.Service desk

D.Problem management

AnswerB

Change enablement is a proactive practice designed to maximize the number of successful service and product changes by ensuring all changes are properly assessed, authorized, scheduled, and implemented. This practice is crucial for preventing service outages that could arise from uncoordinated or unauthorized modifications to the IT environment. By establishing robust control over changes, it minimizes risk and maintains service stability.

Why this answer

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.

Exam trap

The trap here is that candidates confuse Incident management (restoring service) with Change enablement (preventing unauthorized changes), mistakenly thinking that faster incident resolution will reduce outages caused by unauthorized changes, when in fact only proactive change control can prevent them.

How to eliminate wrong answers

Option A is wrong because Incident management focuses on restoring normal service operation after an outage has occurred, not on preventing unauthorized changes from happening in the first place. Option C is wrong because the Service desk acts as the single point of contact for users reporting issues or requesting changes, but it does not own the authorization or control mechanisms to prevent unauthorized changes. Option D is wrong because Problem management aims to identify and eliminate the root causes of incidents, but it does not provide the proactive change control processes needed to stop unauthorized changes from being made.

Full explanation →

284

MCQhard

You are the IT service manager for a medium-sized e-commerce company that processes online orders. The company uses a three-tier application architecture: a web server, an application server, and a database server. Recently, the company has been experiencing intermittent service degradation during peak hours (12:00-14:00 and 18:00-20:00), causing slow page loads and occasional timeouts. The monitoring system shows that CPU utilization on the application server spikes to 95% during these periods, while the web server and database server remain below 60%. The incident management team has been opening multiple tickets for the same issue, but each ticket is resolved by restarting the application server, which temporarily restores performance. The problem management team has been assigned to investigate the root cause. They have discovered that a recent software update to the application introduced a memory leak that gradually consumes resources until the server becomes overloaded. The development team has identified a fix but needs two weeks to fully test and deploy it. Meanwhile, the business is losing revenue due to poor performance. Which of the following actions should the problem management team take FIRST?

A.Conduct a root cause analysis to fully understand the memory leak.

B.Implement a workaround, such as scheduling a restart of the application server every hour during peak times.

C.Increase the application server's CPU capacity to handle the load.

D.Escalate the incident to the service desk for faster resolution.

AnswerB

Implementing a workaround, such as scheduled restarts, directly addresses the immediate impact of the memory leak by temporarily freeing up resources and restoring service functionality. This aligns perfectly with the primary objective of Incident Management: to restore normal service operation as quickly as possible, minimizing business disruption. A workaround provides a temporary solution, allowing time for Problem Management to identify and deploy a permanent fix without ongoing service degradation.

Why this answer

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.

Exam trap

The trap here is that candidates may choose Option A (root cause analysis) because they confuse the problem management process with incident management, failing to recognize that the root cause is already known and the priority is to restore service with a workaround first.

How to eliminate wrong answers

Option A is wrong because conducting a full root cause analysis is unnecessary at this stage—the development team has already identified the memory leak as the root cause, so further analysis would delay the urgent need to restore service. Option C is wrong because increasing CPU capacity does not resolve the underlying memory leak; the application will still consume resources until it exhausts memory, causing performance degradation regardless of CPU size. Option D is wrong because escalating to the service desk would not resolve the technical issue; the service desk handles incidents, not problem resolution, and the problem management team already owns the investigation.

Full explanation →

285

MCQeasy

Which practice involves the Single Point of Contact (SPOC) for users?

A.Problem Management

B.Service Desk

C.Incident Management

D.Service Level Management

AnswerB

The Service Desk is explicitly defined in ITIL 4 as the single point of contact (SPOC) between the service provider and its users. Its primary function is to handle all user interactions, including logging incidents, fulfilling service requests, and providing information. By centralizing communication, the Service Desk ensures a consistent and efficient channel for users to engage with IT services, facilitating value co-creation.

Why this answer

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.

Exam trap

PeopleCert often tests the distinction between a practice (Incident Management) and the function that implements the SPOC (Service Desk), causing candidates to confuse the process with the operational point of contact.

How to eliminate wrong answers

Option A is wrong because Problem Management focuses on identifying the root cause of incidents and preventing recurrence, not on providing a single point of contact for users. Option C is wrong because Incident Management is the process of restoring normal service operation after an incident, but it does not itself act as the SPOC; the Service Desk is the function that handles the initial contact and triage. Option D is wrong because Service Level Management is responsible for negotiating, agreeing, and monitoring service level agreements (SLAs), not for providing a direct user-facing contact point.

Full explanation →

286

MCQhard

An IT manager wants to improve first-level resolution rates by empowering the service desk to resolve more incidents without escalation. Which ITIL 4 concept is being applied?

A.Continual Improvement

B.Shift-left

C.Service Desk

D.Omnichannel

AnswerB

Shift-left is a strategic approach aimed at moving incident resolution and service request fulfillment to the earliest possible point of contact, typically the Service Desk or self-service channels. By empowering first-level support with more knowledge, tools, and authority, or by enabling users with self-service, it directly increases the percentage of issues resolved at the initial interaction. This strategy is precisely designed to improve first-level resolution rates by reducing escalations to higher support tiers.

Why this answer

The scenario describes moving incident resolution tasks from higher-level support tiers to the service desk, which is the essence of 'shift-left' in ITIL 4. By empowering the service desk with better tools, knowledge, and authority, incidents are resolved earlier in the support chain, improving first-level resolution rates and reducing escalation costs. This directly applies the shift-left principle, not just a general improvement or channel strategy.

Exam trap

The trap here is that candidates confuse 'shift-left' with 'Continual Improvement' because both involve making processes better, but shift-left is specifically about moving work earlier in the support lifecycle, not just any improvement.

How to eliminate wrong answers

Option A is wrong because Continual Improvement is a broader, ongoing cycle of evaluating and enhancing all IT services and practices, not a specific technique to empower the service desk for first-level resolution. Option C is wrong because Service Desk is a functional team or tool, not a concept or practice; the question asks which ITIL 4 concept is being applied, not which team is involved. Option D is wrong because Omnichannel refers to integrating multiple communication channels (e.g., chat, email, phone) for a seamless customer experience, not to shifting resolution responsibilities to lower tiers.

Full explanation →

287

MCQhard

A service provider offers a payroll service that calculates employee salaries and generates payslips. The service is delivered according to a schedule and meets all compliance requirements. Which statement BEST distinguishes utility from warranty in this context?

A.Utility refers to the cost of the service; warranty refers to its availability.

B.Utility is the calculation and payslip generation; warranty is the delivery on schedule and compliance.

C.Utility is the on-time delivery; warranty is the calculation of salaries.

D.Utility and warranty are both focused on the functionality of the service.

AnswerB

This option correctly distinguishes between utility and warranty for a payroll service. Utility represents the core functionality that enables the customer to achieve their objective, specifically the accurate calculation of salaries and the generation of payslips, which is the 'fitness for purpose.' Warranty assures that this essential functionality is delivered reliably, meeting agreed-upon performance criteria such as on-schedule delivery and adherence to legal and regulatory compliance standards, which are critical for payroll operations and represent the 'fitness for use.'

Why this answer

Ly distinguishes utility from warranty: utility is the functionality offered by the service (calculating salaries and generating payslips), while warranty is the assurance that the service will meet agreed conditions (delivery on schedule and compliance). In ITIL 4, utility is 'fit for purpose' (what the service does), and warranty is 'fit for use' (how it is delivered reliably).

Exam trap

The trap here is that candidates often confuse utility with warranty by swapping their definitions, especially when both involve time-based or compliance-related aspects, leading them to pick Option C or D.

How to eliminate wrong answers

Option A is wrong because utility is not about cost; cost is a separate consideration in service value, and warranty is not solely about availability but includes capacity, continuity, and security. Option C is wrong because it reverses the definitions: on-time delivery is a warranty aspect, not utility, and salary calculation is utility, not warranty. Option D is wrong because warranty is not focused on functionality; it focuses on the conditions under which functionality is delivered (e.g., performance, reliability).

Full explanation →

288

MCQmedium

A company is reviewing its service management practices and identifies that it lacks a consistent approach to handling known errors. Which practice should be improved to manage known errors effectively?

A.Service level management

B.Incident management

C.Configuration management

D.Problem management

AnswerD

Problem management is the practice responsible for reducing the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors. A known error is a problem that has been analyzed and has a documented root cause and a workaround. Problem management systematically tracks these known errors, facilitating their resolution and preventing recurring incidents.

Why this answer

Known errors are documented in the Known Error Database (KEDB) and are a key output of problem management. Problem management is responsible for identifying the root cause of incidents and documenting workarounds or permanent fixes as known errors, making option D correct.

Exam trap

The trap here is that candidates confuse incident management with problem management, assuming that handling known errors is part of restoring service quickly, but ITIL 4 explicitly assigns known error management to problem management, not incident management.

How to eliminate wrong answers

Option A is wrong because service level management focuses on negotiating and monitoring service level agreements (SLAs), not on documenting or managing known errors. Option B is wrong because incident management handles restoring normal service operation after an incident, but it does not own the process of identifying root causes or maintaining known error records. Option C is wrong because configuration management maintains the configuration management database (CMDB) and tracks configuration items (CIs), but it does not manage the lifecycle of known errors or their workarounds.

Full explanation →

289

MCQmedium

An IT department is implementing a new service desk tool. They decide to automate password resets to reduce call volume. This is an example of which guiding principle?

A.Focus on value

B.Collaborate and promote visibility

C.Optimise and automate

D.Keep it simple and practical

AnswerC

The "Optimise and automate" guiding principle directs organizations to make the best use of their human and technical resources by improving processes and automating tasks wherever possible and sensible. Automating a routine task within a new service desk tool directly aligns with this principle, as it aims to reduce manual effort, minimize errors, improve efficiency, and free up human resources for more complex, value-adding activities. This principle explicitly encourages continuous improvement through streamlining and technological enablement.

Why this answer

The guiding principle 'Optimise and automate' directly applies to using technology to streamline repetitive, manual tasks. Automating password resets reduces human intervention, minimizes errors, and frees up service desk resources, which is a core application of this principle in ITIL 4.

Exam trap

The trap here is that candidates confuse 'Optimise and automate' with 'Keep it simple and practical' because automation can reduce manual effort, but the question specifically highlights the act of automating a process, which directly maps to the 'Optimise and automate' principle, not simplicity.

How to eliminate wrong answers

Option A is wrong because 'Focus on value' emphasizes delivering outcomes that matter to stakeholders, not the specific method of automation; while password resets add value, the question explicitly describes the automation mechanism, not the value justification. Option B is wrong because 'Collaborate and promote visibility' concerns cross-team communication and transparency of work, not the technical automation of a single process. Option D is wrong because 'Keep it simple and practical' advocates for minimal complexity and avoiding over-engineering, but automating a password reset is not inherently complex or impractical—it is a standard, efficient improvement that aligns more with optimization than simplicity.

Full explanation →

290

MCQeasy

What is the definition of 'value' in ITIL 4?

A.The monetary worth of a service

B.The perceived benefits, usefulness, and importance of something

C.The cost savings achieved by using a service

D.The output produced by a service

AnswerB

This option accurately reflects the ITIL 4 definition of value. Value is understood as the perceived benefits, usefulness, and importance of something from the perspective of a stakeholder. It is subjective and context-dependent, encompassing both tangible outcomes and intangible benefits that contribute to achieving an organization's objectives, making it a cornerstone of the ITIL 4 service value system.

Why this answer

ITIL 4 defines value as the perceived benefits, usefulness, and importance of something, which is a subjective assessment by stakeholders rather than an objective measure. This definition emphasizes that value is co-created through the use of services and depends on the outcomes and experiences of the service consumer, not just on technical outputs or financial metrics.

Exam trap

The trap here is that candidates often confuse value with tangible metrics like cost savings or outputs, but ITIL 4 deliberately defines value as a subjective perception of benefits and importance, not as an objective financial or production measure.

How to eliminate wrong answers

Option A is wrong because it reduces value to monetary worth, ignoring the subjective and co-created nature of value in ITIL 4, which includes non-financial aspects like user satisfaction and business outcomes. Option C is wrong because cost savings are only one potential benefit of a service, not the definition of value itself; value encompasses both benefits and costs in a holistic manner. Option D is wrong because outputs are the tangible deliverables of a service (e.g., a report), whereas value is about the outcomes and perceived importance that those outputs enable for the customer.

Full explanation →

291

MCQhard

An IT team has redesigned a customer portal, delivering new features on time and within budget. However, customer satisfaction scores have dropped because users find the new interface confusing. Which statement best describes this situation?

A.The team achieved an outcome without delivering an output

B.The team delivered both an output and an outcome as planned

C.The team achieved a positive outcome but failed to deliver a valuable output

D.The team delivered an output but did not achieve the intended outcome

AnswerD

Outputs are the deliverables produced; outcomes are the results stakeholders value. Delivering the portal on time and budget satisfies scope and cost, yet the drop in satisfaction shows the intended outcome — usable, clear customer service — was not achieved.

Why this answer

The IT team successfully delivered the redesigned customer portal (the output) on time and within budget, but the drop in customer satisfaction scores indicates that the intended outcome—improved user experience and satisfaction—was not achieved. In ITIL 4, an output is a tangible deliverable (like a new feature or a service), while an outcome is the result or value realized by the customer. Here, the output was delivered, but the outcome failed, making option D correct.

Exam trap

The trap here is that candidates often confuse 'output' with 'outcome' and assume that delivering a feature on time and within budget automatically implies a successful outcome, but ITIL 4 emphasizes that value is only realized when the output leads to the desired outcome.

How to eliminate wrong answers

Option A is wrong because the team did deliver an output (the redesigned portal), so it is not a case of achieving an outcome without an output. Option B is wrong because the planned outcome (improved customer satisfaction) was not achieved, so both output and outcome were not delivered as planned. Option C is wrong because the output (the portal) was delivered, but the outcome was negative, not positive; the statement 'positive outcome' is incorrect.

Full explanation →

292

MCQeasy

What is the difference between utility and warranty in ITIL 4?

A.Utility is about cost; warranty is about quality

B.Utility is for customers; warranty is for users

C.Utility is about functionality; warranty is about performance and availability

D.Utility is provided by the service provider; warranty is provided by the customer

AnswerC

Utility precisely describes the functionality a service provides, addressing what the service does and whether it is 'fit for purpose' in supporting customer outcomes. Warranty, conversely, focuses on the non-functional aspects, ensuring the service is 'fit for use' through guaranteed levels of performance, availability, capacity, and security. This distinction highlights that a service must not only do what is needed but also do it reliably and consistently.

Why this answer

Utility is 'fit for purpose' (does it do what it should?), while warranty is 'fit for use' (is it available, secure, etc.?).

Full explanation →

293

MCQmedium

A service desk analyst resolves a user's issue by following a script. Which metric is most appropriate to measure the analyst's performance?

A.Customer Satisfaction (CSAT)

B.Mean Time to Resolve (MTTR)

C.Number of incidents logged

D.First Call Resolution (FCR)

AnswerD

First Call Resolution (FCR) is a critical Key Performance Indicator (KPI) that measures the percentage of incidents or service requests fully resolved during the user's initial contact with the service desk. When a service desk analyst successfully resolves a user's issue completely during the first interaction, without needing further follow-up or escalation, this directly exemplifies and contributes to a high FCR rate. It reflects the efficiency and effectiveness of the service desk at the point of initial contact.

Why this answer

First Call Resolution (FCR) is the most appropriate metric because it directly measures whether the analyst resolved the issue during the initial contact without escalation or follow-up. Following a script to resolve a user's issue on the first call demonstrates effective adherence to standardized procedures and minimizes customer effort, which is the core purpose of FCR in ITIL 4.

Exam trap

The trap here is that candidates often confuse FCR with MTTR, thinking that resolving quickly is the same as resolving on the first call, but MTTR can be low even if the issue requires multiple contacts, whereas FCR specifically measures one-and-done resolution.

How to eliminate wrong answers

Option A is wrong because Customer Satisfaction (CSAT) measures overall user happiness with the service experience, not the specific performance of resolving an issue by following a script; a user could be satisfied even if the issue was not resolved on the first call. Option B is wrong because Mean Time to Resolve (MTTR) measures the average time from incident logging to resolution, which can be influenced by factors like queue time and complexity, not the efficiency of following a script on the first contact. Option C is wrong because the number of incidents logged is a volume metric that reflects workload, not the quality or effectiveness of the analyst's resolution performance when using a script.

Full explanation →

294

MCQmedium

Which change type is pre-authorized and follows a defined procedure?

A.Emergency change

B.Service change

C.Normal change

D.Standard change

AnswerD

Standard changes are pre-authorized, low-risk changes that are frequently implemented and follow a well-documented, repeatable procedure. Because their risks are understood and managed, they do not require individual assessment and approval each time they are performed. This pre-authorization allows for efficient execution, aligning perfectly with the description of a change that is pre-authorized and follows a defined process.

Why this answer

Standard changes are pre-authorized and follow a defined, low-risk procedure, such as applying a routine security patch or provisioning a new user account. They do not require additional approval because the risk is well-understood and the implementation steps are documented in a standard operating procedure (SOP). This aligns with ITIL 4's definition of a standard change as a change that is fully documented, low risk, and can be implemented without a formal change advisory board (CAB) meeting.

Exam trap

The trap here is that candidates confuse 'pre-authorized' with 'no change record needed'—standard changes still require a change record for tracking, but they skip the approval step because the procedure is already approved.

How to eliminate wrong answers

Option A is wrong because an emergency change is not pre-authorized; it requires urgent approval (often via an emergency CAB) and follows a separate, accelerated procedure to address high-impact incidents. Option B is wrong because 'service change' is a generic term in ITIL 4 for any change affecting a service, not a specific change type with pre-authorization and a defined procedure. Option C is wrong because a normal change requires formal assessment and approval by the change authority (e.g., CAB) before implementation; it is not pre-authorized.

Full explanation →

295

MCQmedium

Which practice ensures that the performance of a service is measured and analyzed to meet current and future demand?

A.IT Asset Management

B.Availability Management

C.Capacity and Performance Management

D.Service Configuration Management

AnswerC

Capacity and Performance Management ensures that services and their components can meet current and future demand in a cost-effective manner, while achieving agreed performance targets. This practice involves monitoring, analyzing, and tuning service performance, such as response times, throughput, and resource utilization, to prevent bottlenecks and ensure optimal operation under various loads. It directly addresses the 'how well' a service performs to deliver value.

Why this answer

Capacity and Performance Management is the ITIL 4 practice whose explicit purpose is to ensure that services, service components, and resources meet current and future agreed-upon capacity and performance requirements in a cost-effective manner. It involves monitoring, measuring, and analyzing performance data against demand forecasts so that capacity can be scaled proactively. This directly matches the question's wording about measuring and analyzing service performance to meet current and future demand.

Exam trap

ITIL4F often tests the confusion between Availability Management and Capacity and Performance Management, since both deal with service performance metrics — candidates must remember that availability is about uptime/reliability while capacity is about meeting demand and performance levels.

How to eliminate wrong answers

Option A is wrong because IT Asset Management focuses on tracking the lifecycle, value, and cost of assets (hardware, software, licenses) rather than measuring service performance against demand. Option B is wrong because Availability Management is concerned with ensuring services meet agreed availability targets (uptime, reliability, MTBF/MTTR), not with capacity sizing or performance tuning against demand. Option D is wrong because Service Configuration Management maintains accurate configuration records (CIs and their relationships in the CMDB), which supports other practices but does not itself measure or analyze performance.

Full explanation →

296

MCQhard

A team is implementing a new IT service management tool. They decide to release a basic version with core features first, gather user feedback, and then add enhancements in subsequent releases. Which ITIL 4 guiding principle is being applied?

A.Start where you are

B.Think and work holistically

C.Keep it simple and practical

D.Progress iteratively with feedback

AnswerD

This principle advocates for organizing work into smaller, manageable iterations, allowing for continuous learning and adaptation based on feedback received at each step. The scenario explicitly states that the team is implementing a new ITSM tool using "iterative releases with feedback loops," which is a direct and precise application of this guiding principle. This approach enables early value delivery, reduces risk, and ensures the solution evolves effectively to meet changing requirements through continuous improvement.

Why this answer

The team's approach of releasing a basic version first, gathering user feedback, and then adding enhancements in subsequent releases directly aligns with the ITIL 4 guiding principle 'Progress iteratively with feedback'. This principle emphasizes delivering value incrementally, using feedback loops to refine and improve the service or product, which is exactly what the team is doing with their IT service management tool releases.

Exam trap

The trap here is that candidates may confuse 'Progress iteratively with feedback' with 'Keep it simple and practical' because both involve incremental steps, but the key differentiator is the explicit use of user feedback to guide subsequent releases, which is the hallmark of the iterative principle.

How to eliminate wrong answers

Option A is wrong because 'Start where you are' focuses on leveraging existing processes, tools, and data rather than building from scratch, but the scenario describes a new tool implementation with iterative releases, not an assessment of the current state. Option B is wrong because 'Think and work holistically' involves considering the entire system and its interdependencies, which is not the primary focus of releasing a basic version and adding enhancements based on feedback. Option C is wrong because 'Keep it simple and practical' advocates for minimizing complexity and avoiding over-engineering, but the scenario's core action is the iterative release cycle with feedback, not just simplicity.

Full explanation →

297

Multi-Selectmedium

Which TWO of the following are key components of the Service Desk practice?

Select 2 answers

A.Root cause analysis

B.Configuration baseline

C.Shift-left

D.Single point of contact (SPOC)

E.Omnichannel communication

AnswersD, E

A single point of contact (SPOC) satisfies the Service Desk practice’s requirement to provide a consistent, centralised entry for all user incidents and service requests. This mechanism ensures that users always log issues through one dedicated channel, preventing fragmented communication and enabling proper ticket logging, routing, and escalation according to ITIL4F’s service desk design.

Why this answer

The Service Desk practice is built around being the single point of contact (SPOC) for users, meaning option D is correct because the service desk serves as the centralized entry point through which all users can report incidents, make requests, and receive updates, ensuring consistent handling and communication. Option E is also correct because omnichannel communication is a key component of the modern Service Desk, enabling users to interact through multiple channels such as phone, email, chat, self-service portal, and walk-in while maintaining a consistent experience. Option A (root cause analysis) belongs primarily to the Problem Management practice, which investigates underlying causes of incidents rather than being a core Service Desk component.

Option B (configuration baseline) is part of Service Configuration Management, which defines and controls approved configurations of configuration items. Option C (shift-left) is a broader improvement strategy often associated with the Service Desk but is not itself listed as one of the two key components in this context.

Exam trap

The trap here is that candidates often confuse the Service Desk practice with other practices like Problem Management or Service Configuration Management, leading them to select root cause analysis or configuration baseline as key components, when in fact the service desk is about operational contact and communication, not analysis or configuration control.

Full explanation →

298

MCQmedium

What is the PRIMARY difference between a problem and an incident?

A.Incidents are unplanned interruptions; problems are the cause of incidents

B.Incidents are always resolved within 24 hours; problems may take longer

C.Problems are logged by users; incidents are logged by the service desk

D.Incidents require a change request; problems do not

AnswerA

An incident, according to ITIL 4, is an unplanned interruption to a service or a reduction in the quality of a service. Its primary goal is to restore normal service operation as quickly as possible. Conversely, a problem is defined as a cause, or potential cause, of one or more incidents, even if the cause is not yet known. Problem management focuses on identifying these root causes and preventing future incidents, or at least minimizing their impact, making this the fundamental differentiating factor.

Why this answer

The primary difference is that an incident is an unplanned interruption or reduction in quality of an IT service, while a problem is the underlying cause of one or more incidents. In ITIL 4, incidents are managed to restore normal service operation as quickly as possible, whereas problems are analyzed to identify and eliminate root causes to prevent recurrence. This distinction is foundational because incidents are reactive events, while problems drive proactive improvement through problem management.

Exam trap

The trap here is that candidates confuse the symptom (incident) with the cause (problem) and assume time-based or role-based distinctions, when ITIL 4 explicitly defines them by their purpose and lifecycle, not by arbitrary metrics or logging sources.

How to eliminate wrong answers

Option B is wrong because ITIL 4 does not mandate any specific resolution time for incidents; SLAs may define targets, but incidents can take longer than 24 hours depending on complexity. Option C is wrong because both incidents and problems can be logged by users, the service desk, or automated monitoring tools; the source of logging does not define the difference. Option D is wrong because neither incidents nor problems inherently require a change request; a change request may be raised as part of the resolution process for either, but it is not a defining characteristic.

Full explanation →

299

MCQeasy

An organization wants to improve its ability to detect and respond to security incidents. Which practice should be enhanced to achieve this objective?

A.Problem Management

B.Availability Management

C.Incident Management

D.Information Security Management

AnswerD

Information Security Management is the dedicated practice responsible for protecting an organization's information assets by identifying, assessing, and treating information security risks. It encompasses establishing security policies, implementing controls, conducting vulnerability assessments, and, critically, developing and executing robust security incident detection and response procedures to safeguard confidentiality, integrity, and availability against malicious activities.

Why this answer

Enhancing Information Security Management (ISM) directly improves an organization's ability to detect and respond to security incidents because ISM defines the policies, controls, and monitoring mechanisms (e.g., SIEM rules, intrusion detection signatures, and incident response playbooks) that enable proactive threat detection and structured response. While Incident Management handles the lifecycle of an incident once detected, ISM is the practice that establishes the security posture and detection capabilities in the first place.

Exam trap

The trap here is that candidates confuse Incident Management (the process for handling incidents) with Information Security Management (the practice that establishes detection and prevention controls), leading them to select Incident Management because it seems directly related to 'responding' to incidents, but the question specifically asks about improving the ability to 'detect and respond', which requires the security controls defined by ISM.

How to eliminate wrong answers

Option A is wrong because Problem Management focuses on identifying and eliminating the root causes of incidents to prevent recurrence, not on detecting or responding to security incidents in real time. Option B is wrong because Availability Management ensures that IT services meet agreed availability targets (e.g., uptime percentages) and does not directly address security detection or response mechanisms. Option C is wrong because Incident Management is the process for managing the lifecycle of all incidents, including security incidents, but it does not itself enhance detection capabilities; detection is a prerequisite that ISM provides through security controls and monitoring.

Full explanation →

300

MCQmedium

An organization is adopting ITIL 4 and wants to ensure that all activities within the Service Value System (SVS) are aligned with the organization's strategic objectives. Which key component of the SVS should be used to enforce this alignment?

A.Governance

B.Service value chain activities

C.Continual improvement

D.Guiding principles

AnswerA

Governance is the critical component within the ITIL 4 Service Value System (SVS) responsible for directing and controlling the organization to achieve its strategic objectives. It establishes the policies, frameworks, and decision-making authorities that ensure all service management activities are aligned with the overall business strategy. Through effective governance, the organization can monitor performance, manage risks, and enforce compliance, thereby guaranteeing that the SVS consistently contributes to desired outcomes.

Why this answer

Governance is the key component of the Service Value System (SVS) that ensures all activities are aligned with the organization's strategic objectives. It provides the framework for decision-making, accountability, and oversight, directing how the SVS operates to meet stakeholder needs. Without governance, the service value chain activities, continual improvement, and guiding principles may operate in isolation from strategic goals.

Exam trap

The trap here is that candidates confuse 'Guiding Principles' as the mechanism for alignment because they are prescriptive, but ITIL 4 explicitly separates governance as the formal control system that enforces strategic direction, while principles are advisory and not binding.

How to eliminate wrong answers

Option B is wrong because service value chain activities are the operational steps (plan, improve, engage, design & transition, obtain/build, deliver & support) that produce value, but they do not inherently enforce alignment with strategic objectives—they require governance to direct them. Option C is wrong because continual improvement is a practice that ensures ongoing optimization of services and processes, but it is a method for improvement, not a mechanism for enforcing strategic alignment across the entire SVS. Option D is wrong because guiding principles (e.g., focus on value, start where you are) are recommendations that influence behavior and decision-making, but they are not a formal control mechanism; governance provides the authority and policies to enforce alignment.

Full explanation →

ITIL 4 Foundation (ITIL4F) — Questions 226–300