ITIL-V4-FOUNDATION Practice Questions

The ITIL service value system (SVS) describes how all the components and activities of an organization work together as a system to enable value co-creation. The five core components of the ITIL SVS are the ITIL service value chain, the ITIL practices, the ITIL guiding principles, governance, and continual improvement. The four dimensions of service management (organizations and people; information and technology; partners and suppliers; value streams and processes) are a separate, though related, key concept. They represent perspectives that are relevant to the whole SVS, including the service value chain and all ITIL practices, ensuring a holistic approach is taken. They are not, however, a component of the SVS itself.

A. The guiding principles are a core component of the SVS. They provide recommendations that can guide an organization in all circumstances, regardless of changes in its goals, strategies, or structure.

B. Governance is a core component of the SVS. It is the means by which an organization is directed and controlled, and it is realized through activities that evaluate, direct, and monitor.

C. Practices are a core component of the SVS. They are sets of organizational resources designed for performing work or accomplishing an objective, supporting the activities of the service value chain.

1. AXELOS. (2019). ITIL® Foundation: ITIL 4 Edition. TSO (The Stationery Office).

Section 4.1

"Service value system overview

" Figure 4.1 explicitly illustrates the five components of the SVS: guiding principles

governance

service value chain

practices

and continual improvement.

Section 4.1

Paragraph 1 states

"The ITIL SVS includes the following components: ITIL service value chain

ITIL practices

ITIL guiding principles

governance

continual improvement."

Chapter 3

"The four dimensions of service management

" introduces the four dimensions as a separate model

not as a component of the SVS. It states they are "critical to the effective and efficient facilitation of value for customers and other stakeholders" and apply to the SVS in general.

The ‘watermelon SLA’ effect describes a situation where service level agreement (SLA) reports show that all operational targets are being met (appearing ‘green’ on the outside), yet the customer is dissatisfied with the service (feeling ‘red’ on the inside). This disconnect occurs when the metrics used in the SLA are focused on internal, technical, or operational measures (e.g., server availability) rather than on the business outcomes and user experience that the customer truly values. The service provider may believe they are succeeding, while the customer's perception is one of failure.

A. This describes a poorly structured SLA for multiple customers, not the specific disconnect between reported performance and customer satisfaction.

C. This refers to a problem of inconsistent measurement and lack of trend analysis, which is a different issue from the 'watermelon SLA' effect.

D. This describes the ideal, positive outcome of a well-designed SLA, which is the opposite of the negative 'watermelon SLA' effect.

1. AXELOS. (2019). ITIL® Foundation: ITIL 4 Edition. TSO (The Stationery Office).

Section 5.2.15

Service level management practice: "This is sometimes called the ‘watermelon SLA’ effect; the SLA is all ‘green’ on the outside

but when you look more closely

it is ‘red’ on the inside

showing dissatisfaction from the customer’s perspective. This happens when the focus of the SLAs and reports is on operational metrics

and the real experience of the customers and users is not sufficiently taken into account."

The official ITIL 4 Foundation guidance defines service management as "a set of specialized organizational capabilities for enabling value for customers in the form of services." These capabilities are the resources, processes, and skills an organization uses to manage and deliver services. The core purpose is to ensure that the services provided help customers achieve their desired outcomes, thereby co-creating value. This definition emphasizes the provider's role in developing the necessary competencies to deliver services effectively.

A. This is the definition of an outcome, which is a result for a stakeholder, not the management discipline itself.

B. This is the definition of a service offering, which describes the services available to a specific consumer group.

C. This describes a service relationship, which involves the joint activities between a provider and consumer to co-create value.

1. AXELOS. (2019). ITIL® Foundation

ITIL 4 Edition. TSO (The Stationery Office).

Correct Answer (D): Section 2.1.1

"Service management is defined as a set of specialized organizational capabilities for enabling value for customers in the form of services." (p. 8)

Incorrect Option (A): Section 2.3.1

"An outcome is a result for a stakeholder enabled by one or more outputs." (p. 15)

Incorrect Option (B): Section 2.3.3

"A service offering is a formal description of one or more services

designed to address the needs of a target consumer group." (p. 17)

Incorrect Option (C): Section 2.4

"A service relationship is a cooperation between a service provider and service consumer. Service relationships include service provision

service consumption

and service relationship management." (p. 18) Option C describes the activities within this relationship.

The 'Information and technology' dimension of service management focuses on the information and knowledge used to deliver services, and the technologies required to manage them. A critical aspect of managing information assets is ensuring their protection. This dimension explicitly addresses the challenges of information management, which include considerations for security, privacy, and regulatory compliance. It covers the technologies and information architecture that are fundamental to implementing and maintaining data security controls.

