Skip to content

ITIL 5 PM : Plan, Implement and Control - PIC (Domain 2)

ITIL 5 – Practice Manager : Certified ITIL Practice Manager - Domain 2 - Plan, Implement and Control (PIC)

30 questionsmedium

The introduction of ITIL Version 5 in early 2026 marks a pivotal transition in the management of digital capabilities. The framework has evolved from a traditional focus on IT Service Management (ITSM) into a comprehensive model for Digital Product and Service Management (DPSM). This evolution addresses the modern necessity for organizations to operate with increased velocity and flexibility, particularly through the integration of artificial intelligence (AI) and highly automated workflows.

The Plan, Implement and Control (PIC) domain is one of the three specialized modules within the ITIL 5 Practice Manager designation. It is designed specifically to bridge the gap between development velocity and operational stability. By mastering PIC, practitioners learn to govern the movement of new and changed capabilities into production while mitigating business risks through structured authorization and configuration control.

1. The Architectural Evolution to Digital Product and Service Management (DPSM)

Modern digital operations require a unified approach that eliminates the legacy divide between software development teams and steady-state operations groups. ITIL 5 addresses this by establishing an AI-native operational model. A central component of this shift is the decommissioning of the ITIL 4 three-group classification of practices. In its place, the framework now organizes practices into two logical groupings:

  • Product and Service Management Practices: This category contains 22 practices, including the core PIC practices. It ensures that technical management and traditional service management are directly aligned to support the unified lifecycle of a digital product.
  • General Management Practices: This category comprises 12 practices focused on broader corporate capabilities, such as relationship management and continuous learning.

PIC resides at the heart of Product and Service Management, focusing on the governance of code deployment pipelines, configuration record integrity, and the financial lifecycle of technology assets. As organizations move toward rapid delivery models, the PIC practices provide the necessary “checks and balances” to ensure that speed does not compromise service quality or compliance.

2. The Practice Manager Designation: Certification Pathway and Requirements

To earn the ITIL 5 Practice Manager credential, candidates must navigate a structured learning path that validates both foundational knowledge and specialized operational capability. The designation is intended for service desk managers, operational leaders, and transformation consultants.

The qualification requirements are as follows:

  • Foundation Prerequisite: Candidates must hold either an ITIL 5 Foundation certificate or a legacy ITIL 4 Foundation certificate. This recognition of legacy certifications ensures that prior investments in the ITIL 4 ecosystem remain valid entry points into the Version 5 scheme.
  • Specialized Practice Module: Candidates must successfully complete at least one of the specialized three-day modules: Monitor, Support and Fulfil (MSF), Plan, Implement and Control (PIC), or Collaborate, Assure and Improve (CAI).
  • Core Corequisite: The ITIL Transformation (Version 5) module is a mandatory requirement. This replaces the legacy ITIL 4 Specialist: Create, Deliver and Support (CDS) requirement, shifting the focus from steady-state support to active leadership of organizational change.

The PIC module itself is evaluated through a 60-question, closed-book, multiple-choice examination. Candidates are allotted 90 minutes and must achieve a passing score of at least 65% (39 correct answers) to receive the certification.

3. The Product and Service Lifecycle Model

In Version 5, the legacy service value chain has been modernized into a unified Product and Service Lifecycle Model. This model consists of eight interconnected activities that organizations navigate iteratively rather than sequentially:

  1. Discover: Identifying needs and opportunities.
  2. Design: Planning human-centric and experience-driven solutions.
  3. Acquire: Obtaining necessary components from third parties.
  4. Build: Developing and constructing the product or service.
  5. Transition: Moving components from build to live environments (a core focus of PIC).
  6. Operate: Maintaining steady-state performance.
  7. Deliver: Providing the value to the consumer.
  8. Support: Addressing disruptions and user needs.

A significant change in Version 5 is the separation of “Design” and “Transition.” This allows organizations to manage transition and release pipelines as highly automated, continuous integration (CI) workflows, while keeping the Design activity focused on experience-driven requirements. PIC practices are primarily engaged during the Transition and Build activities, ensuring that every movement of software or hardware is accounted for and authorized.

4. Change Enablement: Governing Risk and Innovation

Change Enablement is the primary governance mechanism within the PIC domain. Its purpose is to ensure that all technology-related changes are authorized and scheduled safely to mitigate potential business disruptions.

Practice Success Factors (PSFs)

  • Effective Authorization: Establishing a change authority that balances the need for speed with the necessity of risk evaluation.
  • Change Scheduling: Coordinating changes to avoid resource conflicts and minimize impact on business operations.
  • Post-Implementation Review: Evaluating the outcomes of changes to improve future authorization and execution processes.

Operational Process and Governance

The practice distinguishes between different types of changes, such as standard, normal, and emergency changes. In modern environments, Change Enablement increasingly focuses on automating the authorization of standard changes through pre-defined CI/CD pipelines. This allows low-risk, repetitive changes to move at high velocity while preserving human oversight for high-impact, complex transitions.

Key Metrics

  • Change Success Rate: The percentage of changes that achieve their intended outcomes without causing incidents.
  • Change Lead Time: The duration from the initial request for change to its successful implementation.
  • Unplanned Change Percentage: The ratio of emergency or unauthorized changes compared to planned initiatives.

