First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Concepts and definitions of high-velocity IT
In ITIL 4 High-velocity IT, which pair of terms best captures the two complementary dimensions of 'high velocity' that organizations must balance?
- Cost reduction and headcount growth
- Documentation depth and approval layers
- Speed of delivery and stability of service Correct answer.
- Compliance auditing and vendor consolidation
Explanation
High-velocity IT is defined by the ability to deliver quickly while keeping services stable and reliable. The two dimensions are frequently characterized as getting products and services to market fast and getting them to market right, meaning quality and resilience are not sacrificed for speed. Cost, headcount, compliance auditing and documentation depth are not the defining dimensions in this concept.
Question 2Concepts and definitions of high-velocity IT
Which statement best describes the relationship between high-velocity IT and the ITIL 4 service value chain?
- High-velocity IT is a certification scheme unrelated to the value chain
- High-velocity IT is an operating model that accelerates value streams across the whole service value chain Correct answer.
- High-velocity IT replaces the service value chain with a linear delivery pipeline
- High-velocity IT applies to the engage and plan activities only
Explanation
High-velocity IT is an operating model that helps organizations co-create value quickly and reliably across all service value chain activities, not just a subset. It works with the ITIL 4 components such as practices, guiding principles and governance rather than replacing them. The value chain remains the underlying model for how activities convert inputs into value.
Question 3Concepts and definitions of high-velocity IT
A digital bank wants to release new features weekly while keeping its payment services available. Which characterization of high-velocity IT most directly supports this goal?
- Freezing production changes to protect stability
- Resilient operations combined with fast, frequent delivery of value Correct answer.
- Outsourcing all development to reduce internal coordination
- Maximizing the number of change requests approved per quarter
Explanation
High-velocity IT combines fast, frequent delivery of value with resilient, reliable operations. The bank's goal of weekly releases without losing availability is a textbook example of balancing speed and stability. Freezing changes or counting approvals addresses neither dimension directly.
Question 4Concepts and definitions of high-velocity IT
In the ITIL 4 High-velocity IT model, which three foundational concepts underpin the operating model?
- People, process and technology
- Plan, build and run
- Lean, agile and resilient Correct answer.
- Cost, quality and time
Explanation
The high-velocity IT operating model rests on three foundational concepts: lean, agile and resilient. Lean focuses on eliminating waste and improving flow, agile on iterative and adaptive delivery, and resilient on absorbing disruption and recovering quickly. The other options are general management or project constructs, not the HVIT foundations.
Question 5Concepts and definitions of high-velocity IT
Which statement accurately describes the meaning of 'resilient' as a foundational concept of high-velocity IT?
- The ability to avoid all change to production environments
- The ability to prevent every possible incident from occurring
- The ability to absorb disruption and recover quickly while continuing to provide service Correct answer.
- The ability to document recovery procedures in detail
Explanation
Resilience in high-velocity IT means an organization can absorb shocks and recover quickly so that service continues. It accepts that failures happen and emphasizes rapid detection, response and learning. Prevention of all incidents or avoidance of change is neither realistic nor the definition of resilience.
Question 6Concepts and definitions of high-velocity IT
A product team adopts short iterative cycles, frequent customer feedback and the ability to change direction based on what it learns. Which HVIT foundational concept does this most directly illustrate?
- Resilient
- Agile Correct answer.
- Governance
- Lean
Explanation
Agile is characterized by iterative, incremental delivery that welcomes change based on feedback and learning. The team's short cycles and ability to pivot based on customer input are core agile behaviors. Lean concerns flow and waste, resilient concerns absorbing disruption, and governance concerns direction and control.
Question 7Concepts and definitions of high-velocity IT
Which practice best illustrates the lean foundational concept when applied within high-velocity IT?
- Standardizing all work to a single large batch
- Increasing the number of handoffs between teams
- Identifying and eliminating waste in value streams to improve flow Correct answer.
- Adding approval gates to every deployment
Explanation
Lean thinking in high-velocity IT focuses on removing waste and improving the flow of value to the customer. Waste can include waiting, rework, excess handoffs and large batch sizes. Adding gates, handoffs or large batches increases waste and slows flow.
Question 8Concepts and definitions of high-velocity IT
Which of the following is a recognized objective of high-velocity IT?
- Reducing the frequency of customer feedback
- Maximizing the volume of documentation produced
- Increasing the number of management layers
- Shortening the time from idea to value while maintaining quality Correct answer.
Explanation
A central objective of high-velocity IT is to shorten the time it takes to move from idea to delivered value without compromising quality or stability. This is often expressed as faster time to value with high quality. Adding layers, reducing feedback or maximizing documentation does not serve that objective.
Question 9Concepts and definitions of high-velocity IT
Which term in the High-velocity IT model describes the combination of practices, culture and technology that enables fast and resilient delivery?
- Continual improvement register
- Operating model Correct answer.
- Service catalogue
- Service value system
Explanation
High-velocity IT is described as an operating model that brings together practices, culture and technology to enable fast, resilient delivery of value. The service value system is the broader ITIL 4 construct, while the service catalogue and improvement register are specific artifacts or records.
Question 10Concepts and definitions of high-velocity IT
Which behavior is most consistent with the 'co-created value' emphasis in high-velocity IT?
- Designing services in isolation and releasing them without customer input
- Treating value as something the provider alone defines
- Engaging customers and stakeholders continuously to shape and validate value Correct answer.
- Restricting feedback channels to annual surveys
Explanation
High-velocity IT emphasizes that value is co-created through ongoing interaction between providers and consumers. Continuous engagement and feedback help ensure that what is delivered is what the customer actually values. Isolated design and infrequent feedback undermine co-creation.
Question 11Concepts and definitions of high-velocity IT
Which statement best captures the high-velocity IT view of 'fast'?
- Fast means skipping quality checks to release sooner
- Fast means delivering value quickly while maintaining the quality and stability the customer needs Correct answer.
- Fast means reducing the number of services offered
- Fast means increasing the number of change approvals
Explanation
In high-velocity IT, speed is paired with quality and resilience; it is not speed at any cost. The aim is to get products and services to market quickly and correctly. Skipping quality checks, reducing services or adding approvals does not represent the HVIT view of fast.
Question 12Concepts and definitions of high-velocity IT
A team measures the time from when a customer request is received to when the customer receives the resulting value. Which high-velocity IT concept does this measure most directly support?
- Time to value Correct answer.
- Utilization rate
- Approval cycle count
- Documentation coverage
Explanation
Time to value measures how long it takes from a request or idea to the realization of value by the customer. Shortening this lead time is a central concern of high-velocity IT. Utilization, documentation coverage and approval counts do not measure the customer's realization of value.
Question 13Concepts and definitions of high-velocity IT
Which pair of outcomes does high-velocity IT most emphasize for customers?
- Larger batch releases and fewer feedback loops
- Faster delivery of value and reliable, high-quality service Correct answer.
- More documentation and longer approval times
- Lower prices and fewer features
Explanation
High-velocity IT seeks to deliver value faster while maintaining reliable, high-quality service. These two customer-facing outcomes reflect the dual emphasis on speed and stability. Lower prices, more documentation, longer approvals and larger batches are not the defining outcomes.
Question 14Concepts and definitions of high-velocity IT
Which concept from the HVIT model describes the potential for an organization to adapt and respond to change without losing service quality?
- Configuration
- Resilience Correct answer.
- Capacity
- Compliance
Explanation
Resilience is the capacity to absorb disruption and adapt to change while maintaining service quality. Compliance, capacity and configuration are related management concerns but do not describe the adaptive ability itself. Resilience is one of the three HVIT foundational concepts.
Question 15Concepts and definitions of high-velocity IT
A service provider wants to improve its high-velocity IT capability. Which action most directly reflects the lean foundational concept?
- Adding a second review stage before each release
- Mapping the value stream to find and remove non-value-adding steps Correct answer.
- Increasing batch size to reduce the number of releases
- Hiring more approvers for change requests
Explanation
Lean improvement begins with understanding the value stream and removing steps that do not add value. Mapping the value stream exposes delays, rework and handoffs that can be eliminated. Adding approvers, extra reviews or larger batches increases waste and slows flow.
Question 16Concepts and definitions of high-velocity IT
Which statement about the relationship between high-velocity IT and the ITIL 4 guiding principles is accurate?
- High-velocity IT applies only the principle 'focus on value' and no others
- High-velocity IT ignores the guiding principles because speed requires improvisation
- High-velocity IT replaces the guiding principles with a fixed set of KPIs
- High-velocity IT applies the guiding principles, such as 'progress iteratively with feedback' and 'collaborate and promote visibility', to enable fast and resilient delivery Correct answer.
Explanation
High-velocity IT is consistent with and supported by the ITIL 4 guiding principles. Principles such as progressing iteratively with feedback and collaborating with visibility directly enable fast, resilient delivery. High-velocity IT does not discard or replace the guiding principles.
Question 17Concepts and definitions of high-velocity IT
Which of the following best describes why high-velocity IT emphasizes frequent, small releases over infrequent large releases?
- Small releases reduce the need for customer involvement
- Small releases eliminate the need for any testing
- Small releases reduce risk and enable faster feedback so problems are detected and corrected sooner Correct answer.
- Small releases guarantee that no incidents will occur
Explanation
Frequent small releases lower the risk associated with each change and shorten the feedback loop, so issues are found and fixed faster. They do not remove the need for testing or customer involvement, nor do they guarantee that no incidents occur. The benefit lies in reduced risk and faster learning.
Question 18Concepts and definitions of high-velocity IT
Which statement best captures the meaning of 'value' in the context of high-velocity IT?
- Value is the volume of change records closed each month
- Value is the total cost of the IT department
- Value is the perceived benefit, usefulness and importance of what is delivered, as experienced by stakeholders Correct answer.
- Value is the number of features in the service catalogue
Explanation
In ITIL 4 and high-velocity IT, value is the perceived benefit, usefulness and importance of something as experienced by stakeholders. It is co-created and judged by the consumer, not measured by internal cost or activity volume. Feature counts and closed change records are activity measures, not value itself.
Question 19Concepts and definitions of high-velocity IT
An organization wants to assess whether it is operating in a high-velocity IT manner. Which evidence would most strongly support that conclusion?
- Short lead times from idea to value combined with stable, reliable services Correct answer.
- A large backlog of unapproved change requests
- A high ratio of managers to engineers
- Long lead times from request to delivery combined with frequent outages
Explanation
High-velocity IT is demonstrated by fast delivery of value together with stable, reliable services. Short lead times and reliability are the observable signs of the operating model working. Long lead times, outages, large unapproved backlogs and management-heavy structures indicate the opposite.
Question 20Concepts and definitions of high-velocity IT
Which statement about the scope of high-velocity IT is most accurate?
- It applies only to IT operations teams
- It applies only to software development teams
- It applies across the organization wherever digital products and services are created and delivered Correct answer.
- It applies only to external cloud providers
Explanation
High-velocity IT is not limited to development or operations; it is an operating model for the whole organization involved in creating and delivering digital products and services. It spans teams, practices and value streams. Restricting it to one team type or to cloud providers misrepresents its scope.
Question 21Concepts and definitions of high-velocity IT
Which of the following best explains why high-velocity IT treats culture as part of its operating model rather than an afterthought?
- Behaviors such as collaboration, trust, experimentation and learning directly enable or inhibit fast, resilient delivery Correct answer.
- Culture is only relevant to human resources departments
- Culture determines the color scheme of customer portals
- Culture has no measurable effect on delivery performance
Explanation
High-velocity IT recognizes that delivery speed and resilience depend on behaviors such as collaboration, trust, experimentation and continuous learning. A culture that punishes failure or hoards information slows flow and increases risk. Culture is therefore treated as an integral part of the operating model, not a cosmetic or HR-only concern.
Question 22Concepts and definitions of high-velocity IT
A leadership team asks how high-velocity IT differs from simply 'working faster'. Which response is most accurate?
- It combines speed with quality, resilience and co-created value, so faster delivery does not come at the expense of service reliability Correct answer.
- It is identical; high-velocity IT just means doing the same work at a higher tempo
- It means eliminating governance entirely
- It means reducing the number of services delivered
Explanation
High-velocity IT is not merely working faster; it pairs speed with quality, resilience and co-created value. The aim is to deliver the right things quickly without degrading service reliability. Reducing services or eliminating governance does not capture the concept.
Question 23Concepts and definitions of high-velocity IT
Which statement best describes how high-velocity IT relates to digital transformation?
- High-velocity IT replaces digital strategy with technology procurement
- High-velocity IT is unrelated to digital transformation
- High-velocity IT is the operating model that helps organizations deliver digital transformation outcomes quickly and reliably Correct answer.
- High-velocity IT is only relevant after digital transformation is complete
Explanation
High-velocity IT provides the operating model that enables organizations to realize digital transformation outcomes quickly and reliably. Digital transformation requires both speed and resilience, which is exactly what the model addresses. It does not replace strategy or apply only after transformation is finished.
Question 24Concepts and definitions of high-velocity IT
Which combination of measures would best indicate whether an organization is achieving high-velocity IT outcomes?
- Lead time to value and service availability or reliability Correct answer.
- Total budget spent on hardware
- Number of employees and office locations
- Number of policies and procedures published
Explanation
High-velocity IT outcomes combine speed and stability, so measures of lead time to value alongside availability or reliability are most indicative. Employee counts, policy volumes and hardware spend are inputs or activity measures that do not directly show whether value is delivered fast and reliably. A balanced set of speed and stability measures reflects the dual emphasis of the model.
Question 25Concepts and definitions of high-velocity IT
Which statement best explains why high-velocity IT emphasizes feedback loops across the service value chain?
- Feedback loops provide the information needed to steer delivery, correct course quickly and keep services aligned to customer value Correct answer.
- Feedback loops reduce the need for cross-team collaboration
- Feedback loops increase the number of approvals required
- Feedback loops eliminate the need for governance
Explanation
Feedback loops supply the information that lets teams steer delivery, correct course quickly and keep services aligned with customer value. They support both speed and resilience by enabling early detection and adaptation. They do not increase approvals, eliminate governance or reduce the need for collaboration.
Question 26Concepts and definitions of high-velocity IT
In the ITIL 4 high-velocity IT model, which term describes an organization's ability to absorb disruption and continue delivering services while conditions change rapidly?
- Resilience Correct answer.
- Throughput
- Velocity
- Automation
Explanation
Resilience is the capacity to absorb shocks, recover quickly and keep delivering value when demand, technology or market conditions shift. Velocity and throughput describe speed or volume of work rather than the ability to withstand and rebound from disruption.
Question 27Concepts and definitions of high-velocity IT
Which pair of qualities does high-velocity IT most closely associate with the concept of 'fast'?
- Strict governance combined with long approval cycles
- High speed combined with a clear sense of direction Correct answer.
- Maximum output combined with fixed annual plans
- Low cost combined with minimal staffing
Explanation
In high-velocity IT, fast means both moving quickly and moving in a purposeful direction; speed without direction produces waste. The concept pairs rapid flow with clear objectives so that effort produces value rather than mere activity.
Question 28Concepts and definitions of high-velocity IT
A retailer's online checkout fails during a flash sale, and the team restores service in minutes because the architecture isolates the failing component. Which high-velocity IT concept does this best illustrate?
- Lean
- Resilience Correct answer.
- Co-created value
- Continuous integration
Explanation
Resilience is demonstrated when a system degrades gracefully and service is restored quickly under stress. Isolating components so a single failure does not cascade is a design choice that supports that capacity.
Question 29Concepts and definitions of high-velocity IT
Which statement best describes the role of technology in the high-velocity IT operating model?
- It is a supporting overhead that should be minimized wherever possible
- It guarantees resilience once sufficient tooling is purchased
- It is an enabler that must be combined with culture and ways of working to produce velocity Correct answer.
- It replaces the need for governance and control mechanisms
Explanation
High-velocity IT treats technology as one interdependent element alongside culture and practices; tools alone do not create speed or value. The model stresses that technical capability must be paired with appropriate behaviours and workflows.
Question 30Concepts and definitions of high-velocity IT
Which statement correctly describes the scope of high-velocity IT within ITIL 4?
- It applies only to consumer-facing digital services
- It applies only to organizations above a defined revenue threshold
- It applies to organizations operating in fast-changing digital environments regardless of sector Correct answer.
- It applies only to software companies that release code daily
Explanation
High-velocity IT addresses the challenges of operating in volatile, digitally driven contexts and is not restricted by industry or company size. Any organization facing rapid change and high demand for fast delivery can apply its concepts.
Question 31Concepts and definitions of high-velocity IT
What does the high-velocity IT concept of 'co-created value' emphasize?
- Value emerges from interaction among providers, consumers and other stakeholders rather than being delivered unilaterally Correct answer.
- Value is created only when the contract is signed
- Value is defined solely by the provider's internal quality standards
- Value is measured exclusively by the number of features released
Explanation
Co-created value recognizes that value arises through ongoing interaction and shared contribution between providers and consumers. It rejects the view that a provider can define and deliver value in isolation.
Question 32Concepts and definitions of high-velocity IT
Which statement best explains why high-velocity IT is closely linked to digital transformation?
- Both are concerned primarily with reducing headcount through automation
- Both require replacing all legacy systems before any change can begin
- Both depend on rapidly turning digital capability into new or improved value for customers Correct answer.
- Both are limited to marketing and customer-facing channels
Explanation
Digital transformation and high-velocity IT share a focus on converting digital capability into customer value quickly and continuously. HVIT provides the operating concepts that let organizations sustain that conversion under volatility.
Question 33Concepts and definitions of high-velocity IT
Which behaviour most clearly reflects the high-velocity IT emphasis on trust and collaboration within teams?
- Teams compete internally to be seen as the highest-performing group
- Teams document all work before discussing it with colleagues
- Teams share information openly and raise problems early without fear of blame Correct answer.
- Teams escalate every decision to a central approval board
Explanation
High-velocity IT depends on psychological safety, where people surface issues early so they can be resolved quickly. Open information sharing and blameless problem-raising support the fast feedback that velocity requires.
Question 34Concepts and definitions of high-velocity IT
A team claims to work in a high-velocity way because it deploys frequently. Which additional evidence would most strengthen the claim that it is achieving high-velocity IT outcomes?
- Short lead times from request to value combined with stable, recoverable services Correct answer.
- Adoption of a new tool chain across the whole department
- A larger deployment volume than any other team in the organization
- A reduced number of change requests raised per quarter
Explanation
High-velocity IT outcomes combine fast flow with dependability, so evidence should show both short lead times and services that remain stable and recoverable. Deployment frequency alone can coexist with poor quality and says little about realized value.
Question 35Concepts and definitions of high-velocity IT
Which statement best captures how high-velocity IT views the relationship between speed and quality?
- Speed is the primary goal and quality is addressed in later releases
- Quality can only be assured by slowing delivery and adding review stages
- Speed must always be traded against quality through a formal risk acceptance
- Speed and quality reinforce each other when work is small, feedback is fast and automation supports control Correct answer.
Explanation
High-velocity IT holds that fast flow and high quality are compatible when work is broken small, feedback loops are short and automated controls catch defects early. The model rejects the assumption that speed necessarily degrades quality.
Question 36Concepts and definitions of high-velocity IT
An organization wants to increase its high-velocity IT capability. Which action most directly develops the resilience concept?
- Designing services so that failures are contained and recovery is rehearsed regularly Correct answer.
- Increasing the number of features delivered per sprint
- Reducing the size of the operations team
- Outsourcing all infrastructure management to a single supplier
Explanation
Resilience is built through architectures and practices that contain failure and through rehearsed recovery so the organization can respond under pressure. Feature volume, team size and single-supplier dependence do not directly build that capacity.
Question 37Concepts and definitions of high-velocity IT
Which statement best explains why high-velocity IT treats culture as part of the operating model rather than a separate initiative?
- Culture is owned exclusively by the human resources function
- Behaviours such as collaboration and experimentation determine whether practices and technology actually produce velocity Correct answer.
- Technology alone reliably changes how people work together
- Culture change programmes are cheaper than technology investment
Explanation
In the HVIT model, culture, practices and technology are interdependent, and the same tools yield different results depending on behaviours. Collaboration, experimentation and trust therefore belong inside the operating model, not beside it.
Question 38Concepts and definitions of high-velocity IT
A leadership team asks how high-velocity IT differs from simply instructing staff to work faster. Which response is most accurate?
- It changes how work flows and how value is created, rather than increasing effort within existing processes Correct answer.
- It focuses on individual productivity targets rather than team outcomes
- It replaces process management with informal ad hoc working
- It requires staff to accept longer hours during peak demand periods
Explanation
High-velocity IT is about redesigning flow, feedback and value creation so that speed emerges from the system rather than from individual exertion. Simply demanding more effort within unchanged processes produces burnout, not velocity.
Question 39Concepts and definitions of high-velocity IT
Which statement best describes how the ITIL 4 guiding principles relate to high-velocity IT?
- They remain applicable and guide decisions in fast-changing contexts, for example progress iteratively with feedback Correct answer.
- They are suspended because fast delivery requires bypassing established guidance
- They replace the need for the HVIT concepts entirely
- They apply only to traditional plan-driven service management
Explanation
The guiding principles are universal recommendations that remain relevant in volatile environments; for example, progressing iteratively with feedback directly supports fast learning. High-velocity IT applies them in context rather than setting them aside.
Question 40Concepts and definitions of high-velocity IT
Which statement best explains why high-velocity IT favours frequent small releases over infrequent large ones?
- Smaller releases remove the requirement for stakeholder communication
- Smaller releases make governance and audit impossible
- Smaller releases shorten feedback time and reduce the risk and blast radius of each change Correct answer.
- Smaller releases eliminate the need for testing and quality control
Explanation
Frequent small releases allow the organization to learn quickly and limit the impact of any single failure. This supports both fast value delivery and the resilience that high-velocity IT requires.
Question 41Concepts and definitions of high-velocity IT
A service team wants to move toward high-velocity IT. Which action most directly reflects the lean foundational concept?
- Mapping the value stream and removing steps that add no customer value Correct answer.
- Increasing the number of work items in progress
- Standardizing all work to a single annual release
- Adding more approval gates to increase control
Explanation
Lean thinking in HVIT focuses on value stream optimization by identifying and eliminating waste, such as unnecessary handoffs and waiting. More approvals, more work in progress and rigid annual releases all add delay rather than remove it.
Question 42Concepts and definitions of high-velocity IT
Which combination of measures best indicates that an organization is achieving high-velocity IT outcomes?
- Number of meetings, email volume and office attendance
- Lead time, deployment frequency, service stability and mean time to restore Correct answer.
- Headcount, budget utilization and number of policies
- Total features planned, contract count and supplier spend
Explanation
High-velocity IT outcomes combine flow and dependability, so measures should cover both how quickly value moves and how well services hold up and recover. Lead time and deployment frequency capture flow, while stability and restore time capture resilience.
Question 43Concepts and definitions of high-velocity IT
Which statement best captures the meaning of 'value' in high-velocity IT?
- The total cost of the technology assets owned by the provider
- The perceived benefit realized by stakeholders through timely, useful and dependable services Correct answer.
- The volume of transactions processed by the infrastructure
- The number of features delivered within a release cycle
Explanation
Value in HVIT is judged by the benefit stakeholders actually perceive, which depends on usefulness, timeliness and dependability. Cost of assets, feature counts and transaction volume are inputs or outputs that do not by themselves establish value.
Question 44Concepts and definitions of high-velocity IT
Which statement best explains why high-velocity IT treats automation as a means rather than an end?
- Automation is valuable regardless of whether the automated process is well designed
- Automation succeeds when the largest possible number of tasks is automated
- Automation should be avoided because it removes human oversight
- Automation creates value when it shortens feedback, reduces error and frees people for higher-value judgement Correct answer.
Explanation
In HVIT, automation is justified by the outcomes it enables, such as faster feedback, fewer manual errors and better use of human judgement. Automating a poor process simply produces poor results faster.
Question 45Concepts and definitions of high-velocity IT
A digital bank wants to shorten the time from a customer request to realized value. Which action most directly supports that goal?
- Introducing a quarterly gate review for all customer requests
- Consolidating all teams into one large release train with annual planning
- Increasing the number of specialists each request must pass through
- Reducing batch sizes and handoffs so work flows continuously through the value chain Correct answer.
Explanation
Lead time is shortened by reducing batch sizes and eliminating handoffs that create waiting, allowing continuous flow. Gate reviews, annual planning and additional specialist handoffs all add queue time.
Question 46Concepts and definitions of high-velocity IT
An organization has automated its deployment pipeline but still experiences long outages after releases. Which interpretation is most consistent with high-velocity IT?
- Deployment frequency should be increased until the outages disappear
- Outages are an unavoidable feature of high-velocity IT
- The pipeline should be removed because automation caused the outages
- Automation has improved flow, but resilience requires design and recovery capability that the pipeline alone does not provide Correct answer.
Explanation
High-velocity IT treats speed and resilience as complementary but distinct capabilities; a fast pipeline does not by itself produce services that contain failure and recover quickly. The organization must also invest in resilient design, testing and rehearsed recovery.
Question 47Concepts and definitions of high-velocity IT
A team delivers features rapidly, but customers report that the features solve the wrong problems. Which high-velocity IT concept is most clearly underdeveloped?
- Co-created value through continuous engagement with customers Correct answer.
- Standardization of the technology stack
- Automation of the deployment pipeline
- Throughput of completed work items
Explanation
When output is fast but misaligned with customer needs, the missing element is ongoing engagement that shapes what is built. Co-created value depends on interaction with consumers so that direction is corrected before effort is wasted.
Question 48Concepts and definitions of high-velocity IT
Which statement best explains why high-velocity IT requires both autonomy for teams and alignment with organizational objectives?
- Autonomy removes the need for organizational objectives
- Alignment requires that all decisions be centrally approved
- Autonomy enables fast local decisions, while alignment ensures those decisions contribute to shared outcomes Correct answer.
- Autonomy and alignment cannot coexist in the same organization
Explanation
High-velocity organizations delegate decisions to the people closest to the work so that feedback is acted on quickly, while clear objectives keep those decisions coherent. Without alignment, autonomy fragments effort; without autonomy, alignment becomes slow central control.
Question 49Concepts and definitions of high-velocity IT
An organization measures success only by the number of releases per month. Which critique is most consistent with high-velocity IT?
- Release volume is irrelevant because measurement is unnecessary
- Release volume should be replaced entirely by cost per release
- Release volume is an output measure and should be balanced with measures of value, stability and recovery Correct answer.
- Release volume is the definitive indicator of high-velocity IT maturity
Explanation
High-velocity IT judges performance by outcomes such as realized value, dependability and the ability to recover, not by output volume alone. A balanced set of measures prevents the organization from optimizing activity at the expense of value.
Question 50Concepts and definitions of high-velocity IT
Which statement best explains why high-velocity IT is described as a set of concepts rather than a prescriptive methodology?
- It offers principles and models that organizations adapt to their context instead of a fixed sequence of steps Correct answer.
- It defines a certification path that replaces other frameworks
- It specifies a mandatory tool chain that all adopters must install
- It prescribes a single organizational structure for all adopters
Explanation
High-velocity IT provides concepts and models, such as the HVIT model and its supporting ideas, that organizations apply according to their context. It does not mandate tools, structures or a fixed sequence of implementation steps.