ITIL 5: Digital Product & Service Management practice questions
31 questions on Digital Product & Service Management, one of the 11 areas assessed in ITIL 5 Foundation. Untimed, with an explanation after every answer.
ITIL 5 manages digital products and services together, and this topic tests product thinking. A digital product has an owner, a lifecycle and an ongoing value proposition; a project deliverable has an end point. Questions cover product-centric operating models with persistent teams and funding, value streams, retirement as a planned stage, and how to measure a product’s health.
The traps come from project habits. Accountability does not end at go-live, and renaming project managers as product owners changes nothing without persistent funding. Feature counts and backlog size measure activity; adoption, consumer outcomes and running cost measure health. Retiring a product is not a failure. A value stream follows the flow of work, not the organisation chart.
The ITIL 5 exam is also offered in French, among other languages; these practice questions are in English. Which languages? →
An organisation funds its work as a series of projects: each is approved, staffed, delivered and then disbanded, after which the service is handed to a separate operations group. Which characteristic of product-centric operating models is this arrangement missing?
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.
Which statement best distinguishes a digital product from a project deliverable?
- AA digital product is always software, whereas a project deliverable may be hardware
- BA digital product has an owner, a lifecycle and an ongoing value proposition; a project deliverable has a defined end point(correct answer)
- CA digital product is funded from operating expenditure and a project deliverable from capital expenditure
- DA digital product is managed by a supplier and a project deliverable is managed internally
Why
The defining difference is continuity of accountability and intent: a product exists to keep delivering a value proposition to consumers over time, with an owner and a lifecycle. A project deliverable is scoped to a defined end point. Funding treatment, technology type and sourcing are consequences or coincidences, not the distinction.