Free ITIL-4-SPECIALIST-HIGH-VELOCITY Practice Test Questions and Answers (2026)

The activity described—analyzing how the amount of work done by different user groups varies over time—is a fundamental component of demand and capacity management. This analysis helps to identify and understand Patterns of Business Activity (PBA). By understanding these patterns, a service provider can forecast future demand, plan the required capacity, and develop strategies to manage demand. This includes both supporting demand by ensuring sufficient resources are available during peak times and influencing demand, for example, by offering incentives to use services during off-peak hours. This proactive approach is central to optimizing service delivery and resource utilization.

B. To identify inefficiencies in service delivery: This analysis focuses on the volume of user demand, not the performance or efficiency of the internal service delivery processes themselves.

C. To forecast the costs of delivering services: While demand is a key input for cost forecasting, the primary and most direct use of this specific analysis is to manage the demand and the capacity to meet it.

D. To prioritize resources for the most active user groups: This is a reactive tactic. A strategic approach, as described in option A, involves understanding and managing demand from all user groups based on business value, not just activity levels.

1. AXELOS, ITIL® 4 Specialist: High-Velocity IT. TSO (The Stationery Office), 2020.

Section 4.2.4 (Capacity management): "Capacity management is closely related to demand management. Demand for services is not constant; it varies over time, depending on patterns of business activity (PBA). To ensure that services have sufficient capacity, it is important to understand PBA and translate them into demand profiles for services and components." This directly supports that analyzing work variation over time (PBA) is used to plan how to support demand.

2. AXELOS, ITIL® 4 Foundation, ITIL 4 Edition. TSO (The Stationery Office), 2019.

Section 5.2.3 (Demand management): The purpose of demand management is "to understand, predict, and influence customer demand for services." The analysis described in the question is the foundational step ("understand") required to effectively predict and influence demand.

The core principle of ITIL 4, particularly emphasized in High-Velocity IT (HVIT), is the co-creation of value through enabling customer outcomes. To ensure that a service is truly valuable, its performance must be measured in the context of what the customer is trying to achieve. Therefore, mapping service performance metrics (e.g., availability, transaction speed, resolution times) directly to specific customer outcomes (e.g., processing sales orders, onboarding new employees) is the correct approach. This ensures that the service provider's efforts and resources are focused on activities that directly contribute to the customer's success and perceived value.

A. IT component scorecards should be mapped to service provider outcomes

This mapping is indirect and internally focused. Component performance contributes to service performance, which in turn enables customer outcomes, not directly to the provider's business outcomes.

B. Customer satisfaction feedback should be mapped to service provider outcomes

Customer satisfaction is a reflection of whether customer outcomes are being met. While it influences provider outcomes (like revenue), the primary mapping should be from service performance to customer outcomes.

D. Return on investment (ROI) should be mapped to customer outcomes

ROI is a financial metric for the service provider. Achieving customer outcomes is a key driver for a positive ROI, but the performance reporting link is from the service to the customer outcome.

1. AXELOS, ITIL® 4 Specialist: High-velocity IT, 2020. Section 4.3.3, 'Meaningful measurement and reporting', states: "In HVIT, it is important to map service performance metrics to customer outcomes. This helps to ensure that the service provider is focused on what is important to the customer and that the service is delivering value." This section explicitly supports the correct answer (C) and explains the rationale behind it.

2. AXELOS, ITIL® 4 Specialist: High-velocity IT, 2020. Section 4.3.3 also implicitly refutes the other options by cautioning against focusing solely on internal technical metrics (related to option A) or financial metrics (related to option D) without a clear line of sight to customer value. It emphasizes that metrics should support value co-creation.

A value stream represents the end-to-end series of activities required to create and deliver value to a consumer. When multiple teams contribute to a single service, creating one overarching value stream provides a holistic, shared vision of the entire workflow. This end-to-end perspective is critical in a High Velocity IT environment to visualize the flow of work, identify constraints and bottlenecks across team boundaries, and optimize the entire system for speed and quality. It ensures all teams understand how their contributions fit together to deliver the final outcome, breaking down functional silos and fostering collaboration towards a common goal.

B. The 'four dimensions' are lenses through which to analyze a value stream; they are not separate value streams. This approach would incorrectly fragment the holistic view.

