Skip to content

ITIL 5 MP : ITIL Service (Domain 2)

ITIL 5 – Managing Professional : Certified ITIL Managing Professional - Domain 2 - ITIL Service (Version 5)

30 questionsmedium

The Evolution of Digital Product and Service Management (DPSM)

The transition from traditional IT service management to Digital Product and Service Management (DPSM) represents a fundamental shift in how organizations perceive and deliver value. In the ITIL (Version 5) framework, the focus moves beyond the mere maintenance of IT components to the comprehensive management of digital products throughout their entire existence. This evolution is driven by the complexities of a digital-first economy where value is no longer a one-way delivery but a process of co-creation between providers and consumers.

Digital products are characterized by their integration of technology, data, and connectivity to fulfill specific needs. Under the DPSM model, the service relationship involves several distinct entities: the organization, the service provider, the service consumer, and the digital product vendor. The framework establishes a common language to bridge these roles, ensuring that products are not just functional but are aligned with the strategic objectives of the business and the lived experiences of the users.

Value co-creation serves as the central pillar of this new domain. It recognizes that a service provider cannot produce value in isolation; instead, value is realized when the consumer utilizes the service to achieve their desired outcomes. This relationship is further refined by the concepts of utility (what the service does or its fitness for purpose) and warranty (how the service performs or its fitness for use). Version 5 expands these traditional concepts to include user experience and sustainability, acknowledging that modern digital services must be ethically sound and human-centered to maintain long-term viability.

The ITIL Product and Service Lifecycle Model

The ITIL Product and Service Lifecycle Model is a structured yet dynamic framework designed to manage digital services from their initial conception to their eventual retirement. Unlike linear models, this lifecycle encourages iterative progress and end-to-end accountability. The lifecycle is comprised of eight primary management activities:

  1. Discover: This initial stage focuses on identifying opportunities and requirements. It is informed by the organization’s vision, positioning, and existing portfolio. The goal is to ensure that any new service or product has a clear purpose and a defined path toward value creation.
  2. Design: During this phase, the concepts identified in discovery are translated into technical and operational blueprints. Design is not a siloed activity; it must be integrated into the subsequent build and transition stages to ensure consistency.
  3. Acquire: This activity addresses the procurement of necessary resources. The framework distinguishes between the acquisition of technology, the recruitment of people, and the engagement of third-party services, recognizing that each requires a different management approach.
  4. Build: In the build stage, the designs are converted into tangible digital products or service components. This phase emphasizes the practical application of design principles to create functional outcomes.
  5. Transition: Transition involves moving a product from the build environment into the live operational environment. It requires careful management to ensure that new services do not disrupt existing operations and that all stakeholders are prepared for the change.
  6. Operate: This is the ongoing activity of ensuring that the product performs as intended in the live environment. It involves monitoring, maintenance, and the immediate resolution of issues to maintain service stability.
  7. Deliver: Delivery is the point of contact where the service provider enables value co-creation for the consumer. It is the active provision of the service offering.
  8. Support: The support activity ensures that users can continue to derive value from the service. It focuses on assisting consumers when they encounter difficulties and gathering feedback for future improvements.

These activities do not exist in a vacuum; they are supported by the organization’s value chain activities and management practices, creating a cohesive system for service delivery.

Delivering Resilient and Scalable Digital Services

In modern, complex environments, the ability to deliver services that are both resilient and scalable is a core requirement of the ITIL Service domain. Resilience refers to the capacity of a digital service to maintain its functions and recover quickly from disruptions, while scalability ensures that the service can handle increasing demands without a loss in performance.

Resilience is embedded throughout the lifecycle, particularly in the Design and Operate activities. By emphasizing end-to-end accountability, the framework ensures that service providers are responsible for the performance of the service across all boundaries, including those involving third-party cloud platforms and external partners. Scalability is achieved through the integration of automation and AI-enabled tools, which allow services to adapt dynamically to changing business needs.

The framework highlights that high-quality, reliable services are the result of breaking down organizational silos. Cross-functional collaboration is essential to ensure that the technical aspects of a service (utility and warranty) are balanced with the relational aspects (user experience). When services are designed with resilience and scalability in mind, they can support the organization’s broader business strategy and remain competitive in a rapidly shifting digital landscape.

Managing Multi-Supplier Orchestration and Service Ecosystems

Modern service delivery rarely happens within a single organization. Instead, it takes place within vast ecosystems that include cloud platforms, specialized partners, and multiple external providers. ITIL (Version 5) provides practical guidance for managing this multi-supplier orchestration, ensuring that end-to-end accountability is maintained even when components of a service are outsourced.

The framework identifies three primary types of service relationships that define these interactions:

  • Basic: A standard provider-consumer relationship focused on the exchange of services for a fee.
  • Cooperative: A deeper level of engagement where both parties work together more closely to align their goals.
  • Collaborative (Partnership): A high-trust relationship where the provider and consumer act as partners, sharing risks and rewards to co-create maximum value.

