ITIL Service Value System practice questions

Practices

Why wrong: ITIL practices are specific organizational capabilities designed to perform work or achieve specific objectives, such as incident management or service desk operations. While they provide structured approaches for how work is done, they do not establish the overarching strategic direction, control mechanisms, or regulatory compliance frameworks required to ensure that all new services fundamentally align with the organization's broader business strategy and external requirements. That strategic oversight is a distinct function.

Service value chain

Why wrong: The service value chain (SVC) is an operational model within the ITIL service value system, outlining six key activities (Plan, Improve, Engage, Design & Transition, Obtain/Build, Deliver & Support) that an organization performs to create value for its stakeholders. While it guides the flow of work and value creation, it does not inherently provide the overarching strategic direction, control, or regulatory compliance framework necessary to ensure that new services align with the broader business strategy and external requirements. Its focus is on the process of value creation, not the governance of that process.

Continual improvement

Why wrong: Continual improvement is a practice focused on enhancing products, services, and practices across all stages of the service lifecycle, aiming for ongoing optimization and increased value. While crucial for evolving and refining services, its primary role is to iteratively improve existing or newly deployed services and processes, rather than establishing the initial strategic direction, control, and compliance framework that ensures new services are fundamentally aligned with business strategy and regulatory requirements from their inception. It's about getting better, not setting the initial strategic course.

Incident management

Why wrong: Incident management is primarily a reactive practice focused on restoring normal service operation as quickly as possible following an unplanned interruption or reduction in quality of service. Its core objective is to minimize the negative impact of incidents on business operations. It does not proactively prevent unauthorized changes from occurring; rather, it addresses the symptoms after such changes might have led to an outage.

Service desk

Why wrong: The service desk serves as the single point of contact between the service provider and its users, primarily handling incidents and service requests. While it facilitates communication and provides initial support, its function is not to govern or control the authorization and implementation of changes to services or infrastructure. It acts as an interface for user needs, not a mechanism for preventing unauthorized system alterations.

Problem management

Why wrong: Problem management aims to reduce the likelihood and impact of incidents by identifying and resolving the root causes of actual and potential incidents. While it seeks to prevent the recurrence of incidents, its focus is on underlying systemic issues, not the direct control or authorization of individual changes. It is a reactive-to-proactive practice that investigates patterns and trends, rather than preventing specific unauthorized modifications.

Collaborate and promote visibility

Why wrong: This principle emphasizes fostering effective working relationships and ensuring transparency across all service management activities. While crucial for successful service delivery, 'Collaborate and promote visibility' primarily addresses how teams and stakeholders interact and share information, rather than providing guidance on the initial identification or prioritization of what constitutes value for a new IT service. It focuses on the 'how' of working together, not the 'what' of value creation.

Optimize and automate

Why wrong: The 'Optimize and automate' principle is centered on improving the efficiency and effectiveness of services and processes through streamlining and technological enablement. It encourages the elimination of waste, reduction of human error, and acceleration of delivery once the value-generating activities have been identified. However, this principle does not guide the initial determination of critical requirements or the prioritization of efforts based on stakeholder value for a new service implementation.

Keep it simple and practical

Why wrong: The 'Keep it simple and practical' principle advocates for avoiding unnecessary complexity in processes, services, and solutions, promoting straightforward and workable approaches. It encourages pragmatism and the use of the minimum necessary steps to achieve an outcome, preventing over-engineering. While important for efficient design and implementation, this principle does not provide guidance on which outcomes are most valuable to pursue in the first place for a new service.

The guiding principles

Why wrong: While the ITIL guiding principles (e.g., Focus on value, Collaborate and promote visibility) are essential recommendations that shape organizational culture and decision-making, they are not a sequence of operational steps. They provide a philosophical foundation for how an organization should approach its work, but they do not prescribe the specific activities or a structured framework needed to design, deliver, or improve services to directly enhance customer satisfaction.

The practices