C. A value stream should represent the continuous flow of value, not be artificially segmented by project phases. This would create handoff delays and obscure the end-to-end process.

D. Creating a value stream for each team reinforces organizational silos and focuses on team-specific outputs rather than the integrated flow of value to the customer.

1. AXELOS, ITIL® 4 Specialist: High-velocity IT (2020), Section 3.3.1, 'Use value stream mapping to understand and improve the flow of work': "Value stream mapping helps to visualize the flow of work from end to end... It helps to identify where the bottlenecks are and where there are opportunities to improve the flow." This supports the need for an end-to-end, holistic view (Answer A) rather than fragmented views (Answers B, C, D).

2. AXELOS, ITIL® 4 Foundation (2019), Section 4.5, 'Service value streams': "A value stream is a series of steps an organization undertakes to create and deliver products and services to consumers." This core definition emphasizes a single, complete series of steps for a given outcome, aligning with the concept of one value stream for the entire project.

3. AXELOS, ITIL® 4 Specialist: High-velocity IT (2020), Section 2.2.3, 'Value streams and processes': This section reinforces that value streams are specifically designed to see the "big picture" and understand how value is actually created, which is lost when the view is siloed by team, phase, or dimension.

A service mindset is an attitude focused on the co-creation of value with service consumers. In this scenario, the IT team is focused on the technology (their output), while the users are not realizing the potential value. Adopting a service mindset means shifting focus from the application's features to the outcomes users and the enterprise can achieve. By encouraging users to understand how the new features contribute to organizational objectives, the IT team helps them see the value, fostering willing adoption and co-creating better outcomes. This collaborative and value-centric approach is the essence of the service mindset.

B. By simplifying the new application to make it identical to the old one

This negates the purpose of the new application and destroys the potential for value improvement, which is contrary to a service mindset.

C. By limiting user access to only the new features of the application

This is a coercive, technology-centric approach that can lead to user frustration and is not aligned with the empathetic, collaborative nature of a service mindset.

D. By creating strict policies to enforce the use of new features

This command-and-control method ignores the user's perspective and the co-creation of value, which are central tenets of a service mindset.

AXELOS, ITIL® 4 Specialist: High-velocity IT (2020), Section 2.2.4.1, What is a service mindset?: "A service mindset means that the service provider is focused on the co-creation of value in the form of outcomes that the service consumer wants to achieve." This directly supports option A, which links the application's use to achieving objectives (outcomes).

AXELOS, ITIL® 4 Specialist: High-velocity IT (2020), Section 2.2.4.2, Why is a service mindset important?: The text explains that without a service mindset, "service providers may focus on their own activities and outputs, rather than on the value that is co-created with the service consumer." This highlights the flaw in the IT team's initial approach and why options C and D, which are output-focused, are incorrect.

AXELOS, ITIL® 4 Specialist: High-velocity IT (2020), Section 2.2.4, Helpful models and concepts: "A service mindset is an attitude that focuses on creating value for others." This principle refutes option B, which would actively prevent the creation of new value.

This scenario involves managing the human aspect of a major change where resistance is anticipated. The most appropriate approach combines multiple communication strategies with a mechanism for safe feedback. Using a mix of communication methods (e.g., town halls, emails, team meetings) ensures the message reaches everyone effectively. Crucially, providing an anonymous feedback channel addresses the need for sensitivity and the expectation of resistance. This fosters psychological safety, allowing staff to voice genuine concerns without fear of reprisal, which is essential for successful organizational change management in a high-velocity environment.

A. A single email, even a detailed one, is a poor method for sensitive change communication as it is impersonal, one-way, and can lead to information overload and misinterpretation.

B. Instant messaging is too informal for major announcements and lacks the structure for complex information. It also fails to provide the anonymity needed for sensitive feedback.

C. While using a mix of methods is good, sharing all feedback openly on a public forum would destroy psychological safety and discourage honest, critical input from staff.

1. AXELOS, ITIL® 4 Specialist: High-Velocity IT (2020), Section 3.2.5.1 'Psychological safety': This section emphasizes that psychological safety is a shared belief that a team is safe for interpersonal risk-taking. An anonymous feedback mechanism is a key tool to build this safety, especially during a contentious change, as it allows people to be vulnerable and express concerns without fear.

