ITIL4F ITIL Guiding Principles Practice Test 7 — 15 Questions

Question 1

A service owner is reviewing a process and removes several approval steps that were identified as not contributing to customer value. Which ITIL 4 guiding principle is being applied?

Accepted Answer

Keep it simple and practical. The 'Keep it simple and practical' guiding principle emphasizes eliminating unnecessary complexity, such as approval steps that do not contribute to customer value. By removing these steps, the service owner streamlines the process, reducing waste and improving efficiency without sacrificing quality or control.

Answer

Progress iteratively with feedback

Answer

Focus on value

Answer

Optimise and automate

Question 2

Which THREE of the following are correct descriptions of ITIL 4 guiding principles?

Accepted Answer

Keep it simple and practical: Eliminate steps that do not add value; if in doubt, leave it out.. The 'Keep it simple and practical' guiding principle emphasizes eliminating unnecessary complexity and steps that do not add value. The phrase 'if in doubt, leave it out' directly reflects the principle's focus on avoiding over-engineering and ensuring that processes remain lean and focused on outcomes.

Answer

From manual to automated: Always automate as much as possible to reduce human intervention.

Answer

Design from scratch: Rebuild processes from the ground up to ensure they are modern.

Question 3

Which TWO of the following scenarios best illustrate the 'Think and work holistically' guiding principle?

Accepted Answer

The service design team works with operations, security, and finance to ensure the service meets all requirements.. The 'Think and work holistically' guiding principle in ITIL 4 means understanding how all parts of an organization and its services interconnect and work together as a whole system. Option C is correct because the service design team collaborating with operations, security, and finance demonstrates cross-functional integration, ensuring the service meets all requirements rather than being designed in isolation. Option E is correct because considering the impact of a service update on all other services and stakeholders reflects a holistic view of how changes ripple across the entire service ecosystem. Option A is incorrect because solving incidents without documenting root causes is a siloed, reactive approach that ignores systemic learning and improvement. Option B is incorrect because focusing only on one department's goals while ignoring business needs is the opposite of holistic thinking, which requires alignment across the whole organization. Option D is incorrect because changing a database server without considering the application layer shows a narrow, component-level view rather than understanding interdependencies.

Answer

The service desk solves incidents without documenting root causes.

Answer

The IT team focuses only on their own department's goals and ignores the needs of the business.

Answer

A change is made to the database server without considering how it affects the application layer.

Question 4

Which ITIL guiding principle emphasizes the need to understand what the customer truly values before taking any action?

Accepted Answer

Focus on value. The 'Focus on value' guiding principle directs that all activities, services, and improvements should be directly linked to delivering value to the customer, as defined by the customer's own perception. Before taking any action, ITIL4F requires understanding what the customer truly values—whether it is uptime, speed, cost savings, or compliance—to ensure that every effort contributes to that outcome, not just technical metrics.

Answer

Start where you are

Answer

Keep it simple and practical

Answer

Progress iteratively with feedback

Question 5

A project team is redesigning the change management process. They decide to first review the current process documentation and interview staff to understand existing workflows before making any changes. Which ITIL guiding principle is being applied?

Accepted Answer

Start where you are. The team is starting by reviewing current process documentation and interviewing staff to understand existing workflows before making changes. This directly applies the 'Start where you are' guiding principle, which emphasizes basing improvements on the current state rather than designing from scratch or assuming a new process is needed.

Answer

Progress iteratively with feedback

Answer

Optimise and automate

Answer

Focus on value

Question 6

A software development team is working on a new feature using two-week sprints. After each sprint, they demo the feature to stakeholders and incorporate feedback into the next sprint. Which TWO ITIL guiding principles are being applied?

Accepted Answer

Progress iteratively with feedback and Collaborate and promote visibility. The scenario explicitly describes two-week sprints where the team demos the feature to stakeholders and incorporates feedback into the next sprint. This directly applies the 'Progress iteratively with feedback' principle by using short, iterative cycles with continuous feedback loops, and the 'Collaborate and promote visibility' principle by involving stakeholders in demos and making progress visible. The other options either miss the iterative feedback loop or introduce principles not demonstrated in the given workflow.

Answer

Focus on value and Start where you are

Answer

Keep it simple and practical and Optimise and automate

Answer

Think and work holistically and Focus on value

Question 7

Which of the following is an example of an OUTPUT rather than an OUTCOME?

Accepted Answer

A deployed software update. In ITIL 4, an output is a tangible, deliverable result of an activity, such as a deployed software update. An outcome, by contrast, is the value or benefit realized from that output, like improved productivity or satisfaction. Option A is correct because the deployed update itself is a direct, measurable artifact, not the subsequent effect on users or processes.

Answer

Improved employee productivity

Answer

Increased customer satisfaction scores

Answer

Reduced number of incidents

Question 8

According to ITIL 4, which guiding principle advises that ‘if in doubt, leave it out’?

Accepted Answer

