Skip to content

ITIL 5 Foundation : The ITIL Value System (Domain 4)

ITIL 5 – Foundation : Certified ITIL Foundation - Domain 4 - The ITIL Value System

30 questionsmedium

Introduction to the ITIL Value System (SVS)

The ITIL Service Value System (SVS) represents the foundational architecture of ITIL 5, facilitating the transition from traditional IT Service Management (ITSM) to a comprehensive Digital Product and Service Management (DPSM) paradigm. This domain, which accounts for 40% of the ITIL 5 Foundation examination, focuses on the systemic interaction between various organizational components to ensure the co-creation of value in high-velocity, automated, and cloud-hosted environments.

The SVS is designed to overcome the organizational friction caused by the historic division between product creation and operational support. By integrating agile development models with robust operational governance, the SVS addresses the requirements of Industry 5.0, prioritizing human-centricity, organizational resilience, and sustainability. The system functions as a unifying model that coordinates corporate capabilities through five core components:

  1. Guiding Principles: Recommendations that guide an organization in all circumstances.
  2. Governance: The means by which an organization is directed and controlled.
  3. The Product and Service Lifecycle Model (PSLM): A set of interconnected activities that an organization performs to deliver a valuable product or service.
  4. Management Practices: Sets of organizational resources designed for performing work or achieving an objective.
  5. Continual Improvement: A recurring organizational activity performed at all levels to ensure that performance meets stakeholders’ expectations.

The Seven Guiding Principles: A Universal Foundation

The ITIL Guiding Principles are recommendations that guide an organization’s actions and decisions, regardless of changes in its goals, strategies, type of work, or management structure. In ITIL 5, these principles are essential for navigating the complexities of AI integration and high-velocity delivery.

1. Focus on Value

Everything the organization does must link back, directly or indirectly, to value for itself, its customers, and other stakeholders. This requires a deep understanding of who the service consumer is and what they perceive as valuable.

2. Start Where You Are

Before embarking on any improvement or transformation, organizations must assess the current state. This involves observing existing services and methods to understand what can be reused, updated, or repurposed, rather than starting from scratch without considering the current investment.

3. Progress Iteratively with Feedback

By organizing work into smaller, manageable sections that can be executed and completed in a timely manner, organizations can maintain focus and achieve results more quickly. Using feedback loops before, during, and after each iteration ensures that the work remains aligned with stakeholder needs.

4. Collaborate and Promote Visibility

Working together across boundaries produces results that have greater buy-in, more relevance to objectives, and increased likelihood of long-term success. Hidden agendas and siloed work must be replaced by transparency and shared information.

5. Think and Work Holistically

No service, practice, process, department, or supplier stands alone. The outputs that the organization delivers to itself, its customers, and other stakeholders will suffer unless it works in an integrated way to handle its activities as a whole. All four dimensions of service management must be considered concurrently.

6. Keep It Simple and Practical

If a process, service, action, or metric fails to provide value or produce a useful outcome, it should be eliminated. In a complex system, the most effective path is often the one with the fewest steps necessary to achieve the objective.

7. Optimize and Automate

Resources of all types, particularly human resources, should be used to their most effective effect. Organizations should eliminate anything that is truly wasteful and use technology to achieve whatever it is capable of achieving. Human intervention should only happen where it really contributes value.

Governance: Directing and Controlling the Value System

Governance is the system by which an organization is directed and controlled. In the context of the ITIL SVS, governance ensures that the organization’s strategy is aligned with its operations and that all activities are conducted within acceptable risk boundaries.

Organizational Accountability

Governance defines decision rights and accountability. It answers critical questions such as who approves high-risk AI use, who sets error thresholds, and who signs off on deployments. Without clear governance, accountability diffuses across teams, leading to “unowned risk” that can manifest as regulatory fines or reputational damage.

Governance vs. Management vs. Technology

ITIL 5 emphasizes the distinction between these three layers:

  • Technology: Builds the system (models, infrastructure, data pipelines).
  • Management: Operates the system (teams, workflows, KPIs, vendor oversight).
  • Governance: Controls the system (decision rights, risk ownership, accountability rules).

AI Governance Perspectives

As AI becomes an active partner in value streams, ITIL 5 introduces a specialized AI Governance Model divided into four perspectives:

  1. Decision Authority and Risk Management: Defines who can approve automated actions and establishes operational boundaries.
  2. Ethical Principles and Responsible AI: Implements testing to detect and mitigate algorithmic bias.
  3. Data Governance and Performance Management: Regulates training data quality and monitors for model performance drift.
  4. Regulatory Compliance: Aligns operations with international frameworks like the EU AI Act or Singapore’s MAS FEAT principles.

The Product and Service Lifecycle Model (PSLM): The Engine of Value

Replacing the linear Service Value Chain of previous iterations, the Product and Service Lifecycle Model (PSLM) is the central element of the ITIL 5 SVS. It manages products, services, delivery, and improvement across eight core activities that function as “stepping stones.”

