25 Questions — ITIL 5 – Master : Certified ITIL Master - Domain 6 - High Velocity Culture and Toil Reduction

Expand any question to reveal the correct answer and explanation.

1. 1 An organization is transitionging to a high-velocity culture and implementing blameless postmortems. What is the primary objective of this shift regarding human error?

   Consider the difference between finding a person to blame and finding a process to fix.

   To treat human error as a starting point for investigation into systemic vulnerabilities rather than a conclusion.

   Blameless postmortems seek to understand the environmental and systemic factors that allowed an error to occur, fostering a learning-oriented culture.

   • ✗ To identify the specific individuals responsible for service outages to provide targeted retraining.

     Focusing on individual culpability contradicts the blameless philosophy, which views human error as a symptom of deeper systemic issues.

   • ✗ To eliminate the need for disciplinary action by categorizing all incidents as 'unavoidable technical failures'.

     Simply re-categorizing failures does not improve systemic resilience or address the underlying process gaps that blamelessness aims to fix.

   • ✗ To ensure that all postmortem documentation remains anonymous to protect the psychological safety of the workforce.

     Anonymity is not the goal; rather, the goal is a culture where individuals feel safe to openly discuss their actions to help the organization learn.

2. 2 In the context of ITIL (Version 5) High Velocity IT, which characteristic distinguishes 'toil' from other forms of technical work?

   Focus on the repetitive and tactical nature of the activities.

   The work is manual, repetitive, automatable, and scales linearly with service growth.

   Toil represents administrative or operational tasks that do not provide enduring value and grow at the same rate as the service itself.

   • ✗ The work requires high levels of specialized human judgment and creative problem-solving.

     Toil is specifically characterized by its tactical, repetitive nature and lack of enduring value, whereas creative work is strategic.

   • ✗ The work is essential for long-term service strategy but is currently underfunded.

     Toil refers to the nature of the tasks performed, not their budget status or strategic importance.

   • ✗ The work involves complex cross-functional collaboration and stakeholder management.

     Complex collaboration typically requires the human judgment that toil lacks; toil is often rote and solitary.

3. 3 A team uses AIOps to reduce the 'noise' generated by monitoring systems. According to the ITIL AI Capability Model ($6C$ Model), which capability is being primarily utilized?

   This capability involves recognizing patterns and detecting anomalies in data.

   Cognition

   Cognition encompasses pattern recognition and anomaly detection, which are essential for filtering noise and identifying significant events.

   • ✗ Creation

     Creation involves generating new designs or content, whereas noise reduction is about processing existing data streams.

   • ✗ Communication

     Communication refers to conversational interfaces and portals, not the backend processing of system alerts.

   • ✗ Coordination

     Coordination involves orchestrating workflows and integrations, which usually follows the initial detection of a relevant event.

4. 4 Which component of a High Velocity Culture is most critical for allowing team members to respectfully disagree and take measured risks without fear of retribution?

   Think about the interpersonal environment necessary for innovation and learning from failure.

   Psychological Safety

   Psychological safety is the foundation that enables a safety culture where mistakes are viewed as learning opportunities and dissent is valued.

   • ✗ Automated Change Risk Scoring

     While this supports technical speed, it does not address the interpersonal dynamics required for risk-taking and healthy disagreement.

   • ✗ Incident Command Systems

     Incident Command is a structural approach to managing crises, not a cultural framework for daily interpersonal risk.

   • ✗ Standard Operating Procedures (SOPs)

     Rigid adherence to SOPs can often stifle the very innovation and risk-taking that a high-velocity culture seeks to promote.

5. 5 When implementing 'Change Enablement at Velocity', what is the preferred method for managing low-risk, frequent changes in an ITIL (Version 5) environment?

   Consider how automation and peer-level checks replace traditional, slow approval gates.

   The use of automated peer reviews and integrated continuous delivery pipelines.

   Decentralizing authority through automation and peer review allows changes to flow quickly while maintaining rigorous quality standards.

   • ✗ Weekly review by a centralized Change Advisory Board (CAB) to ensure enterprise-wide alignment.

     Centralized boards often act as approval gates that slow down high-velocity teams without adding significant clarity.

   • ✗ Manual sign-off by a designated Product Owner for every individual code commit.

     Requiring manual intervention for every commit creates a bottleneck that contradicts the principles of high-velocity delivery.

   • ✗ A 'freeze-first' policy where changes are only permitted during designated maintenance windows.

     Change freezes are traditional stability mechanisms that high-velocity organizations seek to replace with continuous resilience.