5. Release Management: Packaging Value for Deployment

Release Management focuses on the operational packaging of new or changed capabilities. It acts as the bridge between the Build activity and the Transition activity, ensuring that all components (software, hardware, documentation, and training) are bundled into a cohesive unit.

Practice Success Factors (PSFs)

  • Release Definition and Planning: Clearly defining the scope of a release and the criteria for its success.
  • Component Assembly: Ensuring all technical and non-technical elements of a release are accounted for and compatible.
  • Staging and Testing: Verifying the release package in a controlled environment before it is handed over for deployment.

Operational Focus

In a digital-first environment, Release Management must support multiple release patterns, ranging from traditional “big bang” releases to phased rollouts and continuous delivery. The practice ensures that even in rapid release cycles, the integrity of the product remains intact and the user experience is protected.

Key Metrics

  • Release Failure Rate: The frequency of releases that require a rollback or post-deployment fix.
  • Deployment Readiness Score: An assessment of how well-prepared a release package is for the production environment.
  • Package Integrity: The accuracy and completeness of release documentation and components.

6. Deployment Management: Moving Software and Hardware

While Release Management focuses on the “package,” Deployment Management governs the actual movement of components across staging, testing, and production environments. It is the technical execution arm of the PIC domain.

Practice Success Factors (PSFs)

  • Automated Deployment Pipelines: Establishing reliable, repeatable workflows for the movement of code and configuration.
  • Environment Parity: Ensuring that testing and staging environments accurately reflect the production environment to reduce deployment errors.
  • Verification and Testing: Confirming that components are functioning as intended immediately following their movement.

Operational Analysis

Deployment Management is often highly automated in modern organizations. However, it also encompasses the physical movement of hardware in data centers or the provisioning of virtualized resources in cloud environments. The practice must maintain strict control over deployment windows and ensure that every movement is logged and visible to the Change Enablement and Service Configuration Management practices.

Key Metrics

  • Deployment Frequency: How often code or components are successfully moved to production.
  • Mean Time to Deploy (MTTD): The average time taken to execute a deployment once the release package is ready.
  • Deployment Error Rate: The percentage of deployments that encounter technical failures during execution.

7. Service Configuration Management: Data Integrity and Dependencies

Service Configuration Management provides the foundational data required for all other PIC practices. It ensures that accurate information about system architectures, dependencies, and Configuration Items (CIs) is available to decision-makers.

Practice Success Factors (PSFs)

  • Configuration Modeling: Defining the relationships and attributes of CIs to reflect the reality of the digital environment.
  • Data Verification and Audit: Regularly checking the accuracy of the Configuration Management Database (CMDB) against the actual environment.
  • Integration with Other Practices: Ensuring that change and incident records are linked to the correct configuration data.

Operational Analysis

In an AI-native world, Service Configuration Management utilizes automated discovery tools to maintain a real-time map of the environment. This data is critical for Change Enablement to assess the “blast radius” of a proposed change and for Incident Management to identify potential root causes of failure.

Key Metrics

  • CMDB Accuracy Rate: The percentage of CI records that match the actual state of the environment during an audit.
  • CI Coverage: The extent to which the CMDB captures all relevant assets and their dependencies.
  • Configuration Drift: The frequency and degree to which the environment departs from its authorized configuration state.

8. IT Asset Management (ITAM): Financial and Compliance Lifecycles

IT Asset Management (ITAM) tracks the financial, contractual, and compliance lifecycles of physical, virtual, and cloud assets. While Configuration Management cares about how things connect, ITAM cares about what things cost and who owns them.

Practice Success Factors (PSFs)

  • Lifecycle Tracking: Monitoring an asset from its initial acquisition through its disposal or decommissioning.
  • Compliance Governance: Ensuring that software licensing and hardware usage adhere to legal and contractual requirements.
  • Financial Optimization: Identifying underutilized assets (particularly in the cloud) to reduce organizational waste.

Operational Analysis

The rise of cloud computing has transformed ITAM, requiring a focus on dynamic, consumption-based assets. ITAM must work closely with the Acquire activity of the lifecycle to manage vendor contracts and ensure that the organization is receiving value for its technology investments.

Key Metrics

  • Asset Utilization Rate: The ratio of actively used assets to the total inventory.
  • License Compliance Score: The percentage of software installations that are fully licensed and compliant with vendor agreements.
  • Total Cost of Ownership (TCO): The comprehensive financial impact of an asset over its entire lifespan.

9. Bridging Velocity and Control: The PIC Strategy

One of the central challenges addressed by the PIC domain is the tension between development velocity (the need for speed) and operational control (the need for stability). Organizations adopting DevOps and Agile methodologies often view traditional governance as a bottleneck. PIC resolves this by integrating governance into the delivery pipeline.

Automated Authorization

By defining “Standard Changes” for well-understood, low-risk deployments, Change Enablement can delegate authorization to the automated testing tools within the deployment pipeline. If the code passes all automated tests, it is authorized to move to production without manual intervention.

Dependency Visualization

Service Configuration Management provides the visualization needed for rapid development. When developers understand the dependencies between their services and the broader infrastructure, they can design more resilient products and avoid unintended consequences during deployment.

