Career Employer

FREE ITIL 4 Foundation Study Guide 2026

The most important things the ITIL 4 Foundation exam tests — an interactive study guide with built-in quizzes and flashcards, organized to all 7 official syllabus learning outcomes.

Check sections to boost your score

Don't know where to start?

To find us again, just search “Career Employer ITIL 4 Foundation

By

This free ITIL 4 Foundation study guide walks through every learning outcome the ITIL 4 Foundation exam tests, organized to the current official PeopleCert/AXELOS candidate syllabus.[1]

It’s interactive, not a wall of text: every module has built-in checkpoint quizzes, flashcards, and practice questions, so you learn by doing — not just reading.

The exam has seven learning outcomes. We teach them in five study modules, leading with the foundations and finishing with the highest-weighted content — the ITIL practices, which alone are 24 of the 40 marks.

Read a module, test yourself at each checkpoint, then drill gaps with our free practice test and flashcards. This guide is a high-yield overview mapped to the official syllabus — not the full ITIL reference book.

ITIL 4 Foundation Exam Snapshot

ITIL 4 Foundation exam at a glance
DetailITIL 4 Foundation Exam
Questions40 multiple-choice (each worth 1 mark)
FormatObjective test questions — 4 options, 1 selected; no negative marking
Time60 minutes (75 minutes for non-native-language candidates)
Passing score26 of 40 correct (65%)
ConditionsClosed book
Certifying bodyPeopleCert (ITIL owner; AXELOS is the prior steward)
EligibilityNone — entry-level foundation qualification
RecertificationRenew every 3 years (retake, higher qualification, or CPD)
LevelFoundation (ITIL 4 edition)

The exam is weighted heavily toward the ITIL practices. Understanding seven practices in detail is worth 17 marks, and knowing the purpose and key terms of 15 practices adds 7 more — together 24 of 40 marks (60%).[1] Study by weight:

ITIL 4 Foundation weighting by learning outcome (official syllabus, marks out of 40)
Understand 7 practices in detail43% · LO7 · 17 marks
Purpose & key terms of 15 practices18% · LO6 · 7 marks
The 7 guiding principles15% · LO2 · 6 marks
Key concepts of service management13% · LO1 · 5 marks
The four dimensions5% · LO3 · 2 marks
The service value chain5% · LO5 · 2 marks
The service value system3% · LO4 · 1 mark

Module 1 · Key Concepts of Service Management

Learning outcome 1, 5 marks. Everything in ITIL 4 rests on a handful of definitions. Get these exactly right — the exam will test the precise wording of , , , and the difference between an and an .

1.1 Service, Value & Value Co-creation

A is “a means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.” The phrase to internalize is “without having to manage specific costs and risks” — the provider takes those on so the consumer can focus on what it actually wants.[1]

is “the perceived benefits, usefulness, and importance of something.” Two words in that definition matter: perceived(value is subjective — it depends on the stakeholder’s viewpoint) and the idea of . ITIL 4 rejects the old model of a provider “delivering” value one-way; instead, value emerges from active collaboration between provider and consumer.

Service, value & co-creation — exact ITIL 4 definitions
TermDefinition
ServiceA means of enabling value co-creation by facilitating outcomes customers want, without them managing specific costs and risks
Service managementA set of specialized organizational capabilities for enabling value for customers in the form of services
ValueThe perceived benefits, usefulness, and importance of something — subjective and co-created
OrganizationA person or group with its own functions, responsibilities, authorities, and relationships to achieve objectives

1.2 Utility, Warranty, Cost, Risk, Output & Outcome

Two concepts together decide whether a service is valuable. is “fit for purpose” — what the service does (it supports performance or removes a constraint).

is “fit for use” — how well it performs, covering availability, capacity, security, and continuity. A service needs both: great functionality that’s always down has no value, and rock-solid uptime for the wrong feature has no value either.

and each come in two flavours: those a service removes from the consumer (part of the value it provides) and those it imposes on the consumer (a trade-off to weigh against the value). Finally, do not confuse an (a deliverable, like a report) with an (the result the stakeholder wants, enabled by outputs, like a faster decision).

Utility vs warranty
UtilityWarranty
Plain EnglishFit for purposeFit for use
Question it answersWhat does the service do?How well does it perform?
CoversFunctionality that supports performance or removes a constraintAvailability, capacity, security, continuity
Needed for value?Yes — both are requiredYes — both are required
Cost, risk, output & outcome
TermDefinitionWatch out for
CostMoney spent on an activity or resourceA service can REMOVE or IMPOSE costs
RiskA possible event causing harm/loss or hindering objectivesA service can REMOVE or IMPOSE risks
OutputA tangible/intangible deliverable of an activityThe deliverable (e.g., a report)
OutcomeA result for a stakeholder enabled by outputsThe result (e.g., a faster decision)

