Explore / Project & Service Management
ITIL 4 Foundation Exam Prep

Learn every ITIL 4 Foundation idea from scratch, with everyday examples and original practice questions in the exam's four styles, weighted the way the 40-question, 60-minute, closed-book exam is (26 to pass). It is independent of PeopleCert, not accredited and promises no pass; the syllabus, offici
Expert · 40 levels · 4 free · Created Oct 2026 · Professionally curated by levelupwith.com
What's inside
- Level 1: The Exam, the Rules and What a Service IsFree
[Key concepts of service management] Sets out the exam facts and this course's independence from PeopleCert, then defines service and service management from first principles.- State the exam format (40 questions, 60 minutes, closed book, 26 correct to pass), that ITIL 4 exams are planned to run until 31 December 2027, and that ITIL (Version 5) now exists
- Explain that ITIL, its syllabus and the official book belong to PeopleCert, are not attached or reproduced here and are obtained from peoplecert.org, and that this course is independent, not accredited and promises no pass
- Define service and service management in your own words using an everyday example such as a taxi ride or a laundry
- Level 2: Organization, Customer, User and SponsorFree
[Key concepts of service management] Explains what ITIL means by an organization and separates the three service consumer roles of customer, user and sponsor.- Define organization, service provider and service consumer
- Tell customer (defines requirements and owns the outcomes), user (uses the service) and sponsor (authorises the budget) apart in a short scenario
- Recognise that one person can hold more than one of these roles at once
- Level 3: Value, Outcome, Output, Cost and RiskFree account
[Key concepts of service management] Teaches how a service creates value by helping with outcomes while taking some costs and risks away from the consumer and introducing others.- Define value, output, outcome, cost and risk and give an everyday example of each
- Distinguish an output (a deliverable) from an outcome (a result for a stakeholder)
- Explain how a service both removes and imposes costs and risks for the consumer, and why value is co-created
- Level 4: Utility and WarrantyFree account
[Key concepts of service management] Shows that a service must be both fit for purpose and fit for use before it can create value.- Define utility as what the service does (fit for purpose) and warranty as how it performs (fit for use)
- Sort requirements such as availability, capacity, security and continuity under warranty and functional requirements under utility
- Explain why utility without warranty, or warranty without utility, fails to deliver value
- Level 5: Service Offerings and Service Relationships
[Key concepts of service management] Explains what a service offering contains and how provider and consumer work together through provision, consumption and relationship management.- Describe the three components a service offering may include: goods, access to resources and service actions
- Define service provision, service consumption and service relationship management and say who performs each
- Answer standard, negative, missing word and list style questions on the key concepts
- Level 6: Focus on Value
[The seven guiding principles] Introduces what a guiding principle is, names all seven, and teaches the first: everything the organization does should link back to value for stakeholders.- Explain what a guiding principle is and why the seven apply in any situation
- Describe focus on value, including knowing who the service consumer is and how they see value
- Explain how customer experience and user experience relate to this principle
- Level 7: Start Where You Are
[The seven guiding principles] Teaches that existing services, processes and people should be assessed and reused before anything new is built.- Explain why you observe the current state directly rather than relying on assumptions or reports
- Describe the proper role of measurement and the risk that measuring changes behaviour
- Recognise a scenario in which this principle is the best answer
- Level 8: Progress Iteratively with Feedback
[The seven guiding principles] Teaches working in small, manageable pieces and using feedback before, during and after each one.- Explain why work is split into smaller sections that can be delivered and judged sooner
- Describe how feedback loops keep each iteration aimed at value
- Explain the idea of a minimum viable product in everyday terms
- Level 9: Collaborate and Promote Visibility
[The seven guiding principles] Teaches working across boundaries with the right stakeholders and making work and its progress visible.- Identify the stakeholder groups worth collaborating with and why involvement beats isolation
- Explain what goes wrong when work is hidden and how visibility supports good decisions
- Explain that collaboration does not mean seeking everyone's agreement on everything
- Level 10: Think and Work Holistically
[The seven guiding principles] Teaches that no service, practice or team stands alone, so results depend on treating the whole as an integrated system.- Explain why improving one part in isolation can harm the overall result
- Relate this principle to end-to-end delivery of value
- Distinguish this principle from collaborate and promote visibility in exam scenarios
- Level 11: Simple, Optimize, Automate and How Principles Interact
[The seven guiding principles] Teaches keep it simple and practical and optimize and automate, then shows how all seven principles are weighed together in a scenario.- Apply keep it simple and practical by removing steps that add no value and using outcome-based thinking
- Explain why work is optimized before it is automated and where human intervention should remain
- Choose the most relevant principle for a scenario and explain how the principles interact
- Level 12: Dimensions: Organizations, People, Information, Technology
[The four dimensions of service management] Introduces the four dimensions as perspectives every service needs and teaches the first two: organizations and people, and information and technology.- Explain why all four dimensions must be considered for every service and what happens when one is neglected
- Describe what organizations and people covers, including roles, responsibilities, culture, skills and structures
- Describe what information and technology covers, including the information and knowledge and the technologies needed to manage services
- Level 13: Dimensions: Partners, Suppliers, Value Streams, Processes
[The four dimensions of service management] Teaches the remaining two dimensions and the external factors that influence all four.- Describe partners and suppliers as the organization's relationships with other organizations involved in its services
- Define value stream and process and tell the two apart
- Place a scenario detail in the correct one of the four dimensions and recognise that external factors act on them all
- Level 14: The Service Value System
[The ITIL service value system] Explains how the components of the service value system work together to turn opportunity and demand into value.- State the purpose of the service value system and its inputs (opportunity and demand) and output (value)
- Name its five components: guiding principles, governance, service value chain, practices and continual improvement
- Explain how working as one system helps to avoid organizational silos
- Level 15: The Service Value Chain: Plan, Improve, Engage
[The service value chain] Introduces the service value chain as six interconnected activities and teaches the purpose of plan, improve and engage.- Explain that the six activities are not a fixed sequence and are combined into value streams
- State the purpose of plan, of improve and of engage
- Match a short description of work to plan, improve or engage
- Level 16: Value Chain: Design, Obtain/Build, Deliver and Support
[The service value chain] Teaches the purpose of design and transition, obtain/build, and deliver and support, and how all six activities connect through inputs and outputs.- State the purpose of design and transition, of obtain/build and of deliver and support
- Explain how the output of one activity becomes the input of another
- Trace an everyday request through several value chain activities as a value stream
- Level 17: Practice Purposes: Security, Relationships, Suppliers
[Purpose and key terms of 15 ITIL practices] Explains what a practice is, then teaches the purpose of information security management, relationship management and supplier management.- Define a practice as a set of organizational resources designed for performing work or accomplishing an objective
- State in your own words the purpose of information security management, relationship management and supplier management
- Tell relationship management (links with stakeholders) from supplier management (suppliers and their performance) in exam questions
- Level 18: IT Asset and Configuration Item
[Purpose and key terms of 15 ITIL practices] Teaches the purpose of IT asset management and service configuration management and the two terms that are easily confused.- Define IT asset as any financially valuable component and configuration item as any component that needs to be managed to deliver an IT service
- State the purpose of IT asset management and of service configuration management
- Decide which of the two practices a scenario describes, for example a cost and lifecycle focus versus a focus on relationships between components
- Level 19: Event and Monitoring and Event Management
[Purpose and key terms of 15 ITIL practices] Teaches what an event is and the purpose of the monitoring and event management practice.- Define event as a change of state that has significance for the management of a service or configuration item
- State the purpose of monitoring and event management in your own words
- Recognise that not every event is an incident and that events differ in significance
- Level 20: Release Management versus Deployment Management
[Purpose and key terms of 15 ITIL practices] Teaches the purposes of release management and deployment management and how to tell them apart.- State the purpose of release management: making new and changed services and features available for use
- State the purpose of deployment management: moving new or changed hardware, software or other components to live environments
- Explain with an everyday example how a component can be deployed without yet being released to users
- Level 21: Incident, Problem and Known Error: Purposes and Terms
[6 Purpose of 15 practices and key terms] Learn the purpose of incident management and of problem management, and the exact meaning of the terms incident, problem and known error, using an everyday example of a broken office printer.- Recall the purpose of incident management and the purpose of problem management in your own words
- Define incident, problem and known error and classify short examples as one of the three
- Answer standard and missing word recognition questions that swap the terms incident and problem
- Level 22: Purposes: Service Request, Service Desk, Service Level
[6 Purpose of 15 practices and key terms] Learn the purpose of service request management, the service desk and service level management, and what each one is there to achieve at a recognition level.- Recall the purpose of service request management, the service desk and service level management
- Match a one-line purpose statement to the correct one of these three practices
- Tell a service request from an incident in a simple everyday example
- Level 23: Purpose Recall Drill: The Confusable Pairs
[6 Purpose of 15 practices and key terms] Consolidate the purposes of all 15 examinable practices and the seven key terms by drilling the pairs the exam likes to swap, such as release versus deployment, IT asset versus configuration item, and relationship versus supplier management.- Match all 15 practices to their purposes without notes
- Separate the commonly confused pairs: release and deployment management, IT asset management and service configuration management, relationship and supplier management, event and incident
- Explain why each wrong option in a purpose question belongs to a different practice or term
- Level 24: Continual Improvement: Scope, Ownership and the Register
[7 Seven practices in detail] Study the continual improvement practice in depth: what it covers, why improvement is everyone's responsibility, the range of methods it can draw on, and how a continual improvement register (CIR) records and prioritises ideas.- Explain what the continual improvement practice aligns and improves, and who is responsible for it
- Describe what a continual improvement register is used for and how ideas in it are logged, prioritised and tracked
- Explain why an organization should pick a small number of improvement methods rather than adopt many at once
- Level 25: The Continual Improvement Model: Seven Steps
[7 Seven practices in detail] Learn the seven steps of the continual improvement model in order, from 'What is the vision?' to 'How do we keep the momentum going?', and what happens at each step.- List the seven steps of the continual improvement model in the correct order
- Match an activity, such as a baseline assessment or setting measurable targets, to the step where it belongs
- Explain why the model is iterative and why skipping a step weakens an improvement
- Level 26: Change Enablement: Scope, Risk and Change Authority
[7 Seven practices in detail] Study change enablement in depth: the definition of a change, how the practice balances the benefit of changes against protecting live services, how it differs from organizational change management, and the role of a change authority.- Explain how change enablement maximises successful changes through risk assessment, authorization and scheduling
- Distinguish change enablement, which covers products and services, from organizational change management, which covers the people side
- Describe what a change authority is and why the right authority is assigned to each type of change
- Level 27: Standard, Normal and Emergency Changes
[7 Seven practices in detail] Learn the three types of change and how each is assessed and authorized, from pre-authorized standard changes to expedited emergency changes.- Define standard, normal and emergency changes and give an everyday example of each
- Explain how assessment and authorization differ between the three types
- Classify a described change in a scenario question as standard, normal or emergency and justify the choice
- Level 28: The Change Schedule and Change Enablement Scenarios
[7 Seven practices in detail] Learn what the change schedule is for, how it helps to plan changes, avoid conflicts and communicate, and apply the whole change enablement practice to negative and list style questions.- Explain how the change schedule is used to plan changes, assist communication, avoid conflicts and assign resources
- Describe how the change schedule helps after deployment by informing incident and problem investigation
- Answer negative and list style questions on change enablement and explain why each distractor is wrong
- Level 29: Incident Management: Logging, Priority and Resolution
[7 Seven practices in detail] Study how incident management restores normal service quickly: every incident is logged and managed, prioritised by agreed classification, resolved within agreed and realistic target times, and handled differently according to its impact.- Explain why every incident is logged and managed so that it is resolved within times that meet customer and user expectations
- Describe how incidents are prioritised so that those with the highest business impact are resolved first
- Explain why low-impact, high-impact and major incidents need different handling and what a good incident record tool provides
- Level 30: Incident Management: Escalation, Swarming, Major Incidents
[7 Seven practices in detail] Learn who resolves incidents and how: user self-help, the service desk, support teams, suppliers and partners, escalation, swarming, separate major incident procedures, and the use of scripts for initial diagnosis.- Trace an incident from self-help through the service desk to a support team, supplier or temporary cross-functional team
- Explain what swarming is and when it helps with a complex incident
- Choose the best next action in an incident scenario and say why the other options belong elsewhere
- Level 31: Problem Management: The Three Phases
[7 Seven practices in detail] Study the three phases of problem management, namely problem identification, problem control and error control, and what is done in each to reduce the likelihood and impact of incidents.- Name the three phases of problem management and place an activity, such as trend analysis of incident records, in the right phase
- Explain how problems are prioritised and analysed on the basis of the risk they pose
- Describe what error control does with known errors, including reassessing them and weighing the cost of a permanent fix
- Level 32: Workarounds, Known Errors and Problem Links
[7 Seven practices in detail] Learn what a workaround is, how it is documented in a problem record and reviewed, and how problem management interfaces with incident management, change enablement, knowledge and continual improvement.- Define a workaround and explain how it relates to a known error and to a problem record
- Explain how problem management works with incident management and why a fix usually goes through change enablement
- Solve scenario questions that ask whether an activity is incident management or problem management
- Level 33: Service Request Management: What Counts as a Request
[7 Seven practices in detail] Study what a service request is, the kinds of request users raise (an action, information, access, a resource, feedback, a compliment or a complaint), and why requests are a normal part of service delivery, not a failure.- Define a service request and list the common kinds of request with an everyday example of each
- Explain why a service request is a normal, pre-agreed part of service delivery and not a degradation of service
- Sort a mixed list of user contacts into service requests and incidents
- Level 34: Service Requests: Standardise, Automate, Set Expectations
[7 Seven practices in detail] Learn the guidelines for handling requests well: standardising and automating fulfilment, setting policies for which requests need little or no extra approval, setting realistic fulfilment times, finding improvement opportunities and redirecting requests that are really incidents or changes.- Explain why service requests should be standardised and automated as far as possible
- Describe how approval policies and clearly communicated fulfilment times manage user expectations
- Explain how some requests are fulfilled with standard changes and what to do when a request is really an incident or a normal change
- Level 35: Service Desk: Single Point of Contact and Channels
[7 Seven practices in detail] Study the service desk as the entry point and single point of contact between the service provider and all its users, how it captures demand for incident resolution and service requests, and the channels users reach it through.- Explain the service desk's role in acknowledging, classifying, owning and actioning user contacts
- List the access channels a service desk may offer, such as phone, portals, chat, email, walk-in and messaging
- Explain how automation and removing technical debt shift the service desk's focus toward people and business understanding
- Level 36: Service Desk: Skills, Structures and Technology
[7 Seven practices in detail] Learn the skills service desk staff need (such as empathy, emotional intelligence, communication, and incident analysis and prioritisation), the difference between centralised, local and virtual service desks, and the supporting technologies each relies on.- Name the key customer service skills of service desk staff and explain why they matter more than deep technical skill
- Contrast a centralised service desk with a virtual service desk and the technology each needs
- Answer list and negative style questions on service desk skills, structure and technology
- Level 37: Service Level Management: SLAs and the Watermelon Effect
[7 Seven practices in detail] Study how service level management sets clear business-based targets: what a service level and a service level agreement (SLA) are, the key requirements of a successful SLA, and the watermelon SLA effect, where targets are met but customers are unhappy.- Define service level and service level agreement and explain how SLM gives a shared view of services and targets
- State the key requirements of a successful SLA, including relating to a defined service and to outcomes, in simple language agreed with the customer
- Explain the watermelon SLA effect and spot it in a scenario
- Level 38: Service Level Management: Information Sources and Skills
[7 Seven practices in detail] Learn where service level management gets its information (customer engagement, customer feedback, operational metrics and business metrics) and the skills it needs, such as relationship management, business liaison, business analysis and supplier management.- Distinguish the four information sources of SLM and give an example of each
- Describe the customer engagement activities of initial listening, discovery and information capture, and of measurement and ongoing progress discussions
- Explain why SLM needs relationship and business skills and why it should not be delegated to a purely operational reporting role
- Level 39: Seven Practices Together: Mixed Scenario Practice
[7 Seven practices in detail] Bring the seven detailed practices together in mixed questions in all four exam styles (standard, negative, missing word and list), with every distractor explained and a method for reading each style under time pressure.- Decide which of the seven practices a scenario describes when several seem to fit
- Apply a reading method to each of the four question styles, including spotting the NOT in negative questions and testing each statement in list questions
- Explain why each distractor in a mixed question is wrong, by naming the practice or term it really describes
- Level 40: Timed Mock Exam: 40 Questions in 60 Minutes Timed mock
[All sections] A closed-book, 60-minute mock of 40 original questions weighted like the exam across all seven learning outcomes, with 26 correct (65%) needed to pass.
Access
Levels 1 and 2 are free to read, no account needed. Levels 3 and 4 are free with a free account. Every level, the podcast edition and the AI tutor come with All Access at £4.99/month or any Creator plan — see pricing.
More like this
- ITIL Foundation (Version 5) Exam Prep
Learn every term, model and purpose in PeopleCert's ITIL Foundation (Version 5) syllabus from scratch, weighted as the exam weights them, and finish with a tim…
Exam prep · PeopleCert · Project & Service Management · Expert · 33 levels · 4 free · Professionally curated by levelupwith.com
- Leading Change: The People Side of Transformation
Learn to lead a new system, process or structure from first announcement to lasting adoption. You will build the case for change, map stakeholders and impacts,…
Course · Project Management · Project & Service Management · Capable · 17 levels · 4 free · Professionally curated by levelupwith.com
- Project Risk Management That People Actually Use
Learn to find, assess, own and report project risks so your risk register drives decisions instead of gathering dust. You will be able to set risk appetite, pl…
Course · Project Management · Project & Service Management · Capable · 18 levels · 4 free · Professionally curated by levelupwith.com
- Leading Your Team Through AI Adoption
Learn to run AI adoption in a team without losing people's trust. Using a running customer service and admin case, you will find good use cases, write a team A…
Course · Project Management · Project & Service Management · Capable · 17 levels · 4 free · Professionally curated by levelupwith.com
- PMI Project Management Professional (PMP) Exam Prep
Prepare for PMI's PMP exam under the outline in effect from July 2026. You will work through all 26 tasks across People, Process and Business Environment, and…
Exam prep · PMP · Project & Service Management · Expert · 50 levels · 4 free · Professionally curated by levelupwith.com
- Stakeholder Management: Mapping, Engaging and Reporting
Learn to find everyone your project affects, map their power and interest, and plan how to engage them. You will practise managing expectations, handling resis…
Course · Project Management · Project & Service Management · Capable · 18 levels · 4 free · Professionally curated by levelupwith.com