The Eight PSLM Activities

  • Discover: Focuses on identifying customer demands, verifying feasibility, and aligning proposals with business strategy before capital investment.
  • Design: Models user experiences and establishes specific service parameters.
  • Acquire: Secures necessary resources, such as software licenses, human competencies, or cloud infrastructure.
  • Build: Compiles code, configures systems, and prepares release packages.
  • Transition: Deploys releases, manages risk, and ensures systems are observable.
  • Operate: Monitors system health, often utilizing site reliability engineering (SRE) principles.
  • Deliver: Coordinates value co-creation during the active use of the service.
  • Support: Addresses incidents and gathers feedback to drive future improvements.

Flexibility and Flow

The PSLM is not a linear process. Agile delivery teams move back and forth between these activities based on complexity and feedback loops. This allows for continuous delivery and rapid adaptation to changing market demands.

The 34 Management Practices: Functional Capabilities

Under ITIL 5, the management practices remain essential functional capabilities. The taxonomy has been simplified into two primary categories: Product and Service Management Practices and General Management Practices.

Practice CategoryDescriptionKey Practices for Foundation
Product & Service ManagementPractices focused on the technical and operational aspects of service delivery.Service Desk, Incident Management, Problem Management, Change Enablement, Service Request Management, Monitoring and Event Management, SLM, Release Management, Deployment Management, Service Configuration Management, ITAM.
General ManagementPractices adopted from general business domains for service management.Continual Improvement, Information Security Management, Relationship Management, Supplier Management, Risk Management.

The Shift in Testing Focus

A significant change in the ITIL 5 Foundation curriculum is that the testing weight for specific practice workflows has been reduced to zero percent. Instead, the focus is on the purpose, key terms, and strategic alignment of these practices within the broader SVS. Detailed operational workflows are now deferred to advanced specialist modules.

Essential Service Management Practices: Desk and Requests

Service Desk

The Service Desk acts as the primary point of contact for users and the service provider. Its purpose is to provide a central interface to capture demand for incident resolution and service requests. In ITIL 5, effective service desk operations require clear communication channels and structured pathways for information flow. Modern service desks increasingly leverage AI and self-service portals to handle routine inquiries, reducing workload and improving user satisfaction.

Service Request Management

The purpose of Service Request Management is to support the agreed quality of a service by handling all pre-defined, user-initiated service requests in an effective and user-friendly manner.

  • Fulfillment: Involves clear pathways for access permissions, hardware upgrades, or information requests.
  • Self-Service: ITIL 5 emphasizes empowering users with self-service portals to log and track their requests independently.
  • Standardization: Requests should be standardized and automated where possible to ensure consistency and speed.

Critical Operational Practices: Incident and Problem Management

Incident Management

Incident Management aims to restore normal service operations as quickly as possible following a disruption, minimizing the negative impact on business operations.

  • Prioritization: Disruptions are prioritized based on business impact and urgency.
  • Automation: Simple tasks like ticket routing and status updates are often automated.
  • Knowledge Management: Effective incident resolution relies on a searchable repository of known solutions and workarounds.

Problem Management

The purpose of Problem Management is to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents and managing workarounds and known errors.

  • Root Cause Analysis (RCA): Techniques like the “5 Whys” or Fishbone diagrams are used to uncover underlying causes.
  • Proactive vs. Reactive: Reactive problem management responds to incidents that have occurred, while proactive problem management analyzes trends and historical data to prevent future disruptions.
  • Known Error Database (KEDB): Once a root cause is identified but not yet permanently fixed, it is managed as a “known error” with a documented workaround.

Strategic Control Practices: Change Enablement and SLM

Change Enablement

Change Enablement balances the need for speed and agility with the need to manage risk. Its purpose is to maximize the number of successful product and service changes by ensuring that risks are properly assessed, authorizing changes to proceed, and managing a change schedule.

  • Risk Assessment: Every change must be evaluated for its potential benefits and risks.
  • Standard vs. Normal Changes: Standard changes are low-risk, pre-authorized, and follow a clear procedure. Normal changes require assessment and authorization according to the change authority.
  • Communication: Details about upcoming changes must be shared with all relevant stakeholders to ensure readiness.

Service Level Management (SLM)

The purpose of SLM is to set clear, business-based targets for service levels and to ensure that the delivery of services is properly assessed, monitored, and managed against these targets.

  • Service Level Agreements (SLAs): Documented agreements between a service provider and a customer that identify required services and expected levels of service.
  • Experience Level Agreements (XLAs): ITIL 5 introduces a stronger focus on XLAs, which measure the actual experience and satisfaction of the user, rather than just technical uptime.
  • Continual Review: SLAs must be regularly updated to stay aligned with evolving business needs.

Monitoring and Event Management: Ensuring System Health

The purpose of Monitoring and Event Management is to systematically observe services and service components, and record and report selected changes of state identified as events.

Key Functional Objectives

  • Detection: Identifying state changes that have a potential impact on service delivery.
  • Correlation: AI and automated tools correlate raw alerts to reduce noise and identify the root cause of complex issues.
  • Categorization: Events are typically classified as informational, warning, or exceptional.
  • Response: Automated responses can be triggered for routine events (e.g., auto-scaling resources), while critical alerts are escalated to incident management.

