Select Two (Multi-Select) Questions

Number of known errors

Why wrong: Known errors are tracked by problem management.

Mean Time to Repair (MTTR)

Why wrong: MTTR is an incident management metric, not typically a service desk metric.

Percentage of changes that are emergency

Why wrong: This is a change management metric.

Define baselines

Why wrong: Incorrect: 'Define baselines' is not a separate phase; it is a sub-activity within the 'Assess current state' step.

Monitor and control changes

Why wrong: Incorrect: 'Monitor and control changes' is not a phase of the Continual Improvement Model; it is part of change enablement.

Service level agreements

Why wrong: SLAs are not a component of the SVS; they are outputs of service level management.

Service desk

Why wrong: The Service Value System (SVS) consists of the guiding principles, governance, service value chain, practices, and continual improvement — not operational support functions. A service desk is a specific practice within the SVS’s "practices" component, not a separate SVS component. It tempts because service desks are central to ITIL service operation, but the SVS is a higher-level framework for value co-creation, not a list of support tools.

Configuration management database

Why wrong: A configuration management database (CMDB) is a tool used to store and manage information about configuration items (CIs) and their relationships, but it is not a component of the ITIL Service Value System (SVS). The SVS components are specifically the guiding principles, governance, service value chain, practices, and continual improvement. A CMDB is tempting because it supports the *practices* component (specifically service configuration management), but it is an operational database, not a structural element of the SVS itself.

Start from scratch to avoid bias from previous decisions

Why wrong: This option is incorrect because the 'Start where you are' principle explicitly advises against starting from scratch. It emphasizes leveraging existing resources, processes, and knowledge rather than discarding them due to perceived biases. Initiating an entirely new effort without considering current capabilities leads to wasted investment, duplicated work, and a failure to capitalize on established organizational strengths and lessons learned.

Focus on the desired future state rather than current limitations

Why wrong: This option is incorrect because, while a desired future state is vital, the 'Start where you are' principle prioritizes a thorough understanding of the *current* state. Ignoring present limitations or capabilities in favor of an idealized future can lead to unrealistic planning, missed opportunities for leveraging existing assets, and significant challenges during implementation. The principle advocates for building a realistic path forward from the existing foundation.

Employee training on how to use the service

Why wrong: While a service provider may offer training materials or courses as an ancillary service, the ultimate responsibility for ensuring a consumer's employees are adequately trained to effectively and safely utilize the service typically rests with the consumer organization. The risk of operational inefficiencies, user errors, or security vulnerabilities stemming from a lack of user proficiency is therefore retained by the consumer, not transferred to the provider, as it falls within the consumer's internal operational domain.

Data loss due to user mistake

Why wrong: Even when a service provider manages the underlying infrastructure and data storage, the responsibility for the integrity and accuracy of data entered or managed directly by the consumer's users often remains with the consumer. If a user accidentally deletes critical information, inputs incorrect data, or misconfigures settings, the resulting data loss or corruption is generally considered a consumer-side operational risk. While providers may offer recovery mechanisms like backups, the primary cause and immediate impact are within the consumer's operational control.

The service includes a user-friendly interface

Why wrong: Usability is a utility aspect.

The service provides a search function

Why wrong: Functionality is a utility aspect.

The service returns search results in under 1 second

Why wrong: Performance is often considered a utility aspect (fit for purpose).

Service desk

Why wrong: The service desk is a crucial function within an organization, acting as a single point of contact between the service provider and users. While essential for service delivery and support, it represents an organizational capability or resource rather than one of the foundational components that constitute the ITIL 4 Service Value System (SVS). The SVS components are higher-level structural elements that define how value is co-created.

Configuration management

Why wrong: Configuration management is defined as an ITIL management practice, which is a set of organizational resources designed for performing work or accomplishing an objective. Practices, such as configuration management, are detailed approaches for specific types of work within the service value chain, but they are not the overarching structural components that form the ITIL 4 Service Value System itself. The SVS components provide the framework within which these practices operate.

