CertPrepNow
PeopleCert / AXELOSITILFND V5Updated 2026-06-08

ITILFND V5 Study Guide

Everything you need to pass the ITIL Foundation (Version 5) exam. Structured study plans, key services, common traps, and practice questions.

You Can Pass This Exam For Free

The ITIL Foundation V5 exam is passable with free resources if you study consistently for 4-6 weeks and focus on understanding concepts rather than memorizing definitions:

  • AXELOS ITIL 5 overview and introductory materials on axelos.com (free registration)
  • PeopleCert official ITIL Foundation exam syllabus and sample questions (free download)
  • ITIL Foundation e-book preview chapters available through publisher previews (partial free access)
  • YouTube lectures on ITIL 4/5 foundations covering SVS, guiding principles, and service value chain
  • Quizlet flashcard decks for ITIL terminology and key definitions (free)
  • Free practice questions on this site

ITIL Foundation V5 is a conceptual exam, not a technical one. You do not need hands-on tool experience. However, the terminology is precise — outcome vs output, utility vs warranty, and the SVS components must be understood exactly as ITIL defines them, not how you might interpret them intuitively.

Choose Your Study Path

No prior ITIL or ITSM experience. You need to build a foundation of service management concepts before learning the ITIL 5 framework specifics.

Week 1Learn the foundational ITIL concepts: what a service is, the difference between products and services, value co-creation, and why service management exists. Understand utility (fit for purpose) and warranty (fit for use) as distinct concepts.
Week 2Study the Four Dimensions of Service Management: Organizations and People, Information and Technology, Partners and Suppliers, Value Streams and Processes. Understand why all four must be considered for any service or practice.
Week 3Master the ITIL Service Value System (SVS): its five components — guiding principles, governance, service value chain, practices, and continual improvement. Memorize all seven guiding principles and when each applies.
Week 4Deep dive into the Service Value Chain: the six activities (Plan, Improve, Engage, Design and Transition, Obtain/Build, Deliver and Support). Understand how they connect to form value streams, not a linear process.
Week 5Study the continual improvement model and its seven steps. Learn the product and service lifecycle: Discover, Design, Acquire, Build, Transition, Operate, Deliver, Support. Understand each lifecycle stage's purpose and how stages are often grouped in pairs.
Week 6Cover value stream mapping concepts: identifying value streams, flow-based thinking, measuring performance. Study ITIL and AI including the 6C AI Capability Model (Creation, Curation, Clarification, Cognition, Communication, Coordination), AI governance, and ITIL compatibility with DevOps/Agile/PRINCE2.
Week 7Review all key terminology with flashcards. Focus on commonly confused pairs: outcome/output, customer/user/sponsor, risk/issue, incident/problem/change.
Week 8Take full practice exams. Review all incorrect answers carefully — ITIL questions often hinge on precise definitions. Focus on the SVS (40% of exam) and key terms (30% of exam).

Exam Overview

Format

40 multiple-choice questions, 60 minutes. Proctored through PeopleCert online or authorized exam centers. Closed book.

Scoring

Percentage-based scoring. Passing: 65% (26 out of 40 correct). No penalty for wrong answers — always answer every question.

Domains & Weights

  • Key ITIL Terms and Definitions30%
  • The ITIL Service Value System40%
  • Four Dimensions of Product and Service Management10%
  • Product and Service Lifecycle10%
  • Value Stream Identification, Mapping, and Management5%
  • ITIL and Artificial Intelligence3%
  • ITIL and Other Frameworks2%

Registration

$690 USD. Available through PeopleCert at authorized test centers or via online proctoring. Exam fee is $690 USD. Register at peoplecert.org. No formal prerequisites, but training is strongly recommended.

Topic Priority Table

Not all topics are tested equally. Focus your study time on Tier 1 first, then Tier 2. Tier 3 topics rarely appear — just recognize what they do.

Tier 1: Must KnowYou must understand these concepts deeply and be able to apply them in scenario questions. These appear across multiple questions and are the foundation of the exam.
Tier 2: Should KnowUnderstand what these are and their key characteristics. Likely to appear in 2-4 questions each.
Tier 3: Recognize OnlyKnow what these are at a high level. Rarely more than 1-2 questions each.
Domain 130% of exam

Key ITIL Terms and Definitions

The largest terminology domain at 30%. Covers fundamental ITIL definitions including service, product, value, utility, warranty, outcome, output, stakeholder roles, risk, and newer concepts like experience management and XLAs. Questions test your ability to apply precise ITIL definitions in scenario contexts.

Key Topics

ServiceProductValueUtilityWarrantyOutcomeOutputCustomerUserSponsorRiskXLA