Real-Time Oversight

Modern Monitoring and Event Management provides real-time oversight of infrastructure, applications, and services. It is essential for maintaining stability in automated environments and serves as a primary input for proactive problem management.

The Continual Improvement Model: Sustaining Excellence

Continual Improvement is a general management practice that ensures an organization’s services and practices remain aligned with changing business needs. ITIL 5 utilizes a 7-step model to provide a structured approach to evolution.

The 7-Step Continual Improvement Model

  1. What is the vision? Define the high-level business objectives and the desired end state.
  2. Where are we now? Perform a baseline assessment of current capabilities and performance.
  3. Where do we want to be? Set measurable targets and KPIs (Key Performance Indicators).
  4. How do we get there? Develop a detailed implementation plan.
  5. Take action: Execute the improvement initiatives.
  6. Did we get there? Evaluate metrics and data to verify that the targets were met.
  7. How do we keep the momentum going? Use the lessons learned to inform the next iteration of the cycle.

Organizational Maturity

The SVS encourages a culture where improvement is everyone’s responsibility. Organizations can evaluate their progress using maturity models (e.g., the ITIL AI Maturity Model) to transition from ad-hoc usage to treating governance and improvement as a strategic advantage.

Integrating AI Governance into the Value System

ITIL 5 is “AI-native by design,” acknowledging that AI is no longer just a tool but a strategic capability embedded in the SVS. This integration requires moving beyond traditional IT governance, which was designed for static, deterministic systems.

The 6C AI Capability Model

To govern AI within the SVS, organizations use the 6C Model to classify AI functions:

  • Creation: Generating new digital assets or summaries.
  • Curation: Correlating alerts and filtering operational noise.
  • Clarification: Translating technical logs into plain-language updates.
  • Cognition: Predicting incident severity and suggesting root causes.
  • Communication: Interacting with humans via natural language assistants.
  • Coordination: Automating routing decisions and orchestrating workflows.

The AI Governance Improvement Model

Organizations can adapt their governance using a four-step lifecycle:

  1. Assess: Evaluate current governance maturity and stress-test readiness.
  2. Design: Define requirements, controls (preventive, detective, corrective), and decision boundaries.
  3. Implement: Deploy governance policies and shadow AI controls.
  4. Maintain: Monitor for performance drift and ensure continual improvement through observability.

Practical Application: Value Stream Identification and Mapping

Domain 5 of the ITIL 5 syllabus, closely linked to the Value System, introduces flow-based thinking through Value Stream Management. This involves mapping the sequence of activities within the PSLM to create value.

Core vs. Enabling Value Streams

  • Core Value Streams: Directly deliver value to the customer (e.g., a software release).
  • Enabling Value Streams: Support the core streams but do not deliver value directly (e.g., an internal infrastructure upgrade).

Optimizing Flow

The goal of mapping value streams is to identify bottlenecks, eliminate waste (Lean principles), and calculate metrics such as lead time and flow efficiency. By understanding how work moves through the SVS, organizations can optimize their Product and Service Lifecycle activities to maximize throughput and minimize delays.


Study Exercises: Short-Answer Questions

1. What is the primary purpose of the ITIL Service Value System (SVS)? Answer: The SVS provides a holistic, systemic model to coordinate all organizational activities and components required to co-create value with stakeholders. It ensures that the organization functions as an integrated whole rather than a collection of silos.

2. How do the ITIL Guiding Principles interact with one another? Answer: The principles are not intended to be used in isolation; they depend on and interact with each other. Organizations should evaluate each principle in context to understand its relevance before applying them collectively to a decision.

3. Define the role of a “Sponsor” according to ITIL 5 definitions. Answer: A sponsor is the specific role within a consumer organization that authorizes the budget for service consumption. They differ from “Customers,” who define requirements, and “Users,” who directly interact with the service.

4. What is the fundamental difference between an “Output” and an “Outcome”? Answer: An output is a tangible or intangible deliverable of an activity (e.g., a software update), whereas an outcome is a result for a stakeholder enabled by one or more outputs (e.g., increased sales efficiency).

5. Name the eight activities of the Product and Service Lifecycle Model (PSLM). Answer: The activities are Discover, Design, Acquire, Build, Transition, Operate, Deliver, and Support.

6. What is the purpose of the “Incident Management” practice? Answer: Its purpose is to restore normal service operations as quickly as possible after a disruption to minimize the negative impact on business quality.

7. How does ITIL 5 define “Governance”? Answer: Governance is the conceptual and visual representation of how an organization is directed and controlled to ensure it co-creates value.

8. What are the four perspectives of the ITIL AI Governance Model? Answer: The four perspectives are Decision Authority and Risk Management, Ethical Principles and Responsible AI, Data Governance and Performance Management, and Regulatory Compliance.

9. What is the goal of the “Optimize and Automate” guiding principle? Answer: It aims to make resources as effective as possible by eliminating waste and using technology for tasks it is capable of performing, reserving human intervention for activities that truly add value.

