The Guiding Principles — ITIL 4 Foundation practice questions

A leader insists every team apply ALL seven guiding principles equally on every decision. What is the BEST critique?

1. Principles are universal but weighted to fit the situation at hand
2. The leader is right — all seven apply with equal force every time
3. Principles belong in strategy only and should be ignored in operations
4. Principles apply to teams and staff but not to leadership decisions

Answer: A — Principles are universal but weighted to fit the situation at hand

A is right because the principles are universal and enduring, yet each is applied according to context rather than by equal quota. B mistakes universality for uniform weighting. C swings to the opposite error of excluding operational work. D invents a scope limit the framework does not place on leaders.

Which guiding principle promotes 'do not begin redesigns or transformations from scratch — assess and reuse what exists'?

1. Start where you are
2. Focus on value
3. Progress iteratively with feedback
4. Optimize and automate
5. Think and work holistically

Answer: A — Start where you are

Start where you are: leverage existing capabilities, processes, people, technology before tearing down. Saves time, retains institutional knowledge. Combine with measure-before-decide. Reduces transformation risk.

Which principle from ITIL continues into v5 and cautions AGAINST automating a broken process?

1. Keep it simple and practical — optimize before you automate
2. Focus on value — automate whatever is cheapest first
3. Collaborate and promote visibility — automation removes the need for communication
4. Think and work holistically — every process must be automated together

Answer: A — Keep it simple and practical — optimize before you automate

A) Correct — optimizing before automating prevents scaling waste; automating a broken process just produces failures faster. B) 'Focus on value' prioritizes value, not cheapness of automation. C) That principle increases communication; it does not remove it. D) Holistic thinking does not demand automating everything simultaneously.

Which scenario BEST applies 'Progress iteratively with feedback'?

1. Deliver one large release after 18 months with no interim checkpoints
2. Skip feedback loops entirely because the team trusts its own judgement
3. Deliver a small slice, measure the outcome, adjust, then continue
4. Defer all feedback gathering until the whole programme has completed

Answer: C — Deliver a small slice, measure the outcome, adjust, then continue

C is right because the principle needs both short cycles and feedback within each cycle. A iterates on far too long a horizon and gathers nothing on the way. B keeps the cycles but strips out the learning that makes them useful. D looks iterative yet collapses into a single end-of-programme review.

Which is the BEST description of how the guiding principles relate to other ITIL elements?

1. They override governance whenever the two give conflicting direction
2. They guide decisions across all SVS components and every practice
3. They apply only within the six activities of the service value chain
4. They are required in projects but not in day-to-day operational work

Answer: B — They guide decisions across all SVS components and every practice

B is right because the principles inform decisions across the whole service value system, the four dimensions and every practice. A inverts the relationship; governance is a distinct SVS component the principles do not outrank. C narrows them to one component. D invents a project-only scope.

Which is the MOST common misapplication of 'Keep it simple and practical'?

1. Cutting steps without checking whether compliance or governance needs them
2. Adding written documentation so that the workflow can be handed over cleanly
3. Engaging affected stakeholders early to agree what the outcome is
4. Asking users for feedback on each iteration before starting the next

Answer: A — Cutting steps without checking whether compliance or governance needs them

A is right because the usual failure is over-simplification: deleting steps that exist to satisfy regulatory or risk-control needs. B, C and D are all legitimate practices that add modest effort for real benefit, and simplicity is a means to value rather than a licence to remove required controls.

Which is the BEST description of the 'focus on value' guiding principle?

1. Cut costs immediately wherever spending can be reduced without breaching a contract
2. Replace user feedback with internal metrics that the provider can measure reliably
3. Maximize profit at all times, treating margin as the measure of every decision
4. Everything the organization does should link back, however indirectly, to value

Answer: D — Everything the organization does should link back, however indirectly, to value

D states the principle: every activity should be traceable to value for stakeholders, and the consumer's perspective defines what counts as value. A treats cost reduction as a goal in its own right. B removes the consumer's voice that the principle depends on. C substitutes one stakeholder's return for the stakeholder value the principle covers.

A department wants to replace its entire service management toolset, redesign every workflow and retrain all staff in a single twelve-month programme, with no deliverable before the end. Which ITIL 4 guiding principle does this plan MOST clearly ignore?

1. Focus on value, because a programme of this size cannot be tied to a stakeholder outcome
2. Keep it simple and practical, because a redesign on this scale always adds unnecessary steps
3. Progress iteratively with feedback, because no part of the work is evaluated before the end
4. Optimize and automate, because manual workflow design ought to be replaced by tooling first

Answer: C — Progress iteratively with feedback, because no part of the work is evaluated before the end

C) Correct — the plan commits everything to one long push with no intermediate feedback loop, which is exactly what progress iteratively with feedback warns against; work should be organised into smaller manageable sections that are completed and evaluated in a timely way. A) tempts because value is always relevant, but nothing in the scenario says the outcome is unidentified — the flaw is the timing, not the target. B) is a real principle but the problem is not that the design is over-elaborate in itself; it is that no feedback arrives before the end. D) reverses the point: automating an unvalidated workflow is a caution of that principle, and the scenario does not mention automation at all.

An organization plans to 'optimize and automate' its incident workflow but finds the underlying workflow has redundant approval steps. What should it do?

1. Automate the redundant approval steps exactly as they stand to move fast
2. Abandon automation and keep running the workflow manually indefinitely
3. Remove the redundant approvals first, then automate the streamlined flow
4. Eliminate the incident workflow entirely and handle each case ad hoc

Answer: C — Remove the redundant approvals first, then automate the streamlined flow

C is right because the principle's sequence is deliberate: optimize, then automate. A is the classic half-application that locks waste in at machine speed. B forfeits the automation benefit entirely. D confuses simplification with removing a control the organization still needs.

Which is the BEST application of 'think and work holistically'?

1. Optimize one team at a time so that each local improvement can be measured cleanly
2. Concentrate on the technology, since tooling determines how the other aspects behave
3. Avoid coordination across teams so that each of them can move at its own pace
4. Consider how the four dimensions and the SVS interact when changing a service

Answer: D — Consider how the four dimensions and the SVS interact when changing a service

D is the principle in use: no service stands alone, so the four dimensions and all SVS components must be considered together. A is the most plausible trap, because local optimization sounds disciplined but can degrade the end-to-end result. B elevates one dimension over the rest. C removes the integration the principle is built on.

Collaborate and promote visibility?

Working with right stakeholders. Transparency builds trust.

What does 'progress iteratively with feedback' recommend for a large initiative?

Break work into smaller, manageable iterations that are executed and completed in a timely way, seeking and using feedback before, during and after each one. Iterations can be sequential or overlapping, and feedback loops keep the work relevant and let it respond to changing circumstances.

Focus on value principle?

Everything should link to value for stakeholders.

Think and work holistically?

Service is more than sum of parts. All components matter.