1.3 Service Relationships & Roles

A is a description of one or more services for a target group, made of three things: goods (ownership transfers to the consumer), access to resources (granted under agreed terms), and service actions (performed by the provider). A is the cooperation between provider and consumer, and it has three parts: , , and .

The is a generic role that splits into three: the defines requirements and owns the outcomes, the uses the service, and the authorizes the budget. One person or organization can hold more than one of these roles at once.

The three service-consumer roles
RoleWhat they do
CustomerDefines the requirements for a service and owns the outcomes of consumption
UserUses the service
SponsorAuthorizes the budget for service consumption
The three components of a service relationship
ComponentWhat it covers
Service provisionProvider activities: managing resources, granting access, fulfilling actions, managing service levels
Service consumptionConsumer activities: using resources, requesting/performing service actions, receiving goods
Service relationship managementJoint activities to ensure continual value co-creation

Checkpoint · Key Concepts of Service Management

Question 1 of 10

In ITIL 4, what is the central reason a service is described as relieving the consumer of the need to manage certain costs and risks?

Module 2 · The Four Dimensions of Service Management

Learning outcome 3, 2 marks. A small slice of the exam, but a foundational idea: every service must balance four dimensions, all surrounded by external . Neglect any one dimension and the service suffers.

2.1 The Four Dimensions

The are the four perspectives you must consider for every product and service so it stays effective and balanced. They apply across the whole service value system, not just to one service.[1]

The four dimensions of service management
DimensionWhat it covers
Organizations & peopleStructures, roles, responsibilities, culture, skills, and competencies
Information & technologyThe information and knowledge needed, plus the technologies used to deliver services
Partners & suppliersRelationships with other organizations involved in the services
Value streams & processesHow the parts of the organization work together to enable value

2.2 External (PESTLE) Factors

The four dimensions sit inside a set of external factors the organization cannot fully control — captured by the acronym PESTLE: Political, Economic, Social, Technological, Legal, and Environmental. These factors act on every dimension and must be considered when designing and managing services.

PESTLE — the external factors
FactorExample influence on services
PoliticalGovernment policy, trade rules, public-sector mandates
EconomicBudgets, exchange rates, market conditions
SocialWorkforce expectations, demographics, customer behaviour
TechnologicalNew platforms (cloud, AI), obsolescence, automation
LegalData-protection law, contracts, compliance requirements
EnvironmentalSustainability targets, energy use, regulations

Checkpoint · The Four Dimensions

Question 1 of 8

Beyond formal reporting lines and job titles, the organizations and people dimension of service management is concerned with the more intangible aspects of how a workforce operates. Which of the following is included within this dimension?

Module 3 · The Seven Guiding Principles

Learning outcome 2, 6 marks. A is “a recommendation that guides an organization in all circumstances, regardless of changes in goals, strategies, type of work, or management structure.” They are universal and enduring. Expect a question on each principle, so know all seven by name and what each one means.[1]

3.1 The Seven Principles

The seven ITIL guiding principles
PrincipleIn one line
Focus on valueEverything maps, directly or indirectly, to value for a stakeholder
Start where you areAssess and reuse what already exists — don't start from scratch
Progress iteratively with feedbackWork in small iterations and use feedback to stay relevant
Collaborate and promote visibilityWork across boundaries with transparency to build buy-in
Think and work holisticallyNo part stands alone — coordinate the whole system end to end
Keep it simple and practicalUse the fewest steps; remove anything that adds no value
Optimize and automateOptimize the work first, then automate — never automate waste

3.2 Applying the Principles Together

The principles are not a menu to pick one from — an organization should consider how all of them apply to a situation, and how they interact. They reinforce each other: keeping it simple supports optimization; collaborating supports visibility; thinking holistically keeps iterations aligned to value.

Checkpoint · The Seven Guiding Principles

Question 1 of 10

In ITIL 4, what best describes the nature of a guiding principle?

Module 4 · The SVS & Service Value Chain

Learning outcomes 4 and 5, 3 marks combined. This is the big-picture model: how everything in ITIL fits together to turn demand into value. Two pieces — the (the whole) and the (its operating model).

4.1 The Service Value System (SVS)

The describes how all the components and activities of an organization work together as a system to enable value creation. Its input is opportunity and demand, and its output is value.[1] It has five components: , , the , , and .