2. AXELOS, ITIL® 4 Specialist: High-Velocity IT (2020), Section 4.1.10 'Organizational change management (OCM)': This section highlights that OCM addresses the "people side of change." A core part of this is not just communicating the vision but also actively listening to and addressing people's concerns. An anonymous channel is a powerful method for listening when direct feedback is perceived as risky by employees.

The 'Organizations and people' dimension of service management covers the formal organizational structures, culture, and the required staffing and competencies. It is concerned with how an organization is structured and managed, including its roles, responsibilities, and systems of authority and communication. This dimension ensures that these elements are well-defined and support the overall strategy and operating model. Governance, management systems, and communication channels are fundamental components of this dimension, as they dictate how people and teams interact and are directed to co-create value.

A. Information and technology: This dimension pertains to the information, knowledge, and technologies required for service management, not the organizational structure, governance, or communication systems.

B. Partners and suppliers: This dimension focuses on an organization's relationships with external entities involved in service delivery, not its internal management and governance structures.

D. Value streams and processes: This dimension is concerned with the activities, workflows, and controls that coordinate work to create value, rather than the overarching organizational governance and communication framework.

1. AXELOS. (2019). ITIL® Foundation, ITIL 4 edition. TSO (The Stationery Office).

Section 3.1.1, Organizations and people: "It is important to ensure that the way an organization is structured and managed, as well as its roles, responsibilities, and systems of authority and communication, is well defined and supports its overall strategy and operating model." This section explicitly links management, systems of authority (governance), and communication to this dimension.

2. AXELOS. (2020). ITIL® 4 Specialist: High-velocity IT. TSO (The Stationery Office).

Section 2.1.1, The ITIL service value system: This section reviews the four dimensions as a core component of the SVS, reinforcing the foundational definitions. The principles of HVIT are applied through these dimensions, but their core definitions remain consistent with the Foundation publication. For example, discussions on culture (Section 3.2.1) are an application of the 'Organizations and people' dimension.

In a High Velocity IT environment, the entire service lifecycle is considered from the earliest stages. Planning for service onboarding during the design phase is a critical 'shift-left' activity. This ensures that the user experience, necessary support structures, documentation, and access mechanisms are built into the service from the beginning, rather than being an afterthought. This proactive approach facilitates a smooth, efficient, and positive transition for users, which is essential for rapid value co-creation and adoption of the new service.

A. Onboarding is the process of making a service operational and available to users; it is not a post-operational activity.

C. Customer and user involvement is crucial in designing an effective onboarding process to ensure it meets their needs and provides a good experience.

D. Onboarding is a mandatory process for new services to enable users to access, understand, and derive value from them.

AXELOS. (2020). ITIL® 4 Specialist: High-Velocity IT. TSO (The Stationery Office).

Section 4.2.6, Service onboarding: "The onboarding process should be planned during the design of the service. This ensures that the onboarding process is designed to provide a good user experience." This directly supports option B and refutes options A and C.

Section 4.2.6, Service onboarding: The entire section describes onboarding as a necessary step to move a service to production and make it available to users, which implicitly refutes the idea that it is optional (Option D).

The core issue identified is a lack of soft skills (listening, empathy) and a behavioral problem (making assumptions) among service desk agents. This is a human-centric problem related to capability and competence. The most direct and effective way to address such a skills gap is through targeted training. Improving the training for service desk staff in areas like active listening, customer service excellence, and empathy will directly address the root cause of the user complaints. This aligns with the ITIL emphasis on investing in people's skills to co-create value and improve the customer experience.

A. Automating service desk processes to reduce human error

Automation addresses process consistency and efficiency, not the quality of human interaction or the interpersonal skills that are lacking.

C. Increase the number of service desk agents available

Adding more agents does not solve the underlying problem of poor communication skills; it would likely just result in more users having the same negative experience.

D. Implement stricter service desk performance metrics

Stricter metrics, particularly those focused on speed (e.g., average handle time), could worsen the situation by pressuring agents to rush, listen less, and make more assumptions.

1. ITIL® 4 Specialist: High-velocity IT, AXELOS (2020), Section 3.2.5 (Valuable investments): This section emphasizes that "Investing in people is probably the most important investment an organization can make. This includes hiring the right people, training them, and providing them with the tools and environment they need to succeed." This directly supports training as the solution to a staff capability issue.