Orchestration in this context requires the coordination of internal teams and external suppliers to ensure a seamless experience for the end-user. This involves aligning various provider perspectives and ensuring that third-party service levels are integrated into the organization’s overall service architecture. Effective orchestration prevents “service gaps” that often occur at the boundaries between different vendors, ensuring that the total service offering remains coherent and effective.

Operational Resilience and Business Continuity

Operational resilience in ITIL (Version 5) is deeply connected to the “Operate” and “Support” activities of the lifecycle. It is defined by the organization’s ability to continue delivering services in the face of adverse conditions. This goes beyond traditional incident management; it requires a proactive approach to identifying potential points of failure and implementing mitigation strategies before they impact the consumer.

Business continuity is supported through the rigorous application of Critical Success Factors (CSFs) and specific metrics within the Operate activity. For a product operation to be considered successful, it must meet predefined quality standards and performance benchmarks. The framework suggests that resilience is not just a technical attribute but also an organizational one, fostered by a culture of psychological safety and trust.

When trust exists between providers and consumers, they can collaborate more effectively during service disruptions. This collaborative approach to resilience ensures that the organization can adapt its service delivery model to maintain business outcomes even during large-scale transformations or external crises. The integration of AI also plays a role here, providing predictive insights that allow teams to anticipate and mitigate risks to continuity.

Experience-Led Service Quality and Stakeholder Trust

A major enhancement in Version 5 is the elevation of experience as a core driver of service quality. Digital experience is defined as the holistic response—emotional, cognitive, and bodily—of a person interacting with digital products and services. This includes their anticipation of the service, their perception during use, and their subsequent evaluation of the outcomes.

Experience-led decision-making recognizes that functional success (the service “working”) is insufficient if the user feels frustrated or disengaged. Trust is the currency of these relationships. The framework outlines several stakeholder roles on both the consumer and provider sides, each with different trust requirements:

  • Consumer Side: Includes the User (who interacts with the service), the Customer (who defines the requirements), and the Sponsor (who authorizes the budget).
  • Provider Side: Includes the Agent (who delivers the service), the Principal (who is accountable), the Provider Sponsor, and the Enabler (who supports delivery).

Tensions often arise between these stakeholders, such as when a customer’s budget constraints conflict with a user’s need for high-end functionality. Experience management seeks to identify these tensions and use “experience signals”—evidence gathered from interactions—to improve the service. Positive experiences build advocacy and loyalty, while negative experiences create distance and risk the consumer’s departure.

Advanced SLA Architectures and Service Level Management

Traditional Service Level Agreements (SLAs) often focus purely on technical uptime, leading to the “watermelon effect” where metrics appear green but the user experience is “red” (poor). ITIL (Version 5) advocates for advanced SLA architectures that distinguish between functional and relational interaction drivers.

Service Level Management in this context involves mapping the entire stakeholder journey using the ITIL Service Journey Model. This model helps organizations identify distinct “experience moments” across the lifecycle, from the initial discovery of a service to its daily operation. By aligning agreements with these moments, providers can ensure that service levels reflect what truly matters to the consumer.

Advanced architectures also incorporate “experience domains,” which provide a broader view of service quality than traditional metrics. These domains allow for the collection of experience evidence through various tiers and tools, ensuring that the data used to evaluate service levels is both trustworthy and coherent. This approach moves the conversation from “did we meet the technical target?” to “did we deliver the intended value and experience?”

AI-Enabled Service Operations and the AI Capability Model

The integration of Artificial Intelligence (AI) is a defining feature of ITIL (Version 5) service operations. AI is not merely a tool but a capability that transforms how services are captured, measured, and improved. The framework introduces the AI Capability Model to help organizations understand how to leverage AI ethically and effectively.

AI supports service operations in several ways:

  • Experience Capture: AI tools can analyze vast amounts of data to identify signals and patterns in user sentiment that would be impossible for humans to detect manually.
  • Automation: Routine tasks within the Operate and Support stages can be automated, allowing human agents to focus on complex, relational interactions.
  • Predictive Maintenance: AI can anticipate service failures before they occur, enhancing the resilience and reliability of the service ecosystem.
  • Agentic AI: The use of intelligent agents that can act autonomously within defined governance parameters to optimize service delivery.

However, the use of AI introduces new requirements for governance and digital ethics. Organizations must ensure that AI-driven decisions are transparent, accountable, and do not compromise human dignity. The AI Capability Model provides a lens through which organizations can evaluate their AI maturity and ensure that their use of technology remains aligned with the ITIL Guiding Principles.

Value Stream Mapping and Integrated Management Practices

Value streams are the sequences of steps an organization takes to create and deliver value to its consumers. In ITIL (Version 5), value stream identification, mapping, and management are essential for understanding how different parts of the organization contribute to the final service offering.

Mapping a value stream involves looking at the end-to-end journey of a product or service and identifying where value is added and where waste or “friction” occurs. Frictions might include broken expectations, unclear agreements, or ineffective reflection loops. By removing these frictions, organizations can streamline their operations and improve both the speed and quality of delivery.

The framework emphasizes that management practices—such as Incident Management, Change Enablement, or Knowledge Management—are most effective when they are integrated into these value streams rather than functioning as isolated departments. This integration ensures that practices support the dynamic needs of the product and service lifecycle. For example, the “Design” activity is supported by various practices that ensure the resulting product is not only functional but also maintainable and aligned with the broader service portfolio.