Service level agreements

Why wrong: Service Level Agreements (SLAs) are documented agreements between a service provider and a customer that specify the services to be provided, the service levels, and the responsibilities of both parties. While critical for defining and managing service expectations and performance, SLAs are outputs or artifacts of the service relationship management practice, not one of the fundamental structural components that comprise the ITIL 4 Service Value System. They represent a contractual aspect rather than an architectural element of the SVS.

It suggests ignoring previous investments to avoid bias

Why wrong: The 'Start where you are' guiding principle explicitly advises against ignoring previous investments or existing assets. Instead, it mandates a thorough assessment of all current resources, processes, and relationships to understand their value and potential for reuse. Discarding established components without proper evaluation would be wasteful and directly contradicts the principle's emphasis on leveraging what is already in place to build upon for future improvements.

It recommends copying best practices from other organisations

Why wrong: The 'Start where you are' principle does not primarily recommend copying best practices from other organizations. While learning from external examples can be beneficial, the core tenet is to first understand and assess an organization's unique internal context, capabilities, and existing solutions. Blindly adopting external practices without a thorough internal assessment often leads to misalignment, resistance, and failure, as they may not suit the specific operational environment or culture.

It requires starting from scratch for every new initiative

Why wrong: This principle explicitly advises against starting from scratch for every new initiative without a compelling, evidence-based reason. It promotes an iterative and evolutionary approach, encouraging organizations to identify and build upon existing, functional components, knowledge, and processes. A complete 'from scratch' approach should only be considered when a detailed assessment reveals no viable existing foundation or when a radical, justified departure from the current state is demonstrably necessary for achieving desired outcomes.

To ensure a shared understanding of the current status and improvement direction

Why wrong: This statement describes a primary purpose of the "Plan" value chain activity, not "Design and Transition." The "Plan" activity focuses on establishing a shared vision, understanding the organizational context, and defining the overall strategy and direction for all products and services. It sets the stage for subsequent activities by ensuring alignment on goals and priorities before detailed design work begins.

To ensure the continual improvement of products and services

Why wrong: This statement accurately describes the purpose of the "Improve" value chain activity, which is a distinct activity within the ITIL service value system. The "Improve" activity focuses on enhancing existing products, services, and practices across all value chain activities, rather than the initial design and deployment of new or changed services. It drives ongoing optimization and value realization.

Service Portfolio

Why wrong: Service portfolio is a management method, not an SVS component.

ITIL Maturity Model

Why wrong: Not a component of SVS.

Organisational culture

Why wrong: Organisational culture is an inherently internal factor, representing the shared values, beliefs, and practices that guide an organization's employees and operations. It is developed and managed within the organization, reflecting its unique identity and influencing internal behaviors rather than originating from external market or societal forces. Therefore, it is not considered an external factor impacting service management.

Internal communication policies

Why wrong: Internal communication policies are established and controlled entirely within an organization to govern how information flows among its employees and departments. These policies dictate the methods, frequency, and content of internal messaging, making them a direct output of organizational governance and management. As such, they are not external influences but rather internal operational frameworks.

Staff training and skills

Why wrong: Staff training and skills represent the capabilities and competencies developed and maintained within an organization's workforce. These are internal resources that the organization invests in and manages to enhance its service delivery capacity and operational efficiency. While external market trends might influence the types of skills needed, the actual development and possession of these skills are internal to the organization.

The ability to process 100 transactions per second

Why wrong: This describes a specific functional capability or performance characteristic of a service, indicating its utility and part of its warranty. While crucial for delivering value, it is an output or a feature of the service, not the ultimate result or benefit experienced by a stakeholder. An outcome would be the business impact enabled by this processing speed, such as faster customer service or reduced operational costs.

A mobile application for employee time tracking

