ITIL-5-Foundation Sample Questions Answers

The organizations and people dimension contributes by ensuring that skills, culture, structure, leadership, and communication support value creation, so option A is correct. ITIL emphasizes that effective product and service management depends not only on processes and tools, but also on human capability and organizational behavior. This dimension includes roles, responsibilities, authority, competencies, culture, collaboration, psychological safety, and continual learning. When these elements are healthy and aligned with strategy, teams are better able to make decisions, adapt to change, manage complexity, and work across boundaries. Defining technologies belongs to information and technology. Managing external relationships belongs to partners and suppliers. Automating workflows relates more to process and technology considerations. Therefore, the human and cultural foundation of effective management is the organizations and people dimension.

Continuous integration is the practice of regularly merging code into a central repository, typically supported by automated builds and tests, so option B is correct. Its purpose is to detect integration issues early, improve quality, and support a smoother flow of changes through the build and transition activities. By integrating frequently, teams reduce the risk and complexity that arise when many changes are combined late. Automated testing and validation are essential because they provide fast feedback and confidence that the new code still works as expected. Option A describes continuous deployment rather than continuous integration. Options C and D do not match the ITIL or software delivery meaning of the term. Continuous integration supports value stream performance by making change safer, faster, and easier to manage.

The band of visibility represents the aspects of service interaction that are visible between the provider and consumer organizations, so option C is correct. In ITIL, it helps distinguish visible interactions from internal activities that occur behind the scenes within either organization. This makes it useful for understanding service relationships, responsibilities, interfaces, and experience. It is not limited to the provider’s view alone, nor is it restricted only to modern digital services. It also does not equal the full service journey, because the journey covers the broader end-to-end experience of the consumer across many interactions and stages. The band of visibility is specifically about what can be seen and experienced across organizational boundaries. This clarity helps in designing services, managing expectations, and improving collaboration.

The governing body is accountable at the highest level for the organization’s performance and compliance, so option A is correct. In ITIL, governance ensures that the organization is directed and controlled in a way that aligns with stakeholder expectations, legal and regulatory obligations, and strategic objectives. The governing body does not usually perform day-to-day operations or manage technical product details directly. Instead, it evaluates the environment and stakeholder needs, directs priorities and policies, and monitors performance and conformance. Financial reporting may be one concern, but governance is much broader and includes value creation, risk, compliance, ethics, and strategic oversight. This high-level accountability is essential because it connects leadership intent with responsible management and assures stakeholders that the organization is being guided appropriately.

Trying to design a workflow for every possible exception usually creates unnecessary complexity, so option B is correct. ITIL explains that organizations operate in contexts of varying complexity and should avoid over-engineering workflows in an attempt to control every scenario in advance. Highly detailed procedures may appear thorough, but they can become hard to understand, slow to use, difficult to maintain, and ineffective when real conditions change. Instead, ITIL recommends designing processes as practical high-level courses of action, supported by situational judgment and continual adaptation. Excessive detail can reduce agility and make work less efficient without improving value. Strong risk control comes from appropriate governance, visibility, learning, and resilience, not from trying to predict every possible exception. Therefore, over-designing workflows tends to add waste rather than improve performance.

This commitment represents sustainability, so option D is correct. ITIL includes sustainability as one of the important categories of service level and service quality consideration. It refers to the assurance that a product or service meets requirements related to environmental stewardship, social progress, and economic growth. Examples include responsible sourcing, low carbon footprint, use of recycled or recyclable materials, clean energy, ethical employment practices, and transparent supply chains. Utility is about what the service does. Warranty is about how well it performs. User experience is about how the user perceives interactions with the service and provider. Since the scenario specifically mentions recyclable components, emissions reduction, and supply chain transparency, it clearly reflects sustainability as defined in ITIL 5.

The organizations and people dimension is directly influenced by leadership commitment to psychological safety and continual learning, so option D is correct. ITIL explains that culture, leadership, skills, communication, structure, and behavior all sit within this dimension. A psychologically safe environment allows people to speak up about risks, learn from mistakes, ask for help, and contribute ideas without fear. Continual learning strengthens competence, adaptability, and improvement. These factors shape how teams work together and how effectively they can support value creation. While all dimensions can be affected indirectly by leadership, this one is most directly concerned with the human and cultural side of management. Partners and suppliers focuses on external relationships, information and technology on technical enablement, and value streams and processes on workflow design and coordination.