Must-Know Concepts

  • Service definition: a means of enabling value co-creation by facilitating outcomes customers want to achieve, without the customer having to manage specific costs and risks
  • Product: a configuration of an organization's resources designed to offer value for a consumer
  • Value: the perceived benefits, usefulness, and importance of something — co-created between provider and consumer
  • Utility (fit for purpose) vs warranty (fit for use) — both required for value creation
  • Outcome vs output — outcomes are results achieved; outputs are deliverables produced
  • Customer (defines requirements and is accountable for outcomes) vs user (uses the service) vs sponsor (authorizes funding)
  • Risk: a possible event causing harm or loss. Services help customers reduce the risks they face by transferring management responsibility
  • Cost: amount of money spent on a specific activity or resource. Services remove costs from customers' side while incurring costs of their own
  • Experience Level Agreements (XLAs): measure user experience and perceived value, complementing technical SLAs
  • Value co-creation: value emerges from the interaction between provider and consumer, not delivered unilaterally

Common Exam Traps

Do not define 'service' as just delivering IT capabilities — the full ITIL definition includes enabling outcomes while managing costs and risks for the customer
Utility is about WHAT the service does (functionality); warranty is about HOW WELL it performs (availability, capacity, security). Neither alone creates value
Output and outcome are almost always tested as a pair — an output (report) is not the same as the outcome it enables (better decision-making)
One person can hold multiple stakeholder roles simultaneously — a small business owner can be customer, user, and sponsor all at once
XLAs do not replace SLAs — they complement them. Both may apply to the same service
Quick Check: Key ITIL Terms and Definitions

Question 1 of 3

An organization deploys a new project management application for its teams. The application is available 99.9% of the time and meets all performance benchmarks. However, user satisfaction surveys show that employees find it difficult to use and it does not support how they actually work. Which ITIL concept does this scenario illustrate?

Domain 240% of exam

The ITIL Service Value System

The heaviest domain at 40%. Covers the SVS and all five of its components: guiding principles, governance, service value chain, practices, and continual improvement. You must know all seven guiding principles and when to apply them, all six service value chain activities, and the seven steps of the continual improvement model.

Key Topics

SVSGuiding PrinciplesGovernanceService Value ChainPracticesContinual Improvement

Must-Know Concepts

  • The SVS has exactly five components: guiding principles, governance, service value chain, practices, and continual improvement
  • All seven guiding principles: Focus on value, Start where you are, Progress iteratively with feedback, Collaborate and promote visibility, Think and work holistically, Keep it simple and practical, Optimize and automate
  • Guiding principles are universal and apply in any circumstances, to any stakeholder, at any level
  • The service value chain has six activities: Plan, Improve, Engage, Design and Transition, Obtain/Build, Deliver and Support
  • Service value chain activities are flexible and interconnected — they form value streams, not a fixed linear process
  • The continual improvement model has seven steps in order: vision → where are we now → where do we want to be → how do we get there → take action → did we get there → how do we keep momentum
  • Governance evaluates, directs, and monitors — it is separate from management
  • Practices are a set of organizational resources (people, processes, technology, information) designed to achieve an objective
  • The SVS inputs are opportunity and demand; the output is value

Common Exam Traps

There are five SVS components, not four or six. Practices is one component (not 'processes'); the service value chain is another (not all of ITIL)
The seven guiding principles are NOT rules or requirements — they are recommendations to be applied as relevant to each situation
Governance and management are NOT the same SVS component. Governance = oversight and direction; management = day-to-day execution
The service value chain is not a linear conveyor belt — every activity can connect to every other activity. Value streams are unique sequences built from these activities
The continual improvement model applies to all levels: services, practices, teams, individuals — not just major IT projects
Quick Check: The ITIL Service Value System

Question 1 of 3

An IT team is planning a service improvement initiative. A senior manager says 'We should completely redesign our support process from scratch.' A team member responds 'We have existing processes, tools, and data that still work — we should build on what we have.' Which guiding principle is the team member applying?

Domain 310% of exam

Four Dimensions of Product and Service Management

A 10% domain covering the four perspectives that must be considered for any service or practice: Organizations and People, Information and Technology, Partners and Suppliers, Value Streams and Processes. Questions test which dimension a scenario represents and the role of external PESTLE factors.

Key Topics

Organizations and PeopleInformation and TechnologyPartners and SuppliersValue Streams and ProcessesPESTLE