2. ITIL® 4 Foundation, ITIL 4 Edition, AXELOS (2019), Section 5.2.14 (Service desk): This section states, "It is important that service desk staff have the right mix of technical and business understanding, as well as excellent customer service and communication skills." The scenario clearly indicates a deficit in these communication skills, reinforcing the need for training.

A value stream is defined as the series of steps an organization undertakes to create and deliver products and services to a consumer. For service support, this translates to a single, end-to-end flow of activities from the initial support request (demand) to the final resolution (value). Creating one value stream for the entire set of support activities provides a holistic view, enabling the organization to visualize the complete workflow, identify bottlenecks, eliminate waste (such as excessive handoffs between teams), and optimize the overall time to resolution. This approach aligns with Lean principles, which are fundamental to high-velocity IT.

A. Create one value stream for each support team: This approach fragments the end-to-end process and reinforces organizational silos, which is contrary to the purpose of value stream mapping.

B. Create one value stream for every lifecycle phase of support requests: This breaks the holistic view of the support process, making it difficult to optimize the overall flow from request to resolution.

D. Create separate value streams for practices, people, tools and suppliers: These are resources and enablers that contribute to the activities within a value stream; they are not value streams themselves.

1. AXELOS, ITIL® 4 Specialist: High-velocity IT (2020), Section 3.2.1, "What is a value stream?": This section defines a value stream as "a series of steps an organization uses to create and deliver products and services to a service consumer." It emphasizes the end-to-end nature of the flow, which supports creating a single value stream for the entire set of activities.

2. AXELOS, ITIL® 4 Specialist: High-velocity IT (2020), Section 3.2.2, "Value stream mapping": This section explains that value stream mapping is used to "analyse the current state and design a future state for the series of events that take a product or service from its conception through to the customer." This analysis requires a complete, end-to-end view, not a fragmented one.

3. AXELOS, ITIL® 4 Foundation, ITIL 4 Edition (2019), Section 4.5, "The ITIL service value chain": This foundational text states, "An organization’s service value chain will have a number of value streams... A value stream is a specific combination of activities and practices, and each one is designed for a particular scenario." For the scenario of "service support," a single, comprehensive value stream is the correct model.

The question asks to identify sources of demand that would initiate a value stream focused on restoring a live service. This is synonymous with identifying triggers for the incident management practice. A source of demand is an input that creates work for the value stream.

1. A user being unable to log in is a direct report of a service failure, creating demand for restoration.

2. A monitoring tool detecting a failure is an automated event that also signals a service failure, creating demand for the restoration value stream.

Both are valid triggers that initiate the process of restoring a service.

3. The service desk calls a user to provide a status update for an incident: This is an activity within the service restoration value stream, not a source of demand that initiates it.

4. A user provides feedback to the incident manager when an incident is closed: This occurs after the service has been restored and is an input for service improvement, not a trigger for restoration.

1. AXELOS, ITIL® 4 Foundation. TSO (The Stationery Office), 2019.

Section 5.2.5 (Incident management practice): "Incidents can be raised by anyone who detects an issue... This includes users, IT staff, and third parties. Incidents can also be logged automatically by monitoring tools that create an incident record when a certain event is detected." This directly supports that both user reports (Option 1) and monitoring tool alerts (Option 2) are sources for initiating service restoration.

2. AXELOS, ITIL® 4 Specialist: High-Velocity IT. TSO (The Stationery Office), 2020.

Section 4.3.3 (Incident management): "In a high-velocity environment, it is important to detect and record incidents as quickly as possible. This is often achieved through automation, where monitoring tools detect a deviation from normal or expected service behaviour and automatically log an incident." This reference explicitly validates automated detection (Option 2) as a key source of demand in HVIT. User-reported incidents (Option 1) remain a fundamental source, as assumed by the practice's existence.

3. AXELOS, ITIL® 4: Create, Deliver and Support. TSO (The Stationery Office), 2020.

Section 5.1.8 (Value stream for user support): This section describes the triggers for a value stream that restores service, stating, "The trigger for this value stream is an issue reported by a user or a potential issue identified by a monitoring system." This confirms that both user reports and monitoring alerts are primary triggers (sources of demand).