ITIL 4 Foundation — All Questions

How many guiding principles are defined in ITIL 4, and what is their purpose?

• a.Six principles that make up the service value chain
• b.Four principles that define the service lifecycle stages
• c.Seven principles that provide universal, enduring recommendations to guide an organization in all circumstances✓
• d.Five principles that describe the continual improvement steps

ITIL 4 defines seven guiding principles: focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; and optimize and automate. They are universal and enduring recommendations that can guide an organization in all circumstances, regardless of changes in goals, strategies, or structure. The principles encourage and support organizations in continual improvement at every level.

An organization plans to redesign a service and wants to discard everything and rebuild from scratch. Which guiding principle warns against this?

• a.Keep it simple and practical
• b.Start where you are✓
• c.Optimize and automate
• d.Focus on value

The 'start where you are' principle advises that organizations should not start over without first considering what is already available to be leveraged. Existing services, processes, and people may already provide significant value and should be assessed objectively before being discarded. Rebuilding from scratch wastes resources and risks losing valuable capabilities that already exist.

A team wants to deliver a large improvement all at once over 18 months. Which guiding principle would recommend a different approach, and what is it?

• a.Focus on value — ignore stakeholder input
• b.Collaborate and promote visibility — always work in isolation
• c.Progress iteratively with feedback — organize work into smaller, manageable sections that are completed in a timely manner using feedback loops✓
• d.Optimize and automate — automate the entire project immediately

The 'progress iteratively with feedback' principle recommends dividing work into smaller, manageable iterations that can be executed and completed in a timely manner. Seeking and using feedback before, during, and after each iteration ensures actions remain focused and relevant. This reduces risk, allows faster response to changing needs, and demonstrates value earlier than a single large effort would.

Which guiding principle stresses that no service, practice, or component stands alone and that the organization must coordinate all four dimensions?

• a.Start where you are
• b.Keep it simple and practical
• c.Think and work holistically✓
• d.Focus on value

The 'think and work holistically' principle states that no service, practice, process, department, or supplier stands alone. Outcomes are delivered to internal and external customers only when the organization works as an integrated whole, coordinating all four dimensions and the elements of the service value system. Taking a holistic view prevents siloed decisions that undermine overall value.

When applying the 'focus on value' guiding principle, what is an important early step?

• a.Understand who is being served and know the consumer's perspective on value and desired experience✓
• b.Divide all work into small iterations regardless of context
• c.Discard all existing services and start again
• d.Automate every process before assessing its usefulness

Focus on value means that everything the organization does should link back to value for stakeholders. An early step is to know who is being served and to understand the consumer's perspective — how they use each service and what a good experience looks like for them. Only by understanding the consumer's view of value can the organization ensure its work genuinely contributes to it.

Which action best reflects the 'collaborate and promote visibility' guiding principle?

• a.Involve the right stakeholders and make work, its flow, and status visible so that better decisions can be made✓
• b.Keep improvement work hidden until it is completely finished
• c.Use the fewest possible steps to reach the objective
• d.Automate the workflow to remove people from it entirely

Collaborate and promote visibility emphasizes working together across boundaries and making work and its consequences visible. Involving the right stakeholders produces better buy-in and more relevant outcomes, and surfacing the true status of work reduces hidden work and improves decision-making. Poor visibility leads to poor decisions and erodes trust, which this principle seeks to prevent.

According to 'keep it simple and practical', if a process or metric provides no value, you should:

• a.Eliminate it, using the minimum number of steps needed to accomplish the objective✓
• b.Outsource it to an external supplier
• c.Add more controls to justify keeping it
• d.Automate it as quickly as possible

Keep it simple and practical advises using the minimum number of steps necessary to accomplish an objective and adopting an outcome-based approach. If a process, service, action, or metric fails to provide value or produce a useful outcome, it should be eliminated. Removing what does not add value keeps work efficient and easier to understand, rather than piling on unnecessary complexity.

According to the 'optimize and automate' guiding principle, what should happen before automating a process?

• a.Discard the process entirely and start from scratch
• b.Nothing — automate immediately to save the most time
• c.Increase the number of manual steps to be safe
• d.Optimize the process first, because automating an inefficient process only magnifies its inefficiency✓

Optimize and automate recommends optimizing work before automating it. Automation applied to an inefficient or wasteful process simply produces that waste faster and at greater scale. The correct sequence is to first make the process as effective and streamlined as it needs to be, and only then introduce automation so that technology delivers maximum value with minimal human intervention.

When assessing the current state, the 'start where you are' principle recommends that you:

• a.Rebuild everything before attempting any measurement
• b.Assume the current state based only on past reports
• c.Ignore existing capabilities entirely
• d.Observe and measure the current state directly wherever possible, rather than relying on assumptions✓

Start where you are advises looking at what already exists rather than building from scratch, and assessing the current state as objectively as possible. Where practical, the current state should be observed and measured directly, because relying on reports or assumptions can be misleading. Accurate observation ensures decisions about what to keep or change are based on evidence, not guesswork.

A team faces a very large improvement program. Applying 'progress iteratively with feedback', they should:

• a.Cancel the program because it is too large to attempt
• b.Complete the whole program in one large release with no interim review
• c.Break the work into smaller iterations, each reassessed using feedback as it proceeds✓
• d.Automate the entire program before starting any of it

Progress iteratively with feedback recommends organizing work into smaller, manageable iterations that can be completed in a timely manner. Each iteration is reassessed using feedback gathered before, during, and after it, so the team can adapt to changing needs and reduce risk. Breaking a large program into feedback-driven iterations delivers value sooner than one big-bang effort.

Which statement reflects the 'think and work holistically' guiding principle?

• a.No service, practice, or component stands alone; the organization must coordinate all four dimensions and the elements of the service value system✓
• b.The simplest single step always creates the most value
• c.Feedback should be avoided so as not to lose momentum
• d.Each department should optimize its own work in isolation

Think and work holistically recognizes that no service, practice, process, department, or supplier stands alone. Outcomes are achieved only when the organization works as an integrated whole, coordinating all four dimensions and the elements of the service value system. Taking this end-to-end view prevents siloed decisions that improve one area while undermining overall value.

A team wants to add a new reporting feature to a service. Which question best applies the 'focus on value' principle?

• a.How will this feature contribute to value for the service consumer and their outcomes?✓
• b.How many steps can we add to make the process thorough?
• c.Can we automate the report before checking whether it is useful?
• d.Which supplier offers the cheapest reporting tool?

Focus on value requires linking every activity back to value for stakeholders. Before building the feature, the most relevant question is how it will contribute to value for the service consumer and help them achieve their outcomes. Asking this first prevents the team from investing effort in work that looks useful internally but does not actually improve the consumer's experience or results.

Which statement about the ITIL 4 guiding principles is correct?

• a.The guiding principles replace the four dimensions of service management
• b.An organization must apply only one guiding principle at a time
• c.The guiding principles are used only during incident management
• d.The guiding principles are universal and enduring recommendations that apply in almost any circumstance, and an organization should review how each applies✓

The seven guiding principles are universal and enduring recommendations that guide an organization in all circumstances, regardless of changes in goals, strategies, or structure. They are not applied one at a time or only in specific practices; instead, an organization should consider how all of them are relevant to a given situation. They complement — rather than replace — other elements such as the four dimensions.

Before automating an approval workflow, a manager first removes unnecessary approval steps and standardizes the required inputs. Which guiding principle does this illustrate?

• a.Focus on value
• b.Collaborate and promote visibility
• c.Start where you are
• d.Optimize and automate✓

This scenario illustrates optimize and automate, specifically the rule that optimization should come before automation. By removing unnecessary steps and standardizing inputs, the manager first makes the workflow as effective as it needs to be. Only after this optimization would automating the streamlined workflow deliver real value, rather than automating waste.

Applying 'focus on value', what should be the very first question a team asks about any activity or improvement?

• a.How many separate approval steps can we add to keep everything under control?
• b.How can we fully automate this activity before we have even assessed it?
• c.Who is the service consumer, and what does value look like from their perspective?✓
• d.Which particular supplier happens to offer the cheapest available components? and the four dimensions of service management are not relevant to it at all

Focus on value means everything the organization does should link back to value for stakeholders. The first step is to identify who is being served and to understand value from their perspective, how they use the service and what a good outcome looks like. Only then can the team ensure its work genuinely contributes to value.

A manager insists that every task in a project be traceable to a benefit for the customer. Which guiding principle is being applied?

• a.Keep it simple and practical, which uses the minimum steps that are needed
• b.Optimize and automate, which sequences optimization before any automation
• c.Start where you are, which assesses what already exists before acting
• d.Focus on value✓

Requiring that every task link back to a benefit for the customer is a direct application of focus on value. This principle holds that all activities should contribute to value for stakeholders, whether directly or indirectly. Work that cannot be tied to value should be questioned and potentially removed.

Understanding the customer experience (CX) and user experience (UX) of a service is emphasized by which guiding principle?