10. What is a “Known Error” in the context of Problem Management? Answer: A known error is a problem that has a documented root cause and a defined workaround, allowing incidents to be resolved more quickly while a permanent fix is developed.


Advanced Design Scenarios: Open-Ended Questions

  1. Scenario: Integrating Agentic AI. An organization plans to deploy “Agentic AI” that will autonomously approve purchase orders and negotiate with suppliers. Design a governance framework based on the four ITIL AI perspectives to manage the risks associated with this level of autonomy.
  2. Scenario: Siloed Product Teams. A company is struggling with friction between its “Build” teams (developers) and “Support” teams (operations). Using the Product and Service Lifecycle Model (PSLM), explain how you would restructure their activities to create a single, continuous value stream.
  3. Scenario: Legacy Transformation. An organization wants to modernize its legacy infrastructure but has a limited budget and high risk-aversion. Explain how the guiding principles “Start where you are” and “Progress iteratively with feedback” would influence your strategic roadmap.
  4. Scenario: Measuring Experience. A service provider consistently meets its technical SLAs (99.9% uptime), yet customer satisfaction is declining. Propose a new approach using Experience Level Agreements (XLAs) and the “Focus on value” principle to address this discrepancy.
  5. Scenario: Shadow AI Proliferation. Employees are independently using unapproved generative AI tools to draft customer emails. Design a strategy using the AI Governance Improvement Model (Assess, Design, Implement, Maintain) to bring these “Shadow AI” activities under organizational control.

Glossary of Key Terms

  • Agentic AI: AI systems that can execute multi-step workflows autonomously without human approval at every individual step.
  • Change Enablement: The practice of maximizing successful service changes by assessing risks and managing the change schedule.
  • Continual Improvement: A recurring activity performed at all levels to ensure performance meets stakeholder expectations.
  • Customer: The role that defines the requirements for a service and takes responsibility for the outcomes of service consumption.
  • Digital Product and Service Management (DPSM): The paradigm shift in ITIL 5 focusing on the end-to-end management of digital offerings rather than just technical infrastructure.
  • Event: Any change of state that has significance for the management of a service or other configuration item.
  • Experience Level Agreement (XLA): An agreement that focuses on the human experience and satisfaction of stakeholders rather than purely technical metrics.
  • Incident: An unplanned interruption to a service or a reduction in the quality of a service.
  • Known Error: A problem that has been analyzed and has a documented root cause and a workaround.
  • Outcome: A result for a stakeholder enabled by one or more outputs.
  • Output: A tangible or intangible deliverable of an activity.
  • Problem: A cause, or potential cause, of one or more incidents.
  • Service Desk: The point of communication between the service provider and all its users.
  • Service Level Agreement (SLA): A documented agreement between a service provider and a customer that identifies required services and expected levels of service.
  • Service Request: A formal request from a user or a user’s authorized representative that initiates a service action which has been agreed as a normal part of service delivery.
  • Service Value System (SVS): A model representing how all the components and activities of an organization work together to facilitate value creation.
  • Sponsor: The role that authorizes the budget for service consumption.
  • User: The role that directly uses or interacts with the service.
  • Value: The perceived benefits, usefulness, and importance of something.
  • Workaround: A solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available.

Leaderboard

No scores saved yet. Be the first!

30 Questions — ITIL 5 – Foundation : Certified ITIL Foundation - Domain 4 - The ITIL Value System

