ITIL-5-Foundation Questions and Answers

A digital product is a combination of an organization’s resources based on digital technology and designed to offer value to consumers, so option C is correct. ITIL treats products as structured configurations of resources that can include software, infrastructure, data, interfaces, knowledge, and supporting capabilities. These products form the basis for digital services and help enable outcomes for consumers. Option A sounds more like a service offering description. Option B describes access to resources as a form of service relationship. Option D describes service actions. The digital product concept is important because it connects strategic intent, design, build, operation, and service delivery. It is not just a piece of software, but a managed combination of resources created to support value creation through technology-enabled services.

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.

A service level agreement is typically used to establish a shared understanding of expected and achieved service quality, so option B is correct. ITIL explains that service quality is often translated into service level metrics and documented through agreements between provider and customer. An SLA identifies the services covered, the agreed service levels, and how those levels will be measured and reviewed. This creates clarity around utility, warranty, sustainability, and experience expectations. A product specification describes product requirements, while service level requirements are usually inputs used to shape a future agreement rather than the formal shared understanding itself. Roadmaps show future direction and planning. Therefore, the SLA is the most appropriate mechanism for defining, communicating, and monitoring the agreed quality of a service relationship.

A digital service primarily exists to enable value co-creation by facilitating the outcomes that customers want to achieve. That is why option B is correct. In ITIL, a service helps consumers achieve desired outcomes without them needing to manage all the specific costs and risks themselves. A digital service does this through digital products, technology resources, service actions, and access mechanisms that support users and customers. Processes and workflows may help deliver the service, but they are not the service’s primary purpose. Likewise, compliance may be important, but it is a supporting requirement rather than the core role. ITIL consistently defines service management around value, outcomes, and stakeholder needs. Therefore, the central purpose of a digital service is to help consumers achieve meaningful results through managed, technology-enabled service relationships.

The information and technology dimension supports product and service management by enabling the data, information, and technology needed to create, deliver, support, and improve services. That is why option A is correct. ITIL emphasizes that this dimension includes applications, infrastructure, automation, analytics, AI, monitoring, communication tools, and the governance of information assets. It also includes data quality, usability, access, security, and technology capability. These elements help organizations make informed decisions, support workflows, and enable digital products and services. Roles and responsibilities belong primarily to organizations and people. Workflow structure belongs to value streams and processes. External relationships belong to partners and suppliers. Therefore, the dimension focused on the technological and informational foundation of management and service delivery is information and technology.

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 sponsor is the role that authorizes the budget for a service, so option C is correct. In ITIL, different stakeholders in a service relationship have different responsibilities. The customer defines requirements and is accountable for the outcomes of service consumption. Users are the people who actually use the service. The sponsor is the person or group that authorizes funding and provides financial support for the service. This role is important because value co-creation depends not only on usage and outcomes, but also on the commitment of resources needed to obtain and sustain the service. A product vendor may provide or support a product, but that does not automatically make them the budget authority in the consumer organization. Therefore, the sponsor is the role most clearly linked to budget authorization.

The guiding principle “collaborate and promote visibility” should be applied by involving stakeholders and sharing information with them, so option A is correct. ITIL stresses that good decisions and effective work depend on people understanding what is happening, why it matters, and how they can contribute. Collaboration helps bring together different perspectives, knowledge, and responsibilities. Visibility ensures that work, progress, risks, and priorities are transparent enough for informed participation and trust. Limiting communication to management weakens collaboration. Reusing existing processes relates more to “start where you are.” Capturing feedback after each iteration relates more closely to “progress iteratively with feedback.” This principle helps organizations reduce silos, improve coordination, and create a more shared understanding of how value is being created across the service relationship.

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.

A problem is the cause, or potential cause, of one or more incidents, which makes option B correct. ITIL clearly distinguishes problem management from incident management. Incident management focuses on restoring service quickly after an interruption or degradation. Problem management looks more deeply at why incidents happened and how similar incidents can be prevented in the future. This is why the root cause idea is central to the definition of a problem. An unplanned interruption is an incident, not a problem. A user request is a service request. A critical incident is still an incident, even if its impact is high. By separating incidents from problems, ITIL enables organizations to both restore service rapidly and reduce repeat disruption through analysis, learning, and long-term corrective actions.

