CCNA ITIL Management Practices Questions

Service requests are predefined, pre-approved, low-risk, and typically involve standard procedures. Incidents are unplanned, and service requests are separate from changes.

The first step is to log the disruption as an incident to initiate restoration of service, even if the cause is suspected to be a change.

In the ITIL 4 Service Value System (SVS), the Governance component is specifically responsible for defining the direction, policies, and control mechanisms that ensure the organization's activities align with its objectives. It provides the overarching framework for decision-making and accountability, guiding how all other SVS components operate. Without governance, the SVS would lack the necessary oversight to ensure value co-creation is achieved in a controlled and compliant manner.

Emergency changes are for urgent situations where delays would cause significant business impact, and they follow an expedited process. Normal changes follow standard assessment and approval.

Service Desk is correct because ITIL 4 defines it as a key service management practice that provides a single point of contact between the service provider and users for managing incidents, service requests, and communication. It is explicitly listed in the ITIL 4 service management practices, focusing on operational support and user interaction.

Problem Identification is a core phase of Problem Management because it involves detecting and logging problems before they are analyzed. In ITIL 4, Problem Management consists of three phases: Problem Identification, Problem Control, and Error Control. Problem Identification ensures that problems are formally recognized, often through trend analysis of incidents or proactive monitoring, so that root causes can be addressed.

In ITIL 4, Monitoring and Event Management defines three types of events: Informational, Warning, and Exception. Option D (Informational) is correct because informational events indicate normal, expected operations (e.g., a scheduled backup completed successfully) and do not require any action beyond logging.

Service requests are pre-approved and typically follow a standard fulfillment process, while incidents are unplanned disruptions.

First-contact resolution is a key performance indicator for the service desk, reflecting its ability to resolve issues on the first interaction.

The Service Value System includes the Guiding Principles, Governance, Service Value Chain, Practices, and Continual Improvement.

Problem Management will investigate the root cause and identify a permanent fix; Incident Management focuses on restoration.

First Contact Resolution (FCR) is a key service desk metric.

Problem Control is the phase where root cause analysis is performed and the root cause is identified. Problem Identification is the first phase (detecting problems), and Error Control is the phase where known errors are managed and workarounds are created.

In ITIL 4, Monitoring and Event Management defines three types of events: Informational, Warning, and Exception. A Warning event (Option B) indicates a condition that may require attention before it becomes critical, such as a disk usage threshold being exceeded. An Informational event (Option C) is a routine notification that does not require action, like a successful backup completion.

The first step is to log the incident, as this captures the disruption and initiates the process to restore service.

ITIL 4 describes three phases: problem identification, problem control (root cause analysis), and error control (known errors).

Password resets are pre-approved, routine requests, typical of Service Request Management.

The first priority is to restore service as quickly as possible, which is the purpose of Incident Management. Option B is correct. Option A is a Problem Management activity; Option C is Change Enablement; Option D is Service Level Management.

Service Desk, Incident Management, and Problem Management are ITIL 4 management practices. Project Management and Financial Management are not part of the ITIL 4 practices list.

CSAT (Customer Satisfaction) directly measures user satisfaction with service desk interactions.

IT Asset Management (ITAM) manages the lifecycle of IT assets from acquisition to disposal.

Service Catalog Management is the correct practice because it provides the single source of consistent information on all agreed services, ensuring that every service is described with its functional and operational characteristics in a standardized format. This practice defines the service catalog structure, which includes service descriptions, service level agreements, and operational details, enabling consistent documentation across the IT organization.

Service Desk practice is responsible for FCR and other service desk metrics.

Standard changes are pre-approved and follow a predefined procedure because they are low-risk, routine, and well-understood. ITIL 4 defines a standard change as one that is implemented through a documented, repeatable process, such as applying a security patch or provisioning a new user account, without requiring additional authorization each time.

This is a service request because it is a pre-defined, pre-approved request for a new laptop (fulfillment of a standard change). It is not an incident because the laptop is still functional, just slow.

Option A is correct because a service request is defined as a standardized, pre-defined request from a user for something that is already approved as part of normal service delivery. ITIL 4 states that service requests are typically low-risk, frequently recurring, and do not require additional authorization because they are pre-approved by the service provider. This allows for efficient fulfillment without the need for a formal change approval process.

Normal changes require assessment and authorization by the CAB, unlike standard (pre-approved) or emergency (urgent) changes.

Problem Management is the ITIL practice specifically designed to analyze recurring incidents by performing root cause analysis (RCA) and identifying underlying causes. By using techniques such as trend analysis, Kepner-Tregoe, or 5 Whys, Problem Management proactively reduces incident volume and resolution time, directly addressing the company's goal.

This is a service request because it is a pre-defined, pre-approved request for a standard item (replacement laptop for a broken one).

Availability Management ensures that services are available as agreed, managing planned and unplanned downtime.

Incident Management aims to restore normal service operation as quickly as possible and minimize adverse impact on business operations.

