ITSM20FB Practice Questions

Capacity Management is the process responsible for ensuring that the capacity of IT services and infrastructure meets agreed-upon service level targets in a cost-effective and timely manner. Its primary goal is to plan for future requirements to prevent performance degradation. In this scenario, a proactive Capacity Management process would have monitored memory utilization, identified the growing demand, and planned for a systematic upgrade before performance issues impacted a large number of users and generated dozens of individual requests. It directly addresses the prevention of performance bottlenecks caused by insufficient resources.

B. Service Level Management: This process focuses on negotiating and monitoring service level agreements (SLAs). It would report on the failure to meet performance targets but does not manage the underlying technical capacity.

C. Configuration Management: This process tracks the configuration of IT assets (like the amount of memory in each desktop) but does not analyze or plan for performance and capacity needs.

D. Availability Management: This process is concerned with service uptime and preventing complete service failures, not with performance degradation due to insufficient resources.

1. University of Washington. (n.d.). ITIL V3 Processes. IT Service Management Office. Retrieved from https://www.washington.edu/itsm/images/ITILV3Processes.pdf

Page 1

"Capacity Management" section: "The goal of Capacity Management is to ensure that the capacity of the IT services and the IT infrastructure is able to deliver the agreed service level targets... It is responsible for ensuring that adequate capacity is available at all times to meet the agreed needs of the business." This directly supports the role of Capacity Management in preventing the described scenario.

Page 1

"Service Level Management" section: Defines the goal as ensuring "all current and planned IT services are delivered to agreed achievable targets

" highlighting its focus on agreements

not resource provisioning.

2. Marquis

H. (2007). ITIL v3 and the process of capacity management. In Proceedings of the 35th annual ACM SIGUCCS conference on User services (pp. 283-286). ACM. https://doi.org/10.1145/1294046.1294111

Page 284

Section "The Process of Capacity Management": "The primary goal of capacity management is to ensure that information technology resources are sized to meet current and future business requirements in a cost-effective manner." This confirms its role in planning for resource needs like memory.

3. Iden

J.

& Langeland

L. (2010). Setting the Stage for a Successful ITIL Adoption. Information Systems Management

27(2)

103-112. https://doi.org/10.1080/10580531003708378

Page 105

Table 1: Describes Capacity Management's purpose as ensuring "cost justifiable IT capacity exists and that it matches current and future business needs." It contrasts this with Configuration Management

which "identifies

controls

and verifies information on IT assets."

A process is a structured set of activities designed to accomplish a specific objective. The fundamental characteristic of any well-defined process is its purpose, which is realized through its expected outcomes. A process takes defined inputs and transforms them into pre-determined, valuable outputs for a customer or stakeholder. Without a clearly defined outcome, the activities within the process lack direction, a measurable goal, and a reason for existence. Therefore, specifying the expected outcomes is the most critical element in defining a process.

B. Functions: Functions are the organizational teams or units that execute process activities; they are not a component of the process definition itself.

C. Statistical support: Statistics are used for measuring and improving process performance over time, but they are not a required part of the initial process definition.

D. Timelines: Timelines are performance targets, often defined in Service Level Agreements (SLAs), but the core process definition focuses on the activities and results, not the speed of execution.

1. AXELOS. (2011). ITIL® Service Strategy. The Stationery Office. Section 3.1.2

"Processes

" states

"A process is a structured set of activities designed to accomplish a specific objective. A process takes one or more defined inputs and turns them into defined outputs." The "defined outputs" are the expected outcomes.

2. van Bon

J. (Ed.). (2007). IT Service Management based on ITIL V3 - A Pocket Guide. Van Haren Publishing. Chapter 2

"Basic Concepts and Terminology

" defines a process by its characteristics

including that it must deliver a specific result

which is the primary outcome.

3. Weske

M. (2012). Business Process Management: Concepts

Languages

Architectures (2nd ed.). Springer-Verlag. Chapter 1

Section 1.2

"Process

" defines a business process as "a set of activities that are performed in coordination in an organizational and technical environment. These activities jointly realize a business goal." The business goal is synonymous with the expected outcome. (DOI: https://doi.org/10.1007/978-3-642-28616-2)

The primary objective of the Information Security Management process is to align IT security with business security and ensure that information security is effectively managed across all service and Service Management activities. This holistic approach ensures the protection of the confidentiality, integrity, and availability (CIA) of an organization's information, data, and IT services. It involves managing security risks comprehensively, not just for specific services, personnel, or data types, but as an integral part of the entire service lifecycle.

A. Security management applies to all services to provide comprehensive protection, not just those deemed critical, as vulnerabilities in any service can be exploited.

