ITIL ITIL-5-Foundation - ITIL Foundation (Version 5)

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 primary purpose of a product in ITIL is to offer value to consumers through a defined configuration of resources, so option A is correct. A product combines resources such as technology, people, information, processes, and partner capabilities in a way that is designed to create value. Services are often built on products, and products provide the structure and capabilities that services use to facilitate outcomes. Option C describes the purpose of a service more directly than the purpose of a product. Products do not replace service management practices, nor is compliance their primary purpose, even though compliance may be a requirement. ITIL integrates product and service management because products are central to how value is made possible, while services are central to how value is experienced and co-created through relationships.

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.

Digital services are always based on digital products, so option B is correct. In ITIL, a digital product is a combination of an organization’s resources based on digital technology and designed to offer value to consumers. A digital service uses those digital products to facilitate outcomes and support value co-creation. This means the product forms the technological and resource foundation for the service. The relationship does not work the other way around, so digital products are not based on digital services. They also do not exist independently in the context of digital service management, because products and services are integrated through the lifecycle and value system. Finally, digital products are not service actions. Service actions are provider activities, while products are configurations of resources. Therefore, digital services depend on digital products.

Support is the activity focused on minimizing the impact of incidents and disasters when they occur, so option C is correct. In ITIL, support includes helping users, restoring normal service, handling incidents, and responding to issues that affect service quality or continuity. Its purpose is not only to react, but to reduce disruption to users and customers as much as possible. Operate maintains live products and supporting systems, while support deals more directly with service interruptions and the human-facing aspects of restoring service. Transition introduces changed products into the live environment, and design defines solutions before they are built. By placing emphasis on rapid assistance, recovery, and user impact reduction, the support activity plays a crucial role in service resilience and in maintaining confidence during service failures or disruptions.

The main purpose of feedback during improvement iterations is to ensure that actions remain relevant and effective as circumstances change, so option B is correct. ITIL promotes iterative progress because environments, stakeholder needs, risks, and information often change during work. Feedback helps teams learn what is working, what is not, and what should be adjusted before moving further. It is not realistic to expect all stakeholders to fully agree at every point, and feedback does not eliminate the need for future adjustments. Instead, it supports better decisions, earlier correction, and more effective alignment with value. This approach reduces waste and improves adaptability. It is closely connected to the guiding principle “progress iteratively with feedback,” which encourages organizations to move in manageable steps and use learning continuously to refine outcomes.

A digital service enables value through the use of digital products, so option A is correct. ITIL explains that digital services largely or fully rely on digital products, which are combinations of an organization’s resources based on digital technology and designed to offer value. The service is what facilitates outcomes for consumers, while the product provides the underlying capabilities, technology, interfaces, data, and resources that make that possible. A digital product does not replace the need for services because service management is still required to support delivery, operation, support, and improvement. A digital service is not limited to internal IT systems, since it can serve internal or external consumers. It is also not independent of a digital product, because the product typically underpins the service relationship and service experience.

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.

The step being performed is “What is the vision?” so option A is correct. In the ITIL continual improvement model, this step establishes the desired direction and ensures that improvement work aligns with organizational goals and objectives. It answers the question of why the improvement matters and what strategic or stakeholder value it is meant to support. Without this first step, later activities may become disconnected from business priorities. “Where are we now?” assesses the current state. “Where do we want to be?” defines the target state more specifically. “Take action” is about implementation. Because the company is ensuring a clear link to goals and objectives before moving ahead, it is working at the vision stage. This creates alignment and gives improvement efforts a clear purpose and justification.