The service value system — inputs, components, output
ElementDetail
InputOpportunity & demand
OutputValue
Component — Guiding principlesRecommendations that guide the organization in all circumstances
Component — GovernanceThe means by which the organization is directed and controlled
Component — Service value chainThe operating model: six interconnected value-creating activities
Component — PracticesThe 34 sets of organizational resources for performing work
Component — Continual improvementRecurring activity at all levels to keep performance aligned with needs

4.2 The Service Value Chain (6 Activities)

The is the central operating model of the SVS — a set of six interconnected activities that an organization performs to create value. The six are: plan, improve, engage, design & transition, obtain/build, and deliver & support. Crucially, they are not a fixed sequence — they combine in different orders to form for different scenarios.

The six service value chain activities
ActivityPurpose
PlanA shared understanding of vision, status, and improvement direction across all four dimensions
ImproveContinual improvement of products, services, and practices across all activities
EngageUnderstand stakeholder needs; ensure transparency and continual engagement
Design & transitionEnsure products/services meet expectations for quality, cost, and time to market
Obtain/buildEnsure service components are available where/when needed and meet specifications
Deliver & supportEnsure services are delivered and supported to agreed specifications and expectations

Checkpoint · The SVS & Service Value Chain

Question 1 of 10

An architect is mapping how work enters and leaves the ITIL 4 service value system (SVS). She needs to label the two inputs that trigger the system and the single result the system is designed to produce. Which labeling correctly reflects the SVS model?

Module 5 · Key ITIL Practices

Learning outcomes 6 and 7 — 24 of 40 marks, the heart of the exam. A is “a set of organizational resources designed for performing work or accomplishing an objective.” ITIL 4 defines 34 practices in three categories. You must know the purpose of 15 of them, and understand 7 in detail.[1]

5.1 The 34 Practices & the Foundation Split

The 34 practices fall into three groups: 14 general management practices (adopted from general business), 17 service management practices (developed in service management), and 3 technical management practices (adapted from technology management) — 14 + 17 + 3 = 34.

For Foundation, two learning outcomes carve the practices into a manageable set. LO6 asks you to recall the purpose of 15 practices (5 marks), plus the definitions of 7 key terms (2 marks).

LO7 asks you to understand 7 practices in detail (17 marks). Critically, the 7 deep-dive practices are part of the 15 — it is not 15 + 7 = 22. So 8 practices are purpose-only, and 7 are both purpose and detail.

The Foundation practice split (LO6 + LO7)
GroupPractices
Understand in detail (LO7, 17 marks)Continual improvement; change enablement; incident management; problem management; service request management; service desk; service level management
Purpose only (the other 8 of the 15, LO6)Information security mgmt; relationship mgmt; supplier mgmt; IT asset mgmt; monitoring & event mgmt; release mgmt; service configuration mgmt; deployment mgmt
Key terms to define (LO6.2, 2 marks)IT asset; event; configuration item; change; incident; problem; known error

5.2 The 7 Deep-Dive Practices

These seven are worth 17 marks — spend your time here. Learn each practice’s purpose and its key terms and distinctions.

minimizes the negative impact of incidents by restoring normal service as fast as possible. An is an unplanned interruption or quality reduction. reduces the likelihood and impact of incidents by tackling their causes: a is a cause (or potential cause) of incidents, a is an analyzed-but-unresolved problem, and a reduces impact while a permanent fix is pending.

Incident vs problem vs service request
ConceptDefinitionHandled by
IncidentUnplanned interruption or quality reductionIncident management — restore fast
ProblemA cause, or potential cause, of incidentsProblem management — find root cause
Known errorA problem analyzed but not resolvedProblem management — error control
Service requestA predefined, agreed, user-initiated requestService request management

handles predefined, agreed (a normal part of delivery, not a disruption) — so they should be standardized and automated. maximizes successful changes by assessing risk and authorizing them; a has three types: (low-risk, pre-authorized), (scheduled and authorized), and (done ASAP). ITIL 4 de-emphasizes a single change advisory board in favour of appropriate change authorities.

The three types of change
TypeHow it's handled
Standard changeLow-risk, pre-authorized, well understood — no extra authorization needed
Normal changeScheduled, assessed, and authorized through a process
Emergency changeMust be implemented as soon as possible; assessment expedited

captures demand for incident resolution and service requests; it is the single point of contact for users and shapes their experience. sets clear, business-based targets so delivery can be measured against a (SLA). Good SLAs are agreed, simply written, and use outcome-based metrics— relying on a single technical metric risks the “watermelon” effect (green outside, red inside).

