ITIL 4 Foundation — All Questions
The figures these questions turn on, laid out by section on dense colour pages you can print: ITIL 4 Foundation cheat sheet PDF — $9.99 →
64 questions
Different stakeholders demand many extra features and controls, threatening to make a service overly complex. Applying 'keep it simple and practical', the team should:
- a.Judge each proposed element by the value it adds and design the simplest solution that still meets the objective✓
- b.Automate all of the extra controls immediately without assessing them first
- c.Refuse to talk to any of the stakeholders about their requests at all
- d.Add every single requested feature and control regardless of the value added
Keep it simple and practical says to use the minimum steps necessary and eliminate anything that does not add value. When competing demands threaten to overcomplicate a service, the team should assess each element by the value it adds and design the simplest solution that still achieves the objective, rather than accepting every request.
What does 'optimize' mean in the 'optimize and automate' principle?
- a.Purchasing the single most expensive tool that is currently available to buy
- b.Removing the process entirely, without carrying out any analysis of it first
- c.Adding as many extra manual checks and controls to the process as possible
- d.Making something as effective and useful as it needs to be, given the resources and constraints involved✓
In optimize and automate, to optimize means to make something as effective and as useful as it needs to be. Optimization considers the context, the resources available and the constraints, and streamlines the process before automation is applied. Only after optimization does automating the work deliver its full value.
Before optimizing a process, 'optimize and automate' recommends first:
- a.Ignoring the current state of the process entirely and starting from a blank page and this remains the case regardless of which service is being delivered
- b.Automating the process straight away so that optimizing it becomes unnecessary
- c.Understanding and agreeing the context, the current state, and the desired outcome the optimization should achieve✓
- d.Removing all of the human involvement from the process immediately and at once
Optimize and automate recommends understanding the context before optimizing, the current state, the agreed objective, and the constraints and resources involved. Only with this understanding can optimization make the process as effective as it needs to be, after which automation can be applied to sustain and scale the improvement.
A team maps the end-to-end customer journey to identify where consumers gain or lose value. Which guiding principle does this primarily support?
- a.Focus on value✓
- b.Keep it simple and practical, which uses the fewest steps that are needed
- c.Optimize and automate, which streamlines a process before automating it
- d.Start where you are, which assesses current capabilities before any action
Mapping the customer journey to see where consumers gain or lose value primarily supports focus on value. Understanding the consumer's experience and where value is created or eroded ensures the organization's efforts are directed at what genuinely matters to the people being served.
An organization is about to buy a new monitoring tool, then discovers its current tool already meets most needs. Applying 'start where you are', it should:
- a.Assess the existing tool objectively and reuse or extend it where it already delivers value✓
- b.Discard both of the tools entirely and simply monitor nothing going forward
- c.Buy the new monitoring tool anyway, without carrying out any assessment first
- d.Automate the purchase of every single monitoring tool that is available to buy and it holds true even when the surrounding circumstances change over time
Start where you are advises assessing what already exists before acquiring something new, and leveraging existing capabilities that provide value. On finding that the current tool meets most needs, the organization should evaluate it objectively and reuse or extend it where appropriate, rather than buying new capability unnecessarily.
Which of these are valid sources of feedback under 'progress iteratively with feedback'?
- a.Only the personal opinion of the single project sponsor, and no other source
- b.User surveys and complaints, performance metrics, and reviews at the end of each iteration✓
- c.No sources whatsoever, because gathering feedback only ever slows the work down
- d.Only automated system alerts and monitoring, and never any feedback from people and no exceptions to this are ever recognized once the service is running
Progress iteratively with feedback relies on feedback loops from many sources, user surveys and complaints, performance and process metrics, checkpoint reviews, and lessons captured after each iteration. Drawing on varied feedback keeps the work relevant, surfaces problems early, and enables the team to adapt as it proceeds.
How can 'collaborate and promote visibility' improve the success of an improvement initiative?
- a.By preventing any information about the status from being shared at all
- b.By keeping the whole initiative completely secret until it has been finished and this is decided entirely by the provider without any consumer input
- c.By deliberately reducing the number of people who know anything about it
- d.By increasing stakeholder buy-in, surfacing hidden work, and creating a shared sense of urgency and ownership✓
Collaborate and promote visibility improves outcomes by involving the right stakeholders, which increases buy-in and the relevance of the work, and by making work and its status visible, which surfaces hidden work and builds shared urgency and ownership. Secrecy and poor visibility, by contrast, lead to poor decisions and weak support.
A change to a database is planned without consulting the teams that depend on it, causing downstream failures. Which principle would have prevented this?
- a.Think and work holistically✓
- b.Optimize and automate, which streamlines a process before it is automated
- c.Focus on value, which links each activity back to value for the consumer
- d.Keep it simple and practical, which uses the minimum number of needed steps
Making a change without considering the teams and systems that depend on it, causing downstream failures, is a failure to think and work holistically. This principle stresses that components are interconnected and that changes in one area can affect others. Considering the whole system, and the dependent teams, would have prevented the failures.
Faced with several competing objectives, 'keep it simple and practical' advises a team to:
- a.Automate absolutely everything first, before even deciding on the objectives
- b.Seek the simplest approach that still satisfies the essential objectives, avoiding unnecessary complexity✓
- c.Satisfy every one of the objectives in full, however complex the result becomes
- d.Abandon all of the objectives entirely in order to keep everything very simple
Keep it simple and practical acknowledges that competing objectives and stakeholder demands can drive complexity. It advises finding the simplest approach that still meets the essential objectives, using the minimum steps necessary and eliminating what adds no value, rather than trying to satisfy every demand at the cost of overwhelming complexity.
To confirm that automation actually improved a process, 'optimize and automate' implies a team should:
- a.Assume that the automation must have worked, without taking any measurements
- b.Remove all of the metrics from the process once the automation is in place
- c.Only measure the number of members of staff who were removed by the change
- d.Measure the process before and after, so the effect of the optimization and automation can be objectively assessed✓
Optimize and automate, and continual improvement more broadly, imply measuring a process before and after change so the effect can be objectively assessed. Understanding the baseline and comparing it to the automated, optimized state confirms whether value was actually delivered, rather than assuming success or dropping measurement.
Want these explained in order? ITIL 4 Foundation — Complete Study Guide (2026) — PDF + EPUB, $14.99 · 14-day refund →
'Understand how each service is used and what a good experience looks like for the consumer' is guidance from which principle?
- a.Start where you are, which assesses the current state as objectively as it can
- b.Keep it simple and practical, which removes anything that adds no real value
- c.Optimize and automate, which streamlines a process before it is automated
- d.Focus on value✓
Understanding how each service is used and what a good experience looks like for the consumer is core guidance from focus on value. This principle requires knowing who is being served and seeing value, including the customer and user experience, from their perspective, so that all work contributes to genuine value.
'Assess the current state as objectively as possible, measuring directly where you can' is guidance from which principle?
- a.Optimize and automate, which streamlines a process before automating it
- b.Collaborate and promote visibility, which surfaces the real status of work
- c.Start where you are✓
- d.Progress iteratively with feedback, which divides the work into iterations
Assessing the current state as objectively as possible, and measuring directly rather than relying on assumptions, is guidance from start where you are. This principle advises understanding what already exists before acting, using accurate observation so decisions about what to keep or change are based on evidence.
'Do not try to do everything at once; organize work into smaller pieces guided by feedback' is guidance from which principle?
- a.Focus on value, which links every activity back to value for the consumer
- b.Progress iteratively with feedback✓
- c.Keep it simple and practical, which uses the minimum steps that are needed
- d.Think and work holistically, which coordinates the whole system end to end
Not trying to do everything at once, and instead organizing work into smaller, feedback-guided iterations, is the essence of progress iteratively with feedback. Breaking work into manageable pieces and using feedback throughout reduces risk, delivers value earlier, and lets the work adapt to changing circumstances.
'Optimize a process before you automate it, so technology does not just accelerate waste' is guidance from which principle?
- a.Optimize and automate✓
- b.Keep it simple and practical, which removes any step that adds no real value
- c.Start where you are, which assesses existing capabilities before taking action
- d.Collaborate and promote visibility, which involves the right people and status
Optimizing a process before automating it, so that technology does not merely accelerate inefficiency, is the central guidance of optimize and automate. The principle sequences the two words deliberately: first make the process as effective as it needs to be, then apply automation to deliver maximum value with minimal manual effort.