The primary purpose of the acquire activity is to secure and allocate the necessary resources efficiently, so option B is correct. In ITIL, value creation depends on having the right people, technologies, suppliers, components, information, and services available when needed. The acquire activity supports this by sourcing, obtaining, and allocating resources in line with strategy, architecture, and operational demand. It may involve procurement, supplier coordination, access arrangements, or other forms of resource acquisition. Incident recovery belongs more to support. User onboarding belongs to deliver. Creating prototypes belongs to design. Acquire is important because value streams cannot perform effectively if critical resources are missing, delayed, poor in quality, or misaligned with requirements. It helps ensure that the organization has the inputs needed to build, operate, and improve products and services.

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.

Managing user onboarding is part of the purpose of the deliver activity, so option A is correct. ITIL explains that deliver focuses on providing services to users, maintaining service quality, managing onboarding and offboarding, and gathering consumer feedback. This activity is concerned with the actual provision of agreed services and the service relationship at the user level. Monitoring support systems belongs more to operate. Designing prototypes belongs to design. Obtaining supplier resources belongs to acquire. Deliver is especially important because it is where many users directly experience the service. User onboarding is a clear example because it involves enabling users to begin using the service properly, often including access setup, guidance, request fulfillment, and communication. This directly supports service consumption and the achievement of user outcomes.

A product specification primarily describes the critical aspects, requirements, and characteristics of a product, so option A is correct. It provides a formal reference that explains what the product must include, how it should perform, and what constraints or acceptance criteria apply. This helps create shared understanding among designers, developers, testers, managers, and other stakeholders. Option B describes a prototype, which is an early version used for exploration and validation. Option C refers more to resilience, reliability, or continuity rather than specification. Option D describes continuous integration practices in software delivery. In ITIL, the product specification is a key design artifact because it supports consistency through later lifecycle activities such as build, transition, operation, and improvement. It helps ensure that what is developed aligns with stakeholder needs.

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 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.

Service quality is most concerned with how well a service meets agreed requirements and expectations, so option A is correct. ITIL defines service quality as the sum of the characteristics of a service that are relevant to its ability to satisfy stated and implied needs. This means quality is broader than speed of incident resolution alone. It includes utility, warranty, sustainability, and user experience, depending on the context of the service relationship. Social responsibility may be part of sustainability, but it does not on its own define overall service quality. Likewise, rapid development does not guarantee quality. ITIL encourages organizations to translate expectations into service level metrics and manage the service accordingly. Therefore, service quality is fundamentally about meeting what has been agreed and what stakeholders genuinely need.

The main purpose of the discover activity is to align product capabilities with consumer needs and organizational strategy, so option C is correct. Discover is concerned with understanding the market, stakeholders, opportunities, constraints, and strategic direction before design and build work begins. It helps the organization identify what should be created or improved and why that matters. This includes gathering insights, understanding service consumers, exploring demand, and confirming relevance. Developing and testing products belongs more to build and related activities. Securing resources belongs to acquire. Maintaining and monitoring products belongs to operate. Discover is valuable because it reduces the risk of building the wrong thing and helps ensure that product and service decisions are grounded in value, context, and strategic fit rather than assumptions alone.

An organization’s purpose describes what it does for its consumers and other stakeholders and why it exists, so option D is correct. In ITIL, purpose provides the fundamental reason for the organization’s existence and connects its activities to value creation. It explains the broader intent behind products, services, and relationships. A value stream is a series of steps used to create and deliver value in a specific context. A value chain is the set of high-level lifecycle activities that enables value through products and services. An operating model shows how the organization arranges its capabilities, workflows, and resources to fulfill its purpose. Purpose is therefore the most foundational concept among these. It defines the “why,” while the other concepts describe how value is organized, managed, and delivered in practice.