ITIL Foundation V5 Exam Flashcards

Q: What is the ITIL Foundation (Version 5) exam format?

PeopleCert lists 40 multiple-choice Objective Test Questions, a 60-minute time limit, closed-book conditions, and a 65% pass mark (26 of 40 correct). Each question is worth one mark with no negative marking, so candidates should answer every question.

Q: What changed in Version 5 compared with ITIL 4 Foundation?

Version 5 reframes Foundation around digital product and service management, introduces the eight-activity ITIL Product and Service Lifecycle (discover, design, acquire, build, transition, operate, deliver, support), adds value stream mapping and management, sustainability, experience, and AI-enabled ways of working, and uses a two-group practice model (general practices and product and service management practices) instead of ITIL 4's three-group split.

Q: Does PeopleCert publish ITIL Foundation Version 5 pass rates?

No official public pass-rate percentage was found on PeopleCert's current exam page or syllabus. The pass rate is therefore listed as not published rather than estimated.

Q: What are the official Version 5 syllabus weights?

Key ITIL terms and definitions 30%, four dimensions 10%, product and service lifecycle 10%, ITIL Value System 40%, value stream identification, mapping, and management 5%, ITIL and AI 2.5%, and ITIL and other frameworks 2.5%.

Q: How long is the ITIL Foundation (Version 5) certificate valid?

PeopleCert shows renewal every 3 years with 60 CPD points needed for renewal. Candidates can also keep certifications current by completing a different course from the same product suite and passing the associated exam before the renewal date.

Question 1

What makes ITIL v5's 'digital product and service management' different from ITIL 4's 'service management'?

Accepted Answer

v5 broadens the scope so products and services are managed together, reflecting how modern providers bundle a digital product (e.g. a SaaS platform) with the service actions that help consumers use it. Naming both signals that products are first-class value objects, not just containers for services, which is why v5 adds a Product and Service Lifecycle alongside the Value System.

Question 2

Product vs service (ITIL v5 distinction)

Accepted Answer

A product is a configuration of an organization's resources designed to offer value to a consumer; ownership can be transferred. A service is the means of enabling value co-creation by facilitating outcomes the consumer wants, without the consumer managing the specific costs and risks. Products can be sold outright; services are consumed through a relationship.

Question 3

Digital service vs digital product

Accepted Answer

A digital service is delivered through digital channels (an online booking flow, a managed API) where the consumer interacts without owning the underlying platform. A digital product is the asset itself (the app, the platform) that a provider configures and offers. The exam tests whether you can tell a service relationship from a product sale.

Question 4

Goods within a service offering

Accepted Answer

Goods are tangible or transferable items a consumer can take ownership of (e.g. a laptop handed over as part of an onboarding offering). Ownership transfers to the consumer, unlike access to resources or service actions where the provider retains the asset. Spotting 'ownership transfers' is the fastest way to identify the goods component.

Question 5

Three components of a service offering

Accepted Answer

1) Goods — ownership transfers to the consumer. 2) Access to resources — granted under agreed terms, ownership stays with the provider (e.g. a managed analytics platform). 3) Service actions — performed by the provider on request (e.g. resetting a password). Mix the three to build an offering; confusing 'access' with 'goods' is a common exam trap.

Question 6

Utility vs warranty

Accepted Answer

Utility is fitness for purpose — what the service does and which constraints it removes for the consumer. Warranty is fitness for use — the assurance the service will perform as agreed (capacity, availability, security, continuity). A service can have utility without warranty (right thing, unreliably) or warranty without utility (reliable but wrong thing); both are needed for value.

Question 7

Value co-creation (why value is not 'delivered')

Accepted Answer

Value is the perceived benefit, usefulness, and importance of something, and it is defined by the consumer, not the provider. v5 stresses co-creation: the provider's offering only creates value when the consumer actively uses it, supplies feedback, and accepts costs and risks. Treating value as something the provider ships one-way is the v3-era mistake v5 explicitly rejects.

Question 8

Service relationship and the three consumer-side roles

Accepted Answer

A service relationship is the cooperation between a service provider and a service consumer. On the consumer side three roles appear: the customer defines requirements and takes responsibility for outcomes, the user uses the service, and the sponsor authorizes budget. A single person can hold multiple roles, but the roles themselves are distinct.

Question 9

Output vs outcome

Accepted Answer

An output is a tangible or intangible deliverable produced by an activity (a report generated, a ticket closed). An outcome is the result a stakeholder experiences because of one or more outputs (a faster decision, fewer outages). Outputs are easy to count; outcomes are what customers actually value, and confusing them leads teams to optimize for activity over impact.

Question 10

User experience (UX) vs customer experience (CX)

Accepted Answer