Governance, Ethics, and Continual Improvement in Service Delivery

Governance in ITIL (Version 5) is described as an “enabling” function. Its purpose is to provide the direction and control necessary to ensure that the organization’s activities remain aligned with its strategic goals and ethical standards. In the context of digital services, this includes AI governance, digital ethics, and sustainability.

Continual improvement is the heartbeat of the ITIL Value System. The framework introduces a specific model for experience improvement consisting of four modes:

  1. Notice: Actively gathering signals and evidence of the current state.
  2. Interpret: Analyzing the evidence to understand the underlying causes of a situation.
  3. Hypothesize: Proposing potential improvements based on the interpretation.
  4. Experiment: Testing the hypotheses in a controlled manner to see if they lead to the desired outcomes.

This iterative cycle ensures that improvements are data-driven and focused on enhancing both the system’s performance and the stakeholders’ experience. By applying this model across all four dimensions of service management—Organizations and People, Information and Technology, Partners and Suppliers, and Value Streams and Processes—organizations can foster a culture of resilience and sustainable change.

Practice Section

Short-Answer Questions

  1. What are the four primary dimensions of product and service management in ITIL (Version 5)?
  2. Define the concept of “value co-creation” in the context of service relationships.
  3. List the eight activities of the ITIL Product and Service Lifecycle Model.
  4. How does Version 5 define “digital experience”?
  5. What is the difference between “utility” and “warranty”?
  6. Identify the three roles within the consumer stakeholder group.
  7. What is the primary purpose of the “Discover” activity in the service lifecycle?
  8. Briefly describe the “Notice – Interpret – Hypothesize – Experiment” model.
  9. What is the role of the “Enabler” in a service provider organization?
  10. Why is “multi-supplier orchestration” important in modern service delivery?

Answer Key

  1. The four dimensions are Organizations and People, Information and Technology, Partners and Suppliers, and Value Streams and Processes. They ensure a holistic approach to service management by considering all factors that influence value creation.
  2. Value co-creation is the process where providers and consumers work together to realize value. It acknowledges that value is not a finished product delivered by the provider but is generated through the consumer’s use of the service.
  3. The eight activities are Discover, Design, Acquire, Build, Transition, Operate, Deliver, and Support. These represent the end-to-end management of a digital product or service.
  4. Digital experience is the holistic response—emotional, cognitive, and bodily—of a person to their interactions with digital products and services. It includes the person’s anticipations, perceptions, and evaluations of those interactions and their outcomes.
  5. Utility refers to the functionality offered by a product or service to meet a particular need (fitness for purpose). Warranty refers to the assurance that a product or service will meet its agreed requirements (fitness for use).
  6. The consumer roles are the User (uses the service), the Customer (defines requirements), and the Sponsor (authorizes the budget). Each role has different perspectives and needs regarding the service.
  7. The purpose of the Discover activity is to identify opportunities and requirements for new or changed services. It ensures that the organization’s vision and portfolio inform the creation of value.
  8. This is a continual improvement model focused on experience. It involves noticing signals, interpreting their meaning, forming hypotheses for improvement, and conducting experiments to validate those hypotheses.
  9. The Enabler is a stakeholder within the provider organization who supports the delivery of services. They provide the necessary resources, tools, or internal services that allow the primary provider to function.
  10. Multi-supplier orchestration ensures that services remain seamless and high-quality when delivered through a complex ecosystem of multiple vendors and cloud platforms. It maintains end-to-end accountability across organizational boundaries.

Open-Ended / Design Questions

  1. Designing for Resilience: You are tasked with designing a new digital banking service that must remain operational during high-traffic events. Using the ITIL Product and Service Lifecycle, describe how you would integrate resilience into the Design, Build, and Operate stages.
  2. Ecosystem Management: An organization is moving from a single internal IT department to a multi-vendor model involving three different cloud providers. Design a governance strategy that ensures end-to-end accountability and prevents “service gaps” between these providers.
  3. Experience Mapping: Select a common digital service (such as a ride-sharing app). Map the “experience moments” for both a User and a Sponsor across the Discover, Deliver, and Support activities of the lifecycle.
  4. AI Ethics Integration: Your organization plans to implement an AI-enabled chatbot for customer support. Develop a set of ethical guidelines based on the ITIL AI Capability Model to ensure the bot maintains customer trust and transparency.
  5. Value Stream Optimization: An organization is experiencing a high number of “frictions” (delays) when transitioning products from Build to Operate. Propose a value stream mapping initiative to identify these frictions and suggest two management practices that could be better integrated to improve the flow.

