Free ITIL Foundation V5 Exam Flashcards

Memorize 55 essential terms and definitions for the ITIL Foundation (Version 5). See the term, recall the definition, then flip to check yourself.

55 Flashcards
10 Topics
100% Free
TermClick to flip

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

Tap to reveal definition
Card 1 of 55Key Terms

Filter by Topic

Jump to Card

About These ITIL Foundation V5 Flashcards

These 55 flashcards are designed to help you memorize key terms and definitions for the ITIL Foundation (Version 5). Each card shows a term on the front and its definition on the back—the classic flashcard format for vocabulary memorization. Use these alongside our practice questions to build both recall and comprehension.

Topics Covered

Key Terms15 cards
Four Dimensions5 cards
Product and Service Lifecycle6 cards
Guiding Principles7 cards
Value System and Value Chain5 cards
Practices and Practice Terms6 cards
Continual Improvement4 cards
Value Streams3 cards
AI in ITIL2 cards
Complementary Frameworks2 cards

Complete Flashcard Reference

Review every term in this set. Open any term to reveal its definition.

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

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.

Product vs service (ITIL v5 distinction)

A product combines an organization's resources to offer value. A service helps consumers achieve desired outcomes while the provider takes responsibility for specific costs and risks. A product can underpin several services; a sale or ownership transfer is not required for something to be a product.

Digital service vs digital product

A digital product combines resources based on digital technology to offer value. A digital service relies largely or entirely on digital products. A payroll platform is a digital product; the payroll service enabled by that platform is a digital service. Ownership transfer is a separate question about the offering.

Goods within a service offering

Goods are items supplied with ownership transferred to the consumer, such as equipment sold as part of an offering. Lending a company-owned laptop or granting platform access does not transfer ownership and is not, by itself, a transfer of goods.

Three components of a service offering

An offering can include goods, access to resources, and service actions in different combinations. Goods transfer ownership; access grants use under agreed terms; service actions are activities performed by a provider or jointly with a consumer, such as training or fulfilling an agreed request. Every offering need not include all three.

Utility vs warranty

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.

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

Value reflects benefits, usefulness, and importance perceived by stakeholders. Providers, consumers, and other stakeholders contribute to its co-creation through resources, use, relationships, and feedback. A provider cannot determine a consumer's value perception unilaterally, and the provider can also realize value from the relationship.

Service relationship and the three consumer-side roles

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.

Output vs outcome

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.

User experience (UX) vs customer experience (CX)

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.

The four dimensions of product and service management

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.

Organizations and people dimension focus

Culture, leadership, skills, roles, team structure, responsibilities, and communication. An AI rollout may fail because staff lack training or accountability is unclear even when the tool works. Review these human and organizational conditions alongside technology, suppliers, and workflows.

Partners and suppliers dimension focus

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, use this dimension to review the supplier relationship and commitments, while still checking the impact on the other three.

Information and technology dimension focus

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.

PESTLE external factors and the holistic approach

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.

Eight ITIL Product and Service Lifecycle activities (v5)

Discover, design, acquire, build, transition, operate, deliver, support. These eight activities form the Version 5 lifecycle/value chain. They can overlap, repeat, and run concurrently; the list is not a mandatory sequence or a simple one-to-one renaming of the six ITIL 4 activities.

Discover lifecycle activity

Discover continually aligns product roadmaps and related service offerings with consumer needs and organizational strategy. Research and feedback reveal needs and opportunities throughout the lifecycle, including after a product enters use.

Design lifecycle activity

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.

Acquire vs build

Acquire secures and allocates necessary resources for sustainable, scalable products and services; sources can be internal or external. Build develops, configures, integrates, and tests components. Acquisition is broader than purchasing, and building may involve partners rather than only internal staff.

Transition lifecycle activity

Transition introduces new or updated products into operational environments and manages supplier onboarding or offboarding. Readiness checks and controlled introduction reduce disruption. It can recur whenever a product changes, rather than occurring only once after build.

Operate vs deliver vs support

Operate maintains and monitors digital products and supporting systems for performance and reliability. Deliver provides services to users, manages user onboarding/offboarding, maintains service quality, and collects feedback. Support identifies and resolves incidents, carries out disaster recovery, and captures feedback. Their work overlaps but their purposes differ.

Seven ITIL guiding principles

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.

Focus on value

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.

Start where you are

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.

Progress iteratively with feedback

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.

Collaborate and promote visibility

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'.

Think and work holistically

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.

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

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.

Components of the ITIL Value System (v5)

Five components: guiding principles, governance, value chain, management practices, and continual improvement. Practice guides, operating models, metrics, and success factors help explain and apply these components; they are not extra Value System components.

Governance vs management

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.

How v5 changed the Service Value Chain from ITIL 4