Why wrong: ITIL practices (e.g., Service Desk, Incident Management) are sets of organizational resources designed for performing work or accomplishing a specific objective. While individual practices contribute significantly to service delivery and customer satisfaction, they are not a holistic, end-to-end operational model for improving the entire service creation and delivery flow. The service value chain provides the overarching framework that integrates and orchestrates these practices into a cohesive system for value co-creation.

The governance

Why wrong: Governance in ITIL 4 refers to the means by which an organization is directed and controlled, ensuring that policies and strategies align with organizational objectives, including value creation. However, governance primarily focuses on oversight, decision-making authority, and accountability at a strategic level. It does not define the detailed, day-to-day operational activities or the sequence of steps required to create, deliver, or improve services to directly enhance customer satisfaction.

Service level agreement

Why wrong: A Service Level Agreement (SLA) is a documented agreement between a service provider and a customer that specifies the services to be provided, the responsibilities of both parties, and the agreed-upon service levels. While essential for defining expectations and managing service delivery, an SLA is an output or artifact resulting from service management practices, rather than a foundational, structural component of the ITIL Service Value System itself. The SVS provides the overarching framework within which such agreements are developed and managed.

Service owner

Why wrong: A Service Owner is a specific role within an organization, accountable for the end-to-end management, performance, and continual improvement of a particular service. While crucial for effective service management and operating within the ITIL framework, a role is not considered one of the five high-level components that constitute the ITIL Service Value System (SVS). The SVS defines the system's structure, whereas roles operate within that structure to achieve service value.

Incident management

Why wrong: Incident management is a practice within the service management domain, not a component of the ITIL Service Value System (SVS), which consists of the guiding principles, governance, service value chain, practices, and continual improvement. It is tempting because incident management is a core operational process in ITIL 4, but the SVS defines the overarching system that coordinates all practices, not the practices themselves.

Keep it simple and practical

Why wrong: This option describes one of the seven ITIL guiding principles, which are universal recommendations that can guide an organization in all circumstances, regardless of changes in its goals, strategies, or management structure. Guiding principles provide a foundational mindset and approach for decision-making and actions across the entire service value system. They are not specific operational activities within the service value chain itself, which are focused on the practical transformation of demand into value.

Service catalogue management

Why wrong: Service catalogue management is an ITIL management practice, specifically categorized under service management practices, focused on providing a single source of consistent information on all services and service offerings. Practices are sets of organizational resources designed for performing work or accomplishing an objective, detailing how specific types of work are done. While this practice is crucial for defining and presenting services, it is a detailed operational capability that supports the service value chain activities, rather than being one of the six high-level activities that directly transform demand into value.

Upgrade to a more powerful database server with more CPUs.

Why wrong: This approach addresses a symptom (lack of processing power) rather than the root cause of inefficient queries. While a more powerful server might temporarily mask the performance issue by providing more resources, it represents a significant capital expenditure without resolving the underlying software inefficiency. The problem will likely recur as data volume or query complexity grows, making it an unsustainable and costly solution that doesn't align with ITIL's 'Optimize and automate' principle.

Implement a caching layer to reduce database load.

Why wrong: Implementing a caching layer can reduce direct database load for frequently accessed data, but it acts as a workaround rather than a fundamental fix for inefficient queries. While it might improve response times for cached data, the underlying slow queries still consume resources and impact uncached operations. This introduces additional architectural complexity, potential data staleness issues, and does not adhere to the 'Start where you are' or 'Optimize and automate' principles by ignoring the existing inefficiency.

Hire a database consultant to review the entire database architecture.

Why wrong: Hiring a database consultant to review the entire architecture is a broad, costly engagement that does not directly target the specific, suspected root cause of inefficient queries. The scenario demands a focused, low-cost intervention, such as query optimisation or indexing, not a full architectural audit. This option is tempting because a consultant can provide expert guidance on systemic design flaws, and it would be correct if the problem were a poorly normalised schema or capacity planning failure rather than isolated query inefficiency.