• a.Optimize and automate, which streamlines work before applying technology
• b.Think and work holistically, which coordinates all the moving parts together
• c.Progress iteratively with feedback, which divides work into small iterations
• d.Focus on value✓

Focus on value includes understanding the whole experience a consumer has with a service, the customer experience (CX) and user experience (UX). Knowing how the service feels to use, and what a good experience looks like, helps ensure the service delivers genuine value from the consumer's point of view.

A team discovers a weekly report that no one reads and that informs no decision. Applying 'focus on value', they should:

• a.Automate the production of the report so that it is generated much faster and it makes no difference whether the work is large or small in scale
• b.Add even more data to the report in order to try to justify keeping it
• c.Stop producing the report, since it contributes nothing to value for any stakeholder✓
• d.Assign additional members of staff to maintain and distribute the report

Focus on value requires that activities contribute to value for stakeholders. A report that no one reads and that drives no decision adds no value, so the value-focused response is to stop producing it. This also aligns with keep it simple and practical, which says to eliminate what provides no value.

A team is asked where to begin an improvement. Applying 'start where you are', they should first:

• a.Assess and measure the current situation objectively to understand what exists and can be reused✓
• b.Automate the existing process straight away without pausing to look at it
• c.Discard all of the current services entirely and rebuild everything from nothing and the guiding principles do not need to be considered in this case
• d.Assume that the current state simply matches an old report they read before

Start where you are advises assessing the current state objectively before acting, so the organization understands what already exists and can be reused. Rather than assuming or rebuilding blindly, the team should look at current services, processes, people, and tools, because these often already provide significant value.

Why does 'start where you are' recommend observing and measuring the current state directly?

• a.Because measurement is only ever required for processes that are automated
• b.Because written reports are always more accurate than any direct observation and the same rule is applied in exactly the same way by every organization
• c.Because the current state has no bearing at all on future decisions anyway
• d.Because relying on reports or assumptions can be misleading, so direct observation gives more accurate evidence✓

Start where you are recommends measuring directly wherever possible, because reports and second-hand accounts can be inaccurate or biased. Direct observation gives more reliable evidence about the current state, so decisions about what to keep, change, or discard are based on facts rather than assumptions.

A team wants to solve a problem by buying entirely new tools, ignoring capable systems they already own. Which principle challenges this, and how?

• a.Start where you are, because it says to look at what already exists and can be leveraged before acquiring something new✓
• b.Keep it simple and practical, because it says to always buy the newest option
• c.Optimize and automate, because it says to automate a process before assessing it
• d.Focus on value, because it says that features always matter more than value does

Start where you are advises against building or buying from scratch without first considering what is already available to be leveraged. Existing systems may already provide much of what is needed. Assessing and reusing them where appropriate avoids wasted spending and preserves valuable existing capabilities.

A team reuses an existing, well-functioning approval process for a new service instead of designing a new one. Which principle does this reflect?

• a.Keep it simple and practical, which removes anything that adds no value
• b.Start where you are✓
• c.Optimize and automate, which optimizes a process before it is automated
• d.Collaborate and promote visibility, which involves the right stakeholders

Reusing an existing, well-functioning process rather than designing a brand-new one reflects start where you are, which advises leveraging what already exists and provides value. Assessing current capabilities and building on them, instead of starting over, saves effort and preserves proven ways of working.

Applying 'progress iteratively with feedback', how should a large initiative be structured?

• a.As a fully automated program that requires no human input or review at all
• b.As a series of smaller, manageable iterations, each informed by feedback and completed in a timely manner✓
• c.As one single enormous release that is delivered all at once at the very end
• d.As a project with no reviews of any kind until it is entirely and fully finished

Progress iteratively with feedback recommends dividing work into smaller, manageable iterations that can be executed and completed in a timely manner. Feedback is sought before, during, and after each iteration, keeping the work relevant and allowing quick response to change. This reduces risk and delivers value sooner.

When should feedback be gathered according to 'progress iteratively with feedback'?

• a.Before, during, and after each iteration, so the work stays relevant and can adapt✓
• b.Only once, right at the very end, after all of the work has been completed
• c.Never at all, so that the team's momentum is not interrupted or slowed down
• d.Only before any of the work has started, and then never again after that

Progress iteratively with feedback stresses using feedback loops throughout, before, during, and after each iteration. Continual feedback ensures the work remains focused and relevant, surfaces issues early, and lets the team adapt to changing needs. Feedback is central to the principle, not an afterthought at the end.

A team is tempted to deliver every improvement in a single massive change after two years of silent work. Which principle warns against this?