A. Organizations and people: This dimension focuses on culture, roles, and organizational structures, not the technical and informational aspects of data security.

C. Partners and suppliers: This dimension deals with managing relationships with external vendors, which may include security agreements, but it is not the core dimension for data security itself.

D. Value streams and processes: This dimension defines the workflows and activities for service delivery; while security can be a process, the underlying concern for data itself resides in another dimension.

1. AXELOS. (2019). ITIL® Foundation

ITIL 4 edition. TSO (The Stationery Office).

Section 3.2.2

Information and technology: "The challenges of information management

such as those related to security and regulatory compliance

are also a focus of this dimension." This statement directly links security and compliance to the Information and technology dimension.

The ITIL continual improvement model provides a structured approach for implementing improvements. It outlines a high-level, iterative methodology with a series of defined steps to guide improvement initiatives at all levels of an organization. The steps include: 'What is the vision?', 'Where are we now?', 'Where do we want to be?', 'How do we get there?', 'Take action', 'Did we get there?', and 'How do we keep the momentum going?'. This model ensures that improvement efforts are linked to the organization's goals and are managed in a consistent and effective manner.

A. The ‘improve’ value chain activity is a component of the service value chain that facilitates improvement, not the step-by-step model itself.

B. The ‘continual improvement register’ is a tool used to track and manage improvement ideas, not a methodology with defined steps for implementation.

D. The ‘engage’ value chain activity focuses on understanding stakeholder needs and fostering relationships, not on the process of implementing improvements.

1. AXELOS. (2019). ITIL® Foundation

ITIL 4 Edition. TSO (The Stationery Office).

Correct Answer (C): Section 5.1

"The ITIL continual improvement model

" describes the model and its steps for guiding improvement initiatives.

Incorrect Option (A): Section 4.5.1.6

"Improve

" defines this as one of the six value chain activities.

Incorrect Option (B): Section 5.2.1

"Continual improvement

" mentions the continual improvement register (CIR) as a tool for logging ideas.

Incorrect Option (D): Section 4.5.1.1

"Engage

" defines this value chain activity's purpose as understanding stakeholder needs.

The purpose of the service configuration management practice is to manage information about Configuration Items (CIs). A CI is any component that needs to be managed to deliver an IT service. The practice ensures that accurate and reliable information about the configuration of services and the CIs that support them is available when and where it is needed. This information includes details about the CIs, their attributes, and their relationships with other CIs, which are recorded in a configuration management system (CMS).

A. suppliers: Suppliers are organizations that provide goods and services; they are not the configurable components that deliver a service.

B. assets: While all CIs are assets, not all assets are CIs. 'CIs' is the specific term for components managed by this practice.

C. customers: Customers are the consumers of services, not the underlying components that are managed to provide those services.

1. AXELOS. (2019). ITIL® Foundation: ITIL 4 Edition. TSO (The Stationery Office).

Section 5.2.8

"Service configuration management": The purpose is explicitly stated as: "to ensure that accurate and reliable information about the configuration of services

and the CIs that support them

is available when and where it is needed." (p. 113).

Section 5.2.8.1

"Configuration items": Defines a CI as "any component that needs to be managed in order to deliver an IT service." (p. 113).

A value stream is a specific combination of activities and practices designed for a particular scenario. It maps the path from a specific demand or opportunity (the trigger) to the co-creation of value for a consumer. Organizations define different value streams for different types of work, such as resolving a major incident, fulfilling a service request, or onboarding a new customer. This ensures that the steps taken are optimized and relevant for that specific context, aligning with the ITIL guiding principle of 'focus on value'.

A. A value stream is a combination of value chain activities, but it is not required to use all six for every scenario.

C. A value stream only incorporates the specific ITIL practices that are relevant and necessary to support the activities within that stream.

D. While many value streams involve suppliers, it is not a mandatory requirement; a value stream can be entirely internal.

1. AXELOS. (2019). ITIL® Foundation

ITIL 4 edition. TSO (The Stationery Office).

Section 4.5

The ITIL service value chain: This section explains that a value stream is a "series of steps an organization undertakes to create and deliver products and services to consumers." It emphasizes that these are specific combinations of activities.

Section 4.5.1

Value streams for service management: This section explicitly states

"To carry out a certain task

or to respond to a particular situation

organizations create value streams." This directly supports that value streams are designed for specific scenarios (Option B). The examples provided (e.g.

resolving an incident vs. creating a new service) illustrate different value streams that use different combinations of value chain activities

refuting Option A.

Section 5

ITIL management practices: This chapter details the 34 practices

describing them as resources to support value chain activities. There is no text suggesting all practices must be used in every value stream

which would contradict the guiding principles (refuting Option C).