UX is the experience of the person directly using the service — usability, friction, task completion. CX is the experience of the person who commissions or buys the service, covering the whole relationship including contractual and outcome dimensions. The user and the customer can be different people with different success criteria.

Question 11

The four dimensions of product and service management

Accepted Answer

1) Organizations and people — culture, roles, skills, structure. 2) Information and technology — data, knowledge, platforms, tools. 3) Partners and suppliers — external relationships and supply chains. 4) Value streams and processes — how work flows and is organized. All four must be considered together; optimizing one in isolation causes failures in the others.

Question 12

Organizations and people dimension focus

Accepted Answer

Covers culture, leadership, workforce skills, role design, team structure, and ways of working. If a GenAI rollout fails here, it is usually because roles and culture were not prepared — not because the technology was wrong. This is where 'people and culture eat strategy for breakfast' shows up in v5.

Question 13

Partners and suppliers dimension focus

Accepted Answer

Covers relationships with external organizations that supply goods, services, or capabilities the provider relies on — including SaaS vendors, outsourced operations, and contractors. When a critical SaaS supplier changes its data retention policy, this dimension is the first thing to review, while still checking the impact on the other three.

Question 14

Information and technology dimension focus

Accepted Answer

Covers the knowledge, data, platforms, and technology used to manage products and services — including the information needed to make decisions and the tools that store, process, and secure it. A common mistake is to equate this dimension with 'IT' in the narrow sense; it explicitly includes information and knowledge management, not just hardware and software.

Question 15

PESTLE external factors and the holistic approach

Accepted Answer

PESTLE = Political, Economic, Social, Technological, Legal, Environmental. These are external factors that affect all four dimensions from outside the organization. v5 insists on a holistic approach because a change that looks purely technical (e.g. a new AI feature) ripples through people, partners, and processes, and is shaped by PESTLE forces.

Question 16

Eight ITIL Product and Service Lifecycle activities (v5)

Accepted Answer

Discover, design, acquire, build, transition, operate, deliver, support. v5 splits the old ITIL 4 value chain activities into these eight lifecycle activities, which are iterative and non-linear — you can move back and forth between them rather than marching top to bottom.

Question 17

Discover lifecycle activity

Accepted Answer

Discover explores what is needed, what opportunities exist, and what value could be created for which stakeholders. It is the research and opportunity-shaping activity that precedes design — understanding problems before committing to solutions. Skipping discover is a classic reason products get built that nobody wants.

Question 18

Design lifecycle activity

Accepted Answer

Design shapes how a product or service should work, feel, integrate, and meet stakeholder needs — including user experience, architecture, and service levels. It is concerned with intent and fit, not with building. Human-centred design techniques belong here.

Question 19

Acquire vs build

Accepted Answer

Acquire obtains external resources or capabilities the organization does not build itself — buying a SaaS platform, contracting a supplier, licensing a dataset. Build constructs or assembles internally. v5 keeps them separate so providers can mix buy and make deliberately rather than defaulting to 'build it ourselves'.

Question 20

Transition lifecycle activity

Accepted Answer

Transition moves a product, service, or change safely into live use — including validation, release planning, and cutover. It is the bridge between build and live consumption. Done badly, transition is where outages, rollback failures, and unhappy users are created.

Question 21

Operate vs deliver vs support

Accepted Answer

Operate keeps live products and services reliable, secure, and performing as expected (monitoring, event handling, runbook execution). Deliver provides the service to consumers as agreed (service levels, access provisioning). Support helps users and consumers when they have questions or issues — the three are related but distinct, and v5 lists them as separate lifecycle activities.

Question 22

Seven ITIL guiding principles

Accepted Answer

1) Focus on value. 2) Start where you are. 3) Progress iteratively with feedback. 4) Collaborate and promote visibility. 5) Think and work holistically. 6) Keep it simple and practical. 7) Optimize and automate. They are universally applicable, enduring, and meant to guide decisions — not be followed once and discarded.

Question 23

Focus on value

Accepted Answer

Every decision should be judged by what value it creates for the consumer and the organization, including sustainability and outcomes rather than just output. The trap is internal optimization (e.g. shipping the easiest-to-build feature) that delivers no consumer value. If a choice does not improve outcomes for someone who matters, it fails this principle.

Question 24

Start where you are

Accepted Answer

Before building new, assess what already exists and works — current services, data, tools, processes, and capabilities. Reusing and improving current state is usually cheaper and less risky than greenfield rebuilds. The principle protects against the 'not invented here' bias that destroys working assets.

Question 25

Progress iteratively with feedback

Accepted Answer

Break work into small, manageable increments, release them, and use the feedback to adjust the next increment. Big-bang delivery delays feedback and magnifies risk; small increments surface problems early. This is why v5 aligns with Agile and Lean ways of working.