6. 6 An SRE team defines an Availability SLO of $99.9\%$. If the service is down for $60$ minutes in a $30$-day period, how does this affect their error budget?

   Calculate the total allowable downtime for $99.9\%$ over a month ($30 \times 24 \times 60 \times 0.001$).

   The error budget is completely exhausted and likely in a deficit, requiring a halt on new feature releases.

   Exceeding the allowable downtime defined by the SLO consumes the entire error budget, triggering a shift in focus toward stability.

   • ✗ The error budget is unaffected because $60$ minutes is within the allowable downtime for $99.9\%$ availability.

     At $99.9\%$, the total allowable downtime for $30$ days is approximately $43.2$ minutes; $60$ minutes exceeds this.

   • ✗ The error budget is increased automatically by the AIOps system to compensate for the unexpected volatility.

     Error budgets are fixed targets based on business requirements; they do not expand simply because a failure occurred.

   • ✗ The incident is excluded from the error budget calculation if it was caused by a third-party vendor.

     SLOs measure the user experience, which is impacted regardless of whether the root cause was internal or external.

7. 7 In a High Velocity IT environment, what is the primary role of an 'Incident Commander' during a major service disruption?

   Think of this role as the conductor of an orchestra rather than a musician.

   To lead the response, set priorities, and coordinate the efforts of specialized technical teams.

   Incident Command provides a clear role-based structure to manage resources and decision-making during high-pressure events.

   • ✗ To personally perform the technical troubleshooting and root cause analysis.

     The commander should lead and orchestrate rather than performing the hands-on technical work.

   • ✗ To handle all external communications with customers and the media.

     Communications are typically handled by a Liaison or specialized role, allowing the commander to focus on incident strategy.

   • ✗ To document every action taken during the incident for later use in a 'blame-filled' report.

     While documentation is important, its purpose in high velocity IT is learning, not assigning blame.

8. 8 Why does ITIL (Version 5) advocate for 'Team Topologies' that favor cross-functional product teams over functional silos?

   Consider the impact of organizational structure on the speed of value delivery.

   To reduce the number of handoffs and align teams with the end-to-end product lifecycle.

   Cross-functional teams have the collective skills to move a product from 'Discover' to 'Support' without external dependencies.

   • ✗ To ensure that all employees have identical skill sets to maximize resource fungibility.

     The goal is diverse, complementary skills within a team, not identical skills across the entire workforce.

   • ✗ To centralize specialized knowledge within 'centers of excellence' to improve technical depth.

     Centralizing knowledge in silos often creates the very bottlenecks that cross-functional teams are designed to eliminate.

   • ✗ To lower personnel costs by replacing senior specialists with generalist 'full-stack' developers.

     Team topologies are about optimizing flow and value delivery, not necessarily reducing headcounts or specialist roles.

9. 9 Which term describes the practice of understanding the internal state of a system solely from the data it provides externally, such as logs, metrics, and traces?

   This concept is essential for managing complex, distributed systems where traditional monitoring is insufficient.

   Observability

   Observability allows teams to diagnose 'unknown unknowns' by analyzing the outputs and telemetry emitted by the system.

   • ✗ Monitoring

     Monitoring generally refers to checking for known 'failure' states, whereas this term refers to broader system understanding.

   • ✗ Introspection

     In computing, introspection often refers to a program examining its own type or properties, which is narrower than systemic observability.

   • ✗ Compliance Auditing

     Auditing is a governance activity focused on adherence to rules, not the real-time technical diagnosis of system health.

10. 10 According to the ITIL (Version 5) Master Breakdown, how does 'Shift-Left' impact the workforce culture in high-performing teams?

    Think about the timing of testing and operational planning within the software lifecycle.

    It encourages operational and security considerations to be integrated earlier into the development process.

    Shifting left ensures that non-functional requirements are addressed during design and build, reducing late-stage failures.

    • ✗ It requires all developers to move their desks to the left side of the office to improve airflow.

      This is a literal and incorrect interpretation of a metaphorical term used for process optimization.

    • ✗ It mandates that all senior leadership roles be filled by former developers to ensure technical alignment.

      While technical leadership is valuable, 'shift-left' refers to the timing of activities in the lifecycle, not hiring policies.

    • ✗ It focuses on moving all 'low-value' customers to self-service portals to save support costs.

      This describes a support strategy, but 'shift-left' in HVIT primarily refers to moving testing, security, and ops 'earlier' in time.

