ITIL-4 domain - 43% of the exam

Understand 7 ITIL practices

Understand 7 ITIL practices is 43% of the ITIL-4 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

119
Practice questions
4
Objectives
66
Medium
53
Hard

Where people go wrong

  • Mixing up known error, workaround and root cause

    The wrong answers hand each term the definition of another. A workaround is described as a permanent resolution or as the status of the underlying problem, and a root cause is described as a workaround or a known error record. A root cause is the underlying reason a problem or incident exists. A workaround reduces or eliminates impact while a full resolution is unavailable. A known error is a problem that has been analysed and not resolved, with its cause understood.

    See it in a sample question
  • Swapping standard, normal and emergency changes

    The wrong answers attach one change type's handling to another. Per-occurrence board assessment is placed on standard changes, and pre-defined authorisation without separate assessment is placed on emergency changes. A standard change is low-risk and pre-authorised, following a documented procedure with no fresh authorisation each time it is enacted. An emergency change must be implemented as soon as possible, so its assessment and authorisation are expedited, often through a separate change authority, rather than skipped.

    See it in a sample question
  • Giving the service desk another practice's job

    The wrong answers credit the service desk with root-cause investigation, which belongs to problem management, with negotiating service targets, which belongs to service level management, or with authorising changes, which belongs to change enablement. Others read single point of contact as a single channel. The service desk captures demand for incident resolution and service requests and is the entry point for users. It can offer phone, chat, portal and email, because single point of contact means one consistent, coordinated route.

    See it in a sample question
  • Explaining a watermelon SLA as a breach

    The wrong answers account for the unhappy customer with something else: a breached target, a backlog of service requests, a supplier failure or a missing feature. In each scenario every agreed target was met. A watermelon SLA is green on the outside and red on the inside. The individual metrics report success while the customer's experience is poor, because the measures track components or activity rather than the outcomes the customer values.

    See it in a sample question
  • Swapping steps of the continual improvement model

    Each wrong option describes a different step from the one named. The vision step is confused with the baseline and with target-setting, 'Where are we now?' with target-setting and vision, and 'Did we get there?' with planning and with 'How do we keep the momentum going?'. The vision step sets high-level direction. 'Where are we now?' captures an honest baseline. 'Did we get there?' checks results against measurable targets after action is taken.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleUnderstand 7 ITIL practiceshard

In ITIL 4, how is a workaround best defined in the context of incident and problem management?

  • AA permanent correction that removes the cause of a problem so that the associated incidents can no longer occur.
  • BA documented instruction telling users which service requests they may raise without approval from the service desk.
  • CA prioritisation rule that determines the order in which incidents are assigned to support teams for investigation.
  • DA solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available. Correct
A workaround reduces or eliminates the impact of an incident or problem when a full resolution is not yet available. Workarounds let service be restored or maintained before a permanent fix exists. They are often recorded against known errors so that the same workaround can be reused quickly when related incidents recur, which links problem management directly to faster incident resolution.

Why A is wrong: This describes a permanent resolution rather than a workaround; a workaround is by definition temporary and does not remove the underlying cause.

Why B is wrong: This describes service request handling and has nothing to do with reducing the impact of incidents or problems, so it misplaces the concept in another practice.

Why C is wrong: Prioritisation is a separate incident management activity; a workaround is a means of reducing impact, not a scheme for ordering work, so this confuses two different things.

Why D is correct: This is the ITIL 4 definition of a workaround: it lessens or removes the impact when a complete resolution cannot yet be applied, and it can be associated with both incidents and problems.

Free sampleUnderstand 7 ITIL practiceshard

In ITIL 4, which statement most precisely captures the defining feature of a standard change as distinct from a normal change?

  • AA standard change is a low-risk, pre-authorised change that follows a documented and repeatable procedure, so it needs no fresh assessment each time it is raised. Correct
  • BA standard change is any change of small scope that a single team can complete quickly, regardless of whether a procedure for it exists.
  • CA standard change is a change that must be scheduled and assessed by a change advisory board before each occurrence to confirm it remains low risk.
  • DA standard change is an urgent change made to resolve an ongoing incident, authorised after the fact because there was no time to seek approval first.
A standard change is a pre-authorised, low-risk change enacted through a documented, repeatable procedure without fresh assessment each time. The defining trait of a standard change is that risk assessment and authorisation happen once when the procedure is established, so each subsequent instance follows that pre-approved procedure rather than being reassessed. Scope, speed, and urgency do not define the type.

Why A is correct: This matches ITIL 4: a standard change is pre-approved, low-risk, and enacted through an established, repeatable procedure, with authorisation given once to the procedure rather than to each instance.

Why B is wrong: Small scope and speed feel like the point of a standard change, but the defining feature is pre-authorisation through a documented repeatable procedure, not size or how fast a team can finish it.

Why C is wrong: Per-occurrence board assessment describes the handling of a normal change, not a standard change; a standard change is authorised once as a procedure and does not return for repeated assessment.