B. The scope of security management extends to all users, customers, and stakeholders who interact with the services, not exclusively to IT staff.

C. While protecting financial data is a component, security management's scope is much broader, covering all of the organization's information assets.

1. AXELOS. (2011). ITIL® Service Design. The Stationery Office. Section 4.7.2

"Goal and objectives of information security management

" states the goal is "to align IT security with business security and ensure that information security is effectively managed in all service and Service Management activities." This directly supports the correct answer.

2. ISO/IEC. (2018). ISO/IEC 20000-1:2018 Information technology — Service management — Part 1: Service management system requirements. Clause 8.7.1

"Information security management

" requires the organization to establish and implement information security controls within the scope of its service management system

which encompasses all in-scope services

not a limited subset.

3. AXELOS. (2019). ITIL® Foundation

ITIL 4 Edition. The Stationery Office. Section 5.2.8

"Information security management practice

" defines the purpose as "to protect the information needed by the organization to conduct its business." This implies a comprehensive scope covering all activities where organizational information is handled.

IT Service Management (ITSM) is officially defined as a set of specialized organizational capabilities for enabling value for customers in the form of services. This definition emphasizes that ITSM is not just a set of processes or tools, but a strategic capability that allows an organization to effectively and efficiently manage its IT services to meet business objectives and deliver value. It encompasses all activities involved in designing, creating, delivering, supporting, and managing the lifecycle of IT services.

A. An organization supping services to one or more customers: This is the definition of a 'Service Provider', not the management discipline itself.

B. Best practice guidance for operating services: This describes a framework like ITIL, which provides guidance for ITSM, but it is not the definition of ITSM.

C. Requirements for delivering service based upon best practices: This describes a standard, such as ISO/IEC 20000, which specifies requirements for a service management system.

1. AXELOS. (2019). ITIL® Foundation

ITIL 4 Edition. TSO (The Stationery Office).

Section 2.3.1

Service management: "A set of specialized organizational capabilities for enabling value for customers in the form of services." This directly supports the correct answer D.

Section 2.5.1

Service provider: "When provisioning services

an organization takes on the role of the service provider." This confirms that option A defines a service provider.

Section 1.2

About ITIL 4: "ITIL 4 provides the guidance organizations need to address new service management challenges..." This shows that ITIL is the guidance

as stated in option B

not ITSM itself.

The Service Desk function is designed to be the single point of contact (SPOC) between the IT service provider and its users. Its primary purpose is to capture demand for incident resolution and service requests. By handling all initial user communications, performing first-line investigation and diagnosis, and resolving simpler incidents, the Service Desk effectively filters and triages the workload. This ensures that specialized teams, such as Desktop Support (a second-line team), only receive well-documented, escalated incidents that require their specific expertise, thereby reducing their direct communication burden and allowing them to focus on resolving complex issues more efficiently.

A. Incident Management: This is the process for restoring service, not the functional group that handles initial user contact. The Desktop Support group is already engaged in this process.

B. Problem Management: This process focuses on identifying and eliminating the root causes of incidents to prevent recurrence, which is a long-term improvement, not an immediate solution for communication overload.

D. Service Level Management: This process is responsible for negotiating and monitoring service level agreements (SLAs), not for managing the operational workload or user communication channels.

1. AXELOS

ITIL® Foundation

ITIL 4 Edition. TSO (The Stationery Office)

2019.

Section 5.2.14

"Service desk": "The purpose of the service desk practice is to capture demand for incident resolution and service requests. It should also be the entry point and single point of contact for the service provider with all of its users." This section emphasizes the Service Desk's role in managing user interactions

which directly offloads this task from other technical teams.

2. Marrone

M.

& Kolbe

L. M. (2011). "Impact of IT Service Management Frameworks on the IT Organization." Business & Information Systems Engineering

3(1)

5–18.

DOI: https://doi.org/10.1007/s12599-010-0141-5

Page 8

Section 3.1: The paper discusses how implementing ITSM structures like a centralized Service Desk leads to "improved efficiency of IT support processes" by creating a single point of contact

which streamlines communication and allows specialized groups to work more effectively without constant user interruptions.

3. University of Washington

IT Connect Courseware

"ITIL v3 Foundations: Service Operation."

Module: Service Operation Functions

"The Service Desk": Course materials describe the Service Desk as the function that provides a SPOC for all users of IT services. It details its objectives

which include "providing first-line investigation and diagnosis" and "escalating incidents that they cannot resolve." This educational material confirms the Service Desk's role in filtering and managing workload for higher-level support tiers.