11. 11 An organization is using 'Chaos Engineering' as part of its High Velocity IT strategy. What is the ultimate goal of this practice?

    Focus on the relationship between controlled experimentation and systemic resilience.

    To build confidence in the system's ability to withstand turbulent and unexpected conditions in production.

    Chaos engineering uses controlled experiments to identify weaknesses and verify that resilience mechanisms work as intended.

    • ✗ To intentionally disrupt services during peak hours to test the patience of the customer base.

      Intentionally causing outages without a controlled experimental framework is reckless and not the goal of chaos engineering.

    • ✗ To identify which specific engineers are making the most errors in the codebase.

      Chaos engineering tests the system's architectural resilience, not individual performance or culpability.

    • ✗ To replace traditional testing phases with random automated failures to save time.

      Chaos engineering complements traditional testing; it does not replace it and requires a stable baseline to be effective.

12. 12 Which of the following would be considered 'Toil' according to ITIL 5 principles?

    Identify the task that is repetitive, provides no long-term value, and could be automated.

    Manually resetting the same service account password three times a day because the automation tool is broken.

    This task is manual, repetitive, tactical, and could be eliminated through a permanent fix, making it classic toil.

    • ✗ Designing a new automated deployment pipeline for a cloud-native application.

      Designing an automated pipeline is a project-based activity with enduring value, which is the opposite of toil.

    • ✗ Facilitating a strategic workshop to define the product vision for the next fiscal year.

      Strategic workshops require high human judgment and have significant enduring value for the organization.

    • ✗ Writing a 'blameless postmortem' report after a major systemic outage.

      While it can be time-consuming, a postmortem report provides enduring value through organizational learning and improvement.

13. 13 A team implementing High Velocity Culture uses 'Error Budgets' to manage the tension between speed and stability. If a team has consistently exceeded its error budget, what action should they take?

    Think about how a team should pivot its focus when service reliability targets are at risk.

    Prioritize reliability-focused tasks and toil reduction over new feature development until the budget is restored.

    Error budgets provide a data-driven signal to rebalance efforts toward stability when reliability targets are missed.

    • ✗ Increase the budget to $100\%$ to allow for more innovation without the fear of failure.

      A $100\%$ error budget would imply no reliability requirement, which is not a sustainable service management practice.

    • ✗ Disregard the budget and continue pushing features to meet the aggressive marketing deadline.

      Ignoring an error budget defeats its purpose as a governance mechanism for maintaining service health.

    • ✗ Fire the least productive member of the team to signal that performance must improve.

      This is a 'blame-based' reaction that destroys psychological safety and fails to address the systemic causes of instability.

14. 14 In ITIL (Version 5), 'AIOps' is often used to execute 'Coordination' tasks. Which of the following is an example of this?

    Look for an action that involves active orchestration or cross-platform integration.

    Automatically triggering a failover to a redundant server when a primary server heartbeat is lost.

    Coordination involves orchestrating automated workflows and cross-platform integrations to maintain service availability.

    • ✗ Predicting that a hard drive will fail in the next $48$ hours based on vibration patterns.

      This is an example of 'Cognition' (predictive analytics), not the orchestration of an automated response.

    • ✗ A chatbot providing a link to the password reset portal for a user.

      This is an example of 'Communication', facilitating an interface between a human and a system.

    • ✗ Scanning an infrastructure environment to identify all servers missing a critical security patch.

      This is typically part of 'Curation' or 'Cognition' (filtering/analysis), rather than the coordination of a response.

15. 15 High-velocity organizations often utilize 'Lean' principles to improve flow. What is 'waste' (Muda) in a service delivery context?

    Consider the core Lean definition of any step that doesn't add value.

    Any activity that does not directly contribute to the co-creation of value for the stakeholder.

    Lean focuses on eliminating non-value-adding steps to streamline flow and increase the speed of delivery.

    • ✗ The leftover budget at the end of a fiscal year that was not spent on hardware.

      While this might be 'wasteful' in a financial sense, it is not the definition of 'waste' in Lean process optimization.

    • ✗ Technical documentation that is more than six months old.

      Old documentation might be obsolete, but it is only 'waste' if the process of creating/maintaining it doesn't add value.

    • ✗ The energy consumed by servers that are running at less than $50\%$ capacity.

      This is environmental or resource waste, but Lean 'Muda' specifically refers to process-level inefficiencies.