Financial Safeguards

Rapid deployment in the cloud can lead to “bill shock.” IT Asset Management provides the necessary financial controls to ensure that automated provisioning does not exceed budget boundaries. This allows the organization to scale its digital products rapidly while maintaining fiscal responsibility.

10. AI-Native Operations in PIC

The ITIL 5 framework positions artificial intelligence as a core enabler of the PIC practices. To manage this integration, the framework introduces the AI Capability Model (6Cs), which classifies AI functions into six areas:

  1. Creation: Generating code, documentation, or release packages.
  2. Curation: Filtering and organizing configuration data.
  3. Clarification: Analyzing complex dependency maps to explain potential risks.
  4. Cognition: Detecting patterns in deployment failures to predict future issues.
  5. Communication: Automating status updates for changes and releases.
  6. Coordination: Orchestrating the movement of components across various environments.

In the PIC domain, AI is used to evaluate algorithmic risks and manage the throughput of highly automated deployment pipelines. For instance, AI models can analyze historical change data to assign risk scores to new requests, allowing the system to automatically approve low-risk changes while flagging high-risk ones for human review.

11. Integration with ITIL Transformation (Version 5)

Because digital transformations often introduce organizational friction, the mandatory ITIL Transformation module provides the models and patterns needed to execute PIC-related changes safely.

The Transformation Model Layers

  • Governance Layer: Sets the strategic boundaries and ethical compliance for the transformation.
  • Positioning Layer: Evaluates the current operational baseline and team readiness for new PIC practices.
  • Execution Layer: Governs the actual deployment of changes to people, processes, and tools.
  • Learning Layer: Integrates post-implementation feedback into the organizational value system.

Execution Patterns for PIC

The transformation module defines three patterns that are highly relevant when implementing PIC practices:

  • Implement Pattern: Used for predictable, ordered environments, such as standardizing a hardware deployment process.
  • Discover Pattern: Applied in complex, unpredictable environments where the organization is experimenting with new CI/CD pipelines.
  • Contain Pattern: Deployed in chaotic situations where a failed deployment has caused a major outage, requiring immediate stabilization before long-term fixes are implemented.

12. Short-Answer Questions

Question 1: What is the primary difference between Service Configuration Management and IT Asset Management? Question 2: Which ITIL 5 lifecycle activity is most closely associated with the movement of code into a live environment? Question 3: What are the three execution patterns defined in the ITIL Transformation module? Question 4: How does Change Enablement support high-velocity deployment models like DevOps? Question 5: Name the six functions of the AI Capability Model (6Cs). Question 6: What is the mandatory corequisite for the ITIL 5 Practice Manager designation? Question 7: Define a “Standard Change” in the context of Change Enablement. Question 8: What is the purpose of the “Staging” phase in Release Management? Question 9: Why did ITIL 5 separate the “Design” and “Transition” activities? Question 10: What are the components of a “Release Package”?

Answer Key for Short-Answer Questions

  1. Service Configuration Management focuses on the technical relationships and dependencies between components, while IT Asset Management focuses on the financial, contractual, and compliance lifecycles of those components.
  2. The Transition activity is most closely associated with moving components from the build environment to the live operational environment.
  3. The three execution patterns are the Implement pattern (ordered), the Discover pattern (complex), and the Contain pattern (chaotic).
  4. It supports high velocity by automating the authorization of standard, low-risk changes within CI/CD pipelines, allowing them to proceed without manual human intervention.
  5. The six functions are Creation, Curation, Clarification, Cognition, Communication, and Coordination.
  6. The ITIL Transformation (Version 5) module is the universal and mandatory corequisite for all advanced designations, including Practice Manager.
  7. A Standard Change is a low-risk, pre-authorized change that follows a well-established procedure and is frequently implemented.
  8. Staging provides a controlled environment to verify that a release package is technically sound and meets all requirements before it is deployed to production.
  9. Separating them allows organizations to treat Transition as a highly automated technical workflow while maintaining a human-centric, experience-driven focus during the Design activity.
  10. A Release Package includes the software code, hardware components, supporting documentation, and any training materials required for the new or changed service.

13. Advanced Design and Architectural Scenarios

Scenario 1: The Global CI/CD Pipeline Architecture An international financial organization is moving to a fully automated CI/CD pipeline for its core banking application. Design a PIC-aligned governance model that allows for hourly code deployments while satisfying strict regulatory requirements for auditability and risk authorization. How would you utilize Service Configuration Management to ensure that automated changes do not impact interconnected legacy systems?

Scenario 2: The Multi-Cloud Asset Lifecycle A digital product company uses a combination of three different public cloud providers. The company is experiencing significant “configuration drift” and unpredicted costs. Develop an IT Asset Management and Configuration Management strategy to regain control. Specifically, address how you would track the financial lifecycle of ephemeral (short-lived) cloud assets and ensure compliance with software licensing across multiple platforms.

Scenario 3: AI-Driven Change Authorization You are tasked with implementing an AI-native Change Enablement practice. The goal is to use the “Cognition” and “Clarification” functions of the AI Capability Model to analyze change requests. Propose a framework for how the AI would evaluate risk, what data it would require from the CMDB, and what criteria would be used to determine when a human change authority must override an AI-generated decision.

