ITIL 4 Foundation ITIL4F Questions 526–531 | Page 8/8

526

MCQmedium

In which phase of Problem Management are known errors created and managed?

A.Incident management

B.Problem control (root cause analysis)

C.Error control

D.Problem identification

AnswerC

Error control is the specific phase of problem management where a problem, once its root cause has been identified and confirmed, is formally documented as a "known error." This phase involves creating and maintaining known error records, which detail the root cause, symptoms, and any available workarounds. Additionally, error control is responsible for initiating change requests to implement permanent solutions for these known errors, thereby preventing future incidents.

Why this answer

Known errors are created and managed during the Error Control phase of Problem Management. This phase focuses on documenting known errors in the Known Error Database (KEDB) after root cause analysis is complete, and managing them through their lifecycle until a permanent resolution (e.g., a change via RFC) is implemented. Error Control ensures that workarounds are available and that the known error is tracked for future resolution.

Exam trap

The trap here is that candidates confuse Problem Control (root cause analysis) with Error Control, mistakenly thinking known errors are created during root cause analysis rather than after it, when the cause is known and documented as a known error.

How to eliminate wrong answers

Option A is wrong because Incident Management handles restoring normal service operation as quickly as possible, not the creation or management of known errors. Option B is wrong because Problem Control (root cause analysis) identifies the underlying cause of problems but does not create or manage known errors; that occurs in the subsequent Error Control phase. Option D is wrong because Problem Identification is the initial phase where problems are detected and logged, not where known errors are created or managed.

Full explanation →

527

Multi-Selectmedium

Which THREE are key metrics for the Service Desk practice?

Select 3 answers

A.First Contact Resolution (FCR)

B.Average time to resolve an incident

C.Number of problems recorded

D.Customer Satisfaction Score (CSAT)

E.Mean Time Between Failures (MTBF)

AnswersA, B, D

First Contact Resolution (FCR) is a critical metric for the service desk practice, measuring the percentage of incidents or service requests successfully resolved during the initial interaction with the customer. A high FCR rate indicates efficient service delivery, reduces customer effort, and minimizes the need for follow-up contacts, thereby improving overall customer satisfaction and optimizing service desk resource allocation. It directly reflects the service desk's ability to provide immediate value and effective support.

Why this answer

Key service desk metrics include First Contact Resolution (FCR), Customer Satisfaction Score (CSAT), and average time to resolve incidents (which relates to Mean Time to Resolve). MTBF is an availability metric. Number of problems is a problem management metric.

Full explanation →

528

MCQmedium

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

A.Log the incident and categorize it

B.Check the known error database for a workaround

C.Route the call directly to problem management

D.Tell the user it is not an incident and ask them to call back

AnswerA

In ITIL 4, the first action for any reported service disruption is to log and categorise the incident, as this creates a permanent record and enables prioritisation based on impact and urgency. The stem specifies a “call” from a user, which triggers the incident management process; logging immediately satisfies the requirement to capture the initial report before any diagnosis or escalation can occur.

Why this answer

According to ITIL 4, the first step in incident management is to log and categorize the incident to ensure it is recorded and prioritized. Option A is correct because immediate documentation enables proper handling. Option B (checking the known error database) is premature because this step is typically done after logging and categorization, not as a first response.

Option C (routing to problem management) is incorrect because problem management deals with root cause analysis after incidents are logged. Option D (closing and asking to call back) is unacceptable as service must be restored.

Full explanation →

529

Multi-Selectmedium

Which TWO of the following are characteristics of an 'outcome' in ITIL 4?

Select 2 answers

A.It represents a result for a stakeholder

B.It is achieved by using outputs

C.It is the same as utility

D.It is always measurable in terms of functionality

E.It is a tangible deliverable

AnswersA, B

An outcome in ITIL 4 represents the desired effect or result that a service consumer achieves through the use of a service. It is fundamentally stakeholder-centric, focusing on the value realized by the individual or organization consuming the service. This result addresses a specific need or objective, contributing directly to their business goals or personal aspirations. Therefore, an outcome is the ultimate value proposition delivered to a stakeholder.

Why this answer

In ITIL 4, an outcome is defined as a result for a stakeholder, which is why option A is correct. Outcomes are achieved by using outputs (option B), as outputs are the tangible or intangible deliverables that enable the desired result. This distinction is central to understanding value co-creation in service management.

Exam trap

The trap here is confusing outputs with outcomes, as candidates often pick 'tangible deliverable' (option E) thinking it describes an outcome, but ITIL 4 explicitly defines outcomes as results, not deliverables.

Full explanation →

530

MCQmedium

An organization wants to implement a tool that tracks the lifecycle of IT assets from procurement to disposal. Which practice is primarily responsible for this?

A.Service Configuration Management

B.Monitoring and Event Management

C.Supplier Management

D.IT Asset Management

AnswerD

IT Asset Management is the practice of planning, procuring, deploying, managing, and retiring IT assets across their entire lifecycle, from acquisition to disposal. This practice ensures that the organization gains optimal value from its assets, manages associated costs, controls risks, and meets regulatory and contractual requirements. It specifically encompasses tracking assets through all phases, including financial, contractual, and operational aspects, making it the precise fit for tracking the complete lifecycle of assets.

Why this answer

IT Asset Management (ITAM) is the practice responsible for tracking the complete lifecycle of IT assets, including procurement, deployment, maintenance, and disposal. It ensures financial and contractual accountability, aligning with ISO 19770 standards for asset management processes.

Exam trap

The trap here is confusing Service Configuration Management (which tracks configuration items) with IT Asset Management (which tracks financial and lifecycle attributes), leading candidates to choose A when the question explicitly asks about procurement-to-disposal tracking.

How to eliminate wrong answers

Option A is wrong because Service Configuration Management focuses on maintaining accurate configuration data (CIs) in the CMDB, not on financial lifecycle tracking or disposal. Option B is wrong because Monitoring and Event Management deals with real-time observation of services and infrastructure, not asset lifecycle management. Option C is wrong because Supplier Management oversees vendor relationships and contracts, but does not directly manage the internal lifecycle tracking of assets from procurement to disposal.

Full explanation →

531

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 service request, to fulfil the users' need to access the payroll system

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

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

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

AnswerB

An incident is defined as an unplanned interruption to an IT service or a reduction in the quality of an IT service. When users cannot access the payroll system due to a login failure, it constitutes an unplanned interruption, directly impacting their ability to perform work. The primary objective upon identifying such an event is the swift restoration of normal service operation to minimize business impact, making an incident record the appropriate initial response.

Why this answer

An unplanned interruption to a service is an incident. Even though it occurred after maintenance, users are now unable to access the service, which constitutes a loss of service — the definition of an incident. Option A is wrong because a service request is for pre-approved, routine fulfilments, not for reporting an unplanned interruption.

Option C is wrong because a change request is used to authorize changes to IT infrastructure, not to record service disruptions. Option D is wrong because a problem record is used to investigate the root cause of incidents, but the immediate issue is an incident that should be logged first.

Full explanation →

ITIL 4 Foundation (ITIL4F) — Questions 526–531