16. 16 The ITIL 5 Managing Professional (MP) syllabus includes 'High Velocity Culture & Toil Reduction' with a $12.5\%$ weighting. Which of these is a key concept in 'High Velocity Culture'?

    Identify the human element that allows for rapid adaptation and learning.

    Psychological safety and trust

    These cultural elements are necessary for teams to experiment, learn from failure, and move quickly with confidence.

    • ✗ Command-and-control leadership

      High velocity requires decentralized decision-making and autonomy, which is the opposite of command-and-control.

    • ✗ Rigid adherence to $v3$ lifecycle stages

      High velocity culture favors flexibility and integrated lifecycles over the rigid, sequential stages of older frameworks.

    • ✗ Annual performance reviews based on ticket volume

      Measuring activity (tickets) rather than outcomes (value/experience) is a traditional management practice that HVIT seeks to evolve.

17. 17 How does 'Toil Reduction' directly contribute to organizational resilience in ITIL (Version 5)?

    Think about the opportunity cost of having experts perform rote, manual tasks.

    By freeing up technical talent to focus on high-value activities like reliability engineering and architectural improvements.

    Reducing toil allows engineers to invest time in the strategic work that prevents future incidents and builds systemic strength.

    • ✗ By ensuring that all employees work exactly $40$ hours per week to prevent burnout.

      Resilience is about system and team capability, not just enforcing specific work hours.

    • ✗ By automating every single task so that human intervention is never required.

      Automating everything is often impossible and risky; resilience requires human judgment for novel or complex situations.

    • ✗ By shifting all repetitive tasks to low-cost offshore providers.

      Outsourcing toil does not reduce it; it just moves it, and can actually decrease resilience due to increased handoff complexity.

18. 18 A team holds a postmortem where they create a 'Timeline of Events'. Why is this important in a blameless culture?

    Consider how knowing what someone knew at the time helps explain why they made a specific choice.

    To understand the context and information available to the responders at each point in the incident.

    Understanding the 'local rationality' of responders helps identify systemic flaws in the tools, data, or processes they used.

    • ✗ To determine who made the first mistake and calculate the financial impact of their error.

      Blameless cultures avoid using timelines to isolate individuals for punishment or financial liability.

    • ✗ To provide evidence for the legal department to sue the vendor responsible for the outage.

      While legal evidence may be a byproduct, the primary cultural goal is internal learning and process improvement.

    • ✗ To prove that the incident could have been avoided if the team had followed the manual exactly.

      This 'hindsight bias' ignores the complexity of real-time operations and is counterproductive to systemic learning.

19. 19 In the ITIL AI Capability Model, 'Curation' is described as filtering and structuring knowledge. How does this help reduce toil?

    Think about how well-organized information helps users help themselves.

    By maintaining accurate, searchable knowledge that allows users to self-solve issues before raising tickets.

    Good curation enables self-service, which prevents repetitive support requests (toil) from reaching the service desk.

    • ✗ By automatically writing new feature code so developers don't have to.

      This describes 'Creation' or 'Coordination', not the curation of knowledge bases.

    • ✗ By monitoring social media for negative comments about the IT department.

      This is a sentiment analysis task (Cognition) rather than the internal curation of service knowledge.

    • ✗ By ensuring that every employee has a physical copy of the ITIL 5 Foundation handbook.

      Distributing physical books is a logistical task, not the digital curation of dynamic operational knowledge.

20. 20 What is the 'Second Story' in the context of blameless postmortems?

    This term refers to looking past the obvious surface-level cause of a failure.

    The deeper, systemic explanation of why an incident occurred, moving beyond 'human error'.

    The 'First Story' is often 'someone messed up'; the 'Second Story' investigates why the system allowed that mess-up to happen.

    • ✗ The official PR statement released to the public that omits the technical details.

      The 'Second Story' is a concept for internal learning, not a sanitized public relations narrative.

    • ✗ The backup plan that is executed only if the primary resolution fails.

      This refers to a contingency plan or technical redundancy, not a narrative approach to incident analysis.

    • ✗ A fictional scenario used during training to simulate a major service outage.

      While simulations are useful, the 'Second Story' specifically refers to the analysis of real, past incidents.