Question 26

Collaborate and promote visibility

Accepted Answer

Work across boundaries (silos, teams, providers, consumers) and make work, decisions, and status visible to those affected. Hidden work creates hidden failures; visible work creates shared accountability. Acting on this principle means involving the right stakeholders and removing information asymmetry, not just 'being nice'.

Question 27

Think and work holistically

Accepted Answer

No dimension, practice, value chain activity, or team is sufficient on its own. A change to a mobile app must consider user experience, service desk impact, supplier readiness, security, and release workflow together. Holistic thinking is the antidote to optimizing one dimension at the expense of the other three.

Question 28

Keep it simple and practical + optimize and automate (and the order)

Accepted Answer

Keep it simple and practical means use only the processes, tools, and metrics that actually create value — strip out the rest. Optimize and automate means simplify and improve a process BEFORE automating it; automating a broken process just produces failures faster. The implied order is always optimize first, then automate.

Question 29

Components of the ITIL Value System (v5)

Accepted Answer

Guiding principles, governance, the value chain, management practices, practice guides, the operating model, metrics, critical success factors, and the continual improvement model. Together they form the system that turns demand into value; the Value Chain is one component, not the whole system.

Question 30

Governance vs management

Accepted Answer

Governance is the act of directing and controlling an organization by setting objectives, policies, and constraints, and by evaluating outcomes — it sits above and around delivery. Management activities plan, design, deliver, and operate within the boundaries governance sets. Confusing the two leads either to over-managed teams with no direction, or over-directed teams with no execution.

Question 31

How v5 changed the Service Value Chain from ITIL 4

Accepted Answer

v5 replaces the six ITIL 4 value chain activities with the eight-activity Product and Service Lifecycle. 'Plan' and 'Improve' move up into the Value System as governance and continual-improvement concerns; 'Engage' is distributed across activities such as discover, deliver, and support; 'Design and transition' is split into Design and Transition; 'Obtain/build' is split into Acquire and Build; 'Deliver and support' is split into Operate, Deliver, and Support.

Question 32

Operating model (v5 term)

Accepted Answer

An operating model describes how an organization configures its practices, people, partners, technology, and value streams to deliver its strategy. In v5 the operating model is part of the Value System, not a separate layer — it operationalizes governance and guiding principles into day-to-day work. It is the 'how we actually run' answer to the 'what we aim to do' of strategy.

Question 33

How value chain activities are used in practice

Accepted Answer

Value chain activities are not a fixed sequence — they are combined and repeated to deliver value. A single change might touch discover, design, build, transition, operate, deliver, and support several times. The exam tests whether you treat the chain as a linear waterfall or as a flexible, combinable set of activities that can be revisited.

Question 34

Two v5 practice groups (replaces ITIL 4's three)

Accepted Answer

v5 Foundation scope uses two practice groups: general practices and product and service management practices. This replaces the ITIL 4 grouping of general, service management, and technical management practices. Use v5 wording in the exam — calling them 'service management practices' or 'technical management practices' is the older ITIL 4 frame.

Question 35

Release (ITIL term)

Accepted Answer

A release is a version of a service or product — or a set of changes to a service or product — made available for use at one time. It is the unit of transition into live use. A release bundles one or more changes so consumers experience them together; releasing is not the same as building, deploying, or approving a change.

Question 36

Incident vs event

Accepted Answer

An event is any detectable occurrence that has significance for the management of a product or service (a login, a threshold crossing, a deployment). An incident is an unplanned interruption or reduction in the quality of a service. Incidents are usually preceded by events, but most events are not incidents — the distinction matters for monitoring and prioritization.

Question 37

Problem vs error vs known error

Accepted Answer

A problem is a cause, or potential cause, of one or more incidents. An error is an identified defect or flaw — once the cause is found, the problem becomes an error. A known error is an error that has been analyzed but not yet resolved, and for which a workaround exists. The progression is problem → error → known error, with workarounds distinguishing the last.

Question 38

CI/CD, SRE, and observability (v5 distinctions)

Accepted Answer

CI/CD is the practice of continuously integrating code and deploying it through automated pipelines, shortening the build-to-release cycle. SRE (Site Reliability Engineering) applies engineering practices to operations — error budgets, service levels as objectives — to keep live services reliable. Observability is the ability to infer a system's internal state from its external outputs (logs, metrics, traces), going beyond monitoring to enable diagnosis.

Question 39

Practice Guides and Practice Success Factors (PSFs)

Accepted Answer

Practice Guides are ITIL publications that give detailed, practical guidance on individual management practices. A practice success factor (PSF) is a statement of what a practice must do to succeed — a capability condition, not a task. PSFs explain why a practice exists and what 'good' looks like; they are distinct from metrics, which measure whether the PSF is being achieved.

Question 40

Seven continual improvement model steps

Accepted Answer

1) What is the vision? 2) Where are we now? 3) Where do we want to be? 4) How do we get there? 5) Take action. 6) Did we get there? 7) How do we keep the momentum going? The model is iterative — step 7 loops back to step 1 as the vision and context evolve.

