Overview
This category covers the definitions that ITIL (Version 5) builds everything else on. It is split into four syllabus topics: product and service management (digital products, digital services, goods, utility, warranty, user experience and sustainability), service offerings, value co-creation (value, outcomes, outputs, costs and risks), and service relationships (roles, relationship types, the service journey, service quality and service level agreements).
The big shift from ITIL 4 is framing. Version 5 describes itself as guidance for digital product and service management rather than IT service management alone, so a product and the service built around it are treated as two views of one solution. Two new recall items stand out: user experience and sustainability now sit next to utility and warranty as qualities of a solution, and a digital product vendor appears as a role alongside the service provider and service consumer.
How it's tested
Questions here are short and definition-led. Expect a paraphrased definition with four candidate terms, a list question where two of four statements about a concept are true, or a one-line scenario asking which role a named person plays. Precision on the Version 5 terms matters more than reasoning about a long scenario.
-
Name the concept
A definition such as a result for a stakeholder enabled by outputs is given, and you choose outcome over output, value or benefit.
-
Who plays which role?
A short story names a finance director, a department head and staff using a tool; you match each to sponsor, customer or user.
-
Utility, warranty or experience?
A requirement like 99.9% availability or an easy checkout flow is described, and you identify which quality of a solution it represents.
A stem says a payroll team now spends less time reconciling data since a new reporting service went live, and asks what this describes. The time saved is a result the team experiences, so it is an outcome. The report the service produces is an output. Value would be the team's perception of benefit and importance, which is broader than the single result described, so outcome is the best fit.
Syllabus topics 4
Official syllabus topics from the PeopleCert outline, in outline order.
1.1 Product and service managementDigital product and service management, products, digital products and services, goods, utility, warranty, user experience and sustainability.
- What it means
- Version 5 treats a product as a configuration of an organization's resources designed to offer value to a consumer, and a digital product as one built mainly on digital technology. A digital service is how that product is made useful to consumers through interaction. Digital product and service management is the discipline of managing both views together across their lifecycle, supported by continual improvement.
- What to understand
- Learn four qualities as a set. Utility is what a solution does, its fitness for purpose. Warranty is how well it performs against agreed requirements such as availability, capacity, security and continuity. User experience is how interacting with it feels to the people using it. Sustainability covers its environmental, social and economic effects over time. Also recall goods as tangible items whose ownership transfers to the consumer, and know that the Product and Service Lifecycle and continual improvement are listed here as key concepts too.
- How it shows up
- Expect a requirement to classify, or a definition of product, digital product or digital service with plausible swaps between them.
- Common confusion
- Treating user experience as part of utility; Version 5 recalls it as a separate quality alongside utility, warranty and sustainability.
1.2 Service offeringWhat a service offering contains: goods, access to resources and service actions.
- What it means
- A service offering is a formal description of one or more services aimed at the needs of a target consumer group. It bundles three kinds of element: goods that are transferred to the consumer, access to resources that the consumer may use under agreed terms without owning them, and service actions that the provider performs to address the consumer's needs.
- What to understand
- The key test is ownership and responsibility. With goods, ownership passes to the consumer, who then carries responsibility for them. With access to resources, ownership stays with the provider and the consumer only gets agreed use, such as a licence to a cloud application. Service actions are things the provider does, for example user support or replacing equipment. One offering often contains all three, and different consumer groups may receive different offerings built from the same product.
- How it shows up
- A described bundle, such as a laptop plus helpdesk plus storage, is broken down and you classify each part.
- Common confusion
- Calling a software licence a good; the consumer usually receives access to a resource, not ownership of it.
1.3 Value co-creationValue, outcomes and outputs, costs, risks, and how value is co-created through use.
- What it means
- Value is the perceived benefits, usefulness and importance of something, and it is judged by the stakeholder, not declared by the provider. Version 5 stresses that value is co-created: the provider and consumer both contribute, and value only appears when the product or service is actually used. An output is a deliverable of an activity, while an outcome is a result for a stakeholder that outputs enable.
- What to understand
- A service relationship changes the consumer's costs and risks. Some costs are removed, such as buying and running servers, while new ones are imposed, such as subscription fees or training. Likewise some risks are removed, such as hardware failure, and new ones introduced, such as dependency on the provider. Value results when outcomes are worth more than the costs and risks imposed. Recall that risk is a possible event that could cause harm or loss or make objectives harder to reach.
- How it shows up
- A scenario lists effects of a new service and asks which is an output, which an outcome, or which cost was removed rather than imposed.
- Common confusion
- Thinking the provider creates value alone and hands it over; Version 5 says value is co-created through use.
1.4 Service relationshipsProvider, consumer and vendor roles, sponsor, customer and user, relationship types, the service journey, service quality, service level and SLAs.
- What it means
- A service relationship is the cooperation between a service provider and a service consumer, covering provision, consumption and relationship management. Version 5 also recalls the organization as the wider entity and adds the digital product vendor as a role that supplies digital products used inside services. Within the consumer, the sponsor authorizes budget, the customer defines requirements and owns outcomes, and the user actually uses the service.
- What to understand
- Know three relationship types and how they differ. A basic relationship is transactional, built on standard products with little tailoring. A cooperative relationship adds agreed outcomes and shared work beyond the standard product. A collaborative relationship, also called a partnership, involves shared goals and joint responsibility for value. Recall the service journey as the steps a consumer takes across the relationship, service quality as the totality of characteristics that bear on meeting needs, service level as one or more metrics defining expected quality, and the SLA as the documented agreement between provider and customer. Be ready to explain how utility, warranty, experience and sustainability shape relationships.
- How it shows up
- A named person is described by what they do, and you assign sponsor, customer or user; or a relationship description is matched to its type.
- Common confusion
- Assuming one person cannot hold several roles; a sole trader can be sponsor, customer and user at once.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Digital product and service management
The Version 5 scope: managing digital products and the services built on them as one solution across their lifecycle.
- Remember
- Version 5 positions ITIL as guidance for this discipline, wider than IT service management.
- Tested as
- Framing questions test whether you recognise the Version 5 scope statement.
- Trap
- Choosing the ITIL 4 phrase service management as the definition of the whole framework.
-
Utility
The functionality offered by a solution to meet a particular need; what it does.
- Remember
- Utility answers 'is it fit for purpose?'
- Tested as
- Requirements describing features or functions map to utility.
- Trap
- Labelling a performance target such as response time as utility.
-
Warranty
Assurance that a solution will meet agreed requirements; how well it performs.
- Remember
- Availability, capacity, security and continuity are warranty concerns.
- Tested as
- Requirements about levels, targets and reliability map to warranty.
- Trap
- Treating a new feature request as a warranty matter.
-
User experience and sustainability
Two qualities Version 5 recalls next to utility and warranty: how interaction feels, and long-term environmental, social and economic effects.
- Remember
- There are four qualities to recall, not two.
- Tested as
- Appears in list questions asking which statements about solution qualities are true.
- Trap
- Dropping both and answering with the older two-quality model.
-
Value
The perceived benefits, usefulness and importance of something.
- Remember
- Value is judged by the stakeholder and is co-created through use.
- Tested as
- Definition questions offer outcome or benefit as distractors.
- Trap
- Defining value as the price paid or the output delivered.
-
Outcome vs output
An output is a deliverable of an activity; an outcome is a result for a stakeholder enabled by outputs.
- Remember
- Reports, configured devices and resolved tickets are outputs; time saved is an outcome.
- Tested as
- Classification questions present effects of a service and ask which is which.
- Trap
- Calling a delivered report an outcome.
-
Service offering elements
Goods, access to resources and service actions.
- Remember
- Only goods transfer ownership to the consumer.
- Tested as
- Bundles are broken down for classification.
- Trap
- Classifying a licence or cloud storage as goods.
-
Sponsor, customer, user
Consumer roles: authorizes budget, defines requirements and owns outcomes, uses the service.
- Remember
- One person can hold more than one role.
- Tested as
- Short scenarios ask who plays which role.
- Trap
- Assuming the person paying is always the customer.
-
Relationship types
Basic, cooperative and collaborative (partnership) relationships.
- Remember
- Moving from basic to collaborative means more shared goals and joint responsibility.
- Tested as
- A relationship description is matched to its type.
- Trap
- Picking partnership for any long contract, even when it is purely transactional.
-
Service level agreement
A documented agreement between a provider and a customer that identifies services required and the expected level of service.
- Remember
- Service level is the metric set; the SLA is the agreement that records it.
- Tested as
- Recall items separate service level, service quality and SLA.
- Trap
- Treating a service level and an SLA as the same thing.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Four qualities of a solution in Version 5
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Utility | What the solution does for the consumer | Concerned with function and fitness for purpose | Mixing it up with ease of use, which is experience |
| Warranty | How well the solution meets agreed requirements | Concerned with levels such as availability and security | Calling every non-functional requirement utility |
| User experience | How interacting with the solution feels to people | Concerned with the human side of use | Folding it into utility as in older study notes |
| Sustainability | Long-term environmental, social and economic effects | Looks beyond the immediate relationship | Treating it only as energy use |
Service offering elements
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Goods | Tangible items supplied to the consumer | Ownership and responsibility transfer to the consumer | Listing a software subscription here |
| Access to resources | Agreed use of provider-owned resources | Ownership stays with the provider | Assuming access means ownership |
| Service actions | Work the provider performs for the consumer | An activity, not a thing | Forgetting that support desks are service actions |
Relationship types
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Basic | Transactional use of standard products | Little tailoring and limited shared goals | Thinking basic means low quality |
| Cooperative | Agreed outcomes plus some shared work | Goes beyond the standard product | Confusing it with full partnership |
| Collaborative (partnership) | Shared goals and joint responsibility for value | Deepest trust and integration | Applying it to any long-term contract |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Output presented as outcome
- What candidates pick
- The deliverable, such as a dashboard or a configured laptop.
- Why it looks right
- It is concrete and easy to point at.
- Why it's wrong
- A deliverable is an output; the outcome is the result a stakeholder achieves by using it, such as faster decisions.
Clue to watch for Look for wording about what a stakeholder can now achieve.
-
Payer assumed to be customer
- What candidates pick
- The person signing the budget as the customer.
- Why it looks right
- In everyday speech the payer is the customer.
- Why it's wrong
- ITIL separates the sponsor, who authorizes budget, from the customer, who defines requirements and owns outcomes.
Clue to watch for The stem says who approves funding versus who sets requirements.
-
Two-quality answer
- What candidates pick
- An option naming only utility and warranty as the qualities of a solution.
- Why it looks right
- It matches ITIL 4 Foundation study material.
- Why it's wrong
- Version 5 recalls user experience and sustainability as qualities in their own right, so a two-item list is incomplete.
Clue to watch for A question asking for the complete set or naming Version 5.
-
Ownership confusion
- What candidates pick
- Goods for any item the consumer receives, including software access.
- Why it looks right
- Receiving something feels like owning it.
- Why it's wrong
- Only goods transfer ownership; licences and hosted capacity are access to resources that remain the provider's.
Clue to watch for Words like subscribe, licence, hosted or rented.
-
Partnership by duration
- What candidates pick
- Collaborative relationship for a long fixed contract with standard terms.
- Why it looks right
- Long contracts sound like partnerships.
- Why it's wrong
- Relationship type depends on shared goals and joint responsibility, not on contract length.
Clue to watch for Check whether goals are shared or the service is standard.
Answer framework
Use this sequence on definition-led questions, which form most of this category.
- Identify which of the four topics the stem belongs to: product and service management, offerings, value co-creation or service relationships.
- Recall the Version 5 term exactly, including the newer items such as digital product vendor, user experience and sustainability.
- For classification stems, apply one test each: function or level for utility and warranty, ownership for goods, and deliverable or result for output and outcome.
- For role stems, separate budget authority, requirement ownership and actual use before matching sponsor, customer and user.
- If two options remain, pick the one matching ITIL wording rather than everyday business meaning, which is usually the distractor.
Practice question
Want more like this? The ITIL 5 Foundation practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with the vocabulary cards. Write each Version 5 definition on one side and a short example on the other, and drill until you can produce the term from a paraphrase. Group them by syllabus topic so the four parts stay distinct. Spend most time on service relationships, because it holds eleven of the twenty-eight assessment criteria, and on the four solution qualities, because they are where ITIL 4 habits do the most damage.
Then practise classification. Take a familiar service such as a streaming subscription or a company laptop scheme and break it down: list the goods, resources and actions; name the sponsor, customer and user; state one output and one outcome; and say which costs and risks were removed or added. Doing this for three or four services builds the quick judgement the exam needs.
Finish with timed sets of 12 to 15 recall questions. Review each miss by asking whether you lacked the definition or misread a qualifier such as 'best describes'. Revisit this category in the final week, since it carries more marks than any category except the value system.
FAQ
How much of the exam comes from Key ITIL terms and definitions?
Key ITIL terms and definitions is weighted at 30% in the Version 5 syllabus, which works out to about 12 of the 40 questions. PeopleCert gives the percentage; the question count is our estimate.
What is new compared with ITIL 4 Foundation?
The scope is digital product and service management, user experience and sustainability join utility and warranty, the digital product vendor appears as a role, and relationship types and the service journey are recall items.
Are these questions mostly recall?
Largely yes. Many criteria in this category are Bloom's level 1, so you recognise definitions. A few, such as distinguishing relationship types, ask you to explain, which means short scenarios.
Do I need to learn definitions word for word?
Not verbatim, but closely. Distractors often change one key word, such as replacing perceived benefits with delivered outputs, so the precise idea inside each definition matters.
Can one person hold several consumer roles?
Yes. In a small business the owner can authorize spending, define requirements and use the service, making them sponsor, customer and user at once.
Is sustainability tested in depth?
At Foundation level you recall it as a quality of a solution and explain how it affects service relationships. Detailed environmental reporting methods are outside this syllabus.
Other Enterprise Architecture & IT Governance certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 1 knowledge
Check that you can classify offering elements, separate outputs from outcomes, and name sponsor, customer and user roles quickly under exam timing.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the ITIL 5 Foundation AI tutor Get any concept explained your way