The standard software development lifecycle (SDLC), which is a foundational concept for ITIL's software development and management practice, follows a logical progression. The process begins with an idea (Ideation), moves to planning (Design), then creation (Develop). Following development, the product is rigorously checked (Test) to ensure it meets requirements before being released to users (Deploy). It is then used and maintained (Operate) until it is no longer needed (Retire).

The correct sequence is: Ideation -> Design -> Develop -> Test -> Deploy -> Operate -> Retire.

None of the provided options (A, B, D) match this correct sequence. Specifically, option A incorrectly places deployment before testing. Therefore, 'None of the above' is the correct answer.

A. This option incorrectly places 'Deploy' before 'Test'. Software must be validated through testing before it is deployed to a live environment for operational use.

B. This option incorrectly begins the lifecycle with 'Retire'. Retirement is the final phase when a service or product is decommissioned.

D. This option presents an illogical sequence. For instance, it places 'Test' before 'Develop' and 'Design' after 'Deploy', which violates the fundamental process flow.

1. AXELOS. (2019). ITIL® Foundation: ITIL 4 Edition. TSO (The Stationery Office).

Section 5.2.4

Design and transition: This section describes the value chain activity that ensures products and services meet expectations. It explicitly lists key activities in the logical order of "...development

testing

and deployment of new and changed components..." This official text confirms that testing precedes deployment

invalidating option A.

2. Purdue University

College of Engineering. (n.d.). Systems Development Life Cycle.

This university courseware outlines the standard phases of the SDLC as: 1. Planning (includes ideation)

2. Systems Analysis and Requirements

3. Systems Design

4. Development

5. Integration and Testing

6. Implementation (Deployment)

7. Operations and Maintenance. This academic source confirms the standard Develop -> Test -> Deploy sequence.

A security breach is a type of security incident, often involving unauthorized access to services or data. The 'Information security management' practice is responsible for preventing and managing such incidents. A key component of this practice is 'access management,' which ensures that users are granted the right to use a service, but access is denied to unauthorized users. When a potential breach is detected, it is logged as a security incident. The 'Incident management' and 'Information security management' practices then work together to investigate and resolve it, with access management providing the policies and logs to identify the nature of the breach.

A. Change management: This practice (now 'change enablement' in ITIL 4) manages the lifecycle of changes to services, not the real-time detection and logging of security incidents.

B. Service level management: This practice focuses on setting, monitoring, and achieving agreed-upon service levels with customers, not on the operational task of detecting security breaches.

D. Continual service improvement: This practice (now 'continual improvement') aims to align services with changing business needs by identifying and implementing improvements, rather than managing active security incidents.

1. AXELOS

"ITIL® Foundation

ITIL 4 Edition" (2019):

Section 5.2.8

Information security management: "The purpose of the information security management practice is to protect the information needed by the organization to conduct its business. This includes understanding and managing risks to the confidentiality

integrity

and availability of information

as well as other aspects of information security such as authentication (ensuring someone is who they claim to be) and non-repudiation (ensuring someone can’t deny that they took an action)." This section establishes the practice's role in security

which includes managing access and responding to security incidents.

Section 5.2.5

Incident management: "The purpose of the incident management practice is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible." It further clarifies that security-related incidents require special handling and are often escalated to a specialist team

which would be governed by the information security management practice. The interaction between these two practices is crucial for handling breaches.

Budgeting is the activity of predicting and controlling an organization's income and expenditure. It involves creating a financial plan (the budget) for a specific period, which helps in allocating resources and managing costs effectively. This process is crucial for financial visibility and ensuring that the organization's spending is aligned with its strategic objectives. Budgeting is a forward-looking activity focused on planning and control, which directly matches the description in the question.

A. Charging: This is the activity of assigning a price for services consumed by customers. It is a component of income generation, not the overall prediction and control of all finances.

B. Governance: This is the high-level framework for directing and controlling an organization. While it includes financial oversight, it is a much broader concept than just managing income and expenditure.

D. Accounting: This is the practice of recording, summarizing, and reporting on past financial transactions. It provides the data for budgeting but is primarily historical, not predictive.

AXELOS. (2019). ITIL® Foundation

ITIL 4 edition. TSO (The Stationery Office).

Glossary

page 181: Defines Budgeting as "The activity of predicting and controlling the spending of money."

Glossary

page 181: Defines Charging as "The activity that assigns a price for services."

Glossary

page 185: Defines Governance as "The means by which an organization is directed and controlled."

Section 5.2.1

Service financial management: This practice

which includes budgeting

accounting

and charging

is described as supporting "the organization's strategies and plans for service management by ensuring that the organization's financial resources and investments are being used effectively." This context places budgeting as the key planning and control activity.