The seven deep-dive practices and their purpose
PracticePurpose (one line)
Continual improvementKeep practices and services aligned with changing needs (general management practice)
Change enablementMaximize successful changes by assessing risk and authorizing them
Incident managementMinimize incident impact by restoring normal service quickly
Problem managementReduce likelihood/impact of incidents by managing causes and known errors
Service request managementHandle predefined, user-initiated requests effectively
Service deskCapture demand for incidents and requests; single point of contact
Service level managementSet and manage clear, business-based service targets

5.3 Continual Improvement & Key Terms

is a general management practice (and an SVS component) that keeps services and practices aligned with changing needs. It uses the seven-step , and improvement is treated as everyone’s responsibility. Improvement ideas are captured in a continual improvement register (CIR).

Finally, LO6.2 asks you to recall the definitions of seven key ITIL terms. Several you already met above — here they are together for the exam.

The seven key ITIL terms to define (LO6.2)
TermDefinition
IT assetAny financially valuable component that can contribute to delivering an IT product or service
EventAny change of state that has significance for the management of a service or CI
Configuration item (CI)Any component that needs to be managed to deliver an IT service
ChangeThe addition, modification, or removal of anything that could affect services
IncidentAn unplanned interruption to a service, or reduction in its quality
ProblemA cause, or potential cause, of one or more incidents
Known errorA problem that has been analyzed but not resolved

Checkpoint · Key ITIL Practices

Question 1 of 10

An IT manager wants the single ITIL 4 practice whose purpose is to keep the organization's information confidential, intact, and available for the business to operate. Which practice should the manager point to?

How to Use This ITIL 4 Foundation Study Guide

This guide is built to be worked, not just read. The most efficient path to a pass:

  • Study by weight. The practices module (Module 5) is 24 of 40 marks — spend the most time there, especially the seven deep-dive practices. Then the guiding principles and key concepts.
  • Check off as you go. Use the Study Guide Contents to mark each section done; it raises your exam-readiness score.
  • Take every checkpoint. The end-of-module quizzes show you exactly which areas need another pass.
  • Drill the weak area. Send your weak spot into the flashcards and a practice test until the score climbs.
  • Memorize the definitions. Much of LO1 and LO6 is recall (Bloom’s level 1) — exact wording wins marks.

ITIL 4 Foundation Concept Questions

Common ITIL concepts candidates search while studying for the Foundation exam — each answered briefly and backed by the official syllabus. Test yourself, then drill them as flashcards.

ITIL 4 Foundation Glossary

The high-yield ITIL 4 terms in one place — hover any dotted term in the guide, or flip the whole deck here as a self-grading flashcard set.