21. 21 A high-velocity team uses 'Peer Review' as their primary change authority. Which organizational risk is this approach primarily designed to mitigate?

    Think about the tradeoff between slow, centralized control and fast, distributed expertise.

    The risk of a centralized Change Advisory Board (CAB) becoming a bottleneck that slows down delivery.

    Peer review provides specialized technical oversight at the speed of the development workflow.

    • ✗ The risk of employees talking to each other too much and wasting time.

      Collaboration is encouraged in HVIT; peer review is a structured way to leverage that collaboration for quality.

    • ✗ The risk of hackers infiltrating the office and changing the server configuration.

      Physical security risks are handled by different controls; peer review is about code quality and operational stability.

    • ✗ The risk of the CEO not knowing every single change that happens in the IT environment.

      It is impractical and undesirable for executives to oversee individual technical changes in a high-velocity environment.

22. 22 In ITIL (Version 5), what is the relationship between 'AIOps' and 'Observability' in a high-velocity environment?

    Consider how one provides the 'eyes' and the other provides the 'brain' for system management.

    Observability provides the telemetry (data) that AIOps uses to detect patterns and automate responses.

    Without the rich data from observability, AI systems lack the context needed for accurate cognition and coordination.

    • ✗ AIOps is the brand name of a specific software, while observability is a legal requirement.

      AIOps is a general practice/technology category, and observability is a technical discipline, not typically a law.

    • ✗ They are the same thing and the terms can be used interchangeably in the exam.

      Interchanging these terms is incorrect; one is about data/transparency (observability) and the other is about processing/action (AIOps).

    • ✗ Observability replaces the need for AIOps by making all systems simple enough for humans to manage.

      Observability often reveals more complexity, which increases the need for AIOps to help humans process the information.

23. 23 Which of these is a symptom of an organization that has 'automated away accountability'?

    Look for a scenario where humans are 'out of the loop' and unable to explain why things are happening.

    No human understands the logic behind an automated decision, and there is no override mechanism.

    Accountability requires that humans can explain, oversee, and intervene in automated processes when necessary.

    • ✗ Teams use automated testing for $100\%$ of their code deployments.

      High levels of automated testing are a best practice and do not inherently remove human accountability for the system.

    • ✗ The service desk uses a chatbot to answer common user questions.

      Using a chatbot for simple tasks is a standard efficiency gain and does not absolve the team of their service responsibilities.

    • ✗ The organization has a dedicated AI Governance module in their training scheme.

      Training in AI governance is a step toward *increasing* accountability, not removing it.

24. 24 In the High Velocity IT domain, what is 'Shift-Left' applied to 'Security' often called?

    Think of the common portmanteau for Development, Security, and Operations.

    DevSecOps

    DevSecOps is the specific integration of security practices into the DevOps and continuous delivery lifecycle.

    • ✗ SafeMode

      SafeMode is usually a computer diagnostic mode, not an organizational process for shifting security left.

    • ✗ SecOpsShift

      While it uses the right words, 'DevSecOps' is the globally recognized industry term for this integration.

    • ✗ GuardRails

      Guardrails are the specific policies or automated checks used within a DevSecOps approach, not the approach itself.

25. 25 A team wants to reduce 'Toil' by $50\%$ over the next six months. What is the first step they should take?

    Consider the importance of data-driven decision-making and establishing a baseline.

    Measure and categorize current activities to identify which tasks actually constitute toil.

    You cannot reduce what you haven't measured; a baseline is essential for identifying the most impactful automation opportunities.

    • ✗ Buy a new expensive AIOps tool and hope it solves the problem automatically.

      Tooling without process understanding and data baseline is rarely successful in reducing toil.

    • ✗ Cancel all meetings to give everyone more time to do manual work.

      Reducing meetings might increase capacity, but it doesn't change the nature of the work from toil to high-value.

    • ✗ Require every team member to work $2$ extra hours a day to 'catch up' on automation tasks.

      This approach leads to burnout and ignores the fact that toil scales linearly with the service; more hours just means more toil.