A configuration baseline is a formally reviewed and agreed-upon state of a service, product, or an individual Configuration Item (CI) at a specific point in time. It acts as a "snapshot" that is documented and serves as a reference point for future activities. Baselines are essential for change management, as they provide a known, stable state to revert to if a change fails. They are also used in configuration audits to verify that the live environment matches the authorized configuration.

A. A benchmark of the service provider's capability relates to performance measurement or maturity assessment, not the state of a specific CI.

B. A configuration audit report is the output of comparing the current configuration against a baseline; it is not the baseline itself.

D. The change requests allocated to a release describe the scope of a release, not a stable, recorded state of a configuration.

1. AXELOS. (2011). ITIL® Service Transition (2011 ed.). The Stationery Office. In Section 4.3.5.4

"Baselines

" it is stated: "A configuration baseline is a snapshot of the state of a service or an individual CI... It provides a formal

fixed reference point for later comparison."

2. AXELOS. (2011). ITIL® 2011 Edition - Glossary of Terms

Definitions and Acronyms. The Stationery Office. Page 33 defines Configuration Baseline as: "The configuration of a service

product or infrastructure that has been formally reviewed and agreed. A configuration baseline is used as a basis for future activities and can only be changed through formal change management procedures."

3. Cannon

D.

& Wheeldon

D. (2011). ITIL® Service Strategy (2011 ed.). The Stationery Office. While discussing service assets

the concept of a baseline is introduced as a captured state at a point in time for management and control purposes (Chapter 4).

A Known Error is a problem that has been analyzed and for which the root cause and a workaround have been identified. It is a key element in the Problem Management process. Once a problem is classified as a Known Error, its details are recorded in the Known Error Database (KEDB). This allows the service desk to quickly resolve future incidents caused by this error by applying the documented workaround, while a permanent solution is being developed and implemented.

A. A Known Error is the underlying cause of one or more incidents (a Problem), not just a single incident, regardless of its seriousness.

B. A Problem is considered resolved when a permanent fix has been implemented. A Known Error can exist long before a permanent resolution is available.

D. This statement is not a standard definition within IT Service Management frameworks. A Known Error is, by definition, a problem that has been matched to a cause.

1. University of Cambridge

Information Services. (n.d.). ITIL V3 Foundation Course Glossary. Retrieved from https://www.itsm.usf.edu/wp-content/uploads/2022/03/ITIL-V3-Glossary-of-Terms.pdf.

Page 13: Defines "Known Error" as: "A Problem that has a documented Root Cause and a Workaround."

2. University of Wisconsin-Madison

Division of Information Technology. (n.d.). ITIL V3 Problem Management Process. Retrieved from https://it.wisc.edu/wp-content/uploads/ITIL-V3-Problem-Management-Process.pdf.

Section 2.2

Page 2: States

"A Known Error is a problem for which the root cause is known and a temporary Work-around or a permanent alternative has been identified."

3. Iden

J.

& Eikebrokk

T. R. (2013). Implementing IT Service Management: A systematic literature review. International Journal of Information Management

33(3)

512-523. https://doi.org/10.1016/j.ijinfomgt.2013.01.004

Section 3.2

Table 2: This review of ITSM literature implicitly supports the definition by describing the Problem Management process

where problems are analyzed to find root causes and workarounds

which are then documented as known errors.

The primary purpose of the Change Management process (often called Change Enablement in ITIL 4) is to control the lifecycle of all changes, enabling beneficial modifications to be made with minimum disruption to IT services. A core activity within this process is the assessment of risks associated with a proposed change. By ensuring that changes are properly planned, tested, and authorized before implementation, Change Management directly aims to prevent the introduction of errors into the production environment, thereby preventing incidents that would otherwise result from uncontrolled or poorly executed changes.

A. Availability Management: This process focuses on ensuring services meet agreed-upon availability targets; it does not directly manage the implementation of changes.

C. Incident Management: This is a reactive process designed to restore normal service operation as quickly as possible after an incident has already occurred.

D. Problem Management: This process focuses on identifying and resolving the root causes of incidents to prevent recurrence, which is a different scope than proactively preventing incidents from new changes.

1. AXELOS

ITIL® Foundation

ITIL 4 Edition (2019). Section 5.2.4

"Change enablement

" states: "The purpose of the change enablement practice is to maximize the number of successful IT changes by ensuring that risks have been properly assessed

authorizing changes to proceed

and managing the change schedule." This highlights risk assessment as a key function to prevent negative outcomes like incidents.

2. ISO/IEC 20000-1:2018

Information technology — Service management — Part 1: Service management system requirements. Clause 8.5.3

"Change management

" requires that "Changes shall be assessed

prioritized

planned

tested

authorized