The Version 5 lifecycle/value chain uses discover, design, acquire, build, transition, operate, deliver, and support. ITIL 4 used plan, improve, engage, design and transition, obtain/build, and deliver and support. Planning, improvement, and engagement remain necessary across Version 5; this is a model change, not their removal from everyday work.

Operating model (v5 term)

An operating model represents how an organization co-creates value with customers and other stakeholders and how it runs itself. It connects structures, capabilities, practices, technology, relationships, and value streams to strategy. It is a syllabus concept within value-chain coverage, not a sixth Value System component.

How value chain activities are used in practice

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.

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

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.

Release (ITIL term)

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.

Incident vs event

An event is a change of state significant to the management of a product, service, or configuration item. An incident is an unplanned interruption or reduction in service quality. Events can be informational, warnings, or exceptions; not every event is an incident.

Problem vs error vs known error

A problem is an actual or potential cause of incidents. An error is a flaw or vulnerability that may cause incidents. A known error is a problem that has been analyzed but remains unresolved. A workaround reduces impact while a complete resolution is unavailable; it is useful but not required for known-error status. These terms are not three mandatory sequential stages.

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

Continuous integration frequently combines and checks code changes. Continuous delivery keeps tested changes ready for deployment, which may require a decision; continuous deployment automatically deploys changes that pass the pipeline. SRE applies engineering to reliable operation. Observability uses system outputs, such as logs, metrics, and traces, to understand internal state.

Practice Guides and Practice Success Factors (PSFs)

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.

Seven continual improvement model steps

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.

Why 'What is the vision?' comes first

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.

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

'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.

Metric vs critical success factor (CSF)

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.

Core value stream vs enabling value stream

A core value stream directly provides products or services to consumers, who may be internal or external. An enabling value stream provides capabilities or resources that support other streams, such as recruiting the staff who deliver a service. Classify the stream by its purpose, rather than its automation level or whether it crosses a company boundary.

Value stream mapping vs value stream management

Value stream mapping visualizes activities, information flows, handoffs, work time, waits, and rework. Maps can describe current or future states and can be revised repeatedly. Value stream management uses that evidence continuously to coordinate and improve flow and outcomes. Mapping is a technique within management, not a once-only requirement.

Value stream map elements + why complexity thinking matters

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.

AI vs GenAI vs Agentic AI (ITIL v5)

AI supports tasks associated with human intelligence. GenAI creates content such as text, images, or code. Agentic AI plans and takes actions toward goals within constraints; it can use generative models. The ITIL AI Capability Model classifies AI functions to help match risks and controls to their use. It does not require organizations to advance through these AI types as maturity stages.

Purpose of AI governance in v5

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.

How ITIL and DevOps complement each other

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.

How ITIL and PRINCE2 complement each other

PRINCE2 provides roles, stages, and controls for finite projects. ITIL guides ongoing product and service management across the lifecycle. A project may develop, migrate, or improve a service while ITIL practices support its work; both approaches can apply during the same initiative. PRINCE2 project governance does not replace ongoing service management.

Strategy, mission, vision, and purpose

Purpose explains why an organization exists; mission describes what it does in pursuit of that purpose; vision describes its desired future. Strategy connects choices and actions to objectives. Business strategy addresses the organization overall, while digital strategy addresses how digital capabilities support or reshape that direction.

Change, transformation, and business as usual

Change alters something. Transformation significantly reshapes an organization or its capabilities toward a desired future state. Business as usual is its ongoing routine work and can still include incremental improvement. VUCA means volatility, uncertainty, complexity, and ambiguity; leadership helps people choose and adapt their direction in those conditions.

Service quality, service level, SLA, and experience level agreement

Service quality concerns how well a service meets needs and expectations. A service level describes measured or agreed service performance. An SLA documents services and agreed levels between provider and customer. An experience level agreement adds agreed experience outcomes and perceptions, complementing technical measures.

Digital product vendor vs service provider

A digital product vendor supplies digital products, while a service provider supplies services that enable consumer outcomes. A consumer uses services and can include customer, user, and sponsor roles. One organization may perform several roles; a vendor may also provide services based on its own or others' products.

Sustainability and value

Sustainability concerns meeting environmental, social, and economic requirements over time. A useful service must be assessed beyond short-term functionality: sourcing, energy use, working conditions, and long-term viability can affect value. These considerations complement utility, warranty, experience, outcomes, costs, and risks.

Frequently Asked Questions

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.

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.

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.

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%.

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

Version 5 certificates have a three-year renewal date. Renew through PeopleCert Plus with 20 CPD points each year for three consecutive years, by passing another ITIL certification, or by retaking the same certification before the renewal date.

Same family resources

Explore More ITIL Certifications

Continue into nearby exams from the same family. Each card keeps practice questions, study guides, flashcards, videos, and articles in one place.