Value streams and processes are important because they show how activities are coordinated to create and deliver value, so option B is correct. In ITIL, the value streams and processes dimension focuses on how work flows through the organization and across organizational boundaries. It helps explain the sequence of activities, dependencies, handoffs, and interactions that transform demand into useful outcomes for stakeholders. This is essential because value creation is rarely achieved by one team or one isolated activity. Tools, reporting lines, and contracts may support management, but they are not the main concern of this dimension. ITIL stresses that actual work as performed should be understood, mapped, analyzed, and improved. Value streams make the flow of value visible, while processes provide structured guidance for recurring activities that support that flow.

Value stream management is not one of the actual steps in value stream mapping, so option D is correct. In ITIL, value stream mapping typically includes identifying the value stream, mapping the current or “as-is” flow, analyzing bottlenecks and waste, and often designing an improved or “to-be” flow. These activities help an organization understand how work, information, and artifacts move across teams to create value. Value stream management is broader than mapping. It includes the ongoing governance, monitoring, optimization, and improvement of value streams over time. In other words, mapping is an important technique within the wider discipline of managing value streams. ITIL treats mapping as a way to visualize and analyze workflows, while management ensures performance, adaptation, and continual improvement of those workflows.

The customer takes responsibility for the outcomes of service consumption, so option C is correct. In ITIL, the customer is the person or organization that defines requirements and is accountable for the outcomes enabled by the service. This is different from the sponsor, who authorizes budget, and different from users, who interact with the service directly. The service provider is responsible for delivering and supporting the service, but it cannot fully control the consumer’s outcomes because those outcomes also depend on how the service is used within the consumer’s environment. This distinction is important in service relationships because value is co-created, not simply delivered one-way. By placing accountability for outcomes with the customer, ITIL reflects the shared nature of value creation and the need for active participation on both sides.

A key success metric for the acquire activity is the quality of the resources and services outsourced from suppliers, so option B is correct. Acquire is concerned with sourcing and allocating the inputs needed for value creation, including third-party services, components, technology, and other resources. Success therefore depends not only on speed and efficiency, but also on whether what is acquired is fit for purpose, reliable, and aligned with needs. Incident counts are more relevant to operate or support. SLA performance is more relevant to live service delivery. Negative impact of changes is more relevant to transition and change-related activities. ITIL views acquisition as a strategic and operational capability that supports the wider lifecycle. Poor-quality acquired resources create downstream problems, so quality is a strong and appropriate success measure.

The team is applying the guiding principle “progress iteratively with feedback,” so option C is correct. ITIL recommends moving in manageable steps rather than attempting to deliver everything in one large release. By releasing a small set of features first, the team reduces risk, gets faster learning, and avoids investing heavily in assumptions that may prove incorrect. Gathering user feedback allows them to refine priorities and make the next release more valuable and relevant. This principle is especially useful in complex or uncertain environments where needs may evolve and outcomes cannot be perfectly predicted in advance. While focus on value and collaboration are also important here, the clearest principle illustrated is iterative progress supported by feedback. It helps improve adaptability, responsiveness, and overall service quality.

The best answer is utility because the question describes a service providing functionality that meets a need. Granting an employee permission to use a file-sharing platform enables them to store, access, and collaborate on information for daily work. In ITIL, utility is about what the service does and whether it is fit for purpose. The platform’s usefulness lies in giving the employee the capability they need. Access to resources may seem close, but the focus of the question is the practical value of the service capability being made available. Warranty would concern how well the platform performs, such as availability or security. Goods are physical or digital items transferred to the consumer. Since this example highlights useful functionality that supports work, utility is the strongest and most accurate answer.

The operate activity has the primary responsibility for maintaining and monitoring digital products and supporting systems, so option C is correct. In ITIL, operate focuses on keeping live products and supporting environments functioning effectively. This includes monitoring system behavior, managing events, maintaining performance, ensuring reliability, and responding to deviations that affect product operation. Deliver is about providing services to users, including onboarding and service-level fulfillment. Support helps minimize the impact of incidents, issues, and disasters on users and services. Transition introduces new or changed products and services into the live environment. Operate is therefore the activity most closely associated with ongoing product health and technical stability. It provides the operational foundation that allows services to be delivered consistently and value to continue flowing.