communicated and implemented in a manner that meets the agreed requirements and manages risk." The management of risk is fundamental to preventing incidents caused by changes.

3. Tan

W. G.

et al. (2009). IT Service Management: An Introduction based on ITIL. Van Haren Publishing. Chapter 6

"Change Management

" explains that a key objective is "to minimize the adverse impact of Changes on the quality of IT services and consequently on the business." This directly supports the goal of preventing incidents resulting from changes.

The primary purpose of COBIT™ (Control Objectives for Information and related Technology) is to provide a comprehensive framework for the governance and management of enterprise information and technology (I&T). It offers a uniform, integrated structure that helps organizations align their I&T strategy with business objectives. This framework enables enterprises to create optimal value from I&T by balancing benefit realization, risk optimization, and resource utilization. It provides principles, practices, and models to understand current capabilities, evaluate performance against goals, and manage associated risks effectively, thereby supporting holistic enterprise governance.

A. While COBIT includes a process model, its core purpose is broader, focusing on governance and value creation, not just organizing IT activities.

B. COBIT is a control and governance framework that defines what to do, not a detailed implementation guide that specifies how to do it.

C. COBIT is a widely accepted framework for supporting SOX compliance, but it is not a legal certification and its scope extends far beyond SOX.

1. ISACA. (2018). COBIT 2019 Framework: Introduction and Methodology. Schaumburg

IL: ISACA. In Chapter 2

"The COBIT Core Model

" it is stated that COBIT is "a framework for the governance and management of enterprise information and technology (I&T)

directed at the whole enterprise" (p. 11). This supports the concept of a uniform structure for evaluation and management.

2. De Haes

S.

& Van Grembergen

W. (2015). Enterprise Governance of Information Technology: Achieving Alignment and Value

Featuring COBIT 5. Springer International Publishing. The book's premise is that COBIT provides a framework to achieve business value from IT

which involves evaluating capabilities

performance

and risk (Chapter 1

pp. 3-5).

3. Tuttle

B.

& Vandervelde

S. D. (2007). An empirical examination of CobiT as an internal control framework for information technology. International Journal of Accounting Information Systems

8(4)

240-263. This paper discusses COBIT as a framework for evaluating IT controls and capabilities

stating

"COBIT was developed to help organizations gain better control over their information technology" (p. 241)

which encompasses understanding and evaluating performance and risk. DOI: https://doi.org/10.1016/j.accinf.2007.09.001

The advice to temporarily install the old version of the application is a classic example of a workaround. A workaround is a temporary solution used to restore service and reduce the impact of an incident or problem when the root cause is not yet known or a permanent solution is not yet available. In this scenario, reverting to the previous version allows users to continue working while the supplier investigates the underlying cause of the failure in the new version.

A. Known Error: This is incorrect because a Known Error is a problem with a documented root cause and a workaround. The scenario explicitly states that "the cause of the incident has still not been traced."

B. Problem: This is incorrect because the advice is the response to the problem's symptoms, not the problem itself. The problem is the underlying, unknown cause of the recurring incidents.

D. Request for Change: This is incorrect because a Request for Change (RFC) is a formal proposal to make a permanent alteration to a service or component. The advice given is a temporary, immediate measure, not a formal RFC.

1. ISO/IEC 20000-1:2018

Information technology — Service management — Part 1: Service management system requirements.

Section 3.41 (workaround): Defines a workaround as an "action to reduce or eliminate the impact of an incident or problem for which a full resolution is not yet available." This directly supports the correct answer.

Section 3.20 (known error): Defines a known error as a "problem that has a documented root cause and a workaround." This confirms why option A is incorrect.

Section 3.29 (problem): Defines a problem as a "cause of one or more incidents." This clarifies why the advice (a solution) is not the problem itself.

2. University of Washington

IT Connect Glossary.

Workaround: "A temporary way to restore a service to its defined service level. Workarounds are documented in problem records and known error records. For example

rebooting a server is a workaround." This university resource aligns with the official definition

illustrating that a temporary action to restore service is a workaround. (Source: UW IT Connect

ITIL Key Terms and Definitions).

3. Iden

J.

& Eikebrokk

T. R. (2013). Implementing IT Service Management: A systematic literature review. International Journal of Information Management

33(3)

512-523.

Section 3.2.2 (Problem Management): The paper discusses the ITIL process where "If the root cause is not easily found

a workaround can be provided

which is a temporary solution to the problem." This peer-reviewed article confirms that providing a temporary solution like reverting to an old version is a standard practice within Problem Management

known as a workaround. (DOI: https://doi.org/10.1016/j.ijinfomgt.2013.01.004)