Change
The addition, modification, or removal of anything that could have a direct or indirect effect on services.
Change enablement
The practice that maximizes successful service and product changes by ensuring risks are assessed, changes authorized, and the schedule managed.
Configuration item
Any component that needs to be managed in order to deliver an IT service.
Continual improvement
A recurring organizational activity performed at all levels to ensure performance continually meets stakeholder expectations.
Continual improvement model
A seven-step model for structuring improvement, from 'What is the vision?' through 'How do we keep the momentum going?'
Cost
The amount of money spent on a specific activity or resource. A service can remove costs from, or impose costs on, the consumer.
Customer
A person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.
Deployment management
The technical practice that moves new or changed components into live (or other) environments.
Emergency change
A change that must be implemented as soon as possible, often with expedited assessment.
Event
Any change of state that has significance for the management of a service or other configuration item.
Four dimensions of service management
Organizations and people; information and technology; partners and suppliers; and value streams and processes — all of which must be balanced for any service.
Governance
The means by which an organization is directed and controlled — evaluating, directing, and monitoring activities and performance.
Guiding principle
A recommendation that guides an organization in all circumstances, regardless of changes in goals, strategies, type of work, or management structure.
Incident
An unplanned interruption to a service, or a reduction in the quality of a service.
Incident management
The practice that minimizes the negative impact of incidents by restoring normal service operation as quickly as possible.
Information security management
The practice that protects the information needed to conduct business — its confidentiality, integrity, and availability.
IT asset
Any financially valuable component that can contribute to the delivery of an IT product or service.
IT asset management
The practice that plans and manages the full lifecycle of all IT assets to maximize value and control cost and risk.
Known error
A problem that has been analyzed but has not been resolved.
Monitoring and event management
The practice that observes services and CIs and records and reports significant changes of state (events).
Normal change
A change that must be scheduled, assessed, and authorized following a standard process.
Organization
A person or a group of people that has its own functions with responsibilities, authorities, and relationships to achieve its objectives.
Outcome
A result for a stakeholder enabled by one or more outputs (for example, a faster decision).
Output
A tangible or intangible deliverable of an activity (for example, a report).
PESTLE factors
External factors — political, economic, social, technological, legal, and environmental — that constrain or influence all four dimensions.
Practice
A set of organizational resources designed for performing work or accomplishing an objective; ITIL 4 defines 34 management practices.
Problem
A cause, or potential cause, of one or more incidents.
Problem management
The practice that reduces the likelihood and impact of incidents by identifying causes and managing workarounds and known errors.
Relationship management
The practice that establishes and nurtures the links between the organization and its stakeholders.
Release management
The practice that makes new and changed services and features available for use.
Risk
A possible event that could cause harm or loss, or make it more difficult to achieve objectives. A service can remove or impose risks.
Service
A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.
Service configuration management
The practice that ensures accurate, reliable information about the configuration of services and their CIs is available when needed.
Service consumer
A generic role for the organization that receives services, covering the roles of customer, user, and sponsor.
Service consumption
Activities performed by an organization to consume services — using resources, performing service actions, and receiving goods.
Service desk
The practice that captures demand for incident resolution and service requests; the single point of contact for users.
Service level agreement
A documented agreement between a provider and a customer identifying the services required and the expected level of service.
Service level management
The practice that sets clear, business-based targets for service performance so delivery can be assessed and managed.
Service management
A set of specialized organizational capabilities for enabling value for customers in the form of services.
Service offering
A description of one or more services designed for a target consumer group, made up of goods, access to resources, and service actions.
Service provider
A role an organization takes when it provides services to consumers.
Service provision
Activities performed by an organization to provide services — managing resources, providing access, fulfilling actions, and managing service levels.
Service relationship
A cooperation between a service provider and a service consumer, including service provision, service consumption, and service relationship management.
Service relationship management
Joint activities by a provider and consumer to ensure continual value co-creation based on agreed service offerings.
Service request
A request from a user that initiates a service action agreed as a normal part of service delivery.
Service request management
The practice that handles all predefined, user-initiated service requests effectively and in a user-friendly way.
Service value chain
The operating model within the SVS: six interconnected activities (plan, improve, engage, design & transition, obtain/build, deliver & support) that create value.
Service value system
ITIL's model showing how all the components and activities of an organization work together as a system to enable value creation.
Sponsor
A person who authorizes the budget for service consumption.
Standard change
A low-risk, pre-authorized change that is well understood and documented and can be implemented without additional authorization.
Supplier management
The practice that ensures suppliers and their performance are managed appropriately to support quality services.
User
A person who uses a service.
Utility
The functionality offered by a product or service to meet a particular need — 'fit for purpose,' or what the service does.
Value
The perceived benefits, usefulness, and importance of something; value is subjective and co-created by the provider and the consumer.
Value co-creation
The idea that value emerges through active collaboration between providers, consumers, and other stakeholders — not delivered one-directionally.
Value stream
A series of steps an organization undertakes to create and deliver products and services to a consumer; a specific combination of value chain activities and practices.
Warranty
Assurance that a product or service will meet agreed requirements — 'fit for use,' covering availability, capacity, security, and continuity.
Workaround
A solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available.

ITIL 4 Foundation Study Guide FAQ

The ITIL 4 Foundation exam has 40 multiple-choice questions, each worth 1 mark, and you get 60 minutes. There is no negative marking. Candidates taking the exam in a non-native language may be granted 25% extra time (75 minutes total).

References

  1. 1.AXELOS. “ITIL 4 Foundation Candidate Syllabus.” axelos.com.
  2. 2.PeopleCert. “ITIL 4 Foundation — Certification.” peoplecert.org.
  3. 3.PeopleCert. “Renew Your Certifications (Recertification Policy).” peoplecert.org.
  4. 4.AXELOS. “ITIL Glossary of Terms and Definitions.” axelos.com.
Career Employer

Career Employer is the ultimate resource to help you get started working the job of your dreams. We cover topics from general career information, career searching, exam preparation with free study materials, career interviewing, and becoming successful in your career of choice.

Follow Us:

All Posts

Career Employer’s Editorial Process

Here at Career Employer, we focus a lot on providing factually accurate information that is always up to date. We strive to provide correct information using strict editorial processes, article editing, and fact-checking for all of the information found on our website. We only utilize trustworthy and relevant resources. To find out more, make sure to read our full editorial process page here.