Glossary of Key Terms

  1. AI Capability Model: A framework used to evaluate and guide the responsible, ethical, and effective adoption of artificial intelligence within digital products and services.
  2. Agentic AI: A form of AI involving intelligent agents capable of acting autonomously to achieve specific goals within a service management context.
  3. Co-creation: The collaborative process where service providers and consumers interact to create value, rather than value being a one-way delivery.
  4. Digital Experience (DX): The holistic emotional, cognitive, and bodily response of an individual to their interactions with digital products, services, and the co-creating organization.
  5. Digital Product and Service Management (DPSM): An integrated approach to managing the full lifecycle of digital products and the services they enable, focusing on value and experience.
  6. Experience Domains: Specific areas of focus used to categorize and measure the quality of the stakeholder experience beyond traditional technical metrics.
  7. Experience Evidence: Data, signals, and qualitative information collected from service interactions used to evaluate and improve the digital experience.
  8. Friction: Any obstacle or inefficiency within a value stream—such as broken expectations or unclear agreements—that hinders the co-creation of value.
  9. ITIL Value System (VS): The core model of ITIL (Version 5) that describes how all the components and activities of an organization work together to enable value creation.
  10. Multi-supplier Orchestration: The coordination and management of multiple internal and external service providers to ensure seamless, end-to-end service delivery.
  11. Operational Resilience: The ability of an organization and its services to continue functioning and recover quickly when faced with disruptions or adverse conditions.
  12. Service Journey Model: A framework used to map the end-to-end path of a service relationship, identifying key touchpoints and experience moments for all stakeholders.
  13. Service Offering: A formal description of one or more services designed to address the needs of a target consumer group, including goods, access to resources, and service actions.
  14. Sustainability: The principle of ensuring that digital products and services are designed and delivered in a way that is ethically, socially, and environmentally responsible over the long term.
  15. Utility: The functionality or “fitness for purpose” of a product or service—what it does to meet a consumer’s needs.
  16. Value Stream: A series of steps an organization follows to create and deliver a product or service to a consumer, integrating various management practices and activities.
  17. Warranty: The assurance or “fitness for use” of a product or service, relating to how it performs in terms of availability, capacity, security, and continuity.

Leaderboard

No scores saved yet. Be the first!

30 Questions — ITIL 5 – Managing Professional : Certified ITIL Managing Professional - Domain 2 - ITIL Service (Version 5)