Scenario 4: Managing a Chaotic Deployment Failure During a major transformation initiative, a new release package was deployed using the “Discover” pattern, but it caused a catastrophic failure across the production environment. Using the “Contain” pattern from the Transformation Model, design an emergency response that stabilizes the environment while preserving deployment logs for a post-mortem analysis by Release and Deployment Management.

Scenario 5: Dependency Mapping in a Microservices Environment An organization has moved from a monolithic architecture to a microservices-based model with thousands of individual CIs. Traditional manual configuration updates are no longer feasible. Design an automated Service Configuration Management process that utilizes “Curation” and “Coordination” AI functions to maintain a real-time dependency map and support the Change Enablement practice in assessing the potential “blast radius” of a single service failure.

14. Glossary of Key PIC Terms

  1. AI Capability Model (6Cs): A framework in ITIL 5 that classifies AI functions into Creation, Curation, Clarification, Cognition, Communication, and Coordination.
  2. Change Authority: A person or group responsible for authorizing a change, ranging from a manual committee to an automated testing tool.
  3. Change Lead Time: The total time elapsed from the creation of a change request until the change is successfully implemented in production.
  4. Configuration Item (CI): Any component that needs to be managed in order to deliver a digital product or service.
  5. Configuration Drift: The phenomenon where the actual state of a system’s configuration gradually departs from its authorized and documented state.
  6. Continuous Integration / Continuous Delivery (CI/CD): Automated technical workflows that allow for the frequent building, testing, and deployment of code.
  7. Contain Pattern: A transformation execution pattern used in chaotic situations to stabilize an environment before attempting systematic change.
  8. Deployment Management: The practice of moving new or changed hardware, software, documentation, or any other component to live environments.
  9. Digital Product and Service Management (DPSM): The holistic model in ITIL 5 that integrates development and operations into a unified lifecycle.
  10. Discover Pattern: A transformation execution pattern used in complex environments where outcomes are unpredictable and require iterative experimentation.
  11. Implement Pattern: A transformation execution pattern used in ordered, predictable environments where the path to change is well-defined.
  12. IT Asset Management (ITAM): The practice of managing the financial, contractual, and compliance lifecycles of technology assets.
  13. Practice Success Factor (PSF): A specific capability or condition within a management practice that is necessary for the practice to achieve its purpose.
  14. Release Management: The practice of planning, designing, building, testing, and staging the operational packaging of a digital product.
  15. Service Configuration Management: The practice of ensuring that accurate and reliable information about the configuration of services is available when and where it is needed.
  16. Service Value System (SVS): In ITIL 5, often referred to simply as the Value System, it describes how all components and activities of an organization work together to co-create value.
  17. Total Cost of Ownership (TCO): A financial estimate intended to help buyers and owners determine the direct and indirect costs of a product or system over its lifecycle.
  18. Transformation Model: A four-layered framework (Governance, Positioning, Execution, Learning) used to manage organizational change in ITIL 5.
  19. Transition Activity: An activity in the Product and Service Lifecycle focused on moving components from development or acquisition into the live environment.
  20. Value Stream Mapping (VSM): A technique used to visualize and analyze the flow of work and information required to deliver a product or service to a consumer.

Leaderboard

No scores saved yet. Be the first!

30 Questions — ITIL 5 – Practice Manager : Certified ITIL Practice Manager - Domain 2 - Plan, Implement and Control (PIC)

