Free ITIL-DSV Practice Test

During a period of significant organizational change, such as a digital transformation, maintaining a strong relationship is crucial. Regularly carrying out customer satisfaction surveys provides a structured mechanism to gather feedback and understand the customer's evolving perceptions and needs. The most critical part of this process is to analyze and act upon the results. This demonstrates that the service provider is listening, values the customer's input, and is committed to partnering with them through the transformation. This proactive engagement and responsiveness are key to fostering trust and maintaining a positive relationship during a potentially disruptive time.

B. Lowering the billing margin is a financial incentive, not a relationship management technique. A good relationship is built on trust and value co-creation, not just on price.
C. Increasing service levels during a major transformation may be impractical or set unrealistic expectations, potentially leading to failures that could damage the relationship.
D. Meeting agreed targets is a baseline operational requirement of any service agreement. While important, it is not a specific, proactive measure to nurture a relationship during a period of heightened change.

1. AXELOS

ITIL® 4: Drive Stakeholder Value. TSO (The Stationery Office)

2020.

Section 4.3.4

"Relationship management techniques": This section discusses the importance of communication and feedback. It states

"Surveys can be used to gather quantitative and qualitative feedback from a large number of stakeholders... The results of surveys should be analysed and acted upon." This directly supports using surveys and acting on them to manage relationships.

Section 2.3.3

"The customer journey": This section emphasizes understanding the customer's experience at all touchpoints. During a transformation

these touchpoints are in flux. Regular feedback is essential to "measure and improve the service experience" and ensure the relationship remains strong.

Section 5.2.5

"Measuring and improving service value": This section highlights that feedback is a critical input for understanding value and making improvements. It notes

"Feedback can be actively collected through surveys

interviews

and reviews." Acting on this feedback is central to the principle of value co-creation

especially during change.

User-centered service design, often realized through design thinking, is a human-centered approach to innovation. It integrates the needs of people, the possibilities of technology, and the requirements for business success. The core activity is not just focusing on the user in isolation but holistically balancing the user's experience and desirability with business viability and technical feasibility. This ensures that the resulting service is not only valuable to the user but also sustainable and achievable for the organization.

A. Value stream mapping is a Lean practice used to analyze and improve the flow of value to a customer; it is a tool for process optimization, not a definition of user-centered design.
B. Building a prototype with minimum functionality describes creating a Minimum Viable Product (MVP), a technique used within design and development, but not the overarching principle of user-centered design.
D. The MoSCoW technique is a method for prioritizing requirements. While useful in service design, it is a specific tool for managing scope, not the definition of the user-centered approach itself. ---

1. AXELOS. (2020). ITIL® 4: Drive Stakeholder Value. TSO (The Stationery Office).

Section 5.1.3.1

'Service design thinking': This section explicitly states

"Service design thinking is a human-centred approach that is used to create new services or improve existing ones. It balances the needs of the user with the needs of the business and the possibilities of technology." This directly supports option C as the correct definition.

2. Brown

T. (2008). Design Thinking. Harvard Business Review

86(6)

84–92.

This foundational academic article on design thinking (a core component of user-centered design in ITIL) defines the approach as a discipline that "uses the designer’s sensibility and methods to match people’s needs with what is technologically feasible and what a viable business strategy can convert into customer value and market opportunity." This corroborates the concept of balancing user

technical

and business needs.

3. Stickdorn

M.

Hormess

M. E.

Lawrence

A.

& Schneider

J. (2018). This Is Service Design Doing: Applying Service Design Thinking in the Real World. O'Reilly Media.

Chapter 1

'An Introduction to Service Design': The book describes service design as an interdisciplinary approach that combines different methods and tools from various disciplines. It emphasizes that a key principle is being "holistic

" which involves considering all relevant stakeholders and the business context

not just the end-user's perspective in isolation. This aligns with the balancing act described in option C.

The shift to remote work has fundamentally changed user behavior and service consumption patterns. To understand these changes, the organization must analyze the new Patterns of Business Activity (PBA). PBA is a key technique in demand management used to identify and understand how and when users consume services. By analyzing these new patterns, the service provider can understand the new demand profile, including peak and off-peak times, which is essential for aligning service capacity and availability with the changed business needs.