Why wrong: This represents a tangible deliverable or a specific product created by a service provider. It is an output of development or delivery activities, a tool or system that enables certain functions. An outcome, in contrast, would be the result achieved by using this application, such as improved payroll accuracy, increased employee productivity due to streamlined time entry, or reduced administrative burden for HR.

A weekly sales report generated by the system

Why wrong: This is a specific deliverable produced by an information system or service. It is an output—a piece of information or a document that results from processing data. While valuable, the report itself is not the ultimate business result. An outcome would be the action taken or the decision made based on the insights gained from analyzing this report, such as adjusting marketing strategies or identifying new sales opportunities, leading to increased revenue or market share.

Error

Why wrong: While 'error' is a common term for system malfunctions, ITIL 4's event management framework classifies events based on their nature and required response, not simply as 'errors'. An actual error condition would typically be categorized as an 'Exception' event, indicating an abnormal operation requiring intervention, rather than 'Error' being a distinct event type itself within the ITIL lexicon. Therefore, 'Error' is not a standard ITIL event category.

Critical

Why wrong: The term 'critical' describes the severity or impact of an event, rather than being a formal event classification type within ITIL 4. Events indicating a significant deviation from normal operation, a service failure, or a breach of established thresholds are formally categorized as 'Exception' events. While such exceptions are often critical in their implications, 'Critical' itself is not one of the three standard event types (Informational, Warning, Exception) defined by ITIL for event management.

Alert

Why wrong: An 'alert' is not an event type but rather a notification or output generated *in response* to a significant event, typically a Warning or Exception event. Its purpose is to draw attention to a situation that requires human intervention or triggers an automated response. While events are occurrences detected by monitoring tools, alerts are the mechanisms used to communicate the need for action based on those events.

Value co-creation eliminates all costs for the consumer

Why wrong: Value co-creation aims to optimize the utility and warranty of services, potentially leading to a reduction in certain costs for the consumer by better aligning services with their needs. However, it does not eliminate all costs, as consumers still incur expenses related to their own resource contributions, consumption of the service, and any associated operational overhead. The focus is on maximizing value for money, not on achieving a cost-free experience.

The provider defines what value is

Why wrong: The assertion that the provider solely defines value contradicts a fundamental principle of ITIL 4, which states that value is always perceived by the consumer. Value is subjective and context-dependent, emerging from the consumer's experience and their assessment of whether the service helps them achieve their desired outcomes. While providers offer value propositions, the ultimate determination of what constitutes value rests entirely with the consumer's perspective and utility.

Value is delivered by the provider to the consumer

Why wrong: The concept of value co-creation fundamentally shifts away from a traditional model where value is simply delivered as a finished product or service from provider to consumer. Instead, value is not a pre-packaged commodity but rather an outcome that emerges from the joint activities and resource integration of both parties within the service relationship. It emphasizes a shared creation process, rather than a unilateral transfer, making 'delivery' an incomplete description.

The system processes transactions within 2 seconds

Why wrong: This statement describes a performance characteristic, specifically the speed at which the system executes transactions. In ITIL 4, performance metrics such as processing speed, capacity, and response times are key components of warranty. Warranty assures users that the service will meet agreed-upon requirements and perform reliably, rather than defining the core functionality or purpose of the service itself.

The system is available 99.9% of the time

Why wrong: This statement quantifies the service's availability, indicating the percentage of time it is operational and accessible to users. Availability, along with other non-functional requirements like capacity, continuity, and security, constitutes the warranty of a service in ITIL 4. Warranty ensures the service is 'fit for use' by performing as expected and meeting agreed service levels, distinguishing it from the service's inherent functionality.

The system is secure and compliant

Why wrong: This statement addresses non-functional attributes of the system, specifically its adherence to security standards and regulatory compliance. Security and compliance are critical aspects of warranty in ITIL 4, as they assure users that the service is 'fit for use' and will perform reliably and safely without undue risk or breach of regulations. These attributes describe how the service performs, not what core functions it provides.