Service value chain activities

Why wrong: Service value chain activities (Plan, Engage, Design & Transition, Obtain/Build, Deliver & Support, Improve) represent the operational model for creating, delivering, and continually improving services. While these activities are essential for value co-creation, they describe the workflow and processes rather than providing the overarching mechanism for strategic enforcement. They execute the work defined by governance, but do not establish or mandate the strategic direction or ensure adherence to it.

Continual improvement

Why wrong: Continual improvement is a core practice focused on enhancing products, services, and practices across all organizational levels. Its purpose is to iteratively improve efficiency, effectiveness, and value delivery over time, often driven by feedback and performance metrics. However, continual improvement operates within the established strategic framework and does not, by itself, define or enforce the initial strategic alignment of the entire Service Value System. It refines existing processes rather than dictating the strategic mandate.

Guiding principles

Why wrong: ITIL 4 guiding principles, such as "Focus on value" or "Collaborate and promote visibility," are universal recommendations that guide an organization in all circumstances, regardless of changes in its goals, strategies, or types of work. While they influence decision-making and foster a desired culture, they are advisory in nature and do not possess the formal authority or control mechanisms required to enforce strategic alignment across the entire organization. They provide guidance, not mandatory directives.

Guiding principles

Why wrong: Guiding principles are fundamental recommendations that can guide an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure. While they are a core component of the ITIL 4 Service Value System (SVS), they function as universal principles that influence all decisions and actions within the service value chain, rather than serving as direct inputs that initiate its activities.

Practices

Why wrong: Practices are sets of organizational resources designed for performing work or accomplishing an objective, such as service desk or incident management. Within the service value chain, practices are utilized to execute specific activities and transform inputs into outputs. They represent the capabilities and methods applied during value creation, but they are not the initial triggers or raw materials that start the service value chain itself.

Governance

Why wrong: Governance refers to the means by which an organization is directed and controlled, ensuring that the organization's activities are aligned with its strategic objectives and policies. It is a critical component of the Service Value System (SVS), providing overarching direction and control across all activities and practices. Governance acts as a framework that guides *how* the service value chain operates, rather than being a direct input that initiates the chain's activities.

Continual improvement

Why wrong: Continual improvement is an ongoing organizational activity and a dedicated practice that ensures services, products, and practices are continuously aligned with stakeholder needs and expectations. It drives the evolution and enhancement of all components within the Service Value System (SVS), including the service value chain. However, continual improvement functions as a mechanism for enhancement and optimization throughout the SVS, rather than an initial input that directly initiates the service value chain's operation.

Governance

Why wrong: In ITIL 4, governance refers to the means by which an organization is directed and controlled, ensuring that the organization's strategy is implemented and objectives are achieved. It establishes policies, assigns responsibilities, and defines decision-making authority. While governance provides the necessary oversight and direction that enables improvement, it does not itself perform the systematic activities of identifying, planning, and implementing improvements; that is the role of a dedicated practice.

The guiding principles

Why wrong: The ITIL guiding principles are universal recommendations that can guide an organization in all circumstances, regardless of changes in its goals, strategies, or type of work. They provide a foundational philosophy and a set of values to influence decisions and actions across the service value system. However, these principles offer general advice and a mindset for improvement, rather than a structured, systematic process or practice for how to execute specific improvement initiatives.

The service value chain activities

Why wrong: The service value chain (SVC) is an operational model in ITIL 4 that outlines the six core activities (Plan, Improve, Engage, Design & Transition, Obtain/Build, Deliver & Support) required to transform demand into value through the creation and management of products and services. While 'Improve' is one of these activities, the SVC itself describes the flow of work for value creation, not a standalone, systematic method for continuous improvement across the entire organization. The 'Improve' activity within the SVC leverages the dedicated continual improvement practice to achieve its objectives.

Focus on value