A. Introducing component capacity management is a response to demand; it focuses on managing IT infrastructure capacity rather than first understanding the user behavior that drives it.
B. Introducing differential charging is a method to influence or shape demand, which can only be effectively implemented after the new demand patterns are understood.
C. Building a customer business case is typically done to justify a new project or investment, not to analyze the ongoing operational effects of a change in working style.

1. AXELOS. (2020). ITIL® 4: Drive Stakeholder Value (DSV). TSO (The Stationery Office).

Section 4.2.3

Managing demand and opportunities: This section explains that a key part of managing demand is understanding customer and user profiles and patterns of business activity (PBA). It states

"Demand from different types of users can be classified in user profiles

which can be consolidated into patterns of business activity." The scenario describes a change that requires exactly this analysis.

2. AXELOS. (2019). ITIL® 4 Foundation

ITIL 4 Edition. TSO (The Stationery Office).

Section 5.1.2

Capacity and performance management practice: This section notes that capacity management "is driven by patterns of business activity and the resulting demand for services and resources." This confirms that analyzing PBA is a prerequisite for effective capacity management.

The primary goal of incident management is to restore normal service operation as quickly as possible. Consistently breaching service level targets for priority 1 (P1) incidents indicates a bottleneck in the resolution process. Improving the triage step to immediately route these critical incidents to a specialized group with the requisite skills and authority is the most effective action. This bypasses lower support tiers, reduces hand-off delays, and ensures that experts begin working on the resolution immediately, directly addressing the excessive resolution time. This aligns with the ITIL practice of having dedicated procedures for major incidents.

B. Shifting all service desk employees is an inefficient use of resources; they may lack the specialized skills required for P1 resolution, causing more confusion.
C. Adding additional staff to the service desk addresses logging capacity, not the specialized technical skill required for rapid P1 resolution.
D. Removing the triage step would be counterproductive, leading to mis-assigned incidents and even longer delays as they are rerouted multiple times.

1. ITIL® 4 Practice Guide: Incident Management. AXELOS. (2020). Section 5.2.5, "Incident resolution," states that "Major incidents often require a separate procedure" and that "A dedicated team is often assigned to a major incident." This supports the concept of guiding P1 incidents directly to a specialized group.

2. ITIL® 4: Drive Stakeholder Value. AXELOS. (2020). Section 4.3.3, "Triaging duty and prioritizing work," emphasizes that "Effective triage requires skill and knowledge to ensure that work is routed to the appropriate team." Improving this step is a logical corrective action.

