ITIL emphasizes that value stream mapping identifies and visualizes how value flows, while value stream management ensures that the value stream performs effectively over time. That is why option A is correct. Mapping is a diagnostic and analytical activity. It helps organizations understand the current flow of work, information, handoffs, delays, bottlenecks, and opportunities for improvement. Management is broader and continuous. It involves monitoring performance, setting measures, coordinating improvements, adapting to changes, and maintaining the health of the value stream over time. Mapping is therefore one important tool within the larger discipline of management. The other options create false distinctions. ITIL applies both concepts across products and services, and neither one is limited only to reporting, auditing, cost, or risk. The real difference is analysis versus ongoing operational stewardship.

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.

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 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 correct answer is partners and suppliers because this ITIL dimension focuses on an organization’s relationships with external parties involved in creating, delivering, supporting, or improving products and services. These may include suppliers, strategic partners, outsourced providers, and other contributors in the wider service ecosystem. ITIL emphasizes that no organization operates alone, so managing agreements, dependencies, expectations, and collaboration with third parties is essential. This dimension also considers sourcing strategies, levels of integration, risk, capability availability, and service coordination across networks. The other dimensions focus on different areas: organizations and people addresses structure, culture, and competencies; information and technology addresses data and enabling technologies; and value streams and processes addresses workflows and how work is organized to create value. Therefore, external relationship management sits within partners and suppliers.

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 main risk is wasting time and losing valuable existing capabilities and resources, so option D is correct. The guiding principle “start where you are” encourages organizations to assess the current state before deciding what to change. Existing services, workflows, knowledge, technologies, relationships, and capabilities may already provide useful foundations for improvement. Ignoring them can lead to unnecessary effort, repeated mistakes, disruption, and the loss of things that were already working well. ITIL does not suggest preserving everything unchanged, but it does recommend understanding and reusing what is valuable before rebuilding. Starting over without evaluation can also damage morale and continuity. This principle helps organizations improve more intelligently by building on reality instead of assuming that total replacement is always the best answer.