• a.Keep it simple and practical, which favours the minimum number of steps
• b.Progress iteratively with feedback✓
• c.Collaborate and promote visibility, which surfaces the true status of work
• d.Focus on value, which links every activity to value for the stakeholders

Delivering everything in one massive change after a long period of silence runs counter to progress iteratively with feedback, which recommends smaller iterations completed in a timely manner and guided by feedback. Iterative delivery reduces risk, provides value earlier, and lets the team respond to change.

A company pilots a new process in one region, gathers feedback, refines it, then rolls it out more widely. Which guiding principle does this illustrate?

• a.Think and work holistically, which coordinates the whole system together
• b.Start where you are, which assesses the current state before taking action
• c.Optimize and automate, which streamlines a process before automating it
• d.Progress iteratively with feedback✓

Piloting in one region, gathering feedback, refining, then expanding is a clear application of progress iteratively with feedback. The work is divided into manageable steps, and feedback from each step shapes the next. This reduces risk and ensures the wider rollout is based on real evidence rather than untested assumptions.

Applying 'collaborate and promote visibility', who should be involved in an improvement?

• a.No one at all outside the immediate team, in order to preserve total secrecy
• b.The right stakeholders whose involvement improves buy-in, relevance, and the likelihood of success✓
• c.Only the external suppliers, and never any of the internal members of staff
• d.Only the single most senior manager, working entirely alone on the improvement and this remains the case regardless of which service is being delivered

Collaborate and promote visibility emphasizes involving the right people in the right roles. Bringing in the relevant stakeholders improves buy-in, increases the relevance of the work, and raises the chance of long-term success. The emphasis is on the right collaboration, not simply more people.

Why does 'collaborate and promote visibility' stress making work and its status visible?

• a.Because poor visibility hides work and leads to poor decisions, whereas surfacing the true status enables better prioritization and trust✓
• b.Because work that stays completely hidden is always the most efficient kind and it holds true even when the surrounding circumstances change over time
• c.Because only managers, and no one else, should ever be able to see the work
• d.Because greater visibility is intended to slow the work down on purpose

Collaborate and promote visibility holds that insufficient visibility of work leads to poor decision-making and undermines trust. Making work, its flow, and its true status visible reduces hidden work, improves prioritization, and helps everyone make better decisions. Transparency is central to the principle.

Applying 'collaborate and promote visibility', how should information be communicated?

• a.Only ever through very long and highly formal written documents
• b.In exactly the same deep technical detail for absolutely every audience and no exceptions to this are ever recognized once the service is running
• c.In a way suited to each audience, using the right method and content so the message is understood and useful✓
• d.As little as is possible, in order to avoid revealing the true status

Collaborate and promote visibility recognizes that good collaboration requires good communication tailored to the audience. The method and content should suit each group so the message is understood and drives better decisions. One-size-fits-all or deliberately minimal communication undermines the collaboration the principle seeks.

A team publishes a shared dashboard showing the real-time status of all work in progress. Which guiding principle does this best support?

• a.Optimize and automate, which applies technology after streamlining work
• b.Start where you are, which assesses existing capabilities before acting
• c.Collaborate and promote visibility✓
• d.Keep it simple and practical, which uses the fewest steps that are needed

Publishing a shared dashboard that makes the real status of work visible to everyone directly supports collaborate and promote visibility. Surfacing work and its status reduces hidden work, improves shared understanding, and enables better, more collaborative decisions across the teams involved.

Which statement captures the core idea of 'think and work holistically'?

• a.Feedback should be actively avoided in order to keep the momentum going
• b.No service, practice, or component stands alone; outcomes suffer unless the whole system is coordinated✓
• c.Each individual team should optimize its own area completely independently and this is decided entirely by the provider without any consumer input
• d.The simplest single step will always, in every case, yield the most value

Think and work holistically recognizes that no service, practice, process, department, or supplier stands alone. The organization delivers outcomes only when it works as an integrated whole, coordinating all four dimensions and the elements of the service value system. Isolated, siloed optimization tends to undermine overall value.

'Think and work holistically' requires coordinating which of the following?

• a.All four dimensions of service management and the elements of the service value system, end to end✓
• b.Only the external suppliers that the organization happens to work with
• c.Only the incident management and problem management practices themselves
• d.Only the information and technology dimension, and none of the other three

Think and work holistically requires taking an end-to-end view, coordinating all four dimensions of service management and the interconnected elements of the service value system. Because everything is connected, a change or decision in one area can affect others, so the whole must be considered rather than any single part.

Why does 'think and work holistically' matter when changing one part of a service?