Expand any question to reveal the correct answer and explanation.

  1. 1 In ITIL (Version 5), what is the most significant structural change regarding the classification of management practices compared to ITIL 4?

    Consider how the transition from ITSM to Digital Product and Service Management affected technical silos.

    The removal of the Technical Management Practices category, with practices repositioned into the Product and Service Management group.

    The updated taxonomy simplifies the model by integrating technical practices like deployment management into the product and service category while eliminating the standalone technical grouping.

    • The expansion of the General Management category to include all 34 management practices to centralize governance.

      General management remains a distinct category for organization-wide functions, rather than absorbing all specialized service practices.

    • The introduction of a dedicated 'AI and Automation' practice group to replace the previous Technical Management category.

      While AI is integrated throughout the framework, it is treated as a partner within existing value streams and dimensions rather than a standalone practice category.

    • A shift where all practices are now categorized based on the eight activities of the Product and Service Lifecycle Model.

      Practices enable lifecycle activities but are not structurally categorized by them; they remain grouped by their functional focus.

  2. 2 Which Guiding Principle is specifically emphasized when an organization is encouraged to evaluate the interdependencies between people, tools, and partnerships to avoid unintended silos?

    This principle acts as a compass for managing complexity across the Four Dimensions.

    Think and work holistically

    This principle focuses on the integrated nature of the Four Dimensions, ensuring that the service provider understands the full context of value delivery.

    • Keep it simple and practical

      This principle aims to eliminate non-value-added steps rather than focusing on the systemic connections between organizational components.

    • Collaborate and promote visibility

      While this principle addresses teamwork, it specifically focuses on breaking down silos through transparency and communication rather than systemic design.

    • Focus on value

      This principle directs attention toward consumer outcomes but does not explicitly deal with the coordination of internal and external resources.

  3. 3 Within the Product and Service Lifecycle Model (PSLM), which activity is primarily responsible for securing specialist skills, cloud infrastructure, or external software licenses?

    Think about the phase where external capabilities and physical or virtual assets are brought into the organization.

    Acquire

    The Acquire activity handles the sourcing and allocation of necessary resources, including infrastructure and third-party capabilities, to enable the build and operation of services.

    • Discover

      Discover is focused on understanding needs and strategic alignment before resources are actually obtained.

    • Transition

      Transition manages the movement of configured solutions into live environments rather than the procurement of their foundational components.

    • Obtain/Build

      This was the ITIL 4 terminology; the PSLM distinguishes between the sourcing of resources and the configuration of the solution.

  4. 4 In the 6C AI Capability Model, which capability is used when an AI system correlates thousands of raw monitoring alerts to reduce 'noise' for human responders?

    This capability focuses on filtering and organizing existing information to improve visibility.

    Curation

    Curation involves organizing, filtering, and correlating information, such as alert deduplication, to make data manageable for stakeholders.

    • Clarification

      Clarification focuses on translating technical or complex data into plain language rather than filtering volumes of raw data.

    • Cognition

      Cognition is centered on predictive analytics and decision-making, such as forecasting resource needs or incident severity.

    • Coordination

      Coordination refers to the automation of routing decisions and workflow orchestration between agents and humans.

  5. 5 What is the specific focus of the seventh step in the ITIL Continual Improvement Model?

    This step is concerned with the long-term sustainability and institutionalization of changes.

    How do we keep the momentum going?

    The final step ensures that improvements are sustained, relevant, and that the organization remains committed to further cycles of evolution.

    • Are we getting there?

      This is step six, which involves measuring progress against the initial objectives to verify if the plan worked.

    • How do we get there?

      This is step four, which focuses on designing the specific plan and work sequences required to reach the target state.

    • What is the vision?

      This is the first step, establishing the strategic direction and high-level goals of the improvement initiative.

  6. 6 How does ITIL (Version 5) define 'Experience Level Agreements' (XLAs) relative to traditional Service Level Agreements (SLAs)?

    Consider how ITIL 5 shifts focus from technical 'outputs' to human-centric 'outcomes'.

    XLAs place user perception and digital experience on equal footing with technical utility and performance metrics.

    Unlike traditional SLAs that often focus on uptime and response times, XLAs measure how stakeholders experience the value of the product or service.

    • XLAs are a subset of SLAs that specifically measure the internal performance of the Service Desk staff.

      XLAs are broad outcome-focused metrics regarding overall user experience, not just individual agent performance targets.

    • XLAs replace SLAs entirely in Industry 5.0 to reflect the shift from technical outputs to human-centricity.

      SLAs remain a core part of utility and warranty; XLAs complement them by adding the experiential dimension of quality.

    • XLAs are legally binding contracts with third-party vendors regarding the user interface design of digital products.

      While XLAs can inform vendor relationships, they are primarily internal or consumer-facing metrics regarding perception rather than design contracts.

  7. 7 Which role within a consumer organization is specifically defined as the person or group that authorizes the budget for service consumption?

    This role is identified by its financial authority over the service relationship.

    Sponsor

    The sponsor role is distinct from the customer (who defines requirements) and the user (who consumes the service) by providing financial authorization.

    • Customer

      The customer is the role that defines the requirements for a service and takes responsibility for the outcomes of service consumption.

    • Stakeholder

      Stakeholder is a broad term for any party with an interest in the service, whereas the budget role is a specific designation.

    • Process Owner

      Process owners are responsible for the performance and improvement of a management practice, not for authorizing service budgets.

  8. 8 When applying the Guiding Principles, how should an organization approach a complex decision involving multiple conflicting priorities?

    Recall how the principles interact with and depend on one another.

    By considering each guiding principle to understand its relevance in context before applying them.

    The principles are interdependent and should be evaluated together to determine which ones are most relevant to the specific situation.

    • By selecting the 'Focus on value' principle as the primary tie-breaker for all organizational decisions.

      While 'Focus on value' is critical, prioritizing one principle over others in all cases ignores the holistic nature of the framework.

    • By applying all seven principles with equal weight to ensure a balanced and standard approach.

      Mechanically applying all principles equally can lead to paralysis; they must be weighted based on the specific circumstances of the decision.

    • By defaulting to the 'Keep it simple and practical' principle to minimize initial risk and complexity.

      Simplicity is a goal, but it may not be the most relevant principle if, for example, the organization needs to 'Start where you are' to preserve existing assets.

  9. 9 Which management practice has the primary functional objective of restoring normal service operation as quickly as possible following a disruption?

    This practice is often compared to firefighting, focusing on speed over detailed investigation.

    Incident Management

    Incident Management prioritizes the rapid restoration of service to minimize negative impact on business operations.

    • Problem Management

      Problem Management focuses on identifying root causes and preventing recurrences, which often happens after service is already restored.

    • Change Enablement

      Change Enablement manages the risk of modifications to ensure stability, rather than responding to unplanned outages.

    • Service Level Management

      This practice sets targets and monitors performance against them but is not the operational response to a disruption.

  10. 10 In the PSLM, the 'Operate' activity is most closely associated with which modern technical discipline for ensuring system health?

    This discipline uses software engineering to solve operations problems.

    Site Reliability Engineering (SRE)

    ITIL 5 integrates SRE principles into the Operate activity to manage system health, observability, and reliability in cloud-native environments.

    • Agile Software Development

      Agile is primarily associated with the Build and Design activities, focusing on iterative creation rather than ongoing system health monitoring.

    • Waterfall Project Management

      Waterfall is a sequential delivery model that is increasingly replaced by the iterative nature of the PSLM.

    • Six Sigma Quality Control

      While Six Sigma focuses on process improvement, it is a data-driven methodology that integrates with Continual Improvement rather than defining the Operate activity.

  11. 11 Which AI Governance perspective is responsible for ensuring that training data quality is regulated and performance drift is detected in live models?

    Look for the perspective that bridges data inputs and operational output monitoring.

    Data Governance and Performance Management

    This specific perspective focuses on the lifecycle of the data feeding the AI and the ongoing accuracy of the model's outputs over time.

    • Decision Authority and Risk Management

      This perspective defines who approves actions and sets operational boundaries rather than managing data quality.

    • Ethical Principles and Responsible AI

      This area focuses on mitigating algorithmic bias and ensuring human-centric design rather than technical data lineage or drift.

    • Regulatory Compliance

      This perspective ensures alignment with external legal frameworks like the EU AI Act rather than internal model performance monitoring.

  12. 12 How does the 'Start where you are' principle contribute to organizational resilience in ITIL (Version 5)?

    This principle focuses on the value of current state assessment before making changes.

    By preventing the waste of existing resources, services, and processes that can be reused or improved.

    Resilience is built by accurately assessing current capabilities to avoid unnecessary 'rip-and-replace' strategies that introduce risk and waste.

    • By mandating that all new digital transformation projects must utilize current legacy infrastructure.

      This principle encourages assessment, not the mandatory use of outdated systems that might hinder value co-creation.

    • By ensuring that initial plans are not modified once the 'Discover' phase of the lifecycle is complete.

      This would contradict the 'Progress iteratively' principle; 'Start where you are' is about the baseline, not the inflexibility of the plan.

    • By focusing exclusively on local improvements before considering the holistic value system.

      Local optimization without a holistic view can lead to systemic failures, which this principle specifically tries to avoid when combined with others.

  13. 13 Which activity within the PSLM focuses on modeling user experiences and establishing service parameters before resources are secured?

    Think about the phase where prototypes and technical specifications are generated.

    Design

    Design translates needs identified in the Discover phase into prototypes, specifications, and service models focused on functionality and experience.

    • Acquire

      Acquire is the subsequent step where the actual resources required for the design are secured.

    • Build

      Build is the execution phase where the design is turned into a functional digital solution through coding or configuration.

    • Discover

      Discover is about strategic alignment and initial demand verification, whereas Design handles the actual modeling of the solution.

  14. 14 In Value Stream Identification, what characterizes an 'Enabling' value stream compared to a 'Core' value stream?

    Think about the relationship between internal support functions and external service delivery.

    Enabling value streams provide internal capabilities that support the delivery of customer-facing core value streams.

    Core value streams directly co-create value with consumers, while enabling streams (like onboarding or infrastructure management) support that delivery.

    • Enabling value streams are exclusively automated, whereas core value streams involve human interactions.

      Both types of streams can involve a mix of human and automated activities; the difference is their position in the value chain.

    • Enabling value streams are only used during the 'Discover' and 'Design' activities of the PSLM.

      Enabling streams can support any part of the lifecycle, including ongoing operations and support.

    • Enabling value streams are defined by the ITIL practices, while core value streams are defined by the organization's business strategy.

      Both are part of the organizational operating model and strategy; practices enable both types of streams.

  15. 15 What is the primary role of 'Governance' within the ITIL Value System (IVS)?

    Consider how an organization ensures that its activities align with its high-level strategy.

    To provide direction and oversight while ensuring that organizational strategy and objectives are achieved.

    Governance ensures that all components of the value system work in concert to achieve the mission and vision through evaluation, direction, and monitoring.

    • To act as a mandatory checklist that must be completed before any PSLM activity can proceed.

      Governance should be an enabling function that guides value creation rather than a rigid, non-value-added administrative hurdle.

    • To specifically manage the financial budgeting of IT asset lifecycles across the organization.

      While related to financial management, governance is broader, encompassing decision rights, accountability, and ethical standards across all activities.

    • To replace the Guiding Principles in high-risk, regulated environments.

      Governance and Guiding Principles are complementary; principles inform the practical decisions that governance oversees.

  16. 16 Under the 'Four Dimensions' model, which dimension is concerned with data models, analytics engines, and technology platforms?

    This dimension embeds the classification of technology functions like the 6C Model.

    Information and Technology

    This dimension focuses on the information and knowledge necessary for service management, as well as the technologies that support it.

    • Organizations and People

      This dimension focuses on human competencies, culture, and organizational structures rather than the technical platforms they use.

    • Value Streams and Processes

      This dimension focuses on the workflows and activities that convert demand into value, using technology as an enabler.

    • Partners and Suppliers

      This dimension deals with the relationships with external parties who may provide technology or information services.

  17. 17 Which capability of the 6C AI Model is responsible for automating routing decisions and triggering recovery scripts during an incident?

    This capability is about the orchestration of workflows and actions across systems.

    Coordination

    Coordination involves orchestrating workflows and automating decision-driven actions like assigning responders or triggering runbooks.

    • Cognition

      Cognition refers to the analysis and prediction phase, whereas coordination is the active execution of a response or workflow.

    • Communication

      Communication focuses on the natural language interaction with human stakeholders rather than the back-end automation of tasks.

    • Curation

      Curation handles the filtering and organization of data alerts rather than the subsequent action based on that data.

  18. 18 What distinguishes 'Problem Management' from 'Incident Management' regarding their relationship with the PSLM?

    Think about the primary objective of each practice when a service disruption occurs.

    Incident Management focuses on rapid recovery in 'Support', while Problem Management focuses on root cause analysis in 'Operate' and 'Support'.

    While both occur late in the lifecycle, incident management is reactive and speed-focused, whereas problem management is investigative and preventive.

    • Problem Management is a General Management practice, while Incident Management is a Product and Service practice.

      Both are categorized as Product and Service Management practices in ITIL 5.

    • Problem Management only occurs during the 'Design' phase to prevent errors before they are built.

      Problem management occurs throughout the lifecycle, but its most visible operational impact is in correcting and preventing live service issues.

    • Problem Management is only concerned with the financial outcomes of incidents.

      This would fall under financial management or general risk management; problem management is technically and operationally focused on stability.

  19. 19 In the PSLM, how do the eight activities function as 'stepping stones'?

    Consider how this model supports Agile and DevOps ways of working.

    Teams can move back and forth between activities iteratively based on feedback and complexity.

    The model is non-linear, allowing agile teams to jump between activities (e.g., from Build back to Design) as new information emerges.

    • Each activity must be fully completed and audited before the next one in the sequence can begin.

      This would describe a rigid Waterfall model, which ITIL 5 explicitly moves away from to support high-velocity environments.

    • They represent a fixed sequence that every value stream must follow to ensure regulatory compliance.

      While the activities provide a structure, the sequence and combination of activities vary by value stream.

    • They are only used when an organization is transforming its entire business model.

      The PSLM is used for the end-to-end lifecycle of any digital product or service, regardless of its scale.

  20. 20 Which Guiding Principle is most directly applied when an organization decides to release a 'Minimum Viable Product' (MVP) and gather user feedback before adding more features?

    This principle emphasizes learning through small, manageable increments.

    Progress iteratively with feedback

    Releasing in small increments allows the organization to gather real-world data and adjust the product based on actual usage and needs.

    • Focus on value

      While an MVP focuses on value, the *method* of small releases and learning cycles is the core of iterative progression.

    • Keep it simple and practical

      Simplification helps, but iterative progression specifically addresses the need for feedback loops to manage uncertainty.

    • Optimize and automate

      Automation supports delivery, but it does not define the strategy of releasing increments for learning purposes.

  21. 21 What is the primary purpose of 'Monitoring and Event Management' in the context of the ITIL Value System?

    This practice is often described as the 'eyes and ears' of IT operations.

    To observe services and infrastructure and detect state changes that may indicate potential issues.

    This practice provides the visibility required to respond to events before they become incidents, supporting both Operate and Support activities.

    • To provide a record of all human interactions with the Service Desk for audit purposes.

      Service Desk operations and Knowledge Management handle interaction logs; Monitoring focuses on technical state changes.

    • To manage the deployment of new software packages into the production environment.

      This is the objective of Release and Deployment Management practices, not Monitoring.

    • To replace the need for Incident Management by automatically fixing every system error.

      Monitoring detects events; while it can trigger automated remediation (coordination), it does not eliminate the practice of incident management.

  22. 22 In the Continual Improvement Model, which step involves defining 'Where are we now?' through baseline assessments?

    This step provides the objective starting point for any improvement journey.

    Step 2

    Establishing a baseline is essential to measure future progress and understand the starting gap between current performance and the vision.

    • Step 1

      Step 1 is about defining the high-level vision and objectives rather than measuring current capabilities.

    • Step 3

      Step 3 is about defining the target state or 'Where do we want to be?' once the baseline is known.

    • Step 6

      Step 6 is about checking if the improvement was achieved, which happens after action is taken.

  23. 23 Which management practice focuses on balancing speed with safety by assessing risks and authorizing modifications to digital products?

    This practice was previously known as Change Control but was renamed to emphasize speed and safety.

    Change Enablement

    Change Enablement ensures that changes are assessed for risk and authorized appropriately to maintain service stability while supporting agility.

    • Release Management

      Release Management focuses on making features available for use, whereas Change Enablement focuses on the authorization and risk assessment of the change itself.

    • Deployment Management

      Deployment is the technical act of moving components to a live environment, whereas Change Enablement is the governing process.

    • Continual Improvement

      Continual Improvement aligns services with business needs over time but does not handle the specific authorization of technical modifications.

  24. 24 Which capability of the 6C AI Model is being utilized when a virtual assistant interacts with a user to gather details about an incident?

    This capability focuses on the 'human-technology' interface layer.

    Communication

    The Communication capability encompasses the natural language interface and interaction between AI agents and human stakeholders.

    • Coordination

      Coordination involves the back-end orchestration of workflows, not the front-end user interaction.

    • Curation

      Curation is about filtering and organizing data alerts, not interacting with people.

    • Creation

      Creation involves generating new assets or summaries, whereas interaction is a specific communication function.

  25. 25 How does ITIL (Version 5) define 'Value Co-creation'?

    Recall that value is not a one-way street in modern service management.

    Value is created through active collaboration between the service provider, the consumer, and other stakeholders.

    Value is not just delivered *to* a customer; it is realized through the joint efforts of all parties in the service relationship.

    • Value is a fixed output delivered by the service provider to the consumer upon payment.

      This describes a traditional 'goods' transfer; ITIL emphasizes that value realization requires consumer participation.

    • Value is exclusively determined by the technical utility and reliability (warranty) of the product.

      Utility and warranty are ingredients of value, but value also includes experience and the achievement of outcomes.

    • Value is created solely by the AI systems within the IVS through autonomous automation.

      AI is a tool for co-creation, but the framework still emphasizes the role of humans and organizational relationships.

  26. 26 Which of the following is a primary objective of 'Service Configuration Management'?

    This practice provides the 'authoritative source' for understanding the IT environment.

    To maintain accurate information about configuration items and the relationships between them.

    Providing a map of how infrastructure, applications, and services are connected is vital for impact analysis and troubleshooting.

    • To package and move new software releases into the live environment.

      This is the role of Release and Deployment Management, though they rely on configuration data.

    • To identify and resolve the root cause of recurring incidents.

      This is the objective of Problem Management, which uses the CMDB to understand system dependencies.

    • To provide the single point of entry for all user-initiated service requests.

      This is the functional role of the Service Desk practice.

  27. 27 Under 'AI Governance', what does 'Human-in-the-Loop' oversight signify?

    This concept is a sign of mature governance when dealing with autonomous agents.

    Defining specific risk thresholds where a human must review and approve an automated AI action.

    Human oversight mechanisms ensure that high-risk decisions are not fully autonomous, maintaining ethical and operational control.

    • Requiring that all AI code must be manually written by humans rather than generated by other AI.

      AI can assist in development, but 'in-the-loop' specifically refers to the decision-making and oversight process during operation.

    • A technical requirement that AI models must be hosted on-premises rather than in the cloud.

      Oversight is about governance and control, not the physical or virtual location of the infrastructure.

    • Ensuring that AI agents only communicate with other humans and never with other AI systems.

      AI-to-AI interaction is common in complex environments; governance ensures those interactions are monitored by humans.

  28. 28 Which Guiding Principle is most applicable when an organization is warned to avoid 'paralysis by analysis' and instead focus on simplifying work?

    This principle asks 'is this activity contributing to value?' and if not, suggests removing it.

    Keep it simple and practical

    This principle focuses on eliminating non-value-added activities and using the minimum number of steps to achieve an outcome.

    • Start where you are

      While this principle avoids waste, it does not specifically address the removal of complex, non-value-added steps in a process.

    • Optimize and automate

      Optimization should happen after simplicity is achieved, as automating a complex, wasteful process only makes it faster at being wasteful.

    • Think and work holistically

      Holistic thinking can sometimes *increase* perceived complexity; the simplicity principle acts as the necessary balance.

  29. 29 Which activity in the PSLM ensures that value is co-created during active use and stakeholder expectations are being met?

    Think about the phase where the customer is actively consuming the service.

    Deliver

    Deliver is the activity where the service is actually provided to the user, ensuring the intended value is tangible and meets specifications.

    • Operate

      Operate focuses on the back-end health and reliability of the systems supporting the delivery, rather than the value realization itself.

    • Support

      Support is focused on restoring service or fulfilling requests when things go wrong or are requested, rather than the primary delivery of value.

    • Transition

      Transition is about the deployment of changes into the live state, not the ongoing provision of value to the consumer.

  30. 30 In the 6C Model, which capability is used when an AI system predicts incident severity or suggests a possible root cause based on historical data?

    This capability involves using machine learning for prediction and deep analysis.

    Cognition

    Cognition deals with advanced analytics, pattern recognition, and predictive modeling to assist in complex decision-making.

    • Curation

      Curation is limited to the organization and filtering of current data, not the prediction of future states or underlying causes.

    • Clarification

      Clarification simplifies technical data into plain language but does not involve the inferential logic of cognition.

    • Creation

      Creation involves generating new text or summaries, whereas cognition is about the analytical engine behind the insights.