Must-Know Concepts

  • The four dimensions must ALL be considered for any service or practice — ignoring any one creates service failures
  • Organizations and People: team structures, culture, roles, competencies, responsibilities, and staffing
  • Information and Technology: data, knowledge, IT infrastructure, AI tools, communication systems, and emerging technologies
  • Partners and Suppliers: relationships with external organizations that contribute to service delivery — contracts, governance, ecosystems
  • Value Streams and Processes: specific activities and workflows that transform inputs into valuable outputs and outcomes
  • PESTLE factors (Political, Economic, Social, Technological, Legal, Environmental) are external constraints that sit outside the four dimensions and affect all of them
  • No dimension is more important than others — balance across all four is required

Common Exam Traps

The four dimensions are NOT SVS components — they are a separate framework for examining any service or practice from multiple angles
PESTLE is NOT a fifth dimension — it represents the external environment that constrains and influences all four dimensions
Partners and Suppliers includes third-party cloud providers, outsourcing partners, and software vendors — not just traditional procurement relationships
Quick Check: Four Dimensions of Product and Service Management

Question 1 of 3

An organization is deploying a new cloud-based CRM system. During planning, they realize they have not defined who will own data quality, who will train users, or how the team will be structured for ongoing support. Which dimension of service management have they neglected?

Domain 410% of exam

Product and Service Lifecycle

A 10% domain covering the eight lifecycle stages specific to ITIL 5: Discover, Design, Acquire, Build, Transition, Operate, Deliver, Support. These are often grouped in four pairs. Questions test which lifecycle stage corresponds to a given activity and how stages connect to the service value chain.

Key Topics

DiscoverDesignAcquireBuildTransitionOperateDeliverSupport

Must-Know Concepts

  • All eight lifecycle stages, often grouped in pairs: Discover and Design, Acquire and Build, Transition and Operate, Deliver and Support
  • Discover: identifying and prioritizing needs and opportunities, aligning with organizational strategy
  • Design: creating the service solution, architecture, and specifications to meet identified needs — designed to delight the user
  • Acquire: obtaining resources, third-party software, cloud infrastructure, or other components needed for the product or service
  • Build: developing, configuring, testing, and validating the service or product
  • Transition: managing the move from development to live environments, ensuring readiness
  • Operate: keeping services running day-to-day, managing the live environment
  • Deliver: the stage where value is realized as users actively consume the service
  • Support: restoring normal operations and resolving issues when things do not go as planned

Common Exam Traps

This 8-stage lifecycle is ITIL 5 specific — do not confuse it with the ITIL v3 lifecycle (Strategy/Design/Transition/Operation/CSI)
The lifecycle is iterative, not sequential — teams can move between activities based on what the work requires
Do not confuse these stages with non-ITIL terms like Develop, Deploy, Optimize, or Retire — the correct ITIL 5 terms are Acquire, Build, Transition, Operate
Quick Check: Product and Service Lifecycle

Question 1 of 3

An IT team is analyzing user feedback and performance metrics for a live customer portal to identify opportunities to reduce page load times and streamline user workflows. Which product and service lifecycle stage does this primarily represent?

Domain 55% of exam

Value Stream Identification, Mapping, and Management

A 5% domain covering value stream concepts: what a value stream is, flow-based thinking, how to map activities and information flows, and how to measure and optimize value stream performance. Questions test conceptual understanding rather than technical mapping techniques.

Key Topics

Value StreamFlow EfficiencyWaste IdentificationValue Stream MappingValue Stream Management

Must-Know Concepts

  • A value stream is a series of steps used to create and deliver a product or service to a consumer
  • Value streams are built from combinations of service value chain activities — they represent specific paths through the SVS for a given scenario
  • Flow-based thinking: optimizing the flow of work through a value stream to maximize efficiency and reduce waste
  • Value stream mapping: a one-time diagnostic visual technique for documenting the steps, information flows, and handoffs in a value stream
  • Value stream management: the ongoing daily practice of ensuring continuous workflow optimization — distinct from the one-time mapping exercise
  • Waste in value streams includes delays, handoffs, rework, and activities that do not add value for the customer
  • Measuring value stream performance: lead time (total time from request to value delivery), flow efficiency (value-adding time / total lead time)

Common Exam Traps

A value stream is not the same as the service value chain — the chain provides activities; a value stream is a specific sequence of those activities for a specific scenario
Value stream mapping identifies BOTH value-adding AND non-value-adding steps — the goal is to visualize the whole before optimizing
Quick Check: Value Stream Identification, Mapping, and Management

Question 1 of 3

An organization maps out all the steps required to fulfill a new employee onboarding request, from the initial HR submission through IT account creation, device provisioning, and first-day access. This exercise is an example of:

Domain 63% of exam

ITIL and Artificial Intelligence