Question 41

Why 'What is the vision?' comes first

Accepted Answer

Without a clear vision, improvement has no direction and no way to judge whether any change is an improvement. The vision aligns the initiative to organizational strategy and to value, so later steps (where are we, where do we want to be) have a reference point. Skipping it produces effort that solves the wrong problem.

Question 42

'Where are we now?' vs 'Where do we want to be?'

Accepted Answer

'Where are we now?' establishes the honest baseline — current metrics, capability, and pain points. 'Where do we want to be?' defines the target state, expressed as measurable improvements against the vision. The gap between them is what the 'How do we get there?' step must close; without both, you cannot size the work.

Question 43

Metric vs critical success factor (CSF)

Accepted Answer

A CSF is a statement of what must be true for success — a condition (e.g. 'incidents resolved within agreed time'). A metric is a measurable value used to track progress against a CSF (e.g. 'average resolution time 4.2 hours'). CSFs define the why and what; metrics quantify the how-well. Confusing them produces vanity metrics that look good but do not indicate success.

Question 44

Core value stream vs enabling value stream

Accepted Answer

A core value stream directly delivers value to an external customer (e.g. the stream that onboards a new paying user). An enabling value stream supports the core by providing capabilities the core depends on (e.g. the internal hiring stream that staffs the support team). Cutting an enabling stream to save money usually breaks a core stream later.

Question 45

Value stream mapping vs value stream management

Accepted Answer

Value stream mapping is a one-time exercise that visualizes the steps, handoffs, delays, and waste in a stream so you can see how value flows today. Value stream management is the ongoing governance — designing, monitoring, and continuously improving streams over time. Mapping produces a snapshot; management keeps the stream healthy.

Question 46

Value stream map elements + why complexity thinking matters

Accepted Answer

A value stream map typically shows the steps, the actors at each step, the flow of information and materials, the time each step takes, and the wait times between steps. Complexity thinking matters because value streams are systems with feedback loops and emergent behavior — linear fixes often cause new bottlenecks elsewhere. Useful maps surface waits and rework, not just the visible work.

Question 47

AI vs GenAI vs Agentic AI (ITIL v5)

Accepted Answer

AI is the broad capability of machines to perform tasks that normally require human intelligence. GenAI produces new content (text, code, images) from learned patterns. Agentic AI goes further — it can take actions and make decisions toward a goal with limited human oversight. v5 treats them as distinct maturity points, not synonyms, and the AI Capability Model places them at increasing capability levels.

Question 48

Purpose of AI governance in v5

Accepted Answer

AI governance ensures AI is used ethically, safely, and in line with organizational policy — covering accountability, transparency, bias, data privacy, and risk. Without it, AI-assisted lifecycle automation (e.g. auto-triaging incidents, GenAI-generated knowledge articles) can create compliance and reputational harm faster than it creates value. Governance is what lets v5 organizations use AI without losing control of it.

Question 49

How ITIL and DevOps complement each other

Accepted Answer

ITIL provides the governance, value system, and practices that define what 'good service management' looks like; DevOps provides the culture, automation, and flow practices (CI/CD, small batches, shared ownership) that make delivery fast and reliable. They are not rivals — ITIL gives DevOps a management frame, and DevOps gives ITIL practical ways to flow value. Picking 'one or the other' loses both.

Question 50

How ITIL and PRINCE2 complement each other

Accepted Answer

PRINCE2 is a project management method — it controls defined, bounded projects with a start and end. ITIL manages the ongoing products and services those projects create, across their whole lifecycle. PRINCE2 governs project delivery; ITIL governs service and product operation and improvement. Using PRINCE2 to run a service, or ITIL to run a one-off project, misapplies both.

Free ITIL Foundation V5 Exam Flashcards

Filter by Topic

Jump to Card

About These ITIL Foundation V5 Flashcards

Topics Covered

Frequently Asked Questions

ITIL Foundation (Version 5)

Explore More ITIL Certifications

ITIL 4 Foundation

ITIL 4 Managing Professional

ITIL 4 Specialist: Create, Deliver and Support

ITIL 4 Strategic Leader

ITIL 4 Strategist: Direct, Plan and Improve

ITIL 4 Leader: Digital and IT Strategy (DITS)

More From This Family