Expand any question to reveal the correct answer and explanation.

  1. 1 In a high-velocity CI/CD environment, which practice is primarily responsible for defining the governance policies that determine if an automated change is authorized to bypass a manual advisory board?

    Consider which practice is tasked with maximizing the number of successful IT changes through risk assessment.

    Change Enablement

    This practice focuses on ensuring that technology-related changes are authorized and scheduled safely by establishing the criteria for different change types.

    • Release Management

      While this practice handles the operational packaging of the code, it does not set the overarching authorization policies or risk thresholds.

    • Deployment Management

      This practice is concerned with the actual movement of software across environments, rather than the strategic authorization and risk assessment of those moves.

    • Service Configuration Management

      This practice provides the data required for an impact analysis but does not hold the authority to approve or govern the change lifecycle.

  2. 2 An organization is deploying an AI-driven service that continuously updates its own algorithms. Which practice must establish the specific 'algorithmic risk' guardrails within the Plan, Implement, and Control (PIC) domain?

    Think about the practice responsible for evaluating risks before a new capability is moved to a live environment.

    Change Enablement

    Under ITIL 5, this practice must account for accountability and risk when automated models or AI execute decisions within a change.

    • IT Asset Management

      This practice focuses on the financial and compliance lifecycle of the assets rather than the operational risks of algorithmic decision-making.

    • Deployment Management

      While it moves the AI model to production, it does not define the governance of the algorithm's inherent logic or its potential for bias.

    • Service Configuration Management

      This practice records the version of the algorithm as a configuration item but does not evaluate the risk of the algorithm's output.

  3. 3 What is the critical distinction between Release Management and Deployment Management within the ITIL 5 Product and Service Lifecycle?

    One is about the 'package' being ready for the consumer, and the other is about the 'bits' moving through the pipeline.

    Release Management focuses on making services available for use, while Deployment Management moves components to live environments.

    Release involves the operational packaging and availability of a service to consumers, whereas Deployment is the technical act of moving hardware or software.

    • Deployment Management focuses on authorization, while Release Management focuses on technical movement.

      Authorization is a Change Enablement function, and the technical movement is actually a Deployment function.

    • Release Management is only used for software, while Deployment Management is only used for hardware.

      Both practices handle software, hardware, documentation, and other service components across the lifecycle.

    • Deployment Management is a strategic activity, while Release Management is purely operational.

      Both practices operate at strategic and operational levels within the PIC bundle to ensure value delivery.

  4. 4 A compliance audit reveals that several virtual cloud instances have been active for six months without being associated with a cost center. Which practice failed to trigger a control point?

    Look for the practice that manages the financial and contractual aspects of technology components.

    IT Asset Management (ITAM)

    ITAM is responsible for tracking the financial and compliance lifecycle of physical, virtual, and cloud assets.

    • Change Enablement

      This practice governs the authorization of the change but does not primarily manage the long-term financial lifecycle or cost-center mapping.

    • Release Management

      This practice handles the packaging of the service but does not typically monitor ongoing financial asset data.

    • Service Configuration Management

      While it tracks the relationship of the virtual server to an application, ITAM is the specific practice for financial accountability.

  5. 5 When mapping a value stream for a 'complex' environment using the ITIL Transformation Model, which execution pattern should be used to manage the deployment of a new, unpredictable feature?

    This pattern involves testing and feedback because the results of the change cannot be fully known in advance.

    Discover Pattern

    The Discover pattern is applied in complex environments where outcomes are unpredictable, requiring iterative experimentation and continuous feedback.

    • Implement Pattern

      The Implement pattern is reserved for ordered, highly predictable environments where the path to change is well-defined.

    • Contain Pattern

      The Contain pattern is used in chaotic, high-risk situations to stabilize immediate failure rather than to deploy new features.

    • Direct Pattern

      There is no 'Direct' execution pattern within the ITIL 5 Transformation Model layers of governance and execution.

  6. 6 Service Configuration Management provides a vital link between the PIC practices by maintaining a 'CMDB'. According to the IT Skeptic's recommendations in the source material, what is a common mistake in configuration scope?

    The advice suggests being 'severe' in how much you choose to track to ensure data quality.

    Failing to limit the scope of Configuration Management Items (CIs) to essential attributes.

    The source recommends severely limiting configuration scope to avoid unmanageable complexity in the CMDB.

    • Including financial data in the Service Configuration Management database.

      While often separated, including some financial links is not the primary scope error highlighted by the IT Skeptic; rather, the overall volume is the issue.

    • Allowing humans to act as configuration experts instead of relying entirely on tools.

      The source specifically suggests a 'CMDB called Sue' where humans are tasked with knowing the environment's configuration.

    • Updating configuration records only during the 'Operate' stage of the lifecycle.

      Configuration must be updated throughout the lifecycle, but the core 'Skeptic' critique is the excessive scope of the data itself.

  7. 7 In the PIC bundle, which Practice Success Factor (PSF) is shared by both Release Management and Deployment Management to ensure a smooth 'Transition' activity?

    Think about the shared goal of moving work safely through the staging and testing phases of the lifecycle.

    Ensuring the stability and performance of components in non-production environments.

    Both practices must collaborate to ensure that components move through testing and staging without degrading or failing before reaching production.

    • Providing the financial authorization for software license procurement.

      Procurement and financial authorization are primarily the domain of IT Asset Management, not Release or Deployment.

    • Mapping the relationships between the CEO and the Product Owners.

      Mapping organizational relationships is a general management practice, often handled by Relationship Management, not technical PIC practices.

    • Maintaining the authoritative records of all physical hardware locations.

      This is a core objective of IT Asset Management and Service Configuration Management rather than a specific Release/Deployment PSF.

  8. 8 When conducting a Compliance Audit for a digital product, which practice provides the 'authoritative source' for proof of software license entitlement?

    This practice handles the business side of assets, including contracts and financial lifecycle.

    IT Asset Management (ITAM)

    ITAM manages the contractual and financial records required to prove compliance with software licensing agreements.

    • Service Configuration Management

      While it shows that the software is installed (the discovery), it does not hold the legal or financial 'entitlement' records.

    • Deployment Management

      This practice moves the software but does not keep records of the purchase or the license terms.

    • Change Enablement

      Change Enablement checks if a license exists before authorizing, but it is not the actual repository or owner of that data.

  9. 9 A 'Standard Change' in an automated deployment pipeline fails, causing a service outage. Which interaction within the PIC practices is responsible for investigating if the configuration data used to build the automated script was inaccurate?

    This requires comparing the actual system architecture with the data stored in the CMDB.

    Service Configuration Management interacting with Change Enablement.

    Service Configuration Management must provide accurate data for the authorization and execution logic of automated changes.

    • IT Asset Management interacting with Release Management.

      ITAM focuses on the financial/contractual state, which is unlikely to be the technical cause of a build script failure.

    • Deployment Management interacting with Relationship Management.

      Relationship Management is a general practice; it would not be involved in technical root cause analysis of a build script.

    • Supplier Management interacting with Service Level Management.

      These are part of the CAI bundle and are not responsible for the technical configuration of internal deployment pipelines.

  10. 10 In the ITIL 5 Product and Service Lifecycle, the activities of 'Design' and 'Transition' have been split. Why is this significant for the Deployment Management practice?

    The split supports the dual need for rapid technical movement and thoughtful, experience-driven planning.

    It allows 'Transition' to be managed as a highly automated CI/CD pipeline while 'Design' focuses on human-centric experience.

    Splitting these allows technical deployment to move at high velocity while ensuring design maintains a focus on user experience.

    • It forces Deployment Management to occur before any Design activities begin.

      Design logically precedes Deployment in the lifecycle; they are not reversed.

    • It eliminates the need for Configuration Management during the Design stage.

      Configuration Management is needed throughout the entire lifecycle to track design artifacts and architectural plans.

    • It ensures that Deployment Management only handles physical hardware while Design handles software.

      Deployment Management handles both software and hardware; the split is about workflow focus, not asset type.

  11. 11 Change Enablement within PIC must manage 'change authority limits'. In an 'ordered' context, how should these limits be structured?

    Ordered environments are highly predictable, which allows for more traditional, defined management strategies.

    Through well-defined, centralized authorization where outcomes are predictable.

    In ordered environments, the Implement pattern applies, meaning the path is clear and outcomes are certain, allowing for structured authorization.

    • By eliminating all change authorities to maximize speed and bypass governance.

      Governance is never eliminated in ITIL; it is adapted. Ordered contexts still require authorization to maintain stability.

    • By using a decentralized, iterative experimentation model for every minor change.

      Iterative experimentation is for 'complex' environments (Discover pattern), not 'ordered' ones.

    • By applying the 'Contain' pattern to ensure no changes are made until the environment becomes chaotic.

      The Contain pattern is for managing existing chaos, not for preventing changes in a stable, ordered environment.

  12. 12 Service Configuration Management must provide information about 'configuration support items'. Which of the following is a primary objective of this activity in the PIC domain?

    This practice is about the 'knowledge' of how parts of the IT environment fit together.

    Providing accurate information about system architectures and dependencies when and where needed.

    This practice ensures that decision-makers have the telemetry and data required to assess impacts and plan deployments.

    • Restoring service as quickly as possible during a major incident.

      Restoring service is the primary objective of Incident Management, which is in the MSF bundle.

    • Negotiating service level agreements with internal customers.

      This is a function of Service Level Management within the CAI bundle.

    • Tracking the depreciation of physical server assets for the finance department.

      Tracking financial depreciation is a specific objective of IT Asset Management (ITAM), not Configuration Management.

  13. 13 In the PIC module, which practice is responsible for ensuring that the hardware and software are 'operationally packaged' before they are deployed?

    Think about the stage where a set of changes is bundled into a single unit for consumer use.

    Release Management

    Release Management controls the operational packaging of new and changed services, ensuring they are ready for use.

    • Deployment Management

      Deployment handles the transport of the package, but Release handles the creation and integrity of the package itself.

    • IT Asset Management

      ITAM manages the lifecycle and costs of the items in the package but not the operational readiness of the package.

    • Service Configuration Management

      This practice identifies the components within the package but does not perform the packaging or release readiness checks.

  14. 14 During a 'Structural Business Change' such as a merger, the PIC practices must integrate two different CMDBs. Which initiation pattern does this situation fall under in the Transformation Model?

    This pattern is triggered when the organization's corporate structure or identity undergoes a significant modification.

    Structural Business Change

    This pattern is specifically deployed to support major corporate restructurings, joint ventures, or mergers and acquisitions.

    • Market Demand

      Market Demand triggers are launched to capture new customers or respond to competitors, not for internal corporate restructuring.

    • Reactive Technology-Driven Change

      This is triggered by legacy obsolescence or failures, whereas a merger is a strategic business decision.

    • Internal Improvement or Remediation

      While a merger might include improvements, it is primarily categorized by the structural change in corporate ownership/form.

  15. 15 If a Deployment Management team moves a new software patch to a staging environment without updating the CMDB, which PIC practice's core value is being compromised?

    This practice is centered on providing reliable data about the state of the digital environment.

    Service Configuration Management

    The value of Configuration Management is to provide accurate and reliable information; failing to update records makes the data unreliable.

    • Release Management

      While it affects the release, the specific failure to maintain a data record is a configuration management failure.

    • IT Asset Management

      Software patches themselves are not usually individual financial assets, making ITAM a secondary concern compared to technical configuration.

    • Change Enablement

      Change Enablement relies on configuration data for authorization, but the data maintenance itself belongs to Configuration Management.

  16. 16 Which tool or technique is used by the Practice Manager within the PIC domain to identify process bottlenecks and optimize the flow of code from discovery to support?

    This technique involves creating a visual representation of all the steps in a process to find waste or delays.

    Value Stream Mapping (VSM)

    VSM is specifically used to visualize operational workflows, identify bottlenecks, and optimize the flow of work.

    • SWOT Analysis

      SWOT is a general strategic tool and is not specifically designed to map the minute-to-minute flow of a technical pipeline.

    • RACI Matrix

      A RACI matrix clarifies accountabilities but does not visualize the temporal or procedural flow of work in a pipeline.

    • The Theory of Constraints (ToC)

      While ToC is used to maximize output, VSM is the specific mapping technique mentioned for identifying and visualizing flow.

  17. 17 An IT Asset Management (ITAM) practice needs to determine which cloud-based virtual machines are currently 'Transitioning' to live operations. Which practice provides the necessary status updates?

    This practice is in charge of the actual transfer of components between different environments.

    Deployment Management

    Deployment Management governs the movement of software and hardware across staging, testing, and production environments.

    • Service Level Management

      This practice monitors targets and metrics but does not manage the physical or virtual movement of assets.

    • Relationship Management

      Relationship Management handles communication and alignment, not technical environment movement.

    • Problem Management

      Problem Management investigates root causes of incidents and is not responsible for moving assets through environments.

  18. 18 Under the 'Execution Layer' of the ITIL Transformation Model, a Practice Manager in the PIC domain is deploying a new automated change authorization tool. What is the primary focus of this layer?

    This layer is where the actual 'work' of implementing the transformation occurs.

    Governing the deployment of changes across people, processes, products, and tools.

    The execution layer is responsible for the actual deployment and management of changes during a transformation.

    • Setting the ethical compliance and overall strategic direction.

      Ethical compliance and overall direction are set in the Governance Layer, not Execution.

    • Capturing feedback and evaluating signals of change for the organization.

      Feedback and learning from signals are handled in the Learning Layer.

    • Analyzing current operational baselines and team readiness.

      Baseline analysis and readiness evaluation are part of the Positioning Layer.

  19. 19 A major security breach occurs, and the organization must immediately deploy an emergency patch to all servers. According to the ITIL 5 Transformation Model, which execution pattern is most appropriate?

    This pattern is designed to stabilize a critical situation before moving to long-term improvements.

    Contain Pattern

    The Contain pattern is deployed in chaotic, high-risk situations (like a breach) to stabilize immediate failure.

    • Implement Pattern

      An emergency patch in a high-risk scenario is not 'highly predictable' or 'ordered,' making the Implement pattern insufficient.

    • Discover Pattern

      Discovery is for complex, unpredictable feature development, whereas an emergency patch is a reaction to a chaotic threat.

    • Governance Pattern

      Governance is a layer of the model, not an execution pattern used to stabilize high-risk failure.

  20. 20 Release Management in the PIC bundle emphasizes 'experience-driven' service design. How does this influence the criteria for a successful release?

    Think about how ITIL 5 prioritizes human-centricity and stakeholder value.

    Success is measured by the user’s experience and engagement rather than just technical uptime.

    ITIL 5 shifts focus toward Digital Experience (DX), making user and customer experience core pillars of success.

    • Success is measured solely by the number of configuration items updated in the CMDB.

      While CMDB updates are important, they are a process metric, not a measure of the ultimate 'success' of the service delivery.

    • Success is determined by whether the deployment was completed under the original budget.

      Budget is an ITAM concern, but Release Management focuses on the value and quality perceived by the user.

    • Success is measured by the total number of lines of code deployed per hour.

      Velocity metrics like lines of code do not reflect user experience or value co-creation.

  21. 21 Which practice within the PIC domain holds the primary responsibility for ensuring technology-related changes are authorized and scheduled safely?

    This practice is the 'gatekeeper' of the change process, focusing on risk mitigation.

    Change Enablement

    Change Enablement ensures that risks are assessed and changes are authorized and scheduled correctly.

    • Deployment Management

      Deployment is the execution of the change, but it does not perform the authorization or high-level scheduling.

    • Release Management

      Release ensures readiness, but Change Enablement is the specific practice that governs the authorization process.

    • Service Configuration Management

      This practice provides information to support the change decision but does not hold the authorization role.

  22. 22 A Practice Manager is using a RACI matrix to clarify team accountabilities during a large deployment. Which PIC practice is most likely to be 'Accountable' for the final data accuracy of the CMDB after the move?

    This practice 'owns' the records that describe the architecture and components of the environment.

    Service Configuration Management

    Service Configuration Management is specifically responsible for providing accurate and reliable information about service configurations.

    • Deployment Management

      Deployment teams are 'Responsible' for the move, but Configuration Management is 'Accountable' for the resulting data accuracy.

    • IT Asset Management

      ITAM is accountable for financial records, but the technical configuration data belongs to Service Configuration Management.

    • Change Enablement

      Change Enablement uses the data but is not the owner or custodian of the configuration data repository.

  23. 23 In the context of PIC, what is 'Service Configuration Management''s role in supporting Change Enablement?

    This practice provides the 'map' that tells Change Enablement what might break if a component is modified.

    It provides accurate data about system architectures and dependencies to evaluate the potential impact of a change.

    This information is essential for Change Enablement to conduct thorough risk assessments and authorize changes safely.

    • It performs the technical deployment of the software after the change is authorized.

      Technical deployment is a function of Deployment Management, not Configuration Management.

    • It manages the financial lifecycle of the assets being changed.

      Financial lifecycle management is the core function of IT Asset Management (ITAM).

    • It creates the operational package that bundles multiple changes together.

      Creating the operational package is a core activity of Release Management.

  24. 24 An organization is using 'on-demand CMDB' experts, as suggested by the source material. These experts are tasked with producing configuration data only when needed. Which PIC practice would most benefit from this during a complex release?

    This role acts as a human alternative to a potentially over-scoped and inaccurate automated database.

    Service Configuration Management

    This human-centric approach to configuration expertise is a specific strategy within Service Configuration Management to manage complexity.

    • IT Asset Management

      ITAM requires continuous financial records for audits; 'on-demand' snapshots are less effective for financial compliance.

    • Deployment Management

      Deployment teams need real-time automation data; an 'on-demand' human team might be too slow for modern CI/CD needs.

    • Change Enablement

      While Change Enablement uses the data, the 'experts' themselves are part of the Configuration Management capability.

  25. 25 During a 'Reactive Technology-Driven Change' caused by a hardware failure, which PIC practice ensures the replacement hardware is recorded and its warranty is activated?

    This practice handles the business, contractual, and financial lifecycle of the physical components.

    IT Asset Management (ITAM)

    ITAM is specifically responsible for managing the financial and compliance aspects of assets, including warranties.

    • Deployment Management

      Deployment installs the hardware but does not typically handle the business contract (warranty) management.

    • Release Management

      Release Management focuses on service availability and packaging rather than physical hardware inventory or warranty terms.

    • Service Configuration Management

      This practice records that the hardware exists, but ITAM is responsible for the financial/contractual 'warranty' data.

  26. 26 What is the primary cognitive competency objective for Domain 5 (Value Stream Identification & Mapping) in the ITIL 5 Foundation exam?

    It involves using tools like VSM to see how work moves through an organization.

    Visualizing operational workflows and optimizing the flow of work.

    This domain tests the ability to apply value stream mapping (VSM) techniques to improve efficiency.

    • Comprehending the difference between utility and warranty.

      Utility and warranty concepts are part of Domain 1 (Key ITIL Terms & Definitions).

    • Understanding how the guiding principles work as a system.

      This is a core objective of Domain 2 (ITIL Value System).

    • Analyzing the four dimensions across Partners & Suppliers.

      This is evaluated in Domain 3 (Four Dimensions of Product and Service Management).

  27. 27 In the PIC bundle, 'Release Management' ensures services are available for use in line with 'policies and agreements'. Which 'agreement' is most relevant to this practice?

    This agreement defines the expected performance, uptime, and quality targets for the service being released.

    Service Level Agreements (SLAs)

    Release Management must ensure that the new or changed services can meet the targets defined in the SLAs.

    • Employment Contracts

      While important, employment contracts are HR/People dimensions and not the primary 'agreement' governing a service release.

    • Building Lease Agreements

      Facilities agreements are too far removed from the digital product and service management (DPSM) lifecycle.

    • Non-Disclosure Agreements (NDAs)

      NDAs are general legal protections and do not specify the operational performance or availability of a digital service.

  28. 28 A Practice Manager in the PIC domain is managing a 'complex' transformation where the outcomes are unpredictable. Which tool should be used to measure outcome achievement iteratively?

    This tool focuses on setting ambitious goals and tracking the specific results that prove success.

    Objectives and Key Results (OKRs)

    OKRs are recommended in the ITIL 5 Transformation curriculum for measuring the achievement of outcomes.

    • Mean Time to Repair (MTTR)

      MTTR is an operational support metric (MSF) rather than a strategic transformation measurement tool for complex outcomes.

    • Lines of Code (LoC)

      LoC measures technical volume, not the achievement of business outcomes or strategic objectives.

    • Total Cost of Ownership (TCO)

      TCO is a financial metric used in ITAM, but it does not measure the strategic 'outcomes' of a transformation initiative.

  29. 29 When moving new code to a live environment, Deployment Management must consider the 'moving' of software, hardware, and which other component?

    This component is essential for users and support staff to understand how to use and maintain the new service.

    Documentation

    Deployment Management is responsible for moving software, hardware, documentation, processes, or any other service component.

    • Financial Capital

      Deployment moves technical components; financial assets are managed through the ITAM practice and finance departments.

    • Staff Members

      While people are a dimension, Deployment Management moves the *tools* and *components* they use, not the humans themselves.

    • Corporate Trademarks

      Legal IP like trademarks are not moved as part of a technical deployment pipeline into a live environment.

  30. 30 The PIC practices are essential for 'governing code deployment pipelines'. What is the ultimate 'Strategic Value' of the PIC bundle as defined in the Research Report?

    Think about how the 'Plan, Implement, and Control' title reflects the balance of speed and stability.

    Effective strategic execution and risk mitigation through controlled changes.

    The PIC bundle focuses on bridging development with control to ensure reliability and minimize business risk.

    • Maximizing the uptime of the service desk through catalog-driven workflows.

      Service desk optimization is the strategic value of the MSF (Monitor, Support and Fulfil) bundle.

    • Strengthening relationship management and managing supplier performance.

      These activities define the strategic value of the CAI (Collaborate, Assure and Improve) bundle.

    • Reducing the total number of IT assets to lower the corporate tax burden.

      While ITAM helps with taxes, the overall 'Strategic Value' of the PIC bundle is broader, focusing on controlled implementation.