A 2.5% domain covering how AI can be applied within ITIL-managed services, including the 6C AI Capability Model, AI governance, and responsible AI adoption. Questions are conceptual and test awareness of AI's role in service management.

Key Topics

6C AI Capability ModelAI GovernanceCreationCurationClarificationCognitionCommunicationCoordination

Must-Know Concepts

  • The 6C AI Capability Model classifies AI into six functions: Creation (generating content/code), Curation (improving data quality), Clarification (helping users understand complex information), Cognition (pattern detection and insights), Communication (chatbots and virtual assistants), Coordination (autonomous orchestration across systems)
  • Different 6C functions carry different risks and require different levels of human oversight
  • AI governance: responsible AI adoption requires oversight, transparency, accountability for AI outputs, and ethical considerations
  • AI does not replace ITIL practices — it enhances and accelerates them
  • AI can support monitoring, anomaly detection, predictive alerting, automated incident routing, and self-healing systems

Common Exam Traps

AI governance is NOT just about technology — it includes policies, accountability, escalation paths, and ethical use considerations
AI adoption in ITIL still requires human oversight — fully autonomous AI service management is not the ITIL recommendation
The 6C functions are distinct — do not confuse Creation (generating new content) with Curation (improving existing content quality)
Quick Check: ITIL and Artificial Intelligence

Question 1 of 3

An organization wants to use AI to automatically detect unusual patterns in service performance data and alert the operations team before users are impacted. Which function of the 6C AI Capability Model does this primarily represent?

Domain 72% of exam

ITIL and Other Frameworks

A 2.5% domain covering how ITIL 5 complements and integrates with other frameworks: DevOps, Agile, PRINCE2. Questions test awareness that ITIL is compatible with, not competing with, these frameworks.

Key Topics

DevOpsAgilePRINCE2Framework Integration

Must-Know Concepts

  • ITIL and DevOps are complementary: DevOps brings speed and automation; ITIL provides governance and service management structure
  • ITIL and Agile are compatible: ITIL's 'Progress iteratively with feedback' principle aligns with Agile values
  • ITIL and PRINCE2: PRINCE2 manages project delivery; ITIL manages the service once it is live — they cover different stages
  • No single framework covers everything — organizations should select complementary frameworks based on their context

Common Exam Traps

ITIL does not conflict with DevOps or Agile — ITIL 5 was designed with these in mind
PRINCE2 and ITIL are not alternatives — they address different activities (project vs service management)
Quick Check: ITIL and Other Frameworks

Question 1 of 3

A software development team uses Scrum for their delivery process and deploys updates to production every two weeks. The IT operations team applies ITIL practices to manage the live service and respond to incidents. Which statement best describes this approach?

Concepts You Must Not Confuse

These pairs appear on nearly every exam. Learn the difference and you'll avoid the most common traps.

Outcome vs Output

Use Outcome when…

The result achieved by a stakeholder through using a service — the actual change in state, capability, or condition. Outcomes are the reason services exist.

Use Output when…

A tangible or intangible deliverable produced by an activity or process. Outputs can be seen, counted, or measured directly.

Exam trap

A software deployment is an output. Improved employee productivity as a result is the outcome. ITIL questions frequently present both and ask which is which. Outputs enable outcomes — they are not the same thing.

Utility vs Warranty

Use Utility when…

Fit for purpose — the service does what the customer needs it to do. Utility describes the functionality that meets a particular need or removes a constraint.

Use Warranty when…

Fit for use — the service performs reliably when needed. Warranty ensures the service is available, has sufficient capacity, is secure, and maintains continuity.

Exam trap

A service must have BOTH utility AND warranty to create value. High utility with poor warranty (e.g., powerful software that crashes constantly) still fails customers. High warranty with no utility (e.g., a perfectly available service that does not meet any need) is equally useless.

Customer vs User

Use Customer when…

Defines service requirements, is responsible for the outcomes the service is meant to support, and represents the consuming organization. Often the person who funds or approves the service.

Use User when…

Uses the service in their day-to-day work. Does not define requirements or approve funding. Interacts with the service directly to get work done.

Exam trap

In a company where HR uses an IT payroll service: HR leadership (customer) defines requirements and owns outcomes; individual HR staff (users) run payroll each week. One person can be both, but the roles have distinct responsibilities.

Incident vs Problem

Use Incident when…

An unplanned interruption or reduction in the quality of a service. Incident management aims to restore normal service operation as quickly as possible.

Use Problem when…

A cause, or potential cause, of one or more incidents. Problem management aims to identify and eliminate root causes to prevent future incidents.

Exam trap