This situation shows transfer of goods and service actions, so option C is correct. The printer being delivered to the customer is an example of transfer of goods because a physical item is provided to the consumer. The ongoing maintenance and support are service actions because they involve activities carried out by the supplier to help the customer use the printer successfully and maintain service performance. Access to resources would apply if the customer were mainly using provider-owned resources under agreed terms, such as software access or shared infrastructure. A service journey is broader and refers to the end-to-end experience across interactions. ITIL identifies these interaction patterns to help organizations understand how value is co-created in different service relationships. In this case, both a physical transfer and ongoing provider activity are clearly present.

The dimension that addresses organizational and cross-organizational workflows is value streams and processes, so option D is correct. ITIL uses this dimension to focus on how work is organized, coordinated, and performed to enable value creation. It includes flows of activities, information, and artifacts within the organization and across organizational boundaries. This dimension is especially important because value is often created through complex interactions among multiple teams, suppliers, and systems. By understanding processes and mapping value streams, organizations can identify delays, bottlenecks, and waste while improving coordination and outcomes. Partners and suppliers focuses on external relationships, organizations and people focuses on structure and skills, and information and technology focuses on enabling systems and data. The workflow dimension is therefore value streams and processes.

The best explanation is that the organization’s purpose determines why it exists, while the operating model shows how it fulfills that purpose, so option B is correct. In ITIL, purpose provides the reason for being, the value intent, and the basis for strategic direction. The operating model then describes how the organization arranges its capabilities, workflows, resources, practices, and interactions to turn that purpose into real value. These two concepts are closely connected. The operating model does not replace purpose, and it is broader than only financial strategy. It also cannot be separated from customer and stakeholder concerns because its whole role is to support value creation. By linking purpose and operating model, ITIL helps organizations align intent, structure, behavior, and execution in a coherent way.

The most appropriate metric for assessing the success of the build activity is the quality of the product solutions, so option D is correct. Build is concerned with creating or modifying solution components so they are fit for intended use in later lifecycle stages. Measures for build therefore focus on the quality, completeness, maintainability, and suitability of what is produced. The other options are associated with different activities. Incident resolution within targets is more relevant to support. Customer satisfaction after service delivery is more relevant to deliver and service experience. First-contact fulfillment is also a service delivery or support measure. ITIL encourages organizations to choose metrics that match the purpose of each value chain activity. Since build is about producing sound product components, the quality of those solutions is the clearest measure of success.

A service is perceived as valuable when its positive effects outweigh its negative effects for the consumer. That is why option C is correct. In ITIL, value is not defined only by what the provider delivers. It depends on the consumer’s perception of benefits, usefulness, and importance. Consumers evaluate whether the service helps them achieve desired outcomes while optimizing associated costs and risks. Even a technically strong service may be seen as low value if it is hard to use, unreliable, expensive, or creates unwanted effort. Conversely, a service with well-balanced utility, warranty, sustainability, and experience may be seen as highly valuable. Provider investment or internal efficiency alone does not determine value. ITIL places emphasis on outcomes and stakeholder perception, which is why consumer judgment about net positive effect is central.

Observability enables understanding of system behavior through outputs such as logs, metrics, and traces, which makes option A correct. In digital product and service management, observability helps teams detect patterns, diagnose issues, understand dependencies, and gain insight into how complex systems behave in real conditions. It supports faster analysis and better decision-making, especially in distributed or rapidly changing environments. It does not guarantee that incidents will be automatically prevented, and it is not primarily about approval of changes. Although observability can contribute to improved reliability, that is a result rather than the direct definition. ITIL’s emphasis on information and technology includes the use of monitoring and analysis capabilities to support operation and continual improvement. Observability is therefore a way to make system behavior visible and understandable.

ITIL considers outcomes, costs, and risks together because value is created when desired outcomes are achieved while associated costs and risks are optimized, so option A is correct. A service does not create value simply because it exists or because it provides functionality. Consumers evaluate value based on whether the service helps them achieve meaningful results and whether the effort, expense, constraints, and uncertainty involved are acceptable. If a service enables outcomes but introduces excessive risk or cost, value may be low. Likewise, minimizing risk without enabling outcomes does not create much value. This balanced view is central to ITIL’s definition of service value. It explains why service relationships must consider utility, warranty, experience, sustainability, and the wider context of service consumption rather than focusing on one factor alone.