ITIL 5: Strategy & Experience Design practice questions
27 questions on Strategy & Experience Design, one of the 11 areas assessed in ITIL 5 Foundation. Untimed, with an explanation after every answer.
This topic covers designing services around how people experience them. Customer experience spans the whole relationship, user experience the interaction with a product, and employee experience the internal side. Expect questions on journey mapping, service blueprints that link visible steps to backstage activities, moments of truth, and how strategy connects to day-to-day delivery.
The recurring trap is trusting provider metrics. A service can meet every agreed service level and still deliver a poor experience, and improving one touchpoint cannot offset a long wait elsewhere. Designing for experience is not just speed, and it applies to APIs and internal platforms too. Strategy and experience design are complementary, neither sequential nor alternatives.
The ITIL 5 exam is also offered in French, among other languages; these practice questions are in English. Which languages? →
Which statement best describes the difference between customer experience (CX) and user experience (UX) in service management?
Ready for exam conditions? 40 questions, 60 minutes, 65% to pass.
Mock examA worked example
A question from the bank with its answer and the reasoning behind it. Every practice question comes with an explanation like this one.
A service scores highly on availability and incident resolution time, yet consumer satisfaction is persistently poor. Which explanation is most consistent with a service design perspective?
- AThe measurements must be inaccurate
- BThe measures capture technical performance but not the friction consumers meet across the end-to-end journey(correct answer)
- CConsumers are not qualified to judge service quality
- DAvailability targets should be raised further
Why
Technical measures describe the provider's view of the components. Consumers experience a journey — requesting, waiting, being handed between teams, re-explaining a problem — and friction there is invisible to availability and MTTR. Journey-level measurement closes that gap. Doubting the data (A) or the consumer (C), or tightening an already-met target (D), all avoid the actual cause.