3. Iden, J., & Eikebrokk, T. R. (2013). Implementing IT Service Management: A systematic literature review. International Journal of Information Management, 33(3), 512-523. This review discusses how structured processes, including proper incident classification and routing (triage), are critical success factors for achieving the benefits of ITSM, such as faster resolution times. (DOI: https://doi.org/10.1016/j.ijinfomgt.2013.01.004)

Establishing a "service mindset" is a cultural initiative focused on embedding customer-centric values and behaviors throughout the organization. The most effective way to achieve this is by developing core competencies like interpersonal skills and service empathy in all staff, not just in customer-facing roles. This ensures that every employee, regardless of their function, understands and prioritizes the consumer's perspective. This organization-wide cultural shift is fundamental to building the trust and partnership mentioned in the objective, leading to higher customer satisfaction.

A. A capability assessment is a performance review; while sharing it can build some trust, it does not actively cultivate a service mindset across the organization.
B. Hiring relationship managers is a valuable but limited approach, as it concentrates the service mindset within a specific role rather than fostering it organization-wide.
C. Detailed SLAs are formal, contractual tools for managing expectations and performance. They can be adversarial and do not inherently foster a collaborative, empathetic service culture.

1. AXELOS

ITIL® 4: Drive Stakeholder Value. TSO (The Stationery Office)

2020.

Section 5.1.4

"Fostering a service mindset

" states: "A service mindset is an important part of an organization’s culture... It includes a deep understanding of what a service is

and what value means for the consumer... It is based on principles of customer-orientation

curiosity

empathy

and a focus on value co-creation." This directly supports developing empathy (D) as central to the service mindset.

Section 4.3.3

"Skills and competencies for relationship management

" highlights that "empathy

trust

and effective and open communication" are crucial skills. The question's objective is to apply this across the organization

making option D the most comprehensive approach.

Section 2.2.2

"The customer journey

" emphasizes understanding the customer's experience

including their emotional state

at all touchpoints. This requires empathy and interpersonal skills from all teams involved in the journey

not just a single point of contact.

An experience metric is designed to measure a user's subjective perception and feelings about a service interaction, rather than purely objective operational outputs. Customer satisfaction is a direct measure of the customer's experience and sentiment regarding the helpline service. This aligns with the ITIL DSV focus on understanding and improving the service journey from the stakeholder's perspective. The shift from traditional Service Level Agreements (SLAs) to Experience Level Agreements (XLAs) emphasizes capturing such sentiment-based metrics to ensure value is co-created and perceived by the customer.

A. Availability of the helpline during agreed hours: This is a classic operational metric measuring service uptime, not the quality or feeling of the customer's interaction.
B. Number of customer queries processed correctly: This is a quality or output metric that measures the provider's accuracy, not the customer's subjective experience.
C. Number of calls processed concurrently: This is a capacity or performance metric measuring the system's load-handling capability, not the individual customer's experience.

1. AXELOS. (2020). ITIL® 4: Drive Stakeholder Value. TSO (The Stationery Office).

Section 4.3.3.3

"From service level agreements (SLAs) to experience level agreements (XLAs)": This section explicitly states

"XLAs are focused on the user experience of a service... They capture the user’s true experience and their level of satisfaction with the entire service." This directly supports that customer satisfaction (D) is an experience metric. The text contrasts this with traditional SLAs that focus on operational metrics like availability (A).

2. AXELOS. (2020). ITIL® 4: Drive Stakeholder Value. TSO (The Stationery Office).

Section 5.2.6

"Measuring and assessing value realization": This section discusses the importance of measuring stakeholder satisfaction and experience. It notes

"It is important to measure stakeholder satisfaction throughout the user journey... Common metrics include customer/user satisfaction (CSAT/USAT)..." This confirms that customer satisfaction is a key metric for assessing value from the user's perspective.

The purpose of the service catalogue management practice is to provide a single, consistent source of information on all services and service offerings and to ensure it is available to the relevant audience. This practice is directly responsible for creating and maintaining the views of the service catalogue, often presented through an online portal. It ensures that the information users see is accurate, up-to-date, and easy to navigate, which directly addresses the requirements outlined in the scenario.

A. Service request management: This practice focuses on the process of fulfilling pre-defined user requests, not on managing the information about the services themselves.
B. Service desk: This is the point of contact for users. It utilizes the service catalogue to assist users but is not responsible for managing its content.
C. Service level management: This practice is concerned with setting, monitoring, and managing service performance targets (SLAs), not with presenting service information to users.

1. AXELOS. (2020). ITIL® 4: Drive Stakeholder Value (DSV). TSO (The Stationery Office).

Section 5.2.7 (Service catalogue management): "The purpose of the service catalogue management practice is to provide a single source of consistent information on all services and service offerings

and to ensure that it is available to the relevant audience." This section further explains that the practice involves managing the information in the catalogue

which is often presented to users via a portal.

Section 5.2.8 (Service request management): Defines the purpose as handling "all pre-defined

user-initiated service requests

" confirming its focus is on fulfillment

not information management.

Section 5.2.6 (Service desk): Describes the service desk's purpose as capturing "demand for incident resolution and service requests

" highlighting its role as an entry point

not a content manager.

Section 5.2.9 (Service level management): States the purpose is "to set clear business-based targets for service performance

" confirming its focus on performance against targets.

According to ITIL 4, the primary purpose of a service is to facilitate the outcomes a customer wants to achieve. This is the foundation of value co-creation. Before a service provider can design a service, manage risks, or define relationship parameters, they must first understand the customer's goals and what they are trying to accomplish. Identifying these desired outcomes is the essential first step in the customer journey, as it defines the "value" that the service must deliver. All subsequent activities, including service design, risk assessment, and defining engagement models, are based on this initial understanding.

A. Feedback mechanisms are established to improve an existing or planned service relationship, which can only be defined after understanding the customer's initial needs.
B. Defining the service provider's involvement in decisions is part of relationship management, which follows the fundamental understanding of what the customer wants to achieve.
C. Dependencies and risks can only be properly assessed after the desired outcomes and the scope of the required service are understood.

1. AXELOS. (2020). ITIL® 4: Drive Stakeholder Value. TSO (The Stationery Office).

Section 3.2.1

"Understanding service consumers and their needs

" states: "The first step in managing any relationship is to understand the parties involved... This includes identifying the outcomes that the service consumer wants to achieve..."

Section 2.1

"The customer journey

" describes the first step

'Explore

' as the stage where the consumer investigates service providers and the provider explores the potential customer's needs and desired outcomes.

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

Section 2.2.2

"Value: outcomes

costs

and risks

" defines an outcome as "a result for a stakeholder enabled by one or more outputs." This establishes that the entire service concept is built upon achieving outcomes.

Psychographic segmentation divides a market based on consumers' psychological attributes, such as lifestyle, values, interests, and personality traits. A preference for organic food is not a simple behavior but a reflection of a consumer's lifestyle choices and values, often related to health, wellness, and environmental consciousness. This aligns directly with the principles of psychographic categorization, which seeks to understand the 'why' behind consumer choices, rather than just the 'what' or 'who'.

A. Behavioural market category: This focuses on observable actions like purchase history, usage rate, or brand loyalty, not the underlying values or lifestyle that drive the behavior.
B. Geographic market category: This segmentation is based on physical location, such as country, region, or city, which is irrelevant to a food preference.
D. Demographic market category: This uses statistical data like age, gender, income, or occupation. A love for organic food is a personal value, not a demographic characteristic.

1. AXELOS. (2020). ITIL® 4: Drive Stakeholder Value. TSO (The Stationery Office).

Section 2.2.3

Page 20: This section details the four main types of market segmentation. It defines psychographic segmentation as "dividing a market based on lifestyle

social class

and personality traits

" which directly corresponds to the example of preferring organic food as a lifestyle choice. It also defines the other three incorrect options.

2. MIT OpenCourseWare. (2010). 15.810 Marketing Management

Lecture Notes: Session 3 - Segmentation

Targeting

and Positioning. Massachusetts Institute of Technology.

Page 4

"Bases for Segmentation": The courseware lists "Psychographic" segmentation as being based on "Lifestyle" and "Personality

" providing academic validation that a preference like loving organic food falls under this category.

3. Wedel

M.

& Kamakura

W. A. (2000). Market Segmentation: Conceptual and Methodological Foundations (2nd ed.). Kluwer Academic Publishers.

Chapter 1

Section 1.2

Page 7: This foundational academic text explains that psychographic segmentation is based on consumers' "activities

interests

and opinions (AIOs)" and "values and lifestyles (VALS)." A preference for organic food is a clear example of these attributes.

The most effective approach, as emphasized in the ITIL 4: Drive Stakeholder Value framework, is for the service consumer to focus on their desired outcomes. By developing a list of needs centered on what they want to achieve, the consumer opens a dialogue for value co-creation. This allows the service provider to apply their expertise to design the most suitable and innovative solution. This outcome-based approach ensures the service directly supports the consumer's business objectives, rather than being constrained by pre-defined technical specifications or replicating legacy functionalities. It shifts the focus from a transactional exchange of specifications to a collaborative partnership aimed at delivering tangible value.

B. Asking for a customized solution is a potential step, but it is not the best initial approach as it presupposes a specific solution path.
C. Basing requirements on a legacy solution is a common anti-pattern that stifles innovation and can carry forward old inefficiencies.
D. Providing a detailed list of requirements can be overly prescriptive, limiting the provider's ability to propose a more effective or efficient solution. ---

1. AXELOS. (2020). ITIL® 4: Drive Stakeholder Value (DSV). TSO (The Stationery Office).

Section 4.3.2

"Gathering and analysing requirements": This section explicitly states

"Requirements should be expressed in terms of what the stakeholder needs to accomplish and why." This directly supports focusing on what should be achieved (Option A) rather than providing a detailed list of requirements (Option D).

Section 4.3

"Agree and plan": The text discusses the importance of mutual understanding of needs and expectations to define value. It emphasizes that "The service provider should work with the service consumer to understand their needs and priorities." This highlights the collaborative nature that begins with the consumer's needs

not a pre-defined solution.