Why wrong: This ITIL guiding principle directs organizations to ensure all activities contribute to value for stakeholders, focusing on the desired outcomes. While defining the target value is crucial for setting the objectives of any redesign, it does not specify the initial action of assessing the current operational state of the service desk. The question specifically asks about the starting point for the redesign, which is distinct from defining the value objective.

Progress iteratively with feedback

Why wrong: This principle advocates for organizing work into smaller, manageable iterations, continuously seeking and applying feedback to improve. While vital for the execution and refinement of the service desk process redesign, it does not address the initial step of understanding the current state of the processes before any iterative changes can even begin. It describes the method of progression, not the preliminary assessment.

Keep it simple and practical

Why wrong: This ITIL guiding principle advises designing solutions that are straightforward, easy to understand, and deliver practical outcomes without unnecessary complexity. While crucial for ensuring the effectiveness and usability of the redesigned service desk processes, it does not specify the initial action of reviewing the current operational environment. It guides the nature and quality of the solution, not the preliminary assessment phase.

Output: improved end-user productivity; Outcome: fewer server incidents

Why wrong: This option incorrectly reverses the definitions of output and outcome. "Fewer server incidents" is a direct, measurable result of the monitoring system's operation and the IT team's actions, making it a clear output. Conversely, "improved end-user productivity" represents a broader business benefit or value realized by the organization due to the reduction in incidents, which correctly identifies it as an outcome. The pairing fails because an output is a direct deliverable, while an outcome is the resulting benefit.

Output: increased server availability; Outcome: monitoring software installed

Why wrong: This pairing is incorrect because "monitoring software installed" is a direct deliverable or an activity completed, making it an output, not an outcome. An outcome represents the value or benefit derived from that output, not the output itself. Furthermore, "increased server availability" is also a direct, measurable consequence of the monitoring system's effective operation, classifying it as an output rather than a higher-level business outcome like enhanced user experience or revenue generation. The option misclassifies both elements.

Output: monitoring software installed; Outcome: decreased server incidents

Why wrong: While "monitoring software installed" is correctly identified as an output, representing a tangible deliverable from the IT team's project, "decreased server incidents" is also an output. A decrease in incidents is a direct, measurable result of the monitoring system's successful operation and the IT team's subsequent actions, not a higher-level business outcome. An outcome, in ITIL 4, refers to the value or benefit realized by stakeholders from the consumption of outputs, such as improved business operations or enhanced user satisfaction, which "decreased server incidents" does not directly represent.

Practices

Why wrong: Practices are organizational resources designed to perform work or accomplish an objective. While they operate within the framework of defined policies and procedures, practices themselves do not establish or define those overarching policies for information security, risk management, or compliance. Instead, they are guided by such policies to ensure consistent and effective service management.

Service value chain

Why wrong: The service value chain (SVC) represents a set of interconnected activities that an organization performs to deliver a service and create value for its stakeholders. While the SVC activities (e.g., Plan, Engage, Design & Transition) are crucial for operationalizing strategy, they are the means by which value is co-created, not the body that defines the overarching policies and strategic direction for the organization.

Continual improvement

Why wrong: Continual improvement is a dedicated practice focused on ensuring that an organization's products, services, and practices are continually aligned with stakeholder needs and business objectives. While it drives ongoing enhancements and optimizes performance, it functions as an effort to improve existing policies and processes, rather than being the body responsible for initially defining the organization's strategic policies and direction.

Configuration management database

Why wrong: A Configuration Management Database (CMDB) is a critical tool and information system used to store information about configuration items (CIs) and their relationships. While essential for supporting various ITIL practices, particularly configuration management and IT asset management, it is not one of the four foundational components of the ITIL 4 Service Value System (SVS). Instead, a CMDB falls under the 'Information and technology' dimension of service management, enabling effective management of service components rather than being a structural element of the SVS itself.

Service level agreements