Expand any question to reveal the correct answer and explanation.

  1. 1 An organization is currently managing software product development through an Agile framework and IT service operations through a traditional process-oriented model. According to ITIL (Version 5), what is the primary structural tension this separate management creates?

    Consider the core innovation of the ITIL (Version 5) framework regarding software and operations.

    Isolated management leads to duplicated processes and fragmented customer experiences.

    The integrated digital product and service management (DPSM) paradigm is specifically designed to resolve the isolation that causes misaligned KPIs and inconsistent user journeys.

    • ✗ The separation prevents the organization from adopting any form of AI-native automation.

      While integration helps, AI can technically be applied in silos; the main issue described in the sources is the lack of a shared language and unified value streams.

    • ✗ It forces the organization to use sequential rather than iterative lifecycle activities.

      Traditional models can still be iterative; the tension arises from the lack of coordination between product engineering and service delivery functions.

    • ✗ It invalidates the utility and warranty of the service offerings provided to consumers.

      Utility and warranty remain valid concepts, but their effective delivery is hindered by fragmented internal management.

  2. 2 During which activity of the ITIL Product and Service Lifecycle Model (PSLM) does an organization focus on conducting structured customer discovery to prioritize backlogs and shape roadmaps?

    This is the first stage of the eight-stage lifecycle model.

    Discover

    The 'Discover' activity is explicitly defined as identifying opportunities and understanding customer needs to provide strategic direction.

    • ✗ Design

      Design focuses on creating the actual solutions that deliver value once the opportunities have been identified and prioritized.

    • ✗ Plan

      While planning occurs, ITIL (Version 5) replaces the high-level 'Plan' activity with more specific lifecycle stages like 'Discover'.

    • ✗ Define

      Terminology such as 'Define' is often part of general management, but 'Discover' is the official stage name in the eight-stage PSLM.

  3. 3 How does Site Reliability Engineering (SRE) integrate into the 'Build' activity within the ITIL (Version 5) Product module?

    Think about how engineering practices affect the continuous integration and delivery process.

    By embedding test automation and technical debt governance into the CI/CD pipeline.

    Integrating SRE into 'Build' ensures that reliability requirements and quality engineering are part of the development process.

    • ✗ By managing the end-user service desk to capture incident telemetry.

      Incident management is primarily part of the 'Support' activity, whereas SRE integration in 'Build' is focused on engineering-level reliability.

    • ✗ By conducting the final manual testing before a service is decommissioned.

      Decommissioning is part of the 'Retire' activity, and SRE emphasizes automation over manual testing.

    • ✗ By solely focusing on the procurement of third-party hardware resources.

      Procurement is handled in the 'Acquire' activity; SRE in 'Build' is concerned with the software and configuration quality.

  4. 4 In the context of ITIL (Version 5) Service, what distinguishes a 'Collaborative' service relationship from a 'Cooperative' one?

    Look for the keyword that implies a 'partnership' level of engagement.

    Collaborative relationships involve joint responsibilities and partnership agreements for value co-creation.

    Collaborative relationships are synonymous with partnerships where both parties share high levels of integration and shared outcomes.

    • ✗ Cooperative relationships are the only ones that allow for the transfer of goods.

      Goods can be transferred in various relationship types; the level of shared responsibility is the true differentiator.

    • ✗ Collaborative relationships are strictly internal between different departments of the same company.

      Collaborative relationships can exist between distinct organizations, such as a service provider and a strategic digital product vendor.

    • ✗ Cooperative relationships require no formal agreements or service level definitions.

      Even basic or cooperative relationships typically involve some form of agreement or defined service expectation.

  5. 5 What is the primary role of the 'Learning' layer within the four-layer ITIL Transformation Model?

    Consider how an organization adapts based on the data it gathers during a change.

    To facilitate the role of measurement, synthesis, and continuous evolution of the transformation process.

    The learning layer is one of the four layers (Governance, Positioning, Execution, Learning) focused on feedback and improvement.

    • ✗ To provide initial technical training for new staff members during the 'Build' phase.

      Technical training is a specific activity, whereas the 'Learning' layer is a broad governance and oversight component of the transformation itself.

    • ✗ To manage the legal procurement of external AI licenses and training data sets.

      Procurement is typically handled under the 'Governance' or 'Execution' layers depending on the context, not 'Learning'.

    • ✗ To serve as the final stage of the twelve-stage model where products are retired.

      The 'Learning' layer is a continuous component throughout the model, not a chronological final stage like 'Retire' in the service lifecycle.

  6. 6 Within the ITIL (Version 5) framework, what does it mean for a service to be 'AI-native'?

    Focus on the 'design from the outset' aspect of the term.

    The framework's practices and value streams are structured so AI can be integrated naturally to enhance decision-making.

    AI-native means the framework was designed from the outset with AI in mind, rather than adding it as an afterthought.

    • ✗ The service must be built entirely by AI agents without any human intervention.

      AI-native supports human-AI collaboration and responsible adoption, not the total removal of human oversight.

    • ✗ The organization must achieve the highest level of the AI Capability Model before beginning the lifecycle.

      The framework helps organizations reach maturity, but being AI-native refers to the structure of the guidance itself.

    • ✗ The service desk must be replaced by generative AI bots to meet the Foundation requirements.

      ITIL suggests AI can enhance the service desk, but the definition of AI-native is about the framework's core design.

  7. 7 Which lifecycle activity in the PSLM is specifically concerned with ensuring system state is monitored from launch through telemetry frameworks?

    This stage is the bridge between building a product and its daily operation.

    Transition

    The sources describe 'Controlled Transition and Observability' as coordinating deployments with telemetry to monitor the state from the moment of launch.

    • ✗ Operate

      While 'Operate' uses telemetry, 'Transition' is where the frameworks are first applied to a new or changed service at launch.

    • ✗ Acquire

      Acquire is about obtaining the resources needed; monitoring the launch state is part of moving into production.

    • ✗ Deliver

      Deliver focuses on fulfillment and service level management for active consumers, rather than the initial technical monitoring at launch.

  8. 8 According to the ITIL (Version 5) Service module, what is the purpose of 'Experience-Led Service Quality'?

    Think about the source of the data used to improve the service.

    To use user feedback and service interactions to drive human-centered support and design.

    Experience-led quality prioritizes how users perceive and trust interactions to influence overall service value.

    • ✗ To ensure that all service levels are met using automated technical metrics only.

      Experience-led quality often challenges purely technical metrics by incorporating human sentiment and perception.

    • ✗ To mandate that customers must design their own service journeys to reduce provider costs.

      Providers remain responsible for design, though they co-create value by understanding the customer's journey.

    • ✗ To provide a justification for increasing the cost of services that have high user satisfaction.

      The focus is on value and trust, not specifically on pricing strategies or cost increases.

  9. 9 When an organization uses the ITIL Continual Improvement Model, which of the following best describes the 'Notice – Interpret – Hypothesize – Experiment' sequence?

    This sequence relates to how an organization responds to experience signals.

    A set of experience improvement modes used to drive enhancements based on signals.

    This sequence is specifically mentioned as a way to drive experience improvements by reacting to evidence and testing changes.

    • ✗ The four official dimensions of product and service management.

      The four dimensions are Organizations/People, Information/Technology, Partners/Suppliers, and Value Streams/Processes.

    • ✗ The four layers of the ITIL Transformation Model.

      The transformation layers are Governance, Positioning, Execution, and Learning.

    • ✗ The mandatory sequence of the eight lifecycle activities in the PSLM.

      The PSLM activities are non-linear and iterative, not a rigid four-step experimental sequence.

  10. 10 What is a 'Digital Product Vendor' in the ITIL (Version 5) Service Relationship Model?

    Consider the difference between someone who creates a tool and someone who uses that tool to help a customer.

    An organization that provides digital products used by service providers to deliver services.

    The framework distinguishes between the vendor (who provides the product) and the service provider (who uses the product to deliver a service).

    • ✗ A internal department that only handles physical hardware maintenance.

      A digital product vendor deals with digital solutions, and the framework describes them as part of a broader ecosystem, not just internal hardware.

    • ✗ The end-user who purchases a service for personal use.

      The end-user is a 'User' or 'Consumer'; a vendor is a provider of a product or resource.

    • ✗ A government agency that regulates AI ethics and compliance.

      Regulators fall under 'External Factors' (PESTLE) or 'Governance' rather than being the 'Digital Product Vendor'.

  11. 11 In the context of the ITIL Value System, what is the 'Enabling Nature of Governance'?

    Think about how rules and direction can actually help people move faster and safer.

    Governance provides the direction and constraints that allow an organization to act with confidence.

    Governance is not just about control; it is described as enabling by providing the necessary alignment and oversight for value creation.

    • ✗ Governance automatically creates value without the need for management practices.

      Governance directs and monitors, but management practices are required to perform the actual work of creating value.

    • ✗ Governance enables the bypass of technical debt protocols for faster builds.

      Governance typically enforces debt protocols and quality standards to ensure long-term sustainability.

    • ✗ Governance is a secondary component that only becomes active during chaotic contexts.

      Governance is a core, continuous component of the ITIL Value System regardless of the organizational context.

  12. 12 Which of the following is an example of an 'Access to Resources' service offering?

    Consider the difference between a task performed for you and the right to use a tool.

    Providing a user with permission to use a cloud-based storage platform.

    Access to resources involves granting users the ability to utilize an infrastructure or platform under agreed terms.

    • ✗ Physically delivering a laptop to an employee's home address.

      This is an example of the 'Transfer of Goods,' as ownership or physical possession changes hands.

    • ✗ A technician performing a manual repair on a broken server.

      This is a 'Service Action,' where the provider performs a task for the consumer.

    • ✗ Creating a strategic vision for a digital transformation project.

      Vision creation is a management or transformation activity, not a specific service offering component like access to resources.

  13. 13 Under 'Service Relationship Management', what is the primary focus of 'SLA and Multi-Supplier Orchestration' in ITIL (Version 5)?

    Focus on the coordination of service levels across an ecosystem.

    Coordinating modern service level architectures across cloud providers and strategic partners.

    Orchestration ensures that the end-to-end service remains consistent even when multiple external vendors are involved.

    • ✗ Ensuring that every supplier uses the exact same project management software.

      While tool alignment helps, orchestration is about aligning outcomes and service levels across the ecosystem.

    • ✗ Replacing all third-party suppliers with a single internal delivery team.

      The focus is on managing complexity in multi-supplier environments, not necessarily consolidating them.

    • ✗ Providing the consumer with the direct contact information for every sub-contractor.

      Orchestration often involves the provider shielding the consumer from the complexity of the sub-contractors.

  14. 14 In the PSLM, which activity involves 'Personalization and Demand Forecasting' to ensure service fulfillment?

    Think about the stage where the service is actively provided to meet user requests.

    Deliver

    The 'Deliver' activity focuses on the ongoing delivery of the service, including fulfilling requests and managing demand.

    • ✗ Design

      Design creates the capability for personalization, but the actual forecasting and delivery occur in the 'Deliver' stage.

    • ✗ Acquire

      Acquire obtains the resources; 'Deliver' uses those resources to satisfy consumer demand.

    • ✗ Support

      Support focuses on restoring service when things go wrong, rather than the proactive management of demand and delivery.

  15. 15 Which transformation pattern type focuses specifically on the establishment of the oversight mechanisms for a change initiative?

    This pattern shares its name with one of the components of the ITIL Value System.

    Governance

    The 'Governance' pattern is one of the three patterns (Initiation, Governance, Execution) used to support transformation work.

    • ✗ Positioning

      Positioning is a layer within the model, not a pattern type; pattern types describe the flow of work.

    • ✗ Discovery

      Discovery is an activity in the PSLM, not a pattern type in the Transformation Model.

    • ✗ Synthesis

      Synthesis is part of the Learning layer's activities, not an overarching pattern type.

  16. 16 How does ITIL (Version 5) define 'Sustainability' in digital product and service management?

    Consider the three pillars of value: economic, environmental, and social.

    The ability of a service to satisfy business needs over the long term while managing environmental and social impacts.

    Sustainability is explicitly listed alongside utility and warranty as a key concept that contributes to value co-creation.

    • ✗ The purely technical metric of how many hours a server can run without overheating.

      This describes technical reliability or uptime, which is part of 'Warranty,' not the broader concept of sustainability.

    • ✗ The financial ability of a consumer to pay for a service indefinitely.

      Financial viability is part of 'Cost' and 'Value,' but sustainability in ITIL includes social and environmental factors.

    • ✗ A guarantee that the service will never be retired or decommissioned.

      All services eventually reach the 'Retire' activity; sustainability is about responsible management during its active life.

  17. 17 In the ITIL Transformation Model, what is the significance of 'Complexity Thinking'?

    Think about how a leader decides to act when the environment is unpredictable.

    It helps leaders choose the correct governance and execution patterns based on ordered, complex, or chaotic contexts.

    The model recognizes that different levels of stability require different approaches to transformation.

    • ✗ It is a technique for making code more difficult to hack by increasing its algorithmic complexity.

      This relates to cybersecurity or obfuscation, which is not what 'Complexity Thinking' refers to in the transformation guidance.

    • ✗ It requires every stakeholder to have a PhD in systems engineering before participating.

      The framework is for all professionals; complexity thinking is about organizational awareness, not academic prerequisites.

    • ✗ It is the stage of the lifecycle where the most expensive resources are acquired.

      Resource acquisition is part of the 'Acquire' lifecycle activity, which is separate from transformation methodology.

  18. 18 What is the primary purpose of the 'Transition' activity in the PSLM from a service provider perspective?

    Consider the step that happens right before a service is fully 'live' and operational.

    To ensure that new or changed products and services are effectively moved into the live environment.

    Transition acts as the bridge that manages the risk and technical requirements of deployment.

    • ✗ To find and acquire the staff needed to build the digital product.

      Finding and hiring staff is part of 'Acquire,' not 'Transition'.

    • ✗ To provide the final customer support for a service that is about to be retired.

      Support for active services is 'Support,' and ending a service is 'Retire'.

    • ✗ To conduct the initial discovery of what the customer might want in three years.

      Long-term identification of needs is part of 'Discover'.

  19. 19 Which of the following describes 'Value Stream Mapping' (VSM) as presented in ITIL (Version 5)?

    Focus on the optimization of the 'flow' of work.

    A technique used to identify and optimize the end-to-end flow of work by identifying bottlenecks and waste.

    VSM is a core part of the Version 5 syllabus to improve visibility and outcomes across the service lifecycle.

    • ✗ A geographic map showing where data centers and physical servers are located.

      This describes a physical or infrastructure map, not the conceptual flow of value through a process.

    • ✗ A list of the highest-paid employees in the IT organization.

      Value streams are about the flow of work and value, not individual compensation or personnel ranking.

    • ✗ A sequential timeline that forbids any iterative or non-linear activities.

      Value streams in ITIL (Version 5) are often complex and iterative, despite being mapped to show flow.

  20. 20 What is the role of 'Human-Centred Design' in the ITIL Product (Version 5) module?

    Think about techniques like empathy mapping used during development.

    Applying empathy mapping and prototyping to ensure products meet actual user needs and emotions.

    Human-centered design is a core capability for creating products that feel as good as they function.

    • ✗ Ensuring that only humans, and never AI, are allowed to write product code.

      The module actually encourages AI-enabled ways of working, while keeping the end result focused on human needs.

    • ✗ A legal requirement to include a photo of a human on every digital product's homepage.

      Design empathy is about functionality and experience, not specific graphical branding requirements.

    • ✗ Reducing the number of human support agents to save organizational costs.

      While automation is discussed, 'Human-Centred Design' focuses on the quality of the experience for the user.

  21. 21 In the ITIL AI Governance extension module, what is the purpose of the '6C AI governance model'?

    This model is mentioned in the context of ethics, trust, and risk management.

    To provide a structured approach for the responsible and compliant adoption of AI.

    The 6C model helps organizations manage risk, transparency, and accountability during AI scaling.

    • ✗ To limit an organization to only six concurrent AI projects at any time.

      Governance is about the quality and responsibility of adoption, not arbitrary project quantity limits.

    • ✗ To ensure that all AI models are written in the C programming language.

      The model refers to governance principles (like Compliance or Clarity), not specific programming languages.

    • ✗ To categorize the six distinct types of hardware processors required for AI.

      Hardware specifications are technical; the 6C model is a governance and capability framework.

  22. 22 What is the primary difference between 'Core' and 'Enabling' value streams?

    Think about which stream touches the end customer directly.

    Core value streams deliver value directly to consumers, while enabling streams support the internal organization.

    This distinction helps organizations prioritize and manage their internal versus external-facing work.

    • ✗ Core value streams are manual, while enabling streams are fully automated.

      Both types of streams can be either manual or automated; the difference is their ultimate target for value delivery.

    • ✗ Enabling value streams are only used during the 'Retire' activity of the lifecycle.

      Enabling streams support activities across the entire lifecycle, such as HR or legal support for build and delivery.

    • ✗ Core value streams are mandatory, while enabling streams are always optional.

      Enabling streams are often critical for the legal or operational success of core value streams.

  23. 23 Which management practice category in ITIL (Version 5) includes 'Deployment Management' and 'Software Development'?

    These practices require deep specialized technical knowledge of code and infrastructure.

    Technical Management Practices

    These practices focus on the technical engineering and delivery aspects of products and services.

    • ✗ General Management Practices

      General practices include things like Strategy or Portfolio management that apply across the whole business.

    • ✗ Service Management Practices

      Service practices include Incident or Problem management, which are more focused on operational support.

    • ✗ AI Management Practices

      While AI-enabled, these specific practices are classified under the 'Technical' umbrella in the standard framework.

  24. 24 How does 'Observability' differ from traditional 'Monitoring' in ITIL (Version 5) Product and Service management?

    Think about how we deduce what is happening inside a complex system without opening it.

    Observability focuses on understanding the internal state of a system based on its external outputs.

    Observability is a more modern approach, often linked with SRE, to manage complex, distributed digital environments.

    • ✗ Monitoring is only used for AI, while observability is for human-centric services.

      Both techniques can be applied to any service; observability is simply a more holistic and data-driven approach.

    • ✗ Observability requires a physical security guard to watch the server room at all times.

      The term refers to system telemetry and data analysis, not physical visual surveillance.

    • ✗ Monitoring is proactive, whereas observability is strictly reactive after a disaster.

      Both can be proactive; observability provides deeper insights that enable better proactive management.

  25. 25 In the twelve-stage ITIL Transformation Model, why is the 'Sequence' of stages important?

    Consider what happens if you try to execute a massive change without first setting up governance.

    To ensure that prerequisites for governance and learning are met before heavy execution occurs.

    Applying the stages in the correct sequence (e.g., Positioning before Execution) helps maintain alignment and reduce waste.

    • ✗ To comply with international laws that mandate alphabetical order for all IT processes.

      The sequence is based on best practices for change management, not alphabetical legal requirements.

    • ✗ Because the model is strictly linear and forbids returning to a previous stage.

      The model is iterative; while there is a logical sequence, feedback loops (from the Learning layer) are constant.

    • ✗ So that the most expensive consultants are only hired during the first three stages.

      The sequence is about project success and logical flow, not specifically about consultant scheduling.

  26. 26 What is the primary focus of the 'Support' activity in the PSLM?

    Think about what happens when a user calls with a problem.

    Restoring normal service and protecting customer value when incidents occur.

    Support is concerned with reactive and proactive measures to ensure the service remains available and useful.

    • ✗ Designing the initial prototype for a new digital product.

      Prototype design happens during 'Design' or 'Build' activities.

    • ✗ Managing the legal contracts with fourth-party cloud vendors.

      Vendor and resource management is part of 'Acquire' or 'Governance'.

    • ✗ Executing the final deletion of all data during decommissioning.

      Data deletion and decommissioning are part of the 'Retire' activity.

  27. 27 How do ITIL (Version 5) and DevOps complement each other in the management of the lifecycle?

    Consider how an organization might balance 'moving fast' with 'ensuring quality'.

    ITIL provides the governance and service mindset, while DevOps provides the delivery speed and technical practices.

    The frameworks are presented as complementary, not competing, to achieve both speed and stability.

    • ✗ DevOps replaces all ITIL practices, making the ITIL framework obsolete for digital organizations.

      ITIL (Version 5) is specifically designed to integrate with and support DevOps environments.

    • ✗ ITIL is only for hardware, while DevOps is only for software code.

      Both frameworks address the full digital product and service lifecycle holistically.

    • ✗ They are identical frameworks with different names used by different countries.

      They have distinct origins and focus areas but overlap in their goal of value creation.

  28. 28 What is the importance of 'Project Management' (like PRINCE2) within the ITIL framework?

    Think about how an organization handles a 'one-off' major effort versus daily operations.

    It provides the structured approach needed to deliver major changes or new products as distinct initiatives.

    ITIL practices often collaborate with project management to ensure lifecycle activities are controlled and successful.

    • ✗ It is a mandatory legal requirement for all AI-native organizations.

      While highly recommended and integrated, it is a management framework choice rather than a universal legal mandate.

    • ✗ It is used exclusively to manage the 'Support' activity when incidents occur.

      Project management is more often associated with 'Design,' 'Build,' and 'Transition' than routine incident support.

    • ✗ It replaces the need for the Continual Improvement Model.

      Continual improvement and project management are complementary; project management handles specific changes, while CI is ongoing.

  29. 29 In the context of Experience, what is the 'Experience Level Agreement' (XLA)?

    Consider what happens when a help desk meets all its time targets, but the user is still frustrated.

    An agreement focused on the human experience and outcomes rather than just technical performance metrics.

    XLAs supplement traditional SLAs by measuring sentiment, trust, and user journey quality.

    • ✗ A legal contract that guarantees a user will never feel unhappy while using a product.

      While they measure sentiment, an XLA is a management tool for improvement, not a legal guarantee of human emotion.

    • ✗ A technical specification for the minimum resolution of a digital display.

      This describes a technical hardware standard, which might influence experience but is not an XLA itself.

    • ✗ An agreement that only applies to external customers and never to internal employees.

      XLAs are equally applicable to employee experience (EX) and customer experience (CX).

  30. 30 Which of the following is a key Success Factor for 'Digital Product Management' in ITIL (Version 5)?

    Think about the integration between the people who make the product and the people who run the service.

    Aligning product-centric development models with operational service overlays.

    Ensuring that the product build remains compatible with how it is serviced and supported is critical for end-to-end value.

    • ✗ Ensuring that every product is retired exactly two years after its first launch.

      Product lifecycles vary; success is measured by value and alignment, not by arbitrary decommissioning dates.

    • ✗ Maintaining a complete separation between the engineers and the service desk.

      The framework actually aims to break down these silos to improve feedback and service quality.

    • ✗ Using only physical hardware resources to avoid the complexity of the cloud.

      The framework encourages modern operating models including cloud and automation to handle complexity.