The ITIL guiding principles
The seven ITIL guiding principles are recommendations meant to hold in any circumstance. The exam tests whether you can recognise which principle a described situation is about, which is harder than reciting the list. Objective 2 of ITIL 4 Foundation, worth 15% of the exam.
- Share of the exam
- 15%
- Questions in a real sitting
- roughly 6 of 40
- Questions in this bank
- 18
- Signed for by a person
- 0
- Machine-checked only
- 18
Partly checked. None of the 18 questions here has been read against the cited source by a person. 18 questions have been checked against their cited clause by an automated pass — which is not the same thing, and is not a signature.
Only questions a person has signed for are used in mock exams here. That is the whole difference between the two kinds of checking above.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
What this objective covers
The 18 questions written for this objective cite 1 ITIL 4 syllabus clause (2).
They break down as 18 single-answer questions.
What this objective is really about
Learning the seven names is the easy part and worth almost nothing on its own. Every question in this area gives you a scenario and asks which principle applies, and the distractors are always other real principles that are plausible but less specific. Your job is to find the one that names the actual failure or the actual behaviour described, not merely one that is broadly relevant.
It helps to hold a one-line trigger for each. Focus on value: is the work connected to something a consumer actually wants? Start where you are: has anyone looked at what already exists before rebuilding? Progress iteratively with feedback: is the work broken into pieces that produce learning? Collaborate and promote visibility: are the right people involved and is the work visible? Think and work holistically: has anything been optimised in isolation? Keep it simple and practical: are there steps that produce nothing? Optimize and automate: has the thing been made good before technology was applied to it?
The distinctions that decide questions
"Start where you are" versus "focus on value" is the first split worth practising. Start where you are is about the current state — assessing it honestly, measuring it directly rather than through somebody else's summary, and reusing what already works. Focus on value is about the destination — whether the work maps to something a consumer or stakeholder cares about. A team that rebuilds from scratch without looking at the old system has broken the first. A team that builds a feature nobody asked for has broken the second.
"Keep it simple and practical" versus "optimize and automate" is the second. Keep it simple owns the question of whether a step should exist at all; optimize and automate owns how well the surviving steps run. The order matters and the exam tests it: automating a process nobody simplified first just produces waste at speed.
"Think and work holistically" versus "collaborate and promote visibility" is the third. Holistic thinking is about the system — services, practices and all four dimensions interacting. Collaboration and visibility is about the people and the transparency of the work. A change that breaks a downstream service because nobody considered it is a holistic failure. Two teams duplicating effort because neither can see the other's backlog is a visibility failure.
Two things that are frequently misremembered
Collaboration does not mean consensus. The principle asks for the right people to be involved so decisions are better informed; it does not require everyone to agree before anything can move, and a question describing an improvement lead who insists on unanimity is describing a misreading of the principle rather than an application of it.
The principles are interdependent and are not a sequence. There is no prescribed order in which to apply them, they are not one-per-value-chain-activity, and they are not limited to improvement work. The only internal ordering worth remembering is inside "optimize and automate", where optimisation genuinely comes first.
Lessons in this objective
The objective cut into the pieces the blueprint declares. Each one has the material written out and the questions that test it.
- Start where you are, iterate, simplify and automate
- Focus on value, collaborate, work holistically
- Simplicity, iteration and how the principles combine
- Spotting the missing principle, and what automation means
Drill this objective
The trainer can run a short practice set drawn from this objective alone, which is what the weight column above is for: revise the heavy objectives first.
Practise The ITIL guiding principles
Questions on this objective
- A team has been asked to replace an ageing service desk tool. Before designing anything, the team inventories the existing tool's integrations, workflows and data, and finds that several components work well and can be carried forward. Which guiding principle is the team applying? machine-checked
- An organization decides to introduce robotic process automation for its user access request handling. Its ITIL adviser insists that the approval steps are first reviewed and the redundant ones removed. What is the reasoning behind this advice? machine-checked
- A programme has been running for eleven months with no deliverable released, because the team intends to hand over the complete solution in one go. Which guiding principle is being ignored? machine-checked
- A manager plans a service improvement using only the monthly summary reports produced by the supplier, and does not observe how the service actually runs. Which guiding principle most directly cautions against this? machine-checked
- During an improvement review, a team finds that a weekly reconciliation report is produced, circulated and archived, but no one uses it for any decision. Which guiding principle states directly that an activity like this should be eliminated? machine-checked
- A change to a payment service is planned by the application team alone. When deployed, it breaks a downstream reporting service and leaves the support team without updated documentation. Which guiding principle would most likely have prevented this? machine-checked
- Two teams each maintain their own private backlog and status spreadsheet. Work is regularly duplicated and urgent items are deprioritized because leadership cannot see them. Which guiding principle addresses this situation? machine-checked
- Which statement best describes what a guiding principle is in ITIL 4? machine-checked
- A service provider adds an elaborate self-service portal feature that no user has asked for and that does not help users achieve any outcome they care about. Which guiding principle has been neglected? machine-checked
- An improvement lead argues that 'collaborate and promote visibility' means every decision must be agreed by all stakeholders before proceeding. How should this be corrected? machine-checked
- A new incident categorization scheme has 140 categories, and analysts routinely pick the wrong one because the distinctions do not change how an incident is handled. What should the team do, and on which guiding principle should they rely? machine-checked
- A team divides a twelve-month improvement into six short cycles, and after each cycle reviews results with users and adjusts the plan for the next cycle. Which guiding principle does the review-and-adjust step illustrate most directly? machine-checked
- Which statement about how the ITIL guiding principles are applied is correct? machine-checked
- A team designing a new access request workflow tries to build a path for every rare exception into the main flow. The result is a form of 40 conditional questions that nearly every user must work through in order to make a routine request. What does 'keep it simple and practical' advise here? machine-checked
- A director proposes decommissioning the entire existing service management toolset and processes on day one of a transformation, on the grounds that a clean slate avoids inherited bad habits. Which guiding principle argues against this, and why? machine-checked
- An organization improves its application deployment tooling but ignores the training, roles and supplier contracts that surround it, and the expected benefit does not materialize. Which guiding principle was not applied? machine-checked
- A provider measures only technical availability and concludes its service is excellent, while users describe the service as frustrating to use. Which guiding principle does this gap most directly relate to? machine-checked
- Within the guiding principle 'optimize and automate', what does automation mean? machine-checked
Practise The ITIL guiding principles
The other objectives in ITIL 4 Foundation
- 1. Key concepts of service management — 12.5% of the exam
- 3. The four dimensions of service management — 5% of the exam
- 4. The ITIL service value system — 2.5% of the exam
- 5. The service value chain — 5% of the exam
- 6. Purpose and key terms of 15 ITIL practices — 12.5% of the exam
- 7. Seven ITIL practices in detail — 47.5% of the exam