Why wrong: Service Level Agreements (SLAs) are formal, negotiated documents that define the agreed-upon service levels between a service provider and a customer. These agreements are crucial outputs and mechanisms within the 'service level management' practice, which is one of the ITIL practices. However, SLAs themselves are not one of the four core components that constitute the ITIL 4 Service Value System; they serve as a means to manage expectations and measure performance, rather than being a foundational building block of the system.

Service desk

Why wrong: The Service Desk is a specific ITIL practice, functioning as the single point of contact between the service provider and the users. Its primary role involves handling incidents, service requests, and providing an interface for all other service management activities. While indispensable for effective service delivery and user support, the Service Desk is categorized under the 'Practices' component of the ITIL 4 Service Value System, rather than being one of the four overarching components that define the system's structure.

Start a problem investigation to find the root cause

Why wrong: Starting a problem investigation to find the root cause is premature for an initial service disruption. Problem management focuses on identifying the underlying causes of incidents to prevent recurrence, which typically begins after an incident has been resolved or when recurring incidents indicate a deeper issue. The immediate priority for a service desk receiving a call about users being unable to access a system is to restore service, not to embark on a lengthy root cause analysis.

Submit a change request to fix the system

Why wrong: Submitting a change request to fix the system is inappropriate for an unplanned service disruption. Change management is designed for planned modifications to services or components, ensuring they are assessed, authorized, and implemented in a controlled manner to minimize risk. A live system failure requires immediate incident response to restore functionality, not the formal, often time-consuming, process of a change request, which would delay service restoration.

Escalate to second-level support immediately

Why wrong: Escalating to second-level support immediately bypasses the critical initial steps of incident management. The service desk's primary role is to be the first point of contact, log the incident, and attempt initial diagnosis and resolution using available knowledge and tools. Escalation is a subsequent step, typically occurring when first-level support cannot resolve the incident within agreed service level targets or requires specialized expertise, not the default first action.

Progress iteratively with feedback

Why wrong: The "Progress iteratively with feedback" guiding principle emphasizes breaking down work into smaller, manageable iterations, evaluating each step, and incorporating lessons learned to continuously improve. While crucial for the successful implementation of any new process, including change management, this principle primarily focuses on the methodology of implementation and continuous improvement rather than the specific goal of maximizing operational efficiency or leveraging technology for automation within the process itself. It guides how you build, not what you build in terms of efficiency.

Keep it simple and practical

Why wrong: The "Keep it simple and practical" guiding principle advocates for using the minimum number of steps necessary to achieve an outcome, avoiding unnecessary complexity in processes, services, and activities. While a simple process is often easier to automate, this principle focuses on the inherent design's clarity, ease of understanding, and practical applicability, rather than the specific act of implementing automation or optimizing for efficiency. It's about reducing complexity, which is a prerequisite for effective automation, but not the principle that prescribes automation itself.

Focus on value

Why wrong: The "Focus on value" guiding principle mandates that all activities performed by the organization must contribute to the creation of value for stakeholders, whether they are customers, users, or the organization itself. While an optimized and automated change management process ultimately delivers value (e.g., faster changes, reduced errors, improved compliance), this principle is about the purpose and outcome of the process, not the specific method of achieving efficiency through automation. It's too broad; automation is a means to deliver value, not the principle that prescribes automation as the primary focus.

Start where you are

Why wrong: This principle advises against discarding existing resources and instead encourages assessing and leveraging current services, processes, people, and technology. It emphasizes building upon what already exists, whether successful or not, to avoid unnecessary waste and accelerate improvement initiatives. However, it does not define the fundamental objective or core offering of a service provider, which is to deliver something of worth.

Collaborate and promote visibility

Why wrong: This principle stresses the importance of working together across organizational silos and ensuring that information, progress, and risks are transparently shared among all relevant parties. It advocates for effective communication and shared understanding to achieve better outcomes and avoid misunderstandings. While vital for effective service delivery, this principle describes *how* a service provider should operate, rather than its fundamental purpose or what it *suggests* it *does* as its core offering.

Progress iteratively with feedback