Contracts and agreements

Why wrong: Contracts and agreements primarily define the relationships and responsibilities between an organization and its external partners or suppliers. These elements are a core component of the "Partners and Suppliers" dimension within the ITIL 4 framework, which focuses on how an organization collaborates with third parties to deliver value. Therefore, they are distinct from the internal structure, capabilities, and human aspects encompassed by the "Organizations and People" dimension.

Data and information

Why wrong: Data and information represent the raw facts and processed knowledge utilized by an organization to support its services and decision-making. These critical assets, along with the knowledge management practices surrounding them, are explicitly categorized under the "Information and Technology" dimension in ITIL 4. This dimension focuses on the information required and the technologies that manage and deliver it, distinguishing it from the human and structural aspects of "Organizations and People."

Tools and technology

Why wrong: Tools and technology encompass the applications, infrastructure, and other technological assets that an organization employs to deliver and support its services. This includes everything from service management software to network hardware. These elements are a key focus of the "Information and Technology" dimension, which addresses the technological resources and capabilities necessary for service provision, rather than the human or organizational aspects.

Better service quality

Why wrong: Neglect in IT service management practices, such as incident management, problem management, or service level management, inherently degrades service quality rather than improving it. Without proactive monitoring, continuous improvement efforts, and diligent resolution of issues, services become less reliable, less available, and fail to meet user expectations. Quality is a direct outcome of deliberate effort and attention, which are absent in a state of neglect.

Improved agility

Why wrong: Organizational agility, the ability to respond quickly and effectively to change, is fundamentally undermined by neglect across IT service management. Neglecting practices like change enablement, deployment management, or even strategic planning prevents an organization from adapting rapidly to new demands or market shifts. Instead of fostering flexibility, neglect creates technical debt, rigid processes, and a reactive posture, severely hindering any potential for improved agility.

Increased innovation

Why wrong: Innovation thrives on dedicated resources, a culture of experimentation, and continuous investment in new ideas and technologies, all of which are absent when an organization is in a state of neglect. Neglecting IT capabilities means a lack of focus on research, development, and the adoption of emerging technologies, stifling any potential for creative solutions or process improvements. Instead of fostering new approaches, neglect leads to stagnation, technical obsolescence, and a diminished capacity for future innovation.

Incident

Why wrong: An incident represents an unplanned interruption to a service or a reduction in the quality of a service, as defined by ITIL 4. It is a reactive event that requires immediate resolution to restore normal service operation as quickly as possible, not a planned modification. Unlike a change, which is a deliberate activity to alter a service, an incident signifies a deviation from expected service delivery.

Problem

Why wrong: A problem, in ITIL 4, is the cause of one or more incidents, even if the causes are not yet known. Problem management focuses on identifying the root cause of incidents to prevent their recurrence, rather than being a change itself. While the resolution of a problem often leads to a change (e.g., a fix or improvement), the problem itself is a state of underlying cause, not the modification activity.

Service request

Why wrong: A service request is a formal request from a user for something standard, such as information, advice, a pre-defined service component, or access to a service. While some service requests might trigger a standard change (e.g., requesting a new laptop), the service request itself is the user's interaction point and demand for a service, not the underlying change activity. It represents a user's need for provisioned resources or information, distinct from a planned modification to the IT infrastructure.

Measure and improve

Why wrong: Not a guiding principle; it is a common activity but not a principle.

Manage and govern

Why wrong: Not a guiding principle; it is a generic management concept.

Plan and implement

Why wrong: Not a guiding principle; it sounds like a generic process step.

Mean Time Between Failures (MTBF)

Why wrong: MTBF is used in Availability Management.

Recovery Time Objective (RTO)

Why wrong: RTO is used in ITSCM.

Mean Time to Restore Service (MTTR)

Why wrong: MTTR is a metric for Incident Management.