Resolving an incident (restoring service) does NOT eliminate the problem. A workaround restores service but the problem persists. Problem management is separate and longer-term. Incidents can be closed before problems are resolved.

Service Value System (SVS) vs Service Value Chain

Use Service Value System (SVS) when…

The complete model showing how all components (guiding principles, governance, service value chain, practices, continual improvement) work together to enable value creation. The SVS is the whole.

Use Service Value Chain when…

One component within the SVS. The six activities (Plan, Improve, Engage, Design and Transition, Obtain/Build, Deliver and Support) that convert demand and opportunity into value.

Exam trap

The service value chain is INSIDE the SVS — it is one of five SVS components. Questions that ask about the SVS should include all five components; questions about the service value chain should list the six activities.

Guiding Principles vs Governance

Use Guiding Principles when…

Universal recommendations that guide decisions and actions in any circumstance, at any level of the organization. They are not rules — they are guidance that should be considered and applied as relevant.

Use Governance when…

The means by which an organization is directed and controlled. Governance evaluates, directs, and monitors organizational activities to ensure accountability and alignment with objectives.

Exam trap

Guiding principles are bottom-up guidance that anyone can use. Governance is top-down oversight and control. Both are SVS components but serve completely different purposes.

SLA (Service Level Agreement) vs XLA (Experience Level Agreement)

Use SLA (Service Level Agreement) when…

A formal agreement between a service provider and customer documenting service targets for measurable technical metrics — availability percentage, response times, resolution times.

Use XLA (Experience Level Agreement) when…

A measure focused on user experience and perceived value — capturing user sentiment, satisfaction, and whether the service meets actual human needs beyond technical metrics.

Exam trap

An SLA can be met while users are still unhappy. XLAs capture what SLAs miss: the human experience of using the service. ITIL 5 introduces XLAs as an evolution of experience management.

Risk vs Issue

Use Risk when…

A possible event that could cause harm or loss, or make it harder to achieve objectives. Risk is about uncertainty and future potential impacts.

Use Issue when…

A problem that has already occurred and requires management attention. Issues are current, not hypothetical.

Exam trap

Risk = potential future event. Issue = something that has already happened. Services help customers reduce risk by taking on management of activities and their associated uncertainties.

Top Mistakes to Avoid

Confusing utility (fit for purpose) and warranty (fit for use) — both are required for value; a service lacking either fails customers
Treating output and outcome as synonyms — outputs are deliverables; outcomes are the results stakeholders achieve through using those deliverables
Listing 'processes' as an SVS component instead of 'practices' — ITIL 5 uses 'practices', which is a broader concept than processes
Confusing the SVS (the whole model, 5 components) with the service value chain (one component of the SVS, 6 activities)
Thinking governance is the same as management — governance provides oversight and sets direction; management handles day-to-day execution
Confusing the ITIL 5 product and service lifecycle (8 stages: Discover, Design, Acquire, Build, Transition, Operate, Deliver, Support) with the older ITIL v3 service lifecycle
Confusing customer (defines requirements, accountable for outcomes) and user (uses the service daily) — they are distinct roles with different responsibilities
Thinking guiding principles are mandatory rules — they are recommendations to be applied as relevant, not requirements
Assuming the service value chain activities must follow a fixed sequence — they can be combined in any order to form value streams
Not knowing all seven guiding principles by name — they are all equally testable

Exam-Ready Checklist

Know the precise ITIL definitions for service, product, value, utility, warranty, outcome, output, risk, and cost
Can distinguish customer, user, and sponsor roles with examples
Understand value co-creation: value emerges from provider-consumer interaction, not provider delivery
Know all five SVS components by name: guiding principles, governance, service value chain, practices, continual improvement
Can name all seven guiding principles and identify which applies to a given scenario
Know all six service value chain activities and understand they are NOT a linear sequence
Know all seven continual improvement model steps in order
Understand all four dimensions and which PESTLE factors influence them externally
Know all eight product and service lifecycle stages in their pairs: Discover and Design, Acquire and Build, Transition and Operate, Deliver and Support
Understand value stream mapping concepts: value streams vs service value chain, flow efficiency, waste identification
Know the 6C AI Capability Model: Creation, Curation, Clarification, Cognition, Communication, Coordination — and that each carries different governance requirements
Understand ITIL compatibility with DevOps, Agile, and PRINCE2
Know that SLAs measure technical performance while XLAs measure user experience
Scored 75%+ on at least two full mock exams (passing score is 65%). Aim for 80%+ for a comfortable margin

Recommended Resources

Free & Official Resources

Paid Courses & Practice Exams

These are recommended if you prefer a structured learning path. They can save time but are not required to pass.

Frequently Asked Questions