ITIL-5-Foundation ITIL Foundation (Version 5) Questions and Answers

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.

An incident is defined in ITIL as an unplanned interruption to a service or a reduction in the quality of a service. That is why option B is correct. The key idea is that an incident affects normal service performance and requires timely attention to restore expected service levels. Option A describes an event, which is any change of state that has significance for service management. Option C describes a problem, which is the cause or potential cause of one or more incidents. Option D refers more closely to a known error, defect, or vulnerability. ITIL separates these terms carefully because each one supports a different management activity. Incident management is focused on restoring service quickly, while problem management seeks deeper root causes and longer-term prevention.

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.

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.

Organizations should consider the interaction of the ITIL Guiding Principles because the principles are interdependent and complement one another, which makes option A correct. ITIL does not treat the principles as isolated rules or a strict sequence. Instead, they are meant to be applied together and balanced according to the situation. For example, focusing on value may need to be combined with thinking holistically, progressing iteratively with feedback, and keeping things simple and practical. In some situations, emphasizing one principle too strongly without considering the others may produce poor results. The real strength of the principles comes from their combined use in guiding decision-making, improvement, and behavior across different contexts. This flexible, balanced approach helps organizations respond effectively to complexity and change.

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.

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

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.

ITIL describes the guiding principles as something that should be used collectively and balanced based on the situation, which makes option D correct. They are not a checklist to follow in a rigid order, and they do not replace governance, practices, or other parts of the value system. Instead, they support decision-making and behavior across all circumstances. In one situation, focus on value may be especially important. In another, collaboration, iterative progress, or simplicity may need more emphasis. The point is that they work together. Applying one principle without considering the others can create imbalance or poor outcomes. This flexible approach allows the principles to remain useful across different industries, organizational types, and contexts. Their value lies in judgment, not mechanical sequence.

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.

Continuous deployment is distinct from continuous delivery because it automatically moves validated changes into the live production environment. That is why option C is correct. In continuous delivery, changes are integrated, tested, and made ready for release, but a deliberate business or operational decision may still be required before deployment to production. In continuous deployment, that final manual release decision is removed, and successful changes flow directly into use. This requires strong automation, testing discipline, monitoring, and confidence in the deployment pipeline. Option B is incorrect because continuous delivery does not require manual code integration; integration is normally frequent and automated. Option D is also wrong because testing becomes more important, not less. ITIL aligns these practices with modern value stream optimization and reliable change flow.

Monitor is the governance activity focused on ensuring adherence with policies, expectations, and strategic direction, which makes option C correct. In ITIL governance, evaluate is used to assess stakeholder needs, environmental conditions, and performance information. Direct is used to establish direction, priorities, and policies. Monitor checks whether actual performance, behavior, and results align with what has been directed and required. It is therefore the activity most closely associated with oversight, compliance, assurance, and accountability. Discover is not one of the governance activities in the ITIL Value System. Monitoring is essential because strategy and policies only create value when the organization confirms they are being followed and that the intended outcomes are being achieved. This keeps governance connected to performance, risk, and continual improvement.

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.

Transition is the activity that ensures new or changed products are introduced into the live environment in a controlled and seamless way, so option B is correct. In ITIL, transition bridges development and live operation. It includes planning releases, validating readiness, deploying changes, minimizing disruption, and confirming that the new or changed product can operate effectively in its target environment. Build focuses on creating or modifying solution components. Deliver is concerned with providing services to users. Operate is about maintaining and monitoring live products and systems. Transition is essential because even a well-designed and well-built product can fail if it is introduced poorly. ITIL therefore treats transition as a distinct lifecycle activity that protects service quality, reduces risk, and supports smooth adoption of changes by both technical teams and service consumers.

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.

Management practices are important because they enable value chain activities by providing the capabilities needed to perform them effectively, so option B is correct. In ITIL, value chain activities are high-level lifecycle activities such as discover, design, build, transition, operate, deliver, support, and acquire. These activities do not happen in isolation. They depend on practices such as architecture, incident management, change enablement, knowledge management, service level management, supplier management, and many others. Practices bring together people, information, technology, partners, and processes to support work in a structured and repeatable way. They do not define the organization’s overall purpose, and they do not force a fixed order of execution. Instead, they supply the organizational capability that allows value chain activities to function and connect effectively within the broader value system.

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.

The purpose of the support activity is to assist users and maintain service performance, so option A is correct. In ITIL, support focuses on helping users, managing incidents and issues, minimizing disruption, and sustaining acceptable service quality when problems occur. It works closely with other activities such as operate and deliver, but its emphasis is on responding to needs, restoring service, and reducing impact. Designing service architectures belongs to design. Building solution components belongs to build. Discovering new opportunities belongs to discover. Support is essential in maintaining trust and user confidence because it is often the activity users encounter most directly when something goes wrong or when they need help. Effective support contributes significantly to perceived service quality and the wider experience of service consumption.

A service journey describes the end-to-end interactions between a service provider and a service consumer, which makes option A correct. ITIL uses this concept to help organizations understand the full consumer experience across the stages of discovering, accessing, using, receiving support for, and continuing with a service. It includes visible touchpoints, interactions, perceptions, and moments that shape user experience and value realization. It is not the same as internal workflows, which belong more to value streams and processes. It is also not the same as the product lifecycle or the formal sequence of value chain activities. By understanding the service journey, organizations can improve service design, communication, support, and experience from the consumer perspective rather than only from an internal operational viewpoint.

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.