- In ITIL 4, what is the central reason a service is described as relieving the consumer of the need to manage certain costs and risks?
- So the consumer can focus on its desired outcomes while the provider takes on specified costs and risks on the consumer's behalf
- So the provider can transfer legal ownership of its infrastructure to the consumer
- So the consumer becomes solely accountable for every risk that arises during delivery
- So the provider can guarantee that no costs or risks of any kind will ever occur
Correct answer: So the consumer can focus on its desired outcomes while the provider takes on specified costs and risks on the consumer's behalf
The correct answer is that the consumer can focus on its desired outcomes while the provider takes on specified costs and risks on the consumer's behalf. ITIL 4 defines a service around facilitating outcomes the consumer wants without that consumer having to manage certain costs and risks, which is different from transferring ownership, shifting all accountability to the consumer, or promising the elimination of every cost and risk.
- A team is told that warranty for a new service has been assured. Which set of characteristics are they being promised under ITIL 4's concept of warranty?
- That the service performs the specific functions the business needs it to perform
- That the service will meet agreed requirements such as availability, capacity, security, and continuity
- That the service has been priced lower than any competing offering
- That the service description has been approved by the target consumer group
Correct answer: That the service will meet agreed requirements such as availability, capacity, security, and continuity
The correct answer is that the service will meet agreed requirements such as availability, capacity, security, and continuity. ITIL 4 defines warranty as the assurance that a service will meet agreed requirements, often summarized as fitness for use; it is not about the functions the service performs (utility), its price, or approval of its description.
- A reviewer asks whether a proposed expense-claims service is fit for purpose. Under ITIL 4, which question are they actually asking?
- Whether the service is available and reliable enough to be used when needed
- Whether the service has enough capacity to handle peak demand
- Whether the service does what is needed to support a required outcome
- Whether the service meets its agreed security and continuity requirements
Correct answer: Whether the service does what is needed to support a required outcome
The correct answer is whether the service does what is needed to support a required outcome. ITIL 4 equates fit for purpose with utility, the functionality offered to meet a particular need; availability, capacity, security, and continuity all relate to fitness for use, which is warranty rather than utility.
- Within an ITIL 4 service relationship, the consumer carries out activities to make use of a provider's services, including using resources and requesting service actions. What is this set of consumer activities called?
- Service provision
- Service consumption
- Service relationship management
- Service offering
Correct answer: Service consumption
The correct answer is service consumption. ITIL 4 defines service consumption as the activities performed by an organization to consume services, such as using the provider's resources and requesting service actions; service provision is what the provider does, service relationship management is the joint activities to manage the relationship, and a service offering is a description of services.
- An organization that supplies services performs activities such as managing resources, providing access to those resources for users, and fulfilling agreed service actions. In the ITIL 4 service relationship model, what are these activities collectively known as?
- Service consumption
- Service relationship management
- Service provision
- Service value realization
Correct answer: Service provision
The correct answer is service provision. ITIL 4 defines service provision as the activities performed by an organization to provide services, including managing resources, providing access to them, and fulfilling agreed service actions; this is distinct from service consumption performed by the consumer and from service relationship management performed jointly.
- Two organizations not only exchange a service but also jointly handle onboarding, ongoing communication, and continual improvement of how they work together. In ITIL 4, which element of the service relationship model covers these joint, ongoing collaborative activities?
- Service relationship management
- Service provision
- Service consumption
- Service offering
Correct answer: Service relationship management
The correct answer is service relationship management. ITIL 4 defines service relationship management as the joint activities performed by a provider and a consumer to ensure continual value co-creation based on agreed and available service offerings; service provision and service consumption describe the one-sided activities of each party rather than the joint management of the relationship.
- A software vendor publishes a catalog page describing a project-tracking service, including its features, terms, and the consumer group it is aimed at. In ITIL 4, this published description is best classified as what?
- An outcome the consumer wants to achieve
- A service relationship
- A service offering
- A warranty commitment
Correct answer: A service offering
The correct answer is a service offering. ITIL 4 defines a service offering as a formal description of one or more services designed to address the needs of a target consumer group, which can include goods, access to resources, and service actions; an outcome is a result, a service relationship is cooperation between parties, and warranty is an assurance about service performance.
- A bike-rental provider lets a member keep a helmet permanently, grants timed access to a fleet of shared bikes, and dispatches a mechanic to perform an on-demand repair. In ITIL 4 terms, which service offering component is the timed access to the shared bikes?
- A good provided to the consumer
- Access to resources granted under agreed terms and conditions
- A service action performed by the provider
- A configuration item recorded in the CMDB
Correct answer: Access to resources granted under agreed terms and conditions
The correct answer is access to resources granted under agreed terms and conditions. ITIL 4 describes service offering components as goods, access to resources, and service actions; allowing timed use of shared bikes without transferring ownership is access to resources, whereas the kept helmet is a good and the dispatched repair is a service action.
- In ITIL 4, value is described as the perceived benefits, usefulness, and importance of something. Which statement best reflects how ITIL 4 treats this perception of value?
- Value is an objective figure the provider calculates and the consumer must accept
- Value is fixed once a service offering is published and cannot change
- Value is determined solely by how much the service costs to deliver
- Value is subjective and is defined by the stakeholder for whom it is created
Correct answer: Value is subjective and is defined by the stakeholder for whom it is created
The correct answer is that value is subjective and is defined by the stakeholder for whom it is created. ITIL 4 states that value is the perceived benefits, usefulness, and importance of something, and that perception differs by stakeholder; it is not an objective provider calculation, a fixed quantity, or simply the cost of delivery.
- A consumer evaluating a new managed-firewall service lists the benefits it gains, the new subscription fees it must pay, and the dependency it now has on the provider's security team. In ITIL 4, these three considerations correspond to which combination of value-related concepts?
- Outcomes, utility, and warranty
- Goods, access to resources, and service actions
- Outcomes, costs, and risks
- Provision, consumption, and relationship management
Correct answer: Outcomes, costs, and risks
The correct answer is outcomes, costs, and risks. ITIL 4 frames the assessment of value around outcomes the consumer wants, the costs involved, and the risks involved; the benefits gained map to outcomes, the subscription fees map to costs, and the new dependency maps to a risk, so a consumer weighs all three when judging value.
- ITIL 4 notes that a service can remove certain risks from a consumer while at the same time imposing new ones. Which pairing best illustrates a risk removed and a risk imposed for a company moving its email to a cloud provider?
- Removed: the risk of buying its own hardware; Imposed: the cost of the monthly subscription
- Removed: the outcome of reliable email; Imposed: the utility of the service
- Removed: the provider's profit margin; Imposed: the consumer's service offering
- Removed: the risk of running and patching its own mail servers; Imposed: the risk of the provider suffering an outage the company cannot control
Correct answer: Removed: the risk of running and patching its own mail servers; Imposed: the risk of the provider suffering an outage the company cannot control
The correct answer pairs the removed risk of running and patching its own mail servers with the imposed risk of a provider outage the company cannot control. ITIL 4 stresses that services have a two-sided effect on risk; the other options confuse a cost with a risk, mislabel outcomes and utility as risks, or use unrelated terms like profit margin and service offering.
- In an ITIL 4 service relationship, an organization can take on more than one stakeholder role. Which scenario correctly shows a single organization acting as both a service consumer and a service provider?
- A bank that buys a cloud platform from a vendor and uses that platform to offer online banking to its account holders
- A vendor that sells software and also audits the security of that same software
- A user who logs into a service and provides feedback about it
- A sponsor who approves the budget for a service used by a separate department
Correct answer: A bank that buys a cloud platform from a vendor and uses that platform to offer online banking to its account holders
The correct answer is the bank that buys a cloud platform and uses it to offer online banking. ITIL 4 explains that an organization can simultaneously be a service consumer in one relationship and a service provider in another; the bank consumes the vendor's platform and provides banking to its customers, whereas the other options describe a single role or a role within one relationship.
- In ITIL 4, what best describes the nature of a guiding principle?
- A recommendation that guides an organization in all circumstances, regardless of changes in its goals, strategies, or management structure
- A mandatory control that must be implemented in full before any service can be delivered
- A detailed step-by-step procedure that replaces an organization's own processes
- A one-time decision that applies only during the initial design of a new service
Correct answer: A recommendation that guides an organization in all circumstances, regardless of changes in its goals, strategies, or management structure
The correct answer is a recommendation that guides an organization in all circumstances regardless of changes in goals, strategies, or structure. ITIL 4 defines a guiding principle as universal and enduring advice, not a mandatory control, a rigid procedure, or a one-time decision.
- Why does ITIL 4 describe the guiding principles as universally applicable to nearly any initiative and relationship?
- Because they apply only to large enterprises with formal service management offices
- Because they are designed to be followed without judgment in every identical way
- Because they embody the core messages of ITIL and of service management more broadly, so they hold across most situations and types of work
- Because they can be used only when adopting brand-new services
Correct answer: Because they embody the core messages of ITIL and of service management more broadly, so they hold across most situations and types of work
The correct answer is that they embody the core messages of ITIL and of service management broadly, so they hold across most situations. ITIL 4 presents the guiding principles as universally applicable recommendations rather than rules limited to a particular organization size, a single rigid application, or only new-service adoption.
- How does ITIL 4 advise that the guiding principles should be used together when an organization makes a decision?
- Only one principle should ever be chosen, and the rest must be ignored for that decision
- They should be applied in a strict fixed sequence that never changes
- They should be considered collectively, with the organization deciding which are most relevant to the specific situation rather than treating them in isolation
- They should be used only after a decision has already been finalized to justify it
Correct answer: They should be considered collectively, with the organization deciding which are most relevant to the specific situation rather than treating them in isolation
The correct answer is that they should be considered collectively, with the organization deciding which are most relevant to the situation. ITIL 4 stresses that the principles interact and reinforce one another, so an organization weighs them together for context rather than picking only one, following a rigid order, or applying them after the fact.
- A service manager wants to involve front-line agents in shaping a new workflow and also wants the planned changes and their progress to be openly shared on a team dashboard so everyone can see and contribute. Which single ITIL 4 guiding principle most directly supports both of these intentions?
- Optimize and automate
- Collaborate and promote visibility
- Start where you are
- Keep it simple and practical
Correct answer: Collaborate and promote visibility
The correct answer is Collaborate and promote visibility. Involving the right people in shaping the work and openly sharing changes and progress so everyone can contribute are the two halves of this principle, which links broad collaboration with transparency to improve outcomes and trust.
- During a major improvement, leaders want to be sure proposed changes will not create unintended problems elsewhere, so they ask teams to map how the four dimensions and related value streams influence one another before acting. Which ITIL 4 guiding principle is guiding this approach?
- Keep it simple and practical
- Focus on value
- Think and work holistically
- Progress iteratively with feedback
Correct answer: Think and work holistically
The correct answer is Think and work holistically. Mapping how the four dimensions and value streams influence one another to avoid unintended effects reflects this principle's insistence that nothing works in isolation and that services must be understood and managed as an integrated whole.
- An improvement team is tempted to design a complete future-state solution and roll it out all at once. Applying Progress iteratively with feedback, what is the better approach, and why?
- Roll everything out at once because a single release reduces total planning effort
- Divide the work into smaller iterations and seek feedback at each stage, so the initiative can be adjusted and stay relevant as conditions change
- Complete the entire design first and collect feedback only at the very end
- Avoid feedback during the work because it would slow the team down
Correct answer: Divide the work into smaller iterations and seek feedback at each stage, so the initiative can be adjusted and stay relevant as conditions change
The correct answer is to divide the work into smaller iterations and seek feedback at each stage so the initiative can be adjusted and stay relevant. Progress iteratively with feedback breaks large efforts into manageable pieces and uses feedback loops throughout, rather than a single big-bang release or feedback gathered only at the end.
- How does the ITIL 4 guiding principle Progress iteratively with feedback relate to organizing large initiatives?
- It requires every initiative to be delivered as one indivisible release
- It treats each iteration as a self-contained effort that should ignore the overall objective
- It forbids any adjustment to iterations once they have started
- It organizes work into smaller, manageable iterations that each contribute to the larger goal, with feedback used to keep them on track
Correct answer: It organizes work into smaller, manageable iterations that each contribute to the larger goal, with feedback used to keep them on track
The correct answer is that it organizes work into smaller, manageable iterations that each contribute to the larger goal, using feedback to keep them on track. The principle breaks big initiatives into timely sections rather than a single release, keeps each iteration tied to the overall objective, and uses feedback to adjust as needed.
- When applying Focus on value, whose perspective does ITIL 4 say an organization must understand to determine what counts as value?
- Only the perspective of the service provider's finance team
- Only the perspective of external regulators
- The perspective of the service consumers, including how they experience the service and what outcomes matter to them
- Only the perspective of the organization's competitors
Correct answer: The perspective of the service consumers, including how they experience the service and what outcomes matter to them
The correct answer is the perspective of the service consumers, including how they experience the service and what outcomes matter to them. Focus on value requires knowing who is being served and understanding the consumer experience and desired outcomes, rather than defining value solely from finance, regulators, or competitors.
- A new department head proposes throwing out all current monitoring tools and historical data to make a clean start. A teammate cites Start where you are. Which reasoning best reflects that principle?
- Existing tools and data should be assessed first, because current capabilities and measurements often contain value worth reusing rather than discarding
- All existing tools must be kept permanently because change is never beneficial
- The decision should wait until an outside consultant rebuilds everything from zero
- Historical data is always misleading and should be deleted before any assessment
Correct answer: Existing tools and data should be assessed first, because current capabilities and measurements often contain value worth reusing rather than discarding
The correct answer is that existing tools and data should be assessed first because current capabilities often contain reusable value. Start where you are warns against discarding what already exists without evaluation and against assumption, urging an organization to examine the current state so useful elements are retained.
- What does the ITIL 4 guiding principle Optimize and automate intend by the word optimize in this context?
- Buying the most expensive technology available regardless of need
- Making something as effective and useful as it needs to be for its context, after understanding the desired outcome and any constraints
- Removing all human involvement from every process immediately
- Maximizing the number of steps so the process appears thorough
Correct answer: Making something as effective and useful as it needs to be for its context, after understanding the desired outcome and any constraints
The correct answer is making something as effective and useful as it needs to be for its context, after understanding the desired outcome and constraints. In Optimize and automate, optimization means improving effectiveness and usefulness in light of the goal and limitations, not buying costly technology, eliminating all human input at once, or adding unnecessary steps.
- An organization rushes to automate a complaints-handling process that is full of redundant approvals and unclear hand-offs, and the automation simply produces errors faster. Which ITIL 4 guiding principle was applied incorrectly, and what was the mistake?
- Focus on value; the mistake was talking to too many stakeholders
- Keep it simple and practical; the mistake was removing useful controls
- Optimize and automate; the mistake was automating before optimizing the flawed process
- Collaborate and promote visibility; the mistake was sharing too much information
Correct answer: Optimize and automate; the mistake was automating before optimizing the flawed process
The correct answer is Optimize and automate, with the mistake being automating before optimizing the flawed process. The principle sequences optimization before automation precisely because automating a wasteful or broken process only makes its problems happen faster, which is what occurred here.
- How does Keep it simple and practical advise an organization to treat a process that has steps which fail to produce useful value but seem harmless to leave in place?
- Keep every step indefinitely because removing anything is too risky
- Add further steps to compensate for the ones that do not add value
- Hide the non-value-adding steps from users rather than removing them
- Eliminate the steps that produce no useful value, since even harmless-seeming non-value-adding activity adds unnecessary complexity
Correct answer: Eliminate the steps that produce no useful value, since even harmless-seeming non-value-adding activity adds unnecessary complexity
The correct answer is to eliminate the steps that produce no useful value, since non-value-adding activity adds unnecessary complexity. Keep it simple and practical holds that if something does not provide value or contribute to a useful outcome it should be removed, favoring the fewest steps needed to achieve the objective.
- A leadership team feels overwhelmed trying to balance simplicity, value, and stakeholder involvement in a large change and asks how ITIL 4 expects the guiding principles to coexist when they appear to pull in different directions. What is the best response?
- Each principle operates independently, so following one means the others can be safely disregarded
- The principles must always be applied in the order they are listed, with no exceptions
- The principles are complementary and meant to be balanced together, with the organization judging how much each applies to the specific context
- Only the principle with the highest search popularity should ever be chosen
Correct answer: The principles are complementary and meant to be balanced together, with the organization judging how much each applies to the specific context
The correct answer is that the principles are complementary and meant to be balanced together, with the organization judging how much each applies to the context. ITIL 4 intends the guiding principles to interact and reinforce one another, so leaders weigh them collectively rather than treating them as independent, strictly ordered, or mutually exclusive.
- To apply Focus on value effectively over time, what does ITIL 4 expect an organization to do as consumer needs and circumstances evolve?
- Lock the definition of value at launch and never revisit it
- Continually reassess what value means to stakeholders so activities keep contributing to current, relevant outcomes
- Define value only once a year regardless of any changes in demand
- Let the provider redefine value without reference to the consumer
Correct answer: Continually reassess what value means to stakeholders so activities keep contributing to current, relevant outcomes
The correct answer is to continually reassess what value means to stakeholders so activities keep contributing to current, relevant outcomes. Focus on value treats value as something understood from the consumer's evolving perspective, requiring ongoing attention rather than a fixed, infrequent, or provider-only definition.
- Beyond formal reporting lines and job titles, the organizations and people dimension of service management is concerned with the more intangible aspects of how a workforce operates. Which of the following is included within this dimension?
- The organization's culture and the leadership, communication, and ways of working that shape how people deliver services
- The contracts and underpinning agreements that govern third-party service providers
- The applications, infrastructure, and data stores that host and support the service
- The series of steps the organization takes to create and deliver a product to a consumer
Correct answer: The organization's culture and the leadership, communication, and ways of working that shape how people deliver services
The correct answer is the organization's culture and the leadership, communication, and ways of working that shape how people deliver services. The organizations and people dimension covers not only formal structures, roles, and responsibilities but also competencies, leadership, communication, collaboration, and the culture needed for effective service management. Contracts belong to partners and suppliers, applications and data stores belong to information and technology, and the series of steps to deliver a product belongs to value streams and processes.
- While applying the information and technology dimension, an architect notes that some technology in scope supports the management of the service itself while other technology is an actual component of the service delivered to customers. According to ITIL 4, how does this dimension treat technology used in service management?
- It excludes any technology that customers interact with directly, considering only back-office tooling
- It includes technologies that both support service management activities and form part of the services themselves, along with the information they handle
- It considers technology only at the point a service is retired, not during design or operation
- It limits its scope to the security of information and ignores the technologies that process it
Correct answer: It includes technologies that both support service management activities and form part of the services themselves, along with the information they handle
The correct answer is that it includes technologies that both support service management activities and form part of the services themselves, along with the information they handle. The information and technology dimension applies to the information and knowledge needed to manage services and to the technologies used, whether those technologies enable service management work or are integral components of the service delivered. It is not restricted to back-office tools, a single lifecycle stage, or only the security aspect of information.
- In ITIL 4, an organization's strategy when dealing with partners and suppliers is shaped by several influencing factors. Which of the following is one such factor that affects how an organization manages this dimension?
- The exact wording of the seven guiding principles
- The number of activities defined in the service value chain
- The pass mark required for the foundation certification exam
- The organizational culture, scarcity of resources, and cost concerns that drive sourcing decisions
Correct answer: The organizational culture, scarcity of resources, and cost concerns that drive sourcing decisions
The correct answer is the organizational culture, scarcity of resources, and cost concerns that drive sourcing decisions. ITIL 4 lists factors that influence an organization's partner and supplier strategy, including its culture, the scarcity of resources, cost considerations, subject matter expertise, and external constraints. The guiding principles, the count of value chain activities, and the exam pass mark are unrelated to how this dimension is managed.
- A continual-improvement lead wants to remove unnecessary handoffs and rework from the way the organization turns a customer request into a delivered result. ITIL 4 says the value streams and processes dimension is concerned with defining the activities, workflows, and the way work is coordinated. What is the primary aim this dimension supports?
- Ensuring every supplier contract is renegotiated on a fixed annual cycle
- Determining which staff competencies and reporting structures the organization needs
- Defining how the various parts of the organization work in a coordinated way to enable value creation efficiently and effectively
- Selecting the data-storage platforms that will host the organization's records
Correct answer: Defining how the various parts of the organization work in a coordinated way to enable value creation efficiently and effectively
The correct answer is defining how the various parts of the organization work in a coordinated way to enable value creation efficiently and effectively. The value streams and processes dimension is concerned with how the organization arranges its activities, workflows, controls, and procedures so that the parts work together to create value, which is why it is the natural home for streamlining handoffs and removing rework. Supplier contracts sit in partners and suppliers, competencies and structures in organizations and people, and storage platforms in information and technology.
- An instructor asks a class to list the four dimensions of service management that ITIL 4 says must be addressed for every product and service. Which option correctly names all four dimensions?
- Plan, engage, deliver and support, and improve
- Organizations and people; information and technology; partners and suppliers; value streams and processes
- Focus on value; start where you are; collaborate and promote visibility; keep it simple and practical
- Governance; practices; the service value chain; and continual improvement
Correct answer: Organizations and people; information and technology; partners and suppliers; value streams and processes
The correct answer is organizations and people; information and technology; partners and suppliers; value streams and processes. These are the four dimensions ITIL 4 says an organization must consider for every product and service to ensure a holistic approach. Plan, engage, deliver and support, and improve are service value chain activities; focus on value and the others listed are guiding principles; and governance, practices, the service value chain, and continual improvement are components of the service value system, not the four dimensions.
- An architect is mapping how work enters and leaves the ITIL 4 service value system (SVS). She needs to label the two inputs that trigger the system and the single result the system is designed to produce. Which labeling correctly reflects the SVS model?
- The inputs are opportunity and demand, and the output is value
- The inputs are utility and warranty, and the output is a service offering
- The inputs are cost and risk, and the output is an output
- The inputs are governance and practices, and the output is a service value chain
Correct answer: The inputs are opportunity and demand, and the output is value
The inputs are opportunity and demand, and the output is value. ITIL 4 depicts the SVS as taking opportunity and demand as inputs and, through its components working together, producing value as its output. Utility and warranty describe whether a service is fit for purpose and fit for use, so they characterize a service rather than serving as inputs to the SVS. Cost and risk are factors weighed when assessing value, not the triggers that feed the system, and naming the output an output simply restates the question without identifying value. Governance and practices are components inside the SVS, not the inputs that flow into it, and the service value chain is itself one of those internal components rather than the system's output.
- A trainer is helping new staff memorize the components that make up the ITIL 4 service value system (SVS). Which list correctly names the five components of the SVS?
- Plan, engage, design and transition, obtain/build, and deliver and support
- Organizations and people, information and technology, partners and suppliers, value streams and processes, and governance
- Guiding principles, governance, service value chain, practices, and continual improvement
- Focus on value, start where you are, progress iteratively, collaborate, and keep it simple
Correct answer: Guiding principles, governance, service value chain, practices, and continual improvement
The five components of the SVS are the guiding principles, governance, the service value chain, practices, and continual improvement. ITIL 4 defines the SVS as the arrangement of these components and activities that together enable value creation. The list beginning with plan and engage names five of the six activities of the service value chain (the sixth activity, improve, is missing), so it lists only part of one SVS component rather than the SVS components themselves. The list of organizations and people, information and technology, and partners and suppliers names the four dimensions of service management, a separate model that surrounds the SVS rather than constituting it. The final list names individual guiding principles, which collectively form just one of the five SVS components rather than the full set.
- A consultant is explaining why ITIL 4 introduced the service value system as an overarching model rather than describing each process in isolation. What does the SVS structure primarily enable an organization to do?
- Eliminate the need for continual improvement once all components are configured correctly
- Combine its components and activities flexibly so they work together as a system to facilitate value creation
- Operate without any external inputs because the system generates its own demand
- Standardize a fixed, mandatory sequence of steps that every organization must follow without adaptation
Correct answer: Combine its components and activities flexibly so they work together as a system to facilitate value creation
The SVS primarily enables an organization to combine its components and activities flexibly so they work together as a system to facilitate value creation. ITIL 4 frames the SVS as a holistic model whose value lies in how the guiding principles, governance, service value chain, practices, and continual improvement interact across the organization. Eliminating continual improvement contradicts the model, because continual improvement is a permanent component woven throughout the SVS rather than a one-time setup. Claiming the system needs no external inputs is wrong, since opportunity and demand are the inputs that trigger the SVS. Describing a fixed mandatory sequence misrepresents the SVS, which is deliberately designed to be combined and adapted to each organization's context rather than imposed as a rigid set of steps.
- In the ITIL 4 service value chain, which statement best describes the purpose of the improve activity?
- To ensure continual improvement of products, services, and practices across all six value chain activities and the four dimensions of service management
- To ensure that service components are available when and where they are needed and meet agreed specifications
- To provide a good understanding of stakeholder needs and maintain good relationships with all stakeholders
- To ensure that services are operated and supported in line with agreed levels during day-to-day use
Correct answer: To ensure continual improvement of products, services, and practices across all six value chain activities and the four dimensions of service management
The purpose of the improve activity is to ensure continual improvement of products, services, and practices across all six value chain activities and the four dimensions of service management. In the ITIL 4 service value chain, improve is the activity dedicated to driving ongoing enhancement everywhere in the chain rather than to one stage. Ensuring components are available when and where needed and meet agreed specifications describes the obtain/build activity. Providing a good understanding of stakeholder needs and maintaining relationships describes the engage activity. Operating and supporting services to agreed levels in day-to-day use describes the deliver and support activity, which keeps live services running rather than improving them across the whole chain.
- A platform team is acquiring cloud infrastructure and assembling and testing the software components for a new payroll service so that everything required is in place and conforms to the agreed specifications before the service is readied for live use. Which service value chain activity is this work primarily part of?
- The plan activity
- The obtain/build activity
- The engage activity
- The improve activity
Correct answer: The obtain/build activity
This work is primarily part of the obtain/build activity, whose purpose is to ensure that service components are available when and where they are needed and that they meet agreed specifications. Acquiring infrastructure and assembling and testing software components so they conform to specification is exactly the procurement-and-build work obtain/build covers in the ITIL 4 service value chain. The plan activity sets the shared vision, current status, and improvement direction across the four dimensions rather than acquiring components. The engage activity handles understanding stakeholder needs and managing relationships and demand, not building service components. The improve activity drives continual improvement across the chain and is not the activity that procures and assembles new components.
- An exam candidate is told that the service value chain is described as an operating model in which the activities work together as a system. Which statement most accurately explains how the activities are connected to each other?
- Each activity runs independently and shares nothing, so the outputs of one activity are never used by another
- Only the engage activity exchanges anything with the others, while the remaining five activities operate in isolation
- Every value chain activity receives inputs and creates outputs, and these inputs and outputs are passed between activities so they form an interconnected system
- The activities are connected only through the continual improvement register, with no direct exchange of inputs and outputs between them
Correct answer: Every value chain activity receives inputs and creates outputs, and these inputs and outputs are passed between activities so they form an interconnected system
The accurate explanation is that every value chain activity receives inputs and creates outputs, and these inputs and outputs are passed between activities so they form an interconnected system. ITIL 4 presents the service value chain as an operating model whose six activities are linked precisely because the output of one activity becomes an input to others, which is what lets them combine into value streams. Saying each activity shares nothing contradicts the very definition of the value chain as an interconnected set of activities. Claiming only engage exchanges anything is wrong because all six activities take inputs and produce outputs that flow to other activities. Asserting the connection runs only through the continual improvement register confuses a specific improvement tool with the input-and-output relationships that actually link the activities.
- A development group has built and tested a new customer portal and must now make sure it meets stakeholder expectations for quality, cost, and time to market and is moved into the live environment ready for operation. According to the ITIL 4 service value chain, which activity is primarily responsible for this work?
- The improve activity, because it enhances products and services after they are live
- The plan activity, because it establishes the direction for new products and services
- The deliver and support activity, because it runs and supports live services
- The design and transition activity, because it ensures services meet stakeholder expectations for quality, cost, and time to market and are moved into live use
Correct answer: The design and transition activity, because it ensures services meet stakeholder expectations for quality, cost, and time to market and are moved into live use
The design and transition activity is primarily responsible for this work, because its purpose is to ensure that services meet stakeholder expectations for quality, cost, and time to market and that new and changed services are moved into the live environment. Readying a tested portal so it satisfies those expectations and transitioning it into operation is exactly what design and transition does in the ITIL 4 service value chain. The improve activity enhances products, services, and practices and is not the activity that transitions a new service into live use. The plan activity sets organization-wide vision and direction rather than transitioning a specific service. The deliver and support activity operates and supports services once they are already live, which is the stage after transition rather than the transition itself.
- A service manager wants to confirm which single value chain activity is the point where demand and feedback from consumers and other stakeholders enter the chain and are translated into requirements that flow on to the other activities. Which activity fills this role?
- The engage activity, because it provides understanding of stakeholder needs and channels demand, requirements, and feedback into the rest of the value chain
- The deliver and support activity, because it is the activity that interacts with users while services are running
- The plan activity, because it decides the overall direction and therefore receives all stakeholder demand
- The obtain/build activity, because it gathers what is needed before a service can be built
Correct answer: The engage activity, because it provides understanding of stakeholder needs and channels demand, requirements, and feedback into the rest of the value chain
The engage activity fills this role, because it provides a good understanding of stakeholder needs and is the activity that channels demand, requirements, and feedback from consumers and other stakeholders into the rest of the value chain. In the ITIL 4 service value chain, engage is the stakeholder-facing activity through which demand and feedback enter and are translated into requirements for the other activities. The deliver and support activity does interact with users, but its role is operating and supporting live services rather than being the entry point for demand across the chain. The plan activity sets vision and direction and consumes engage outputs, but it is not the activity that captures stakeholder demand. The obtain/build activity acquires and assembles components and does not serve as the point where stakeholder demand enters the chain.
- An IT manager wants the single ITIL 4 practice whose purpose is to keep the organization's information confidential, intact, and available for the business to operate. Which practice should the manager point to?
- Information security management
- Relationship management
- Monitoring and event management
- Supplier management
Correct answer: Information security management
The correct answer is information security management. Its purpose in ITIL 4 is to protect the information the organization needs to conduct its business, which is commonly summarized as preserving confidentiality, integrity, and availability; relationship management nurtures stakeholder links, monitoring and event management observes service state, and supplier management oversees external vendors.
- In ITIL 4, the protection goals of confidentiality, integrity, and availability are central to which practice's key terms?
- Service configuration management
- IT asset management
- Deployment management
- Information security management
Correct answer: Information security management
The correct answer is information security management. ITIL 4 frames this practice's key terms around protecting information, often expressed as confidentiality, integrity, and availability, plus authentication and non-repudiation; service configuration management deals with CI information, IT asset management deals with asset value, and deployment management moves components.
- A bank's IT department most often searches for the ITIL 4 practice that establishes and nurtures links with customers, users, suppliers, and internal teams at strategic and tactical levels. Which practice is being described?
- Supplier management
- Service configuration management
- Relationship management
- Information security management
Correct answer: Relationship management
The correct answer is relationship management. Its purpose in ITIL 4 is to establish and nurture the links between the organization and its stakeholders at strategic and tactical levels; supplier management is narrower and focuses on vendors, service configuration management handles CI information, and information security management protects information.
- In ITIL 4, which outcome is the relationship management practice primarily intended to achieve across the organization's full set of stakeholders?
- Maximizing the financial value tracked for hardware and software components
- Ensuring that every change is risk-assessed and authorized before it proceeds
- Recording and reporting selected changes of state across services
- Identifying, analyzing, monitoring, and continually improving relationships so that stakeholder needs are understood and balanced
Correct answer: Identifying, analyzing, monitoring, and continually improving relationships so that stakeholder needs are understood and balanced
The correct answer is identifying, analyzing, monitoring, and continually improving relationships so stakeholder needs are understood and balanced. ITIL 4 frames relationship management around all stakeholder relationships, not just suppliers; tracking financial value is IT asset management, risk-assessing changes is change enablement, and recording changes of state is monitoring and event management.
- A procurement lead needs the ITIL 4 practice that ensures the organization's vendors and their performance are managed so that seamless, quality products and services can be provided. Which practice fits?
- Relationship management
- Release management
- IT asset management
- Supplier management
Correct answer: Supplier management
The correct answer is supplier management. Its purpose in ITIL 4 is to ensure that the organization's suppliers and their performance are managed appropriately to support the provision of seamless, quality products and services; relationship management is broader across all stakeholders, release management makes features available, and IT asset management tracks asset lifecycles.
- In ITIL 4, how does the purpose of supplier management differ from the purpose of relationship management?
- Supplier management protects information, while relationship management restores service
- Supplier management tracks configuration items, while relationship management tracks financial value
- Supplier management focuses on managing vendors and their performance, while relationship management nurtures links with the full range of stakeholders
- Supplier management and relationship management have the same purpose and are interchangeable
Correct answer: Supplier management focuses on managing vendors and their performance, while relationship management nurtures links with the full range of stakeholders
The correct answer is that supplier management focuses on managing vendors and their performance, while relationship management nurtures links with the full range of stakeholders. ITIL 4 treats these as distinct practices with related but different scope; neither is about protecting information, restoring service, tracking CIs, or tracking financial value, and they are not interchangeable.
- An organization wants to plan and manage the full lifecycle of all its IT assets to maximize value, control costs, and support decisions about reuse and disposal. In ITIL 4, which practice has this purpose?
- Service configuration management
- Monitoring and event management
- IT asset management
- Deployment management
Correct answer: IT asset management
The correct answer is IT asset management. Its purpose in ITIL 4 is to plan and manage the full lifecycle of all IT assets to help the organization maximize value, control costs, manage risks, and support decision-making about reuse, retirement, and disposal; service configuration management handles CI relationships, monitoring observes state, and deployment moves components.
- In ITIL 4, which scenario best illustrates a genuine purpose of the IT asset management practice rather than another practice?
- Tracking software licenses and hardware so renewals, costs, and disposals are planned across each asset's lifecycle
- Documenting how servers, applications, and network links depend on one another to support a service
- Authorizing a normal change after assessing its risk and impact
- Observing services and identifying significant changes of state for response
Correct answer: Tracking software licenses and hardware so renewals, costs, and disposals are planned across each asset's lifecycle
The correct answer is tracking software licenses and hardware so renewals, costs, and disposals are planned across each asset's lifecycle. ITIL 4 IT asset management centers on the financial value and full lifecycle of assets; documenting dependencies is service configuration management, authorizing changes is change enablement, and observing significant changes of state is monitoring and event management.
- A network team uses tools to systematically observe servers, applications, and links, then records and reports selected changes of state for appropriate response. In ITIL 4, which practice has this purpose?
- Information security management
- Monitoring and event management
- Release management
- Supplier management
Correct answer: Monitoring and event management
The correct answer is monitoring and event management. Its purpose in ITIL 4 is to systematically observe services and service components and to record and report selected changes of state identified as events; information security management protects information, release management makes features available, and supplier management oversees vendors.
- In ITIL 4 monitoring and event management, an event is best understood as which of the following key terms?
- An unplanned interruption to a service or a reduction in its quality
- Any change of state that has significance for the management of a configuration item or IT service
- A financially valuable component contributing to delivery of an IT service
- A description of one or more services aimed at a consumer group
Correct answer: Any change of state that has significance for the management of a configuration item or IT service
The correct answer is any change of state that has significance for the management of a configuration item or IT service. ITIL 4 defines an event this way within monitoring and event management; an unplanned interruption is an incident, a financially valuable component is an IT asset, and a description of services is a service offering.
- A delivery team has bundled new features and fixes and wants the ITIL 4 practice whose purpose is to make these new and changed services and features available for use. Which practice applies?
- Deployment management
- Service configuration management
- Information security management
- Release management
Correct answer: Release management
The correct answer is release management. Its purpose in ITIL 4 is to make new and changed services and features available for use; deployment management moves components into environments, service configuration management maintains information about components, and information security management protects information.
- In ITIL 4, what is the key term release defined as within the release management practice?
- A version of a service or other configuration item, or a collection of them, made available for use
- A cause, or potential cause, of one or more incidents
- The cooperation between a service provider and a service consumer
- A pre-authorized, low-risk, routine change
Correct answer: A version of a service or other configuration item, or a collection of them, made available for use
The correct answer is a version of a service or other configuration item, or a collection of them, made available for use. ITIL 4 defines a release as such a version or collection within release management; a cause of incidents is a problem, cooperation between provider and consumer is a service relationship, and a pre-authorized low-risk change is a standard change.
- An engineer must move a new application build from staging into the live production environment. In ITIL 4, which practice has the specific purpose of moving new or changed components to live and other environments?
- Deployment management
- Release management
- Change enablement
- Monitoring and event management
Correct answer: Deployment management
The correct answer is deployment management. Its purpose in ITIL 4 is to move new or changed hardware, software, documentation, processes, or any other component to live or other environments; release management decides when features become available for use, change enablement authorizes changes, and monitoring and event management observes service state.
- In ITIL 4, which statement most accurately distinguishes the purpose of deployment management from release management?
- Deployment management nurtures stakeholder relationships, while release management manages suppliers
- Deployment management protects information, while release management tracks configuration items
- Deployment management moves components into target environments, while release management controls when and how features are made available for use
- Deployment management authorizes risky changes, while release management restores interrupted services
Correct answer: Deployment management moves components into target environments, while release management controls when and how features are made available for use
The correct answer is that deployment management moves components into target environments, while release management controls when and how features are made available for use. ITIL 4 separates the technical movement of components from the decision to make features available; the other options confuse these with relationship management, supplier management, information security management, change enablement, or incident management.
- A service owner needs accurate, reliable information about the configuration of services and the components that support them, available when and where it is needed. In ITIL 4, which practice has this purpose?
- IT asset management
- Service configuration management
- Deployment management
- Relationship management
Correct answer: Service configuration management
The correct answer is service configuration management. Its purpose in ITIL 4 is to ensure that accurate and reliable information about the configuration of services, and the configuration items that support them, is available when and where it is needed; IT asset management tracks financial value, deployment management moves components, and relationship management handles stakeholder links.
- In ITIL 4 service configuration management, the data store used to record configuration items and the relationships between them is known by which key term?
- A configuration management database (CMDB)
- A change schedule
- A service level agreement
- A continual improvement register
Correct answer: A configuration management database (CMDB)
The correct answer is a configuration management database (CMDB). ITIL 4 uses the CMDB as the key term for the store of configuration items and their relationships within service configuration management; a change schedule lists planned changes, a service level agreement documents service targets, and a continual improvement register logs improvement ideas.
- In ITIL 4, how do the key terms configuration item and IT asset differ across the configuration and asset practices?
- A configuration item is always more expensive than an IT asset
- A configuration item is a financially valuable component, while an IT asset is any component that needs to be managed
- A configuration item and an IT asset are identical terms with no difference
- A configuration item is any component that needs to be managed to deliver a service, while an IT asset is a financially valuable component that can contribute to delivery
Correct answer: A configuration item is any component that needs to be managed to deliver a service, while an IT asset is a financially valuable component that can contribute to delivery
The correct answer is that a configuration item is any component that needs to be managed to deliver a service, while an IT asset is a financially valuable component that can contribute to delivery. ITIL 4 defines CIs by the need to manage them and IT assets by financial value, so the two sets overlap but are not the same; cost ranking does not define them, and they are not identical terms.
- In ITIL 4 incident management, what is the difference between categorizing an incident and prioritizing it?
- Categorization records what kind of incident it is so it can be routed and analyzed, while prioritization decides the order and speed of handling based on impact and urgency
- Categorization and prioritization are two words for the same activity
- Categorization sets the resolution deadline, while prioritization records the affected technology
- Categorization is done only for major incidents, while prioritization is done only for minor ones
Correct answer: Categorization records what kind of incident it is so it can be routed and analyzed, while prioritization decides the order and speed of handling based on impact and urgency
The correct answer is that categorization records what kind of incident it is so it can be routed and analyzed, while prioritization decides the order and speed of handling based on impact and urgency. ITIL 4 keeps these as distinct steps in handling an incident; they are not the same activity, the descriptions in the third option are swapped, and both apply regardless of incident size.
- ITIL 4 says that some incidents may be resolved by the user themselves through self-help resources rather than by contacting the service desk. What is the main benefit of enabling this kind of self-resolution in incident management?
- It removes the need to record those incidents anywhere
- It allows simple, common issues to be resolved quickly while freeing support staff to focus on more complex incidents
- It permanently fixes the underlying cause of the incidents
- It transfers accountability for service quality entirely to the user
Correct answer: It allows simple, common issues to be resolved quickly while freeing support staff to focus on more complex incidents
The correct answer is that it allows simple, common issues to be resolved quickly while freeing support staff to focus on more complex incidents. ITIL 4 supports self-help and knowledge resources to speed routine resolution; this does not remove the value of records, fix root causes (that is problem management), or shift accountability for service quality to users.
- An ITIL 4 organization wants its incident management to use information about which devices, services, and relationships are affected when an incident occurs. Which other practice most directly supplies that relationship information to support diagnosis?
- Service level management
- Service configuration management
- Service request management
- Supplier management
Correct answer: Service configuration management
The correct answer is service configuration management. ITIL 4 has incident management draw on configuration data about components and their relationships to speed diagnosis; service level management sets targets, service request management fulfils requests, and supplier management governs supplier relationships.
- In ITIL 4, why does incident management emphasize keeping the user informed about the progress of their incident, not just resolving it?
- Because communication replaces the need to actually restore the service
- Because the user's perception of the service depends on being kept informed, so good communication is part of effective incident handling
- Because users must approve every diagnostic step before it is taken
- Because informing the user automatically reclassifies the incident as a problem
Correct answer: Because the user's perception of the service depends on being kept informed, so good communication is part of effective incident handling
The correct answer is that the user's perception of the service depends on being kept informed, so good communication is part of effective incident handling. ITIL 4 treats timely updates as central to a good user experience during incidents; communication does not replace restoration, require user approval of each step, or change the incident into a problem.
- ITIL 4 recommends that an organization hold a review after a major incident is resolved. What is the primary aim of this major incident review?
- To identify what can be learned and improved so similar major incidents are prevented or handled better in future
- To assign blame to the individual responsible for the outage
- To immediately close any related problems without investigation
- To recalculate the service-level targets in the customer's SLA
Correct answer: To identify what can be learned and improved so similar major incidents are prevented or handled better in future
The correct answer is to identify what can be learned and improved so similar major incidents are prevented or handled better in future. ITIL 4 frames major incident reviews around learning and improvement, feeding into problem management and continual improvement; they are not about blaming individuals, auto-closing problems, or resetting SLA targets.
- In ITIL 4, why is it useful to define and agree the criteria for what counts as a major incident in advance?
- So that the organization never has to log routine incidents
- So that major incidents can be ignored until business hours
- So that everyone immediately recognizes a major incident and can trigger the accelerated, coordinated procedure without debate during the crisis
- So that every incident automatically becomes a major incident
Correct answer: So that everyone immediately recognizes a major incident and can trigger the accelerated, coordinated procedure without debate during the crisis
The correct answer is so that everyone immediately recognizes a major incident and can trigger the accelerated, coordinated procedure without debate during the crisis. ITIL 4 recommends agreeing major incident criteria ahead of time to enable a fast, consistent response; it does not stop routine logging, justify delay, or turn all incidents into major ones.
- In ITIL 4 problem management, what typically triggers the problem identification phase to begin?
- Recognizing recurring or significant incidents, analyzing trends, or receiving information from suppliers that points to an underlying cause
- A user submitting a routine, predefined service request
- A customer signing a new service level agreement
- The successful deployment of a standard change
Correct answer: Recognizing recurring or significant incidents, analyzing trends, or receiving information from suppliers that points to an underlying cause
The correct answer is recognizing recurring or significant incidents, analyzing trends, or receiving information from suppliers that points to an underlying cause. ITIL 4 starts problem identification from such signals; signing an SLA, fulfilling a service request, and deploying a standard change are activities of other practices, not problem identification triggers.
- ITIL 4 distinguishes a problem from a known error by how much is understood about it. Which statement captures this distinction correctly?
- A problem and a known error are identical once logged
- A known error has been analyzed and is understood, often with a documented workaround, whereas a problem may still be under investigation with its cause not yet confirmed
- A known error is always resolved permanently, while a problem never is
- A problem affects only one user, while a known error affects everyone
Correct answer: A known error has been analyzed and is understood, often with a documented workaround, whereas a problem may still be under investigation with its cause not yet confirmed
The correct answer is that a known error has been analyzed and is understood, often with a documented workaround, whereas a problem may still be under investigation with its cause not yet confirmed. ITIL 4 treats a known error as a problem whose nature is understood; the two are not identical, a known error is not necessarily fixed, and the user-count distinction is not how ITIL defines them.
- In ITIL 4, why can problem management often work at a slower, more deliberate pace than incident management?
- Because problems never have any business impact
- Because incident management is not allowed to act until problem management finishes
- Because incident management must restore service urgently, while problem management aims to understand and reduce future incidents, which can be analyzed methodically
- Because problem management only runs once per year during planning
Correct answer: Because incident management must restore service urgently, while problem management aims to understand and reduce future incidents, which can be analyzed methodically
The correct answer is that incident management must restore service urgently, while problem management aims to understand and reduce future incidents, which can be analyzed methodically. ITIL 4 contrasts the urgent restoration focus of incidents with the longer-horizon analysis of problems; problems can have real impact, the practices run in parallel, and problem management is ongoing rather than annual.
- An ITIL 4 problem management team has identified a problem, documented a workaround, and recorded it as a known error, but the permanent fix will be expensive and is deferred. Which phase of the practice now keeps that known error under regular review until a fix is justified?
- Problem identification
- Incident detection
- Problem control
- Error control
Correct answer: Error control
The correct answer is error control. ITIL 4 places the ongoing management and periodic reassessment of known errors and their workarounds in the error control phase; problem identification first detects and logs problems, problem control analyzes them and creates workarounds, and incident detection is part of incident management.
- In ITIL 4, what is the relationship between proactive problem management and the continual improvement practice?
- Proactive problem management can surface opportunities to prevent future incidents that feed into continual improvement initiatives
- Proactive problem management replaces continual improvement entirely
- They are unrelated and never share information
- Continual improvement is only allowed to act after a major incident occurs
Correct answer: Proactive problem management can surface opportunities to prevent future incidents that feed into continual improvement initiatives
The correct answer is that proactive problem management can surface opportunities to prevent future incidents that feed into continual improvement initiatives. ITIL 4 connects the preventive analysis of proactive problem management with the improvement of services and practices; the two are related, neither replaces the other, and continual improvement is ongoing rather than triggered only by major incidents.
- An ITIL 4 team schedules regular reviews of monitoring data and incident trends specifically to spot weaknesses before they cause outages, even when no problem has yet been reported. This deliberate, forward-looking activity is best described as which of the following?
- Reactive incident restoration
- Standard service request fulfilment
- Emergency change authorization
- Proactive problem management
Correct answer: Proactive problem management
The correct answer is proactive problem management. ITIL 4 describes proactive problem management as the scheduled analysis of data and trends to find and address potential causes before they create significant incidents; restoring incidents reactively, authorizing emergency changes, and fulfilling service requests are different activities.
- In ITIL 4, the continual improvement model is described as starting from a clear vision and assessing the current state before defining targets. Which guiding principle is most directly reflected by the model's emphasis on assessing where you are now using accurate measurement?
- Start where you are
- Keep it simple and practical
- Optimize and automate
- Collaborate and promote visibility
Correct answer: Start where you are
The correct answer is start where you are. ITIL 4 links the continual improvement model's current-state assessment to the guiding principle of starting where you are, which says to honestly examine and measure the existing situation before improving; the other principles influence improvement too but do not specifically match assessing the current baseline.
- In ITIL 4, which step of the continual improvement model is concerned with planning the specific actions, roadmap, and approach to reach the agreed target state?
- Where are we now?
- Did we get there?
- How do we get there?
- What is the vision?
Correct answer: How do we get there?
The correct answer is 'How do we get there?'. ITIL 4 uses this step to plan the route, actions, and approach for reaching the defined target state, before the team takes action and later checks whether the target was met; assessing the baseline, confirming results, and setting overall direction are separate steps.
- ITIL 4 stresses that continual improvement should be embedded in everything the organization does rather than treated as a separate, occasional activity. What is the main risk of treating improvement as a standalone, occasional project instead?
- Improvement would happen too frequently to manage
- It would force every employee to become a problem manager
- It would make measurement unnecessary
- Improvements would not become part of day-to-day work, so gains may stall and the organization may fall behind changing business needs
Correct answer: Improvements would not become part of day-to-day work, so gains may stall and the organization may fall behind changing business needs
The correct answer is that improvements would not become part of day-to-day work, so gains may stall and the organization may fall behind changing business needs. ITIL 4 wants continual improvement woven into normal activity; treating it as occasional does not make improvement too frequent, remove the need to measure, or turn everyone into a problem manager.
- In ITIL 4, how should improvement ideas captured in the continual improvement register typically be documented so they can be assessed and prioritized effectively?
- As vague headlines with no further detail
- Only after they have already been fully implemented
- With enough information to understand and evaluate them, such as the opportunity, expected benefit, and priority
- As anonymous entries that no one is responsible for
Correct answer: With enough information to understand and evaluate them, such as the opportunity, expected benefit, and priority
The correct answer is with enough information to understand and evaluate them, such as the opportunity, expected benefit, and priority. ITIL 4 recommends capturing improvement ideas in the register with enough detail to assess and prioritize them; vague headlines, after-the-fact-only logging, and ownerless entries would undermine the register's purpose.
- ITIL 4 notes that an organization may maintain more than one continual improvement register, for example at different levels or in different teams. What does this flexibility indicate about how the register is meant to be used?
- That registers must always be a single global document with no exceptions
- That the register is purely a financial accounting record
- That only the most senior team is permitted to keep a register
- That capturing and managing improvement ideas can be scaled to suit the organization, while still ensuring ideas are tracked and prioritized
Correct answer: That capturing and managing improvement ideas can be scaled to suit the organization, while still ensuring ideas are tracked and prioritized
The correct answer is that capturing and managing improvement ideas can be scaled to suit the organization, while still ensuring ideas are tracked and prioritized. ITIL 4 allows one or several continual improvement registers as appropriate; it is not required to be a single global document, is not a financial ledger, and is not restricted to senior teams only.
- In ITIL 4, what is the overall benefit the continual improvement practice aims to deliver to an organization over time?
- Eliminating the need for any other ITIL practices
- Keeping services, practices, and ways of working aligned to evolving business needs so value continues to be delivered
- Guaranteeing that no change will ever be required again
- Ensuring all incidents are resolved before they are reported
Correct answer: Keeping services, practices, and ways of working aligned to evolving business needs so value continues to be delivered
The correct answer is keeping services, practices, and ways of working aligned to evolving business needs so value continues to be delivered. ITIL 4 positions continual improvement as the ongoing pursuit of better alignment and performance; it does not replace other practices, freeze the need for change, or resolve incidents before they occur.
- In ITIL 4 change enablement, what is the purpose of planning remediation for a change before it is implemented?
- To convert the change into a service request
- To guarantee that the change can never fail
- To replace the need to assess the change's risk
- To decide in advance how to recover or back out if the change does not go as expected
Correct answer: To decide in advance how to recover or back out if the change does not go as expected
The correct answer is to decide in advance how to recover or back out if the change does not go as expected. ITIL 4 includes remediation or back-out planning so a failed change can be reversed or recovered; it does not guarantee success, remove the need for risk assessment, or turn the change into a service request.
- An ITIL 4 organization wants standard changes to flow quickly. What must be true about a change for it to be correctly classified and handled as a standard change?
- It must be high risk and require senior board approval each time
- It must be an urgent fix applied during an active outage
- It must be low risk, well understood, and pre-authorized through a documented, repeatable procedure
- It must involve a service the organization has never changed before
Correct answer: It must be low risk, well understood, and pre-authorized through a documented, repeatable procedure
The correct answer is that it must be low risk, well understood, and pre-authorized through a documented, repeatable procedure. ITIL 4 reserves the standard change type for routine, low-risk changes authorized in advance; high-risk board-approved changes are normal changes, urgent fixes are emergency changes, and a never-before-attempted change would not yet be standard.
- ITIL 4 says that after a change has been implemented, it is good practice to review the outcome. What is the main purpose of reviewing a completed change?
- To confirm whether the change achieved its objectives and to capture lessons for future changes
- To decide whether the change should have been a service request
- To recategorize the change as an incident
- To remove the change from the configuration records
Correct answer: To confirm whether the change achieved its objectives and to capture lessons for future changes
The correct answer is to confirm whether the change achieved its objectives and to capture lessons for future changes. ITIL 4 reviews completed changes to verify results and feed learning into improvement; the review does not reclassify the change as a service request or incident, nor does it delete configuration records.
- In ITIL 4, why is it important that change enablement assess the potential impact of a change on other services, components, and changes already scheduled?
- Because impact assessment is only needed for emergency changes
- Because understanding wider impact and possible conflicts helps avoid unintended disruption and supports safe scheduling
- Because changes never affect anything beyond the single component being changed
- Because assessing impact removes the need to authorize the change
Correct answer: Because understanding wider impact and possible conflicts helps avoid unintended disruption and supports safe scheduling
The correct answer is because understanding wider impact and possible conflicts helps avoid unintended disruption and supports safe scheduling. ITIL 4 has change enablement evaluate ripple effects and scheduling conflicts before proceeding; impact assessment is not limited to emergencies, changes can affect many things, and assessment supports rather than replaces authorization.
- In ITIL 4, what does it mean to say a change authority is accountable for a particular change?
- The change authority physically performs the technical work of the change
- The change authority is always the customer who requested the change
- The change authority records all configuration items affected by the change
- The change authority is the person or group whose approval is required before that change proceeds
Correct answer: The change authority is the person or group whose approval is required before that change proceeds
The correct answer is that the change authority is the person or group whose approval is required before that change proceeds. ITIL 4 defines the change authority by responsibility for authorization, not for doing the technical work, recording configuration items, or being the requesting customer.
- An ITIL 4 organization automates approval for a category of low-risk changes so they can proceed without waiting for a person. In change enablement terms, what does this automated approval represent about the change authority?
- That the change authority has been removed and the changes are now unauthorized
- That every automated change must still be approved again by a board
- That automation can serve as a change authority for suitable low-risk changes, granting authorization quickly within agreed rules
- That the change authority must always be a single senior manager
Correct answer: That automation can serve as a change authority for suitable low-risk changes, granting authorization quickly within agreed rules
The correct answer is that automation can serve as a change authority for suitable low-risk changes, granting authorization quickly within agreed rules. ITIL 4 allows the change authority for low-risk changes to be decentralized or automated; this keeps changes authorized rather than uncontrolled, does not require a second board approval, and does not force a single senior approver.
- In ITIL 4 service request management, what is the value of publishing clear expected fulfilment times for different types of service request?
- It allows the organization to skip fulfilling slower requests
- It sets realistic user expectations and lets fulfilment be measured and managed consistently
- It converts each request into an incident if it is late
- It removes any need for approvals on requests
Correct answer: It sets realistic user expectations and lets fulfilment be measured and managed consistently
The correct answer is that it sets realistic user expectations and lets fulfilment be measured and managed consistently. ITIL 4 recommends defining and communicating expected fulfilment times so users know what to expect and performance can be tracked; this does not let the provider skip requests, turn late requests into incidents, or remove necessary approvals.
- ITIL 4 service request management often depends on contributions from many teams to fulfil a request end to end, such as procurement, HR, and IT for onboarding a new employee. What does this illustrate about the practice?
- That fulfilling requests can involve coordinating predefined workflows across several teams while remaining a routine part of service delivery
- That service request fulfilment is always handled by the service desk alone
- That multi-team requests must be reclassified as problems
- That such requests should always be treated as emergency changes
Correct answer: That fulfilling requests can involve coordinating predefined workflows across several teams while remaining a routine part of service delivery
The correct answer is that fulfilling requests can involve coordinating predefined workflows across several teams while remaining a routine part of service delivery. ITIL 4 recognizes that service requests may span multiple teams through defined workflows; they are not handled by the service desk alone, are not problems, and are not emergency changes.
- In ITIL 4, why does service request management treat its requests as a normal, expected part of service delivery rather than as something going wrong?
- Because service requests are unpredictable failures of the service
- Because they are predefined, agreed offerings the user is entitled to, so fulfilling them is part of delivering the service as designed
- Because every service request signals that an incident has occurred
- Because service requests are always urgent and high risk
Correct answer: Because they are predefined, agreed offerings the user is entitled to, so fulfilling them is part of delivering the service as designed
The correct answer is that they are predefined, agreed offerings the user is entitled to, so fulfilling them is part of delivering the service as designed. ITIL 4 frames service requests as routine and expected; they are not failures, not signals of incidents, and not inherently urgent or high risk.
- In ITIL 4, what is the key reason it matters whether a user contact is handled as an incident or as a service request?
- Because the two are charged at different prices to the user
- Because incidents are handled by suppliers and service requests by customers
- Because only service requests are ever logged
- Because each follows a different handling approach: incidents need diagnosis and restoration, while service requests follow predefined fulfilment steps
Correct answer: Because each follows a different handling approach: incidents need diagnosis and restoration, while service requests follow predefined fulfilment steps
The correct answer is that each follows a different handling approach: incidents need diagnosis and restoration, while service requests follow predefined fulfilment steps. ITIL 4 separates them so each gets the right treatment; the distinction is not about pricing, both are logged, and neither is defined by who handles it in that way.
- A user reports that the printing service, which normally works, has suddenly stopped responding for the whole floor. A colleague separately asks to be added to an existing distribution list, a standard offering. In ITIL 4, which classification correctly applies to each?
- The printing outage is an incident; the distribution-list request is a service request
- Both are incidents because both involve the service
- Both are service requests because both were reported to support
- The printing outage is a service request; the distribution-list request is an incident
Correct answer: The printing outage is an incident; the distribution-list request is a service request
The correct answer is that the printing outage is an incident and the distribution-list request is a service request. ITIL 4 classifies the unplanned loss of a working service as an incident and a predefined, agreed addition as a service request; they are not both the same type, and the reversed mapping is incorrect.
- In ITIL 4, the service desk is sometimes contrasted with technical or specialist support teams. What distinguishes the service desk's role from those specialist teams?
- The service desk is the broad point of contact that captures and coordinates user demand, while specialist teams provide deeper expertise on specific technologies
- The service desk provides deep, narrow technical expertise in one technology, while specialist teams are the point of contact
- The service desk and specialist teams have identical roles and are interchangeable
- The service desk exists only to authorize changes, while specialist teams handle users
Correct answer: The service desk is the broad point of contact that captures and coordinates user demand, while specialist teams provide deeper expertise on specific technologies
The correct answer is that the service desk is the broad point of contact that captures and coordinates user demand, while specialist teams provide deeper expertise on specific technologies. ITIL 4 distinguishes the desk's coordinating, user-facing role from specialist depth; the first option reverses them, the roles are not identical, and the desk's purpose is not to authorize changes.
- An ITIL 4 service desk gathers feedback on user satisfaction and feeds recurring themes back to other practices and to improvement efforts. What broader role of the service desk does this illustrate?
- That the service desk should keep all feedback to itself
- That collecting feedback turns the service desk into the change authority
- That the service desk owns and resolves every issue it hears about
- That the service desk, as a key user touchpoint, can capture insight that helps improve services across the organization
Correct answer: That the service desk, as a key user touchpoint, can capture insight that helps improve services across the organization
The correct answer is that the service desk, as a key user touchpoint, can capture insight that helps improve services across the organization. ITIL 4 sees the desk as a valuable source of user feedback feeding continual improvement and other practices; it should share rather than withhold insight, does not resolve everything alone, and does not become the change authority by collecting feedback.
- In ITIL 4, what does service level management rely on in order to judge whether a service is meeting the customer's expectations?
- A single uptime figure reported once a year
- The number of standard changes implemented each month
- Agreed targets together with ongoing measurement, reporting, and review of performance and customer satisfaction
- The size of the configuration management database
Correct answer: Agreed targets together with ongoing measurement, reporting, and review of performance and customer satisfaction
The correct answer is agreed targets together with ongoing measurement, reporting, and review of performance and customer satisfaction. ITIL 4 has service level management compare delivery against agreed targets using continual measurement and review; a once-yearly single figure, change counts, and CMDB size do not capture whether expectations are met.
- ITIL 4 recommends regular service review meetings between the provider and customer as part of service level management. What is the main purpose of these reviews?
- To authorize emergency changes to the service
- To discuss performance against targets, address issues, and ensure the service continues to meet evolving business needs
- To record the technical relationships between configuration items
- To reset all open incidents to a resolved state
Correct answer: To discuss performance against targets, address issues, and ensure the service continues to meet evolving business needs
The correct answer is to discuss performance against targets, address issues, and ensure the service continues to meet evolving business needs. ITIL 4 uses service reviews to keep the provider and customer aligned over time; authorizing emergency changes, recording configuration relationships, and closing incidents belong to other practices.
- In ITIL 4, why does service level management require listening to and engaging with the customer rather than the provider simply choosing targets it can easily meet?
- Because engaging the customer removes the need for any agreed targets
- Because the customer must perform all the measurements themselves
- Because targets the customer does not value can be met while the service still fails to support the business
- Because only easily met targets are ever permitted in an SLA
Correct answer: Because targets the customer does not value can be met while the service still fails to support the business
The correct answer is that targets the customer does not value can be met while the service still fails to support the business. ITIL 4 stresses customer engagement so SLAs reflect real needs and avoid the watermelon effect; the customer does not run all measurement, engagement does not remove agreed targets, and SLAs should reflect value rather than convenience.
- In ITIL 4, what is the precise difference between the customer role and the user role within a service consumer organization?
- The customer defines requirements and takes responsibility for the outcomes of service consumption, while the user actually uses the service
- The customer always pays the invoices, while the user negotiates the contract terms
- The customer supplies the service, while the user manages the resources behind it
- The customer and the user are interchangeable labels for the same activity
Correct answer: The customer defines requirements and takes responsibility for the outcomes of service consumption, while the user actually uses the service
The correct answer is that the customer defines requirements and takes responsibility for the outcomes, while the user actually uses the service. ITIL 4 distinguishes these consumer roles: the customer is concerned with the outcomes and requirements, the user works with the service hands-on, and a separate sponsor role authorizes the budget; paying invoices is the sponsor's concern and supplying the service is the provider's.
- In ITIL 4, which statement correctly describes the sponsor role in a service consumer organization?
- The person or group that authorizes the budget for service consumption
- The person who logs in and operates the service day to day
- The organization that designs and delivers the service
- The independent body that certifies the service against a standard
Correct answer: The person or group that authorizes the budget for service consumption
The correct answer is the person or group that authorizes the budget for service consumption. ITIL 4 defines the sponsor as the role that approves the funding for a service; operating the service day to day is the user role, designing and delivering it is the provider, and certification is not one of ITIL's defined stakeholder roles.
- In ITIL 4, how is service management defined?
- A set of specialized organizational capabilities for enabling value for customers in the form of services
- A single software tool used to record incidents and changes
- The legal contract that fixes the price of a service for its lifetime
- The act of a consumer using a provider's resources to obtain an outcome
Correct answer: A set of specialized organizational capabilities for enabling value for customers in the form of services
The correct answer is a set of specialized organizational capabilities for enabling value for customers in the form of services. ITIL 4 defines service management this way, emphasizing that these capabilities are developed over time through experience; it is not a single tool, a pricing contract, or the consumer-side activity of service consumption.
- In ITIL 4, what is the key distinction between an output and an outcome?
- An output is a tangible or intangible deliverable of an activity, while an outcome is a result for a stakeholder enabled by one or more outputs
- An output is the consumer's perceived benefit, while an outcome is the raw deliverable produced
- An output is always financial, while an outcome is always non-financial
- An output and an outcome describe the same thing from the provider's viewpoint
Correct answer: An output is a tangible or intangible deliverable of an activity, while an outcome is a result for a stakeholder enabled by one or more outputs
The correct answer is that an output is a deliverable of an activity, while an outcome is a result for a stakeholder enabled by one or more outputs. ITIL 4 stresses that producing outputs is not enough; a monthly report (output) only matters if it enables a result such as better decisions (outcome), and confusing the two leads providers to focus on deliverables rather than results.
- An ITIL 4 study explains that a provider should help consumers achieve outcomes rather than simply hand over outputs. Which scenario best shows a provider focused on the outcome instead of just the output?
- A reporting provider not only delivers the dashboard but helps the client interpret it so they make faster purchasing decisions
- A reporting provider emails a completed dashboard file and closes the ticket
- A reporting provider counts how many dashboards it produced this month
- A reporting provider lowers the price of producing each dashboard
Correct answer: A reporting provider not only delivers the dashboard but helps the client interpret it so they make faster purchasing decisions
The correct answer is the provider that helps the client interpret the dashboard so they make faster decisions. ITIL 4 frames value around outcomes, the results stakeholders want, rather than outputs, the deliverables; emailing a file, counting deliverables, or cutting unit cost all stay at the output or efficiency level rather than enabling the consumer's actual result.
- In ITIL 4, an organization is defined in terms of stakeholder roles within service relationships. Which statement best reflects how ITIL 4 treats the term organization?
- A person or a group of people that has its own functions with responsibilities, authorities, and relationships to achieve its objectives
- Only a legally incorporated company that buys or sells services for profit
- The technical infrastructure and applications a provider uses to deliver services
- A single individual who is accountable for every service in the relationship
Correct answer: A person or a group of people that has its own functions with responsibilities, authorities, and relationships to achieve its objectives
The correct answer is a person or a group of people that has its own functions with responsibilities, authorities, and relationships to achieve its objectives. ITIL 4 defines an organization broadly so it can be a whole company, a department, or even one person; it is not limited to incorporated for-profit entities, nor is it the infrastructure or a single accountable individual.
- In an ITIL 4 service relationship, one organization sets the service requirements and another organization actually operates the service through its frontline employees. Mapping these to ITIL 4 roles, which roles are the requirement-setting party and the frontline employees fulfilling?
- The requirement-setting party is acting as the customer, and the frontline employees are acting as users
- The requirement-setting party is acting as the user, and the frontline employees are acting as sponsors
- The requirement-setting party is acting as the provider, and the frontline employees are acting as customers
- Both the requirement-setting party and the frontline employees are acting as sponsors
Correct answer: The requirement-setting party is acting as the customer, and the frontline employees are acting as users
The correct answer is that the requirement-setting party is acting as the customer and the frontline employees are acting as users. ITIL 4 assigns the customer role to whoever defines requirements and owns the outcomes, and the user role to whoever uses the service in practice; sponsors authorize budget and providers supply the service, so neither label fits these two parties here.
- ITIL 4 recommends a sequence of steps for applying Optimize and automate, beginning with understanding and agreeing on the context in which a proposed optimization exists. What should this context include?
- The overall vision and objectives of the organization
- Only the budget approved for the current financial year
- A complete list of every tool the supplier sells
- The personal preferences of the most senior manager
Correct answer: The overall vision and objectives of the organization
The context should include the overall vision and objectives of the organization. ITIL 4 advises that before optimizing, an organization first understands and agrees on the context, which means understanding the organization's vision and objectives so that any optimization actually moves it toward those goals rather than improving something in isolation.
- When applying Optimize and automate, ITIL 4 advises that organizations should not try to automate tasks that are not reasonably well understood. What is the main reason for this caution?
- Automation tools are only sold to organizations with formal documentation
- Automating a poorly understood task risks locking in undesirable behaviour and producing unreliable outcomes
- Poorly understood tasks are always the least important to the customer
- Automation can never be applied to human-centred tasks of any kind
Correct answer: Automating a poorly understood task risks locking in undesirable behaviour and producing unreliable outcomes
Automating a poorly understood task risks locking in undesirable behaviour and producing unreliable outcomes. ITIL 4 warns that automation should be applied where it adds genuine value, and trying to automate something that is not well understood simply makes flawed or unpredictable behaviour run faster and harder to correct.
- A team applying Optimize and automate has improved a workflow as far as practical and now wants to use technology to handle its repetitive steps. According to ITIL 4, what is the chief benefit of using automation for such frequent and repetitive tasks?
- It removes the need to ever measure or review the workflow again
- It guarantees that no stakeholder will ever need to be consulted
- It frees human resources for more complex decision making and increases scalability and consistency
- It eliminates the requirement to understand the workflow at all
Correct answer: It frees human resources for more complex decision making and increases scalability and consistency
Automation frees human resources for more complex decision making and increases scalability and consistency. ITIL 4 positions automation of routine, frequent, and repetitive work as a way to reduce manual effort and human error, letting people focus on tasks that need judgement while the automated work scales reliably.
- ITIL 4 stresses that the guiding principles are intended to support continual improvement at all levels of an organization. How does ITIL 4 say the principles relate to an organization's improvement efforts?
- They apply only to the first improvement an organization ever attempts
- They replace the need to define any improvement objectives
- They are used only when an external auditor requires them
- They guide actions and decisions during improvement in any circumstances, regardless of changes in goals or strategy
Correct answer: They guide actions and decisions during improvement in any circumstances, regardless of changes in goals or strategy
The principles guide actions and decisions during improvement in any circumstances, regardless of changes in goals or strategy. ITIL 4 describes the guiding principles as recommendations that remain relevant across all types of initiatives and through changes to objectives, making them a constant reference for decision making during continual improvement.
- Applying Progress iteratively with feedback, a team divides a large initiative into smaller sections that are executed and completed in a timely manner. What does ITIL 4 say is a key advantage of working this way?
- Maintaining focus is easier and the team can respond to feedback before continuing
- It removes the need to ever seek any feedback
- It guarantees the initiative will require no resources
- It ensures the whole initiative can be delivered in a single release
Correct answer: Maintaining focus is easier and the team can respond to feedback before continuing
Maintaining focus is easier and the team can respond to feedback before continuing. ITIL 4 explains that organizing work into smaller, manageable iterations keeps effort focused, allows quicker delivery of useful outcomes, and creates points where feedback can be gathered and acted on before the next iteration.
- ITIL 4 says that seeking and using feedback before, throughout, and after each iteration provides several benefits. Which of the following is a benefit ITIL 4 attributes to using feedback in this way?
- It removes all need to involve stakeholders in any decision
- It improves the ability to identify risks and respond to failures quickly
- It guarantees that no changes will ever be required again
- It makes measurement and metrics unnecessary
Correct answer: It improves the ability to identify risks and respond to failures quickly
Using feedback improves the ability to identify risks and respond to failures quickly. ITIL 4 lists benefits of well-placed feedback such as better understanding of stakeholder needs, earlier discovery of failure and inefficiency, and improved ability to detect and manage risk across the iterations of work.
- A team applying Think and work holistically is assessing a proposed change to a single service. According to ITIL 4, what should the team take into account to apply this principle correctly?
- Only the technology component, since other dimensions rarely matter
- Only the cost, ignoring people, processes, and partners
- How the four dimensions and the service value system elements work together to deliver value
- Only the opinion of the single most senior stakeholder
Correct answer: How the four dimensions and the service value system elements work together to deliver value
The team should consider how the four dimensions and the service value system elements work together to deliver value. Think and work holistically reminds an organization that services and their components are interconnected, so a change must be assessed for its effect across people, processes, partners, and information and technology rather than in isolation.
- A service architect is told that the four dimensions of service management do not exist in isolation but are constantly shaped by outside conditions such as new laws, economic shifts, competitor behavior, and emerging technologies. In ITIL 4, what is the collective name for this set of external factors that influence how an organization addresses all four dimensions?
- The PESTLE factors (political, economic, social, technological, legal, and environmental)
- The four foundational pillars of service value
- The guiding principles of continual improvement
- The components of the service value chain
Correct answer: The PESTLE factors (political, economic, social, technological, legal, and environmental)
The correct answer is the PESTLE factors (political, economic, social, technological, legal, and environmental). ITIL 4 states that the four dimensions are constrained and influenced by these external PESTLE factors, which an organization cannot control but must account for when shaping each dimension. The guiding principles, service value chain, and 'four pillars' are separate ITIL concepts and do not describe these external influences.
- An organization is deciding how to source the components needed to deliver a new service and is weighing options that range from doing all the work with its own resources to handing the whole activity to an external provider. In ITIL 4, the partners and suppliers dimension describes this range as a service integration spectrum. Which pair of arrangements correctly represents the two extremes of that spectrum?
- Insourcing at one end and outsourcing at the other
- Centralization at one end and decentralization at the other
- Standardization at one end and customization at the other
- Automation at one end and manual operation at the other
Correct answer: Insourcing at one end and outsourcing at the other
The correct answer is insourcing at one end and outsourcing at the other. ITIL 4 describes the partners and suppliers dimension as spanning a service integration spectrum, with insourcing (using internal resources for all design, development, and operation) at one extreme and outsourcing (using an external supplier for a discrete activity) at the other, with service integration and management options in between. Centralization, standardization, and automation describe other operational choices, not the sourcing spectrum of this dimension.
- During a service review, leaders find that staff understand their tasks but feel uncomfortable raising problems, and managers rarely act on improvement suggestions. ITIL 4 stresses that the organizations and people dimension must address shared values and attitudes, not just structures and skills. Why does ITIL 4 emphasize organizational culture and leadership within this dimension?
- Because an organization's effectiveness depends on its culture and leadership style supporting the way people are expected to work
- Because culture determines which hardware and software platforms the service will run on
- Because leadership style sets the contractual terms used with external suppliers
- Because organizational culture defines the documented activities that turn inputs into outputs
Correct answer: Because an organization's effectiveness depends on its culture and leadership style supporting the way people are expected to work
The correct answer is that an organization's effectiveness depends on its culture and leadership style supporting the way people are expected to work. ITIL 4 places organizational culture and leadership within the organizations and people dimension because adequate roles, structures, and skills only deliver value when the culture and management style reinforce the desired behaviors and collaboration. The other options describe concerns of the information and technology dimension, the partners and suppliers dimension, and the value streams and processes dimension respectively, not the reason culture matters here.
- A board member asks how the ITIL 4 service value system keeps the organization's service management activities aligned with overall direction, policies, and acceptable levels of risk. Which component of the SVS is responsible for the means by which an organization is directed and controlled?
- Governance
- The service value chain
- Continual improvement
- The guiding principles
Correct answer: Governance
Governance is the SVS component responsible for the means by which an organization is directed and controlled. In ITIL 4, governance covers evaluating, directing, and monitoring the organization so that its service management activities stay aligned with strategy, policies, and acceptable risk. The service value chain is the operating model of interconnected activities that creates, delivers, and continually improves services, not the directing-and-controlling component. Continual improvement is the recurring component focused on aligning practices and services with changing needs, rather than setting overall direction and control. The guiding principles are recommendations that steer decisions and behavior, but they advise rather than direct and control the organization, which is the defining role of governance.
- An organization is reviewing how its service value chain activities relate to governance. Which statement best describes the relationship between governance and the inputs that drive the plan activity?
- The plan activity operates independently of governance and receives no inputs from it
- The plan activity is influenced by policies, requirements, and constraints provided by governance, which the plan activity translates into shared direction for the other activities
- Governance is one of the six service value chain activities and is performed only after the plan activity finishes
- The plan activity receives its only inputs from the obtain/build activity and passes them to governance
Correct answer: The plan activity is influenced by policies, requirements, and constraints provided by governance, which the plan activity translates into shared direction for the other activities
The correct statement is that the plan activity is influenced by policies, requirements, and constraints from governance, which it translates into shared direction for the other value chain activities. Governance is part of the service value system but is not one of the six value chain activities, so it does not run after plan finishes. The plan activity draws inputs from governance and the organization's strategy, not solely from obtain/build.
- A team wants the single ITIL 4 practice whose purpose is to maximize the number of successful service and product changes by ensuring risks are properly assessed, changes are authorized, and a change schedule is managed. Which practice should they use?
- Change enablement
- Release management
- Deployment management
- Service configuration management
Correct answer: Change enablement
Change enablement is the practice. Its purpose is to maximize the number of successful service and product changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing the change schedule. Release management makes services available for use, deployment management moves components to environments, and service configuration management maintains information about configuration items.
- In ITIL 4 change enablement, what is the key term used for a person or group that authorizes a change?
- Change authority
- Change initiator
- Change owner
- Change sponsor
Correct answer: Change authority
The key term is change authority. In change enablement, a change authority is the person or group responsible for authorizing a change, and authority should be assigned to roles suited to the type and risk of the change. The other labels are not the defined ITIL 4 key term for the entity that authorizes a change.
- An organization wants the ITIL 4 practice whose purpose is to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents and managing workarounds and known errors. Which practice fits?
- Problem management
- Incident management
- Monitoring and event management
- Change enablement
Correct answer: Problem management
Problem management is the practice. Its purpose is to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors. Incident management restores normal service operation as quickly as possible, while monitoring and event management observes services and reports changes of state.
- In ITIL 4 problem management, what is the key term for a problem that has been analyzed but has not been resolved?
- Known error
- Workaround
- Incident
- Event
Correct answer: Known error
The key term is known error. In problem management a known error is a problem that has been analyzed but not resolved. A workaround is a solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available, an incident is an unplanned interruption or reduction in quality of a service, and an event is a change of state significant for management of a service.
- A service provider needs the ITIL 4 practice whose purpose is to set clear business-based targets for service performance so that delivery can be properly assessed, monitored, and managed against those targets. Which practice is this?
- Service level management
- Relationship management
- Capacity and performance management
- Supplier management
Correct answer: Service level management
Service level management is the practice that sets clear business-based targets for service performance so delivery can be assessed, monitored, and managed against those targets. Relationship management maintains links with stakeholders, capacity and performance management ensures services achieve agreed performance cost-effectively, and supplier management oversees vendors.
- In ITIL 4, which key term refers to a documented agreement between a service provider and a customer that identifies both services required and the expected level of service?
- Service level agreement
- Service request
- Service catalogue
- Operational level agreement
Correct answer: Service level agreement
The key term is service level agreement (SLA). It is a documented agreement between a service provider and a customer that identifies both the services required and the expected level of service. A service request is a request from a user, a service catalogue lists available services, and an operational level agreement is an internal agreement, not one between provider and customer.
- A help desk wants the ITIL 4 practice whose purpose is to support the agreed quality of a service by handling all predefined, user-initiated service requests in an effective and user-friendly manner. Which practice should they use?
- Service request management
- Incident management
- Service desk
- Change enablement
Correct answer: Service request management
Service request management is the practice. Its purpose is to support the agreed quality of a service by handling all predefined, user-initiated service requests in an effective and user-friendly manner. Incident management restores service after interruptions, the service desk is the entry point and single point of contact, and change enablement authorizes changes.
- In ITIL 4, which statement best describes the purpose of the service desk practice?
- To capture demand for incident resolution and service requests, acting as the entry point and single point of contact for users
- To set business-based targets for service performance and assess delivery against them
- To plan and manage the full lifecycle of all IT assets
- To reduce the likelihood and impact of incidents by finding their causes
Correct answer: To capture demand for incident resolution and service requests, acting as the entry point and single point of contact for users
The correct purpose is to capture demand for incident resolution and service requests while acting as the entry point and single point of contact for users. Setting performance targets is service level management, managing the asset lifecycle is IT asset management, and finding incident causes is problem management.
- An organization wants the ITIL 4 practice whose purpose is to align the organization's practices and services with changing business needs through ongoing identification and improvement of services, components, and practices. Which practice is being described?
- Continual improvement
- Service level management
- Change enablement
- Relationship management
Correct answer: Continual improvement
Continual improvement is the practice whose purpose is to align the organization's practices and services with changing business needs through the ongoing identification and improvement of services, service components, practices, or any element involved in the management of products and services. Service level management sets targets, change enablement authorizes changes, and relationship management maintains stakeholder links.
- In ITIL 4 incident management, a first-line agent successfully restores a user's service by applying a documented workaround rather than fixing the root cause. According to the practice, is this an acceptable resolution of the incident?
- Yes, but only if the change enablement practice formally authorizes the workaround first
- No, because an incident can only be closed once the underlying root cause has been permanently removed
- Yes, because incident management aims to restore normal service as quickly as possible, and a workaround that restores service is a valid resolution
- No, because applying a workaround converts the incident into a problem that cannot be closed
Correct answer: Yes, because incident management aims to restore normal service as quickly as possible, and a workaround that restores service is a valid resolution
Yes, this is acceptable. ITIL 4 incident management is focused on restoring normal service operation as quickly as possible, so using a documented workaround to get the user working again is a valid resolution. Removing the root cause is the concern of problem management, not a prerequisite for closing an incident.
- In ITIL 4, how should an organization handle the recording of an incident when the same issue is reported by many users at once?
- Link the multiple reports to a single incident record so the response is coordinated and effort is not duplicated
- Create a fully independent incident record for every single user contact with no links between them
- Refuse to log later reports because the first record already exists and duplicates add no value
- Reclassify all the reports as service requests because the volume indicates a normal demand pattern
Correct answer: Link the multiple reports to a single incident record so the response is coordinated and effort is not duplicated
The correct approach is to link the multiple reports to a single incident record. ITIL 4 incident management recommends consistent recording and using tooling that relates records, so many reports of one issue are coordinated under one record, avoiding duplicated effort and giving a clear view of impact.
- In ITIL 4 incident management, what is the value of using swarming for a difficult incident?
- It brings different specialists together to collaborate on the incident at the same time instead of escalating it sequentially between teams
- It guarantees the incident will be reclassified as a major incident with executive oversight
- It transfers full accountability for the incident to the problem management team
- It removes the need to record the incident because resolution is handled verbally
Correct answer: It brings different specialists together to collaborate on the incident at the same time instead of escalating it sequentially between teams
The value of swarming is that it brings different specialists together to work on the incident simultaneously rather than passing the ticket from team to team. ITIL 4 highlights this collaborative technique as a way to resolve complex incidents faster than traditional sequential escalation.
- In ITIL 4 problem management, why is it useful to relate a known error to the incidents it has caused?
- So that the incidents can be automatically deleted once the known error is recorded
- So that when those incidents recur, the service desk can quickly apply the documented workaround and restore service faster
- So that the known error can be reclassified as a service request for the user
- So that change enablement is no longer required to deliver the permanent fix
Correct answer: So that when those incidents recur, the service desk can quickly apply the documented workaround and restore service faster
Relating a known error to its incidents lets the service desk quickly apply the documented workaround when those incidents recur, restoring service faster. ITIL 4 problem management records known errors and workarounds precisely so future incident handling is more efficient.
- In ITIL 4, an organization wants to reduce both the number and impact of incidents over time. Which practice is primarily responsible for this aim?
- Service request management
- Problem management
- Service desk
- Service level management
Correct answer: Problem management
Problem management is primarily responsible for reducing the likelihood and impact of incidents over time. It does this by identifying and analyzing problems, managing workarounds and known errors, and driving permanent resolutions, whereas the other practices focus on fulfilment, contact, and targets.
- In ITIL 4 service request management, why is it recommended to standardize and, where possible, automate the fulfilment of common requests?
- Because it allows requests to bypass any approvals that would otherwise apply
- Because automation removes the need to keep any record of the request being fulfilled
- Because it converts each request into an incident that the service desk can prioritize
- Because requests are predefined and repeatable, standardization and automation make fulfilment faster, more consistent, and more efficient
Correct answer: Because requests are predefined and repeatable, standardization and automation make fulfilment faster, more consistent, and more efficient
Standardizing and automating common requests works because service requests are predefined and repeatable. ITIL 4 says this makes fulfilment faster, more consistent, and more efficient, while still keeping records and any required approvals intact.
- In ITIL 4, an organization is deciding where to set the boundaries of what a service request can cover. Which guidance does service request management give?
- Any user demand, including reports of failures, should be accepted as a service request to simplify intake
- Requests should be limited to predefined, agreed services that can be initiated by the user as a normal part of service delivery
- Only requests that require executive approval should be treated as service requests
- Requests should be defined individually each time, since no two requests are alike
Correct answer: Requests should be limited to predefined, agreed services that can be initiated by the user as a normal part of service delivery
ITIL 4 guidance is that service requests should be limited to predefined, agreed services the user can initiate as a normal part of service delivery. Reports of failures are incidents, not requests, and requests are defined as repeatable offerings rather than created from scratch each time.
- In ITIL 4, what is the main reason the service desk should capture and use feedback from its user contacts?
- To provide insight that supports improvement across other practices and the wider service value system
- To allow the service desk to set the organization's service level targets on its own
- To decide which changes the change authority should approve
- To replace the need for problem management to investigate recurring issues
Correct answer: To provide insight that supports improvement across other practices and the wider service value system
The main reason is that service desk feedback provides insight supporting improvement across other practices and the wider service value system. Through its daily contact with users, the service desk is well placed to surface recurring themes that feed continual improvement and other practices.
- In ITIL 4, an organization measures only the percentage of incidents resolved within target time and calls its service desk successful. What weakness does ITIL 4 highlight in relying on such a single metric?
- A single metric can look positive while users remain dissatisfied, so a balanced set of measures including user experience is needed
- Only the customer, not the provider, is permitted to define any metric
- Resolution time should never be measured because it discourages thorough work
- A single metric is always more accurate than several metrics combined
Correct answer: A single metric can look positive while users remain dissatisfied, so a balanced set of measures including user experience is needed
The weakness ITIL 4 highlights is that a single metric can look positive while users are still dissatisfied. The framework warns against this kind of one-dimensional measurement and recommends a balanced bundle of measures that reflects the actual user experience.
- In ITIL 4 service level management, what is meant by saying that SLAs should be based on outcomes that matter to the customer?
- The provider should pick whatever targets are simplest to meet so the SLA always reports green
- The customer alone should operate the monitoring tools that produce the SLA data
- Targets should reflect what the customer is actually trying to achieve, not just measures that are easy for the provider to report
- SLAs should contain a single overall availability figure and nothing else
Correct answer: Targets should reflect what the customer is actually trying to achieve, not just measures that are easy for the provider to report
Outcome-based SLAs mean targets reflect what the customer is genuinely trying to achieve, rather than measures that are merely easy for the provider to report. ITIL 4 stresses aligning targets to customer value to avoid agreements that look good on paper but miss real needs.
- In ITIL 4 change enablement, what distinguishes a normal change from an emergency change?
- A normal change follows the standard scheduled assessment and authorization, while an emergency change is expedited because it must be implemented as soon as possible
- A normal change is always low risk, while an emergency change is always high risk by definition
- A normal change is pre-authorized, while an emergency change is assessed individually
- A normal change needs no authorization, while an emergency change needs full board approval
Correct answer: A normal change follows the standard scheduled assessment and authorization, while an emergency change is expedited because it must be implemented as soon as possible
A normal change follows the standard scheduled assessment and authorization process, while an emergency change must be implemented as soon as possible and so is expedited. The distinction is about timing and the assessment route, not strictly about risk level, since normal changes can be of any risk.
- In ITIL 4 change enablement, why is the change schedule shared with stakeholders across the organization?
- So that the schedule can replace the need for any change authority to approve changes
- So that teams can plan around upcoming changes, avoid conflicts, and prepare for potential impacts on their services
- So that only emergency changes are visible while normal changes stay hidden
- So that users can submit incidents directly into the schedule
Correct answer: So that teams can plan around upcoming changes, avoid conflicts, and prepare for potential impacts on their services
The change schedule is shared so teams can plan around upcoming changes, avoid conflicts, and prepare for impacts on their services. ITIL 4 uses the schedule to coordinate changes and communicate them broadly, which supports better planning across the organization.
- In ITIL 4, an organization wants change enablement to support a high rate of beneficial changes without causing unnecessary disruption. Which approach best fits the practice?
- Treat every change as an emergency so it can be implemented immediately
- Streamline low-risk changes through standard and pre-authorized routes while applying fuller assessment to riskier changes
- Allow all changes to proceed without assessment to maximize throughput
- Route every change, regardless of risk, through the same lengthy central approval board
Correct answer: Streamline low-risk changes through standard and pre-authorized routes while applying fuller assessment to riskier changes
The best fit is to streamline low-risk changes through standard and pre-authorized routes while applying fuller assessment to riskier changes. ITIL 4 change enablement seeks to maximize beneficial changes while controlling risk, which means matching the rigor of the process to the risk of the change.
- In ITIL 4, an organization completes the 'How do we get there?' step of the continual improvement model. According to the model's sequence, which step comes next?
- What is the vision?
- Take action
- Did we get there?
- Where are we now?
Correct answer: Take action
After 'How do we get there?', the next step in the continual improvement model is 'Take action'. The model runs from vision, current state, target state, planning the route, taking action, checking results, and keeping momentum.
- In the ITIL 4 continual improvement model, what is the focus of the step 'Where are we now?'
- Assessing and measuring the current state honestly so improvement can be planned from an accurate baseline
- Defining the long-term organizational vision and mission
- Confirming whether the improvement achieved its target
- Carrying out the planned improvement actions
Correct answer: Assessing and measuring the current state honestly so improvement can be planned from an accurate baseline
The 'Where are we now?' step focuses on honestly assessing and measuring the current state. ITIL 4 emphasizes accurate baseline measurement here so that targets and plans are built on a realistic understanding of the starting point.
- In ITIL 4 incident management, an organization tiers its support so that the service desk handles common incidents and routes harder ones to specialist groups. What is the main benefit ITIL 4 associates with this approach?
- It removes the need to record incidents that the service desk cannot resolve
- It allows the service desk to authorize emergency changes during the incident
- Incidents are allocated to the appropriate level of resource, so simple ones are resolved quickly and complex ones reach the right expertise
- It guarantees every incident becomes a problem record
Correct answer: Incidents are allocated to the appropriate level of resource, so simple ones are resolved quickly and complex ones reach the right expertise
The main benefit is that incidents are allocated to the appropriate level of resource. ITIL 4 wants simple incidents resolved quickly at first line and complex ones routed to the right specialist expertise, which a tiered support model enables.
- In ITIL 4, why does problem management often record a workaround even before a permanent fix has been found?
- So the change authority is relieved of approving the eventual fix
- So the problem record can be closed immediately without further work
- So service can be restored or maintained for affected users while analysis toward a permanent resolution continues
- So the workaround can replace the need for incident management entirely
Correct answer: So service can be restored or maintained for affected users while analysis toward a permanent resolution continues
Problem management records a workaround early so service can be restored or maintained for affected users while analysis continues toward a permanent resolution. Documenting the workaround reduces incident impact in the meantime, and the problem stays open until a fix is justified.
- In ITIL 4, what is the relationship between the service desk and the channels through which users contact it?
- Channels are chosen by the change authority rather than the service desk
- The service desk may only use a single channel to remain a single point of contact
- Each channel must be operated as a separate, unrelated support function
- The service desk acts as a single point of contact even when it offers multiple channels such as phone, portal, chat, and walk-up
Correct answer: The service desk acts as a single point of contact even when it offers multiple channels such as phone, portal, chat, and walk-up
The service desk acts as a single point of contact even while offering multiple channels such as phone, portal, chat, and walk-up. ITIL 4 stresses that the single point of contact idea is about a coordinated entry to support, not about limiting how many channels exist.
- In ITIL 4 service level management, what is the role of underpinning agreements with suppliers or internal teams?
- They define which incidents qualify as major incidents
- They replace the SLA so that the customer no longer needs one
- They help ensure that the commitments made to customers in an SLA can actually be met by aligning supporting parties' targets
- They are used only to set targets for the service desk's response times
Correct answer: They help ensure that the commitments made to customers in an SLA can actually be met by aligning supporting parties' targets
Underpinning agreements help ensure the commitments made to customers in an SLA can actually be met, by aligning the targets of supporting suppliers and internal teams. Service level management depends on these supporting arrangements so that customer-facing promises are realistic and achievable.
- In ITIL 4, an organization wants to ensure improvement work does not stall after the first wins. Which step of the continual improvement model addresses this directly?
- What is the vision?
- How do we keep the momentum going?
- Where are we now?
- Where do we want to be?
Correct answer: How do we keep the momentum going?
The step 'How do we keep the momentum going?' directly addresses sustaining improvement after early wins. It is the final step of the continual improvement model and focuses on embedding changes and maintaining drive so progress continues.
- In ITIL 4 change enablement, what is the appropriate way to handle a change that has been defined, risk-assessed, and pre-authorized in advance?
- It can be implemented as a standard change following the established procedure without seeking fresh authorization each time
- It should be treated as an emergency change so it can proceed immediately
- It must still be sent to a senior board for individual approval before each instance
- It must be reclassified as a normal change every time it recurs
Correct answer: It can be implemented as a standard change following the established procedure without seeking fresh authorization each time
A change that is defined, risk-assessed, and pre-authorized can be implemented as a standard change following its established procedure, without fresh authorization each time. ITIL 4 uses standard changes precisely so repeatable low-risk work flows quickly under a pre-approved route.
- In ITIL 4, why does incident management benefit from access to a knowledge base of past incidents and resolutions?
- It removes the need to prioritize incidents by impact and urgency
- Agents can reuse proven solutions and workarounds to diagnose and resolve recurring incidents more quickly
- It transfers responsibility for the incident to service level management
- It allows incidents to be closed without recording any details
Correct answer: Agents can reuse proven solutions and workarounds to diagnose and resolve recurring incidents more quickly
A knowledge base benefits incident management because agents can reuse proven solutions and workarounds to diagnose and resolve recurring incidents faster. ITIL 4 supports linking records and knowledge so prior learning speeds up future resolution.
- In ITIL 4 problem management, how does the practice prioritize which problems to investigate when resources are limited?
- By investigating problems strictly in the order they were reported regardless of impact
- By letting the service desk decide based on call volume alone
- By investigating only problems that have an existing permanent fix already available
- By assessing the risk and potential impact of each problem, so effort goes to those that matter most
Correct answer: By assessing the risk and potential impact of each problem, so effort goes to those that matter most
Problem management prioritizes by assessing the risk and potential impact of each problem so effort goes where it matters most. ITIL 4 accepts that not every problem can be worked at once, so it applies risk-based prioritization rather than a simple first-in order.
- In ITIL 4, what does it mean that service request management should keep the request catalog accurate and current?
- Users should be able to rely on the catalog to select valid, available offerings with correct expectations and fulfilment steps
- The catalog should be updated only when a major incident occurs
- The catalog should list every possible incident so users can report failures from it
- The catalog should be hidden from users to reduce request volume
Correct answer: Users should be able to rely on the catalog to select valid, available offerings with correct expectations and fulfilment steps
Keeping the catalog accurate and current means users can rely on it to select valid, available offerings with correct expectations and fulfilment steps. ITIL 4 service request management depends on a trustworthy catalog so requests are well understood and fulfilled smoothly.
- In ITIL 4, an organization assigns a dedicated coordinator and clear communication roles when a major incident occurs. What does ITIL 4 say this kind of arrangement supports?
- Treating the major incident as a routine service request
- A coordinated response with clear communication, so technical staff can focus on restoring service quickly
- The automatic creation of a standard change to fix the cause
- The elimination of any post-incident review once service is restored
Correct answer: A coordinated response with clear communication, so technical staff can focus on restoring service quickly
This arrangement supports a coordinated response with clear communication, letting technical staff focus on restoring service quickly. ITIL 4 recommends dedicated coordination and communication roles for major incidents because of their high impact and the need for fast, organized recovery.
- In ITIL 4, what is the purpose of relating change enablement to incident and problem management?
- Because problems can only be recorded inside the change schedule
- Because changes can both cause incidents and deliver permanent fixes for problems, the practices must coordinate to manage risk and outcomes
- Because every incident must be approved as a change before resolution
- Because change enablement replaces both incident and problem management
Correct answer: Because changes can both cause incidents and deliver permanent fixes for problems, the practices must coordinate to manage risk and outcomes
The practices must coordinate because changes can both cause incidents and deliver permanent fixes for problems. ITIL 4 stresses that change enablement works closely with incident and problem management to manage the risk changes create and to implement resolutions safely.
- In ITIL 4, why is it important that the continual improvement model is applied iteratively rather than as a one-time pass?
- Iteration is required so that improvements bypass any measurement
- Only the first step needs repeating; the rest are done a single time
- The model must be completed fully once and then never used again
- Improvement is ongoing, so revisiting the steps allows the organization to keep adjusting to new conditions and sustain progress
Correct answer: Improvement is ongoing, so revisiting the steps allows the organization to keep adjusting to new conditions and sustain progress
Applying the model iteratively matters because improvement is ongoing; revisiting the steps lets the organization keep adjusting to new conditions and sustain progress. ITIL 4 treats continual improvement as a repeating cycle rather than a single project.
- In ITIL 4 service request management, an onboarding request requires input from HR, IT, and facilities before the new employee is ready. What does the practice contribute to make this reliable?
- Reclassification of the request as a major incident due to its complexity
- Predefined workflows that coordinate the contributing teams so the multi-step request is fulfilled consistently end to end
- A rule that the request must be handled entirely by the service desk alone
- Removal of all approvals so the request completes faster
Correct answer: Predefined workflows that coordinate the contributing teams so the multi-step request is fulfilled consistently end to end
Service request management contributes predefined workflows that coordinate the contributing teams so the multi-step request is fulfilled consistently end to end. ITIL 4 notes that requests often depend on many teams, and predictable workflows make that collaboration reliable.
- In ITIL 4, what is the main reason a service desk should understand the organization's business and not only its technology?
- So it can interpret user needs in context, prioritize appropriately, and provide more relevant support
- So it can take over setting the SLA targets from service level management
- So it can stop logging incidents that seem business-related
- So it can authorize changes without involving a change authority
Correct answer: So it can interpret user needs in context, prioritize appropriately, and provide more relevant support
Understanding the business lets the service desk interpret user needs in context, prioritize appropriately, and give more relevant support. ITIL 4 stresses that business awareness, not just technical knowledge, makes the service desk more effective in its central user-facing role.
- In ITIL 4 problem management, what is the purpose of the error control phase?
- To detect and log problems for the first time from incident trends
- To approve and schedule changes to production systems
- To manage known errors, keep workarounds effective, and identify potential permanent solutions for known errors
- To restore service to a single user as quickly as possible
Correct answer: To manage known errors, keep workarounds effective, and identify potential permanent solutions for known errors
The error control phase manages known errors, keeps their workarounds effective, and identifies potential permanent solutions. In ITIL 4 problem management, error control follows identification and problem control, focusing on the ongoing handling of known errors until a justified fix is delivered.
- Within the ITIL 4 service value system, which component is recommended to apply at every level, runs alongside all other activities, and exists to keep services and practices aligned with changing needs?
- Continual improvement
- Governance
- The guiding principles
- The service value chain
Correct answer: Continual improvement
Continual improvement is the SVS component described here. ITIL 4 presents it as an ongoing component that applies at every level of the organization and runs alongside all value chain activities to keep services and practices relevant as needs change. Governance directs and controls, the guiding principles offer universal recommendations, and the service value chain is the set of interconnected activities that create value.
- ITIL 4 states that a chief purpose of the service value system is to address a particular obstacle that prevents organizations from creating value. Which obstacle is the SVS specifically designed to overcome?
- Organizational silos that block the flow of work and information
- The need to purchase certified service management tooling
- A shortage of formal project management qualifications among staff
- Regulatory requirements imposed by external auditors
Correct answer: Organizational silos that block the flow of work and information
The answer is organizational silos that block the flow of work and information. ITIL 4 designed the SVS as an overarching model in which all components and activities work together, specifically to overcome the silos that fragment work and impede value co-creation. It is not about mandating tool purchases, project qualifications, or satisfying auditors, which are unrelated to the SVS's stated purpose.
- A service value chain map shows one activity whose role is to provide a good understanding of the organization's vision, current status, and improvement direction for all four dimensions and all products and services. Which ITIL 4 service value chain activity is this?
- Plan
- Engage
- Improve
- Obtain/build
Correct answer: Plan
Plan is the value chain activity described. Its purpose is to ensure a shared understanding of the vision, current status, and improvement direction for all four dimensions and all products and services across the organization. Engage centres on stakeholder relationships and demand, improve drives continual betterment, and obtain/build ensures components are available and meet specifications.
- How many activities make up the ITIL 4 service value chain, and which statement correctly characterizes how they are arranged?
- Six activities that are not a fixed sequence but are combined in different orders to form value streams
- Seven activities that must always be performed in the same fixed left-to-right order
- Five activities, each owned by a single practice that cannot share work
- Four activities aligned one-to-one with the four dimensions of service management
Correct answer: Six activities that are not a fixed sequence but are combined in different orders to form value streams
The correct statement is that there are six activities combined in varying orders to form value streams. The service value chain's six activities (plan, improve, engage, design and transition, obtain/build, and deliver and support) are not a rigid sequence; an organization links them in different combinations to create specific value streams. They are not seven, five, or four, and they do not run in a single fixed order or map one-to-one to the four dimensions.
- In ITIL 4, the guiding principle Optimize and automate recommends a particular order of steps so that effort is not wasted. Which sequence reflects how the principle says optimization should proceed before automation is applied?
- Understand and agree the context and objectives, then optimize the work, and only then automate where it adds value
- Automate the existing work first to expose inefficiencies, then optimize whatever remains
- Optimize and automate every activity simultaneously to save time
- Automate only the activities that cannot be optimized by human effort
Correct answer: Understand and agree the context and objectives, then optimize the work, and only then automate where it adds value
The correct sequence is to understand and agree the context and objectives, optimize the work, and then automate where it adds value. ITIL 4 stresses that automating a flawed process simply produces poor outcomes faster, so optimization (informed by clear objectives) must come before automation. The other options invert or merge the steps in ways the principle explicitly cautions against.