Keep it simple and practical. The guiding principle 'Keep it simple and practical' directly advises that if a process, service, or improvement step adds unnecessary complexity without clear value, it should be omitted. The phrase 'if in doubt, leave it out' is a well-known ITIL 4 mantra for this principle, emphasizing that simplicity reduces waste, risk, and overhead in service management.

Answer

Optimise and automate

Answer

Focus on value

Answer

Start where you are

Question 9

An IT team is implementing a new monitoring tool. They choose to integrate it with the existing ticketing system rather than building a new one from scratch. Which principle is applied, and which principle might be overlooked if they don’t consider the impact on other tools?

Accepted Answer

Start where you are is applied; Think and work holistically might be overlooked. The team is reusing the existing ticketing system rather than building a new one, which directly applies the 'Start where you are' principle by leveraging current investments and processes. However, if they fail to assess how the new monitoring tool will interact with other tools (e.g., CMDB, notification services, or reporting dashboards), they overlook 'Think and work holistically,' risking integration failures, data silos, or performance degradation across the service value chain.

Answer

Keep it simple is applied; Focus on value might be overlooked

Answer

Collaborate is applied; Start where you are might be overlooked

Answer

Progress iteratively is applied; Optimise and automate might be overlooked

Question 10

A service desk team introduces weekly meetings where they share common issues and solutions. This is an example of which ITIL guiding principle?

Accepted Answer

Collaborate and promote visibility. The weekly meetings where service desk team members share common issues and solutions directly embody the 'Collaborate and promote visibility' guiding principle. This principle emphasizes that work should be made visible to all stakeholders and that collaboration across teams leads to better outcomes. By openly discussing recurring problems and their resolutions, the team increases transparency and collective knowledge, which reduces silos and improves overall service quality.

Answer

Think and work holistically

Answer

Focus on value

Answer

Progress iteratively with feedback

Question 11

When a change is classified as ‘normal’ in ITIL, what does that mean?

Accepted Answer

It is a change that is not pre-approved and needs assessment by a change authority. In ITIL 4, a 'normal' change is the default category for changes that are not pre-approved (standard) or emergency. These changes require assessment by a change authority before implementation, as they do not follow a pre-defined, low-risk procedure. Option C correctly captures this requirement for evaluation and approval.

Answer

It is a low-risk change that follows a pre-approved procedure

Answer

It is a change that does not require any approval

Answer

It is an emergency change that must be implemented quickly

Question 12

Which ITIL guiding principle states that services should be treated as complex systems where changes in one area can affect the whole?

Accepted Answer

Think and work holistically. The ITIL guiding principle 'Think and work holistically' emphasizes that services are complex systems with interdependent components, where a change in one area (e.g., a configuration item or process) can have cascading effects on the entire service value system. This principle directly addresses the need to consider the whole system, not just isolated parts, to avoid unintended consequences.

Answer

Start where you are

Answer

Focus on value

Answer

Progress iteratively with feedback

Question 13

Which TWO of the following are true regarding the 'Optimise and automate' principle?

Accepted Answer

Automation can free up people for more complex tasks. Automation, when applied after optimization, reduces manual effort for repetitive tasks, freeing people to focus on complex, value-adding activities like problem-solving and innovation. This aligns with the ITIL 4 guiding principle 'Optimise and automate,' which emphasizes that automation should be applied to optimized processes to maximize efficiency and human potential.

Answer

Only technical activities should be automated

Answer

All manual steps should be automated immediately

Answer

Automation should be applied before optimization

Question 14

Which THREE of the following are differences between Utility and Warranty?

Accepted Answer

Warranty covers availability, capacity, and continuity. Warranty in ITIL 4 is defined as the assurance that a service will meet agreed requirements, covering availability, capacity, and continuity. These are the specific dimensions that warranty guarantees, ensuring the service is reliable and sufficient in its delivery. Utility, by contrast, focuses on functionality and performance.

Answer

Warranty ensures the service is fit for purpose

Answer

Utility is more important than warranty

Question 15

Which TWO of the following are examples of applying the 'Progress iteratively with feedback' principle?

Accepted Answer

Implementing a change in phases and gathering user feedback after each phase. Option A is correct because implementing a change in phases and gathering user feedback after each phase embodies the 'Progress iteratively with feedback' principle: work is broken into smaller increments, and feedback from each phase informs the next, reducing risk and enabling course correction. Option D is correct because two-week sprints with daily stand-ups and sprint reviews are a concrete agile implementation of iterative progress with continuous feedback loops, where each sprint delivers a usable increment and reviews capture stakeholder input. Option B is not correct because a big-bang rollout to all users at once is a waterfall-style, non-iterative approach that delays feedback until after full deployment. Option C is not correct because skipping testing removes the feedback and quality-control mechanisms that iterative delivery depends on. Option E is not correct because a single annual release with extensive testing is a long-cycle, non-iterative approach that provides no incremental feedback during the year.

Answer

Rolling out a new system to all users at once to avoid confusion

Answer

Skipping testing to speed up delivery

Answer

Releasing a major update once a year after extensive testing