Guiding principles
40 free practice questions with explanations
PassNova has 40 free ITIL 4 Foundation practice questions on Guiding principles, each with a clear explanation. Practise them in the browser with instant feedback — 100% free, no sign-up, on any device. Updated for 2026.
Guiding principles: example questions & answers
40 worked examples with answers and explanations below. Practise them in the browser with instant feedback on every answer.
How many guiding principles are defined in ITIL 4?
- ASeven✓
- BFour
- CNine
- DFive
Answer: ITIL 4 defines seven guiding principles that can guide an organization in all circumstances, regardless of changes in goals, strategies, or structure.
Which guiding principle recommends that you understand what is genuinely valuable to the service consumer before doing anything?
- AKeep it simple and practical
- BStart where you are
- COptimize and automate
- DFocus on value✓
Answer: The 'focus on value' principle states that everything the organization does should map, directly or indirectly, to value for the stakeholders.
Which guiding principle advises against starting from scratch and recommends assessing the current state before making improvements?
- AThink and work holistically
- BCollaborate and promote visibility
- CProgress iteratively with feedback
- DStart where you are✓
Answer: The 'start where you are' principle advises assessing what already exists and can be reused, rather than starting over from scratch.
Which guiding principle recommends organizing work into smaller, manageable sections that can be executed and completed in a timely manner?
- AOptimize and automate
- BKeep it simple and practical
- CFocus on value
- DProgress iteratively with feedback✓
Answer: The 'progress iteratively with feedback' principle recommends breaking work into smaller iterations and using feedback before, during, and after each iteration.
Which guiding principle emphasizes that working together across boundaries produces results that have greater buy-in and relevance?
- AThink and work holistically
- BKeep it simple and practical
- CCollaborate and promote visibility✓
- DStart where you are
Answer: The 'collaborate and promote visibility' principle stresses that working together across boundaries, with appropriate transparency, leads to better outcomes and greater buy-in.
Which guiding principle states that no service, practice, process, department, or supplier stands alone?
- AThink and work holistically✓
- BOptimize and automate
- CProgress iteratively with feedback
- DFocus on value
Answer: The 'think and work holistically' principle states that no element works in isolation; outcomes are achieved only when components work together as an integrated whole.
Which guiding principle recommends using the minimum number of steps to accomplish an objective and eliminating anything that does not add value?
- AOptimize and automate
- BStart where you are
- CCollaborate and promote visibility
- DKeep it simple and practical✓
Answer: The 'keep it simple and practical' principle advises using the minimum number of steps to accomplish an objective and removing anything that fails to produce useful outcomes.
Which guiding principle advises making the best use of resources and technology, doing manual optimization before automating?
- AOptimize and automate✓
- BFocus on value
- CThink and work holistically
- DKeep it simple and practical
Answer: The 'optimize and automate' principle recommends maximizing the value of work performed by people and technology, optimizing before automating wherever possible.
According to the 'optimize and automate' principle, what should be done before attempting to automate a process?
- AAutomate immediately to save time, then refine the workflow once it is already running
- BOutsource the process
- CRemove the process entirely
- DOptimize the process as much as possible first✓
Answer: The 'optimize and automate' principle states that automating an inefficient process simply makes it inefficient faster; processes should be optimized first.
Which guiding principle would best support a recommendation to remove unnecessary controls and bureaucracy that add no value?
- AStart where you are
- BProgress iteratively with feedback
- CCollaborate and promote visibility
- DKeep it simple and practical✓
Answer: The 'keep it simple and practical' principle encourages eliminating steps, controls, and metrics that do not contribute to value creation.
A team plans to deliver a large project in a single, complete release with no intermediate reviews. Which guiding principle does this most clearly contradict?
- AThink and work holistically
- BProgress iteratively with feedback✓
- CFocus on value
- DOptimize and automate
Answer: Delivering everything at once with no reviews contradicts 'progress iteratively with feedback', which favors smaller iterations and regular feedback loops.
Why is it important to gather and use feedback when applying the guiding principles iteratively?
- AFeedback slows down delivery and should be minimized
- BFeedback is only needed at the end of a project, once the final deliverable has been accepted and the closure report signed off
- CFeedback enhances understanding, improves outcomes, reduces risk, and helps confirm value✓
- DFeedback is only relevant to the service desk, the one practice that deals directly with users
Answer: Seeking and using feedback enhances understanding, improves products and services, reduces risk, uncovers problems earlier, and ensures continued alignment with value.
When applying the 'start where you are' principle, what is the recommended approach to assessing the current state?
- ARely only on existing reports and assume they are accurate, as they come from the teams closest to the work
- BMeasure and observe the current state directly to avoid inaccurate assumptions✓
- CDiscard all existing services and rebuild from a clean sheet so that no legacy constraint is carried forward
- DAsk only senior management for their opinion
Answer: The 'start where you are' principle recommends observing and measuring the current state directly, as second-hand reports or assumptions can be misleading.
Which statement about the guiding principles is correct?
- AAn organization must apply all seven principles in a fixed sequence
- BThe principles only apply to the service desk
- COnly one principle can be applied at a time
- DNot every principle will be equally relevant in every situation, but all should be reviewed for relevance✓
Answer: The guiding principles are universal and enduring, but not all will be equally relevant in every situation. Organizations should review each for its relevance.
An organization wants to give a supplier and an internal team a shared view of work progress to build trust. Which principle is being applied?
- AKeep it simple and practical
- BOptimize and automate
- CStart where you are
- DCollaborate and promote visibility✓
Answer: Promoting visibility and working together across teams and suppliers is the essence of the 'collaborate and promote visibility' principle.
A team proposes adding three new approval steps to a request workflow 'to be safe', though none reduce real risk. Which guiding principle most directly challenges this proposal?
- AKeep it simple and practical✓
- BCollaborate and promote visibility
- CFocus on value
- DStart where you are
Answer: Keep it simple and practical advises removing steps and controls that do not produce useful outcomes or add value, which describes these unnecessary approvals.
Before improving its monitoring, a team is tempted to assume the old setup is useless and rebuild from scratch. Which principle warns them to assess and reuse what already exists first?
- AStart where you are✓
- BProgress iteratively with feedback
- CThink and work holistically
- DOptimise and automate
Answer: Start where you are recommends examining the current state and reusing what can be reused rather than discarding everything and starting over.
A manager wants to automate an error-prone, convoluted approval chain immediately. Applying 'optimise and automate' correctly, what should happen first?
- AStreamline and optimise the chain before automating it✓
- BAutomate the chain exactly as it stands to save time, then tidy it up later
- COutsource the chain to a supplier who already runs a similar approval process
- DDelete all approvals
Answer: Optimise and automate states you should optimise a process before automating; automating an inefficient process simply produces inefficiency faster.
A programme team plans an 18-month build with a single big-bang release and no checkpoints. Which guiding principle does this most clearly violate?
- AKeep it simple and practical
- BOptimise and automate
- CProgress iteratively with feedback✓
- DFocus on value
Answer: Progress iteratively with feedback favours dividing work into manageable iterations with feedback loops, the opposite of a single long build with no checkpoints.
Two departments and a supplier keep duplicating effort because none can see the others' work. Which principle, applied well, would most help?
- ACollaborate and promote visibility✓
- BKeep it simple and practical
- COptimise and automate
- DStart where you are
Answer: Collaborate and promote visibility encourages working together across boundaries with transparency, which reduces duplication and silos.
An improvement to the change process is planned without considering its effect on the service desk, suppliers, or tooling, and it later causes problems elsewhere. Which principle was overlooked?
- AThink and work holistically✓
- BStart where you are
- CProgress iteratively with feedback
- DFocus on value
Answer: Think and work holistically reminds us that no practice or service stands alone; changes must consider the whole system and its interdependencies.
A team is unsure which of several proposed metrics to keep. Applying 'focus on value', which question should drive the decision?
- AWhich metric the most senior person prefers?
- BWhich metric directly relates to value for stakeholders?✓
- CWhich metric has the longest history?
- DWhich metric is easiest to collect?
Answer: Focus on value means everything, including the metrics tracked, should map directly or indirectly to value for stakeholders; that is the deciding question.
A leader insists on a six-month requirements phase before any deliverable is produced, arguing feedback can wait until the end. Which principle's core advice is being ignored?
- AOptimise and automate
- BKeep it simple and practical
- CProgress iteratively with feedback✓
- DThink and work holistically
Answer: Progress iteratively with feedback advises seeking feedback before, during, and after each iteration rather than deferring it to the very end.
When applying 'start where you are', why does ITIL 4 caution against relying solely on existing reports to judge the current state?
- AReports are always confidential, so an improvement team is not permitted to see any of them
- BThe current state does not matter, because improvement starts from the target state alone
- CReports are never produced in IT departments, so there is simply nothing available for an improvement team to read in the first place
- DDirect observation and measurement avoid inaccurate assumptions that reports may contain✓
Answer: Start where you are recommends measuring and observing directly, because second-hand reports or assumptions can be misleading or out of date.
Which statement best captures how the seven guiding principles should be used?
- AApply them strictly in numerical order, finishing with each principle before the next one is considered
- BThey apply only to the continual improvement practice and have no bearing on the other thirty-three practices
- CThey are universal but not all are equally relevant in every situation; review each for relevance✓
- DUse only one principle per project
Answer: The guiding principles are universal and enduring, yet not all will be equally relevant in every situation; each should be reviewed for its relevance.
A team removes several low-value reports, simplifying operations, but a key stakeholder relied on one of them. Which principle reminds us that 'simple' must still preserve what genuinely adds value?
- AKeep it simple and practical✓
- BCollaborate and promote visibility
- COptimise and automate
- DStart where you are
Answer: Keep it simple and practical means using the minimum steps needed, but not at the expense of outcomes that add value; useful elements should be retained.
A provider wants to give customers a shared dashboard of incident status to build trust and reduce 'where is my ticket?' calls. Which principle is being applied?
- ACollaborate and promote visibility✓
- BFocus on value
- COptimise and automate
- DKeep it simple and practical
Answer: Sharing status openly to build trust and align stakeholders is the essence of collaborate and promote visibility.
After a successful pilot, a team plans the next small increment using lessons learned, then reviews again. Which guiding principle does this cycle exemplify?
- AProgress iteratively with feedback✓
- BOptimise and automate
- CThink and work holistically
- DStart where you are
Answer: Delivering in small increments and using feedback between them to shape the next step is progress iteratively with feedback.
A CIO asks staff to 'eliminate any activity, control, or metric that does not produce a useful outcome'. This instruction is a direct application of which principle?
- AKeep it simple and practical✓
- BProgress iteratively with feedback
- CStart where you are
- DCollaborate and promote visibility
Answer: Eliminating anything that fails to produce a useful outcome is the defining guidance of keep it simple and practical.
An organisation maps how a proposed automation will affect people, suppliers, data, and processes before approving it. Which two principles are most evident?
- AFocus on value, and collaborate and promote visibility
- BThink and work holistically, and optimise and automate✓
- CProgress iteratively with feedback, and focus on value
- DStart where you are, and keep it simple and practical
Answer: Considering the whole system (people, suppliers, data, processes) reflects think and work holistically, while planning automation reflects optimise and automate.
A team is paralysed trying to design a 'perfect' solution before acting. Which principle encourages them to make a useful start and refine through feedback instead?
- AProgress iteratively with feedback✓
- BKeep it simple and practical
- COptimise and automate
- DThink and work holistically
Answer: Progress iteratively with feedback discourages waiting for perfection; it favours starting with a manageable increment and improving using feedback.
Which scenario best demonstrates 'focus on value' being applied at the start of an initiative?
- AThe team copies a competitor's service without analysing whether it suits their own consumers at all
- BThe team automates the existing workflow before anyone has established what outcome the initiative is meant to achieve
- CThe team first clarifies what outcomes the consumer considers valuable, then designs accordingly✓
- DThe team selects the newest technology available because it is fashionable and looks impressive to the board
Answer: Focus on value means understanding what is genuinely valuable to the service consumer first, then ensuring all work maps to that value.
A manager argues that because automation is cheaper, the team should automate every task regardless of value. Which principle corrects this by reminding them automation should serve value and be applied where it makes sense?
- AProgress iteratively with feedback
- BCollaborate and promote visibility
- COptimise and automate✓
- DStart where you are
Answer: Optimise and automate advises automating where it adds value after optimising; automation is a means to value, not an end pursued indiscriminately.
Which principle most strongly underpins the practice of reusing existing tools, processes, and people rather than procuring new ones unnecessarily?
- ACollaborate and promote visibility
- BProgress iteratively with feedback
- CStart where you are✓
- DFocus on value
Answer: Start where you are encourages assessing and reusing what already exists before assuming new resources must be acquired.
A change team and a security team distrust each other and withhold information, slowing every release. Which principle, applied jointly, would best break the deadlock?
- ACollaborate and promote visibility✓
- BOptimise and automate
- CStart where you are
- DKeep it simple and practical
Answer: Collaborate and promote visibility addresses silos and distrust by encouraging cross-team working and transparency, improving flow and buy-in.
Which statement about feedback in iterative work is correct according to ITIL 4?
- ASeeking and using feedback throughout reduces risk and improves alignment with value✓
- BFeedback slows progress and should be avoided
- CFeedback should be collected only after the entire project ends
- DFeedback is only useful to the service desk
Answer: Using feedback before, during, and after iterations improves understanding, reduces risk, surfaces issues earlier, and keeps work aligned with value.
An improvement that looks sensible in isolation harms overall flow because it shifts a bottleneck downstream. Which principle would have caught this before implementation?
- AThink and work holistically✓
- BKeep it simple and practical
- CFocus on value
- DStart where you are
Answer: Think and work holistically considers the end-to-end system, revealing that a local optimisation can degrade the whole; isolated changes can shift bottlenecks.
A team breaks a large migration into several small, reviewable stages so it can adjust based on what each stage reveals. This is the clearest example of which principle?
- AKeep it simple and practical
- BOptimise and automate
- CCollaborate and promote visibility
- DProgress iteratively with feedback✓
Answer: Dividing work into small stages and adjusting based on feedback from each is progress iteratively with feedback.
Which combination of principles is most relevant when an organisation wants to cut waste while ensuring the simplified result still delivers what stakeholders need?
- AThink and work holistically, and start where you are
- BOptimise and automate, and start where you are
- CCollaborate and promote visibility, and progress iteratively with feedback
- DKeep it simple and practical, and focus on value✓
Answer: Cutting waste is keep it simple and practical, while ensuring the result still meets stakeholder needs is focus on value; together they prevent over-simplification.
Why does ITIL 4 describe the guiding principles as 'enduring'?
- AThey are legally mandated in most countries, so an organisation that ignores them can be fined by its regulator
- BThey apply only during major incidents, when normal decision-making has been suspended by the incident manager
- CThey expire whenever a new version of ITIL is published, at which point a completely fresh set of principles has to be learned by everyone from scratch
- DThey remain applicable over time despite changes in goals, strategies, type of work, or management structure✓
Answer: The guiding principles are enduring because they hold true and remain useful regardless of changes in an organisation's goals, strategies, work, or structure.