Why D is wrong: Urgency and retrospective authorisation describe an emergency change; a standard change is planned and pre-authorised, the opposite of an unplanned urgent fix.

Free sampleUnderstand 7 ITIL practicesmedium

Tollgate Media runs its service desk across phone, chat, a web portal and email so users can reach it in whatever way suits them, and every contact is logged in the same system. A manager argues that offering several channels weakens the desk's identity as a single point of contact. How should this be assessed against ITIL 4 guidance?

  • AThe manager is mistaken, because a single point of contact is about one coordinated function handling contacts consistently, not about limiting users to one channel Correct
  • BThe manager is correct, because ITIL 4 requires a service desk to operate through exactly one communication channel to remain a single point of contact
  • CThe manager is correct, because using multiple channels turns the service desk into part of the service level management practice
  • DThe manager is mistaken, but only because email and chat do not count as real contact channels under ITIL 4
Single point of contact means one coordinated service desk function handling contacts consistently, not a single access channel. ITIL 4 presents the service desk as the single point of contact in the sense of one unified, coordinated function that captures and manages every contact consistently. It is expected to offer multiple access channels, so many channels do not undermine its single-point-of-contact role.

Why A is correct: Correct: ITIL 4 describes the service desk as a single point of contact meaning one recognisable, coordinated function; it can and should offer multiple access channels while capturing and managing every contact consistently.

Why B is wrong: Tempting because single point of contact contains the word single, but ITIL 4 attaches that idea to a unified function and consistent handling, not to restricting users to one channel.

Why C is wrong: Tempting because both practices concern the customer relationship, but the channels a desk uses do not reassign it to service level management; the two practices have distinct purposes regardless of channel count.

Why D is wrong: Tempting because it reaches the right verdict, but the reasoning is wrong: ITIL 4 recognises varied channels including phone, chat, portals and email as legitimate ways to reach the desk.

Free sampleUnderstand 7 ITIL practicesmedium

A service provider reports that every SLA target for a service was met last month, yet the customer says the service felt poor throughout. In ITIL 4, this situation is described as which of the following?

  • AA workaround, because service continued to be delivered despite an unresolved underlying weakness.
  • BAn OLA breach, because an internal supporting team must have failed to meet its own targets during the month.
  • CA watermelon SLA, because the reported metrics are green while the customer's actual experience is red. Correct
  • DA service request backlog, because unhappy customers indicate a build-up of unfulfilled requests.
A watermelon SLA is one where reported targets are all met yet the measures fail to reflect the customer's actual poor experience. ITIL 4 uses the watermelon metaphor to warn that meeting narrow, component-level targets can mask overall dissatisfaction; good SLAs measure outcomes the customer cares about, not just easy-to-hit metrics.

Why A is wrong: A workaround is a way of reducing or eliminating an incident's impact when a full resolution is unavailable. It is tempting because both involve dissatisfaction persisting, but it does not describe a gap between metrics and experience.

Why B is wrong: An OLA breach would normally show up as a missed target, but here all targets were met. It is a plausible distractor because internal handoffs affect experience, but it does not explain green metrics with an unhappy customer.

Why C is correct: Correct. A watermelon SLA is green on the outside and red on the inside: individual measures are met, yet they fail to reflect the customer's real experience of the service.

Why D is wrong: A backlog of service requests is unrelated to how well SLA targets reflect experience. It is tempting because both concern dissatisfaction, but the scenario is specifically about metrics that look good while experience is poor.

Free sampleUnderstand 7 ITIL practicesmedium

Within the continual improvement model, what is the primary aim of the 'Where are we now?' step?

  • ATo define the measurable targets that describe the desired future state of the service.
  • BTo agree the high-level direction and long-term goals that the organisation is working towards.
  • CTo assess the current state through an honest baseline of existing services and their measurements. Correct
  • DTo carry out the specific improvement actions that were previously planned and agreed.
Recognise that 'Where are we now?' establishes an honest baseline of the current state for later comparison. An improvement can only be measured against a known starting point, so this step captures an unbiased baseline of current services and metrics; skipping or fudging it leaves later steps with nothing reliable to compare the outcome against.

Why A is wrong: This describes the 'Where do we want to be?' step, which sets the target state; it is tempting because both steps concern the state of a service, but this one looks forward rather than assessing the present.

Why B is wrong: This describes the 'What is the vision?' step, which sets direction; it is a plausible confusion because vision and current state are adjacent early steps, but agreeing goals is not the same as assessing where things stand now.

Why C is correct: Correct. The 'Where are we now?' step establishes an honest, factual baseline of the current services and their measurements so that later progress can be judged against a known starting point.

Why D is wrong: This describes the 'Take action' step, where planned improvements are executed; it is wrong because 'Where are we now?' comes before any action and simply establishes the facts of the current situation.

Other domains in this exam

See also the ITIL-4 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by PeopleCert / Axelos. Original, blueprint-aligned practice material only.