The primary goal of a 'shift-left' strategy in ITIL 4 is to resolve more incidents and service requests at the first point of contact (tier 0 or tier 1) without escalating to higher support levels. This reduces mean time to resolution (MTTR), lowers operational costs, and improves user satisfaction by minimizing handoffs. While automation and empathy can support shift-left, they are enablers, not the core objective.

A standard change is a pre-approved, low-risk change that follows a defined procedure, such as a password reset or server patch cycle. The ITIL 4 framework defines it as a change that does not require individual assessment or authorization by the Change Authority because its risk is well-understood and the implementation steps are documented in a standard operating procedure (SOP). This matches the description in the question exactly.

Problem control involves root cause analysis and resolution.

Service requests are for pre-defined, pre-approved services (standard changes or information requests), while incidents are unplanned interruptions or reductions in service quality.

The ITIL continual improvement model defines a sequence of steps: '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?'. After defining the vision (step 1), the next step is to assess the current state (step 2) to establish a baseline before setting measurable targets or creating an improvement plan.

The service desk is the single point of contact for users to report incidents, submit service requests, and seek guidance.

In ITIL 4, Monitoring and Event Management categorizes events into three types: Informational, Warning, and Exception. An Informational event (Option B) is a routine notification that indicates normal operation, such as a scheduled task completion or a configuration change log entry, requiring no immediate action.

Error control is the phase where known errors are managed, workarounds are documented, and resolution is pursued. Problem identification is the first phase, and problem control involves root cause analysis.

Problem identification (B) is a key activity of Problem Management because it involves detecting and logging problems before they cause major incidents. This proactive approach relies on analyzing incident trends, monitoring alerts, and reviewing known error data to identify underlying issues. Without problem identification, the process cannot initiate root cause analysis or create known error records.

Option A is correct because Service Level Management (SLM) is responsible for monitoring actual service performance against agreed targets and producing reports to demonstrate compliance or identify gaps. This activity ensures that both the service provider and the customer have visibility into whether service levels are being met, enabling informed decisions about improvements or corrective actions.

A standard change is pre-approved by the change authority and follows a defined, low-risk procedure. It does not require a separate change advisory board (CAB) meeting for each occurrence, as its risk is well-understood and the implementation steps are documented and repeatable.

The primary purpose of Incident Management is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations. This practice focuses on resolving incidents (unplanned interruptions or reductions in quality) to return the service to its agreed service level, rather than analyzing root causes or handling routine requests.

Using a known error workaround during incident resolution is part of Incident Management. Option B is correct. Option A is incorrect because problem control identifies the root cause; Option C is incorrect as error control is about documenting known errors; Option D is incorrect.

The first step in Incident Management is to log the incident. All details should be captured before proceeding with triage or escalation.

Monitoring and Event Management is responsible for detecting and classifying events. Option D is correct.

The SVS includes guiding principles, governance, service value chain, practices, and continual improvement.

Password resets are typically pre-approved, routine requests best handled as service requests via self-service. Option D is correct. Option A is for unplanned disruptions; Option B for changes; Option C for incidents.

Problem Management identifies the root cause of incidents to prevent recurrence.

The ITIL Continual Improvement Model includes 7 steps: 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?, How do we keep the momentum going?

An event that signals a potential service degradation is a warning event.

Standard, normal, and emergency are the three types. But here we ask for two, so normal and emergency are correct.

Service Level Management is responsible for negotiating, agreeing, and monitoring SLAs.

Change Enablement (option C) is the correct practice because it specifically governs the lifecycle of changes, including authorization, review, and control of changes to prevent unauthorized modifications. In a software company experiencing production outages due to unauthorized changes, implementing Change Enablement ensures that every change is assessed, approved, and logged before deployment, directly addressing the root cause of the outages.

Service Configuration Management (D) is the ITIL 4 practice responsible for maintaining the Configuration Management Database (CMDB). It ensures that accurate and reliable information about configuration items (CIs) and their relationships is available when and where needed, supporting all other service management practices.

Standard changes are pre-approved, low risk, and follow a defined procedure. Options A and D are correct. Option B describes emergency changes; Option C describes normal changes; Option E is false as standard changes are pre-approved.

Service requests are predefined, pre-approved, and typically low-risk. This matches the description of a standard change, but in ITIL 4, service requests are a distinct practice separate from changes.

ITIL 4 defines three types of changes: standard, emergency, and normal. Emergency changes (Option C) are those that must be implemented as soon as possible to resolve an incident or security vulnerability, following a specific emergency change process with reduced testing and approval. Standard changes (Option D) are pre-authorized, low-risk, and follow a defined procedure, such as password resets or server patching.

The ITIL 4 Service Value System (SVS) is a model representing how all components and activities of an organization work together to facilitate value creation. The Service Value Chain (B) is the central operating model of the SVS, outlining six key activities (Plan, Improve, Engage, Design & Transition, Obtain/Build, Deliver & Support) that guide the creation of value. The Guiding Principles (D) are the core recommendations that guide an organization in all circumstances, applicable to all roles and initiatives within the SVS.