Why wrong: This principle encourages breaking down work into smaller, manageable increments, allowing for continuous learning, adaptation, and improvement based on feedback. It promotes agility and responsiveness by enabling adjustments throughout the service lifecycle, rather than waiting for a final product. While an essential approach for efficient service development and improvement, this principle describes a method of working, not the core suggestion of what a service provider fundamentally *does* or offers.

Optimize and automate

Why wrong: The "Optimize and automate" guiding principle emphasizes improving the efficiency and effectiveness of services and processes, often through the application of technology and streamlined workflows. While crucial for mature processes, applying this principle prematurely during an initial redesign, without a clear understanding of the current state or desired future state, can lead to automating inefficiencies rather than solving underlying problems. It's a subsequent step, not the starting point for a redesign.

Focus on value

Why wrong: The "Focus on value" guiding principle directs all activities towards creating value for service consumers and other stakeholders. While the ultimate objective of redesigning an incident management process is undoubtedly to deliver better value, this principle itself does not describe the *initial action* of beginning the redesign. It provides the overarching purpose for the redesign, but not the specific approach for commencing the work of assessing and changing the process itself.

Keep it simple and practical

Why wrong: The "Keep it simple and practical" guiding principle encourages organizations to design and implement processes and services that are easy to understand, manage, and use, avoiding unnecessary complexity. While this principle is vital for ensuring the redesigned incident management process is effective and sustainable, it describes a characteristic of the *solution* or the *design approach*, not the initial step of *beginning* the redesign by assessing the current state. It guides *how* to design, not *where* to start.

Focus on value

Why wrong: "Focus on value" is a foundational ITIL guiding principle that ensures all activities, including improvement efforts, are aligned with delivering tangible outcomes and perceived benefits to stakeholders. While essential for defining what to improve and why an improvement is necessary, this principle primarily addresses the objective and justification of an activity. It does not specifically describe the methodology or process by which improvements are incrementally developed, tested, and refined over time, which is a distinct aspect of improvement activities.

Collaborate and promote visibility

Why wrong: "Collaborate and promote visibility" emphasizes the importance of fostering a culture of shared understanding, transparency, and cooperation among all relevant stakeholders. While vital for the successful execution of any improvement initiative by ensuring diverse perspectives are considered and efforts are coordinated, this principle primarily defines the social and communication aspects of working. It describes how people should work together during improvement, rather than the fundamental structure or lifecycle of the improvement process itself.

Think and work holistically

Why wrong: "Think and work holistically" encourages organizations to consider all components of a service and its management system as an integrated whole, taking into account all four dimensions of service management. This principle is crucial for ensuring that improvements in one area do not inadvertently create problems elsewhere, promoting a comprehensive perspective. However, it provides a broad contextual framework for understanding interdependencies, rather than detailing the step-by-step approach or iterative nature of how improvements are actually designed, implemented, and refined.

To define a set of service desk procedures

Why wrong: The Service Value System (SVS) provides a holistic model for how all components and activities of an organization work together to facilitate value creation. Defining specific service desk procedures is a tactical activity within the 'Service Desk' practice, which is merely one component of the broader SVS. The SVS encompasses practices, guiding principles, governance, and continual improvement, making this option far too narrow to represent its primary purpose.

To replace the ITIL continual improvement model

Why wrong: The Service Value System (SVS) integrates continual improvement as one of its key components, specifically through the 'Continual Improvement' practice and the 'Continual Improvement Model'. The SVS does not replace this model; rather, it provides the overarching framework within which continual improvement operates to ensure ongoing value co-creation. The model itself remains a distinct, valuable tool within the SVS.

To specify the structure of ITIL 4 practices

Why wrong: While ITIL 4 practices are essential components within the Service Value System (SVS), specifying their individual structure is not the SVS's primary purpose. The SVS describes how all organizational components and activities, including practices, work together as a system to enable value co-creation. Practices are detailed separately within ITIL guidance, and the SVS provides the framework for their integration and application, rather than solely defining their internal structure.