• a.Because only the specific area being changed ever needs any attention paid
• b.Because each area of a service is completely independent of all the others
• c.Because a change in one area can have effects, sometimes unintended, on other areas, so the whole system must be considered✓
• d.Because holistic thinking removes the whole need for feedback in the first place

Think and work holistically stresses that services and their components are interconnected. A change in one part, a process, a technology, a supplier, can ripple out and affect others, sometimes unintentionally. Considering the whole system when making changes helps avoid improving one area while harming overall value.

Two departments each optimize their own metrics, but overall service to the customer gets worse. Which principle was neglected?

• a.Start where you are, which assesses current capabilities before any action
• b.Progress iteratively with feedback, which divides work into small iterations
• c.Optimize and automate, which streamlines a process before automating it
• d.Think and work holistically✓

When departments optimize their own metrics in isolation and the end-to-end service deteriorates, the principle being neglected is think and work holistically. This principle warns that siloed, local optimization can undermine the whole. Outcomes are delivered only when the organization coordinates its parts as an integrated system.

Applying 'keep it simple and practical', how many steps should a process use?

• a.The minimum number of steps necessary to accomplish its objective✓
• b.As many separate steps as are possible, in order to be thorough and safe
• c.Exactly seven steps in every single case, matching the improvement model
• d.However many steps the newest and most advanced tool happens to require

Keep it simple and practical advises using the minimum number of steps necessary to accomplish an objective, taking an outcome-based approach. Adding unnecessary steps creates complexity and waste. Producing solutions that are as simple as they can be, while still effective, makes work easier to understand, perform, and improve.

According to 'keep it simple and practical', what should be done with an activity that produces no valuable outcome?

• a.Assign additional members of staff to it to make it look more important
• b.Add extra layers of control to the activity to try to justify keeping it
• c.Eliminate it, because anything that fails to provide value or a useful outcome should be removed✓
• d.Automate it as quickly as possible so that the waste simply happens faster

Keep it simple and practical says that if a process, service, action, or metric fails to provide value or produce a useful outcome, it should be eliminated. Removing what does not add value keeps work efficient and understandable. This is preferable to automating, padding, or over-staffing an activity that serves no real purpose.

'Keep it simple and practical' recommends taking which kind of approach?

• a.A tool-based approach that adopts every single new technology that appears
• b.A control-based approach that maximizes the total number of checks and gates and it is fixed at the outset and is never revisited again afterwards
• c.An outcome-based approach that produces practical solutions delivering valuable results✓
• d.A documentation-based approach that records every possible detail in writing

Keep it simple and practical recommends an outcome-based approach: focus on the results that need to be achieved and use the minimum steps necessary to reach them. Practical solutions that deliver valuable outcomes are preferred over piling on controls, tools, or documentation that add complexity without adding value.

An online form asks for 30 fields, most of which are never used. Applying 'keep it simple and practical', the team should:

• a.Remove the fields that serve no purpose, keeping only those needed to achieve the outcome✓
• b.Keep every single field on the form in case one is useful one day later
• c.Automate the collection of all thirty of the fields on the current form and every stakeholder is simply expected to accept it without any question
• d.Add still more fields to the form in order to capture even more data

Keep it simple and practical says to use the minimum number of steps (or here, fields) necessary and to eliminate anything that provides no value. Trimming the form to only the fields needed to achieve the outcome makes it simpler for users and easier to maintain, without losing anything of value.

According to 'optimize and automate', what must happen before a process is automated?

• a.The process should be automated immediately in order to save the most time
• b.The process should be documented in full but then never actually changed
• c.The process should first be optimized, so automation does not simply accelerate an inefficient way of working✓
• d.The process should be outsourced to an external supplier before anything else and it does not depend in any way on the consumer's own point of view

Optimize and automate says optimization should come before automation. Automating an inefficient or wasteful process merely produces that waste faster and at greater scale. The correct sequence is to make the process as effective and streamlined as it needs to be, and only then automate it so technology delivers maximum value.

What is the intended benefit of automation under the 'optimize and automate' principle?

• a.Freeing human resources from routine tasks so they can focus on more complex, higher-value work✓
• b.Replacing the need for all of the other ITIL 4 guiding principles entirely
• c.Removing every trace of human involvement from the organization completely and this stays true across the whole industry and all of its sectors
• d.Guaranteeing that no process will ever need to be reviewed again in future

Optimize and automate uses technology to reduce or remove the need for routine human intervention. The benefit is not to remove people entirely, but to free them from repetitive tasks so they can focus on more complex, judgement-based, and higher-value work. Automation should follow optimization to maximize this benefit.