Scenario practice questions

Partners and Suppliers

Why wrong: This dimension focuses on the relationships an organization has with other organizations that are involved in the design, development, delivery, support, and continual improvement of services. Since the question describes an internal IT team implementing a tool and experiencing internal challenges, there is no mention or implication of issues arising from external partners or suppliers, making this dimension irrelevant to the described problem.

Information and Technology

Why wrong: While the implementation of a new monitoring tool clearly falls within the scope of the Information and Technology dimension, the problem described is not a deficiency in the technology itself or a failure in information management practices. The tool is functioning as intended; the issue lies with the human element's adaptation to and interaction with this new technological solution, rather than the technology's inherent capabilities or limitations.

Value Streams and Processes

Why wrong: This dimension describes how the organization's activities are structured and coordinated to create value for stakeholders. Although a new tool often necessitates adjustments to existing processes or the creation of new ones, the core problem identified—a skill gap and temporary productivity loss—pertains to the human capacity to execute those processes effectively, not a fundamental flaw in the design or flow of the value stream or process steps themselves.

Service Request Management and Problem Management

Why wrong: Service Request Management focuses on fulfilling pre-defined user requests, such as password resets or software installations, which are planned and routine activities. A database server failure represents an unplanned disruption requiring immediate restoration, not a routine request. While Problem Management is correctly associated with investigating the root cause, its pairing with Service Request Management makes this option incorrect for a major incident scenario.

Incident Management and Change Management

Why wrong: Incident Management is indeed critical for restoring service after a database failure. However, Change Management primarily governs the planned addition, modification, or removal of IT services or components to minimize risk. While a change might have triggered the incident or a change might be needed to implement a permanent fix, Change Management itself is not the practice directly responsible for the immediate response to an unplanned outage or the subsequent root cause analysis.

Problem Management and Service Desk

Why wrong: Problem Management is correctly identified as the practice for investigating the underlying causes of incidents to prevent their recurrence. However, the Service Desk is a function, not a management practice, primarily acting as the single point of contact for users to log incidents and service requests. While the Service Desk would log the major incident, it does not directly perform the technical restoration or the in-depth root cause analysis that constitutes the core activities of Incident and Problem Management practices.

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.

Output

Why wrong: An output is a tangible or intangible deliverable produced by an activity. While an output contributes to the overall service, it represents a specific result of a task or process, such as a generated report or a processed transaction. It does not inherently provide a guarantee or assurance about the service's performance characteristics or its fitness for use over time, which is what the question implies with "99% availability."

Utility

Why wrong: Utility describes what the service does, specifically its functionality and whether it is "fit for purpose." It addresses whether the service can perform the required tasks and support the customer's desired outcomes. For instance, a cloud application's utility might be its ability to process data or manage customer relationships. However, utility does not encompass the non-functional requirements like availability or performance levels, which are covered by warranty.

Outcome

Why wrong: An outcome is the result achieved by a stakeholder, enabled by the use of a service. It represents what the customer *wants to achieve* or the value they derive from consuming the service, rather than a characteristic of the service itself. While a service's availability (warranty) contributes to achieving positive outcomes, the outcome itself is the end result or benefit, not a contractual guarantee about the service's operational performance.

Renegotiate service level targets with the customer in Service Level Management

Why wrong: Renegotiating service level targets in Service Level Management addresses the *symptoms* of an overwhelmed service desk by adjusting performance expectations, rather than resolving the underlying technical issue causing the repeated incidents. While it might alleviate pressure on the team by lowering resolution time commitments, it does not improve service quality or prevent the incidents from occurring in the first place, which is crucial for long-term stability.

Implement a faster incident resolution process in Incident Management

Why wrong: Implementing a faster incident resolution process within Incident Management focuses on reducing the *duration* of individual service disruptions, but it does not address the *frequency* or *root cause* of the repeated incidents. The service desk would still be overwhelmed by the sheer volume of recurring issues, even if each one is handled more quickly, failing to provide a sustainable solution to the underlying problem.

Submit a change request to Change Enablement to replace the software

Why wrong: Submitting a change request to Change Enablement to replace software is a premature and potentially drastic step without prior root cause analysis and solution design. Change Enablement manages the implementation of *known* solutions, but it is not the practice responsible for identifying the root cause of recurring problems or designing the appropriate fix, especially when a vendor patch is not available, making this an unsuitable immediate action.

A user reports a system crash (service request) and requests a software upgrade (incident)

Why wrong: This scenario incorrectly classifies both events. A system crash represents an unplanned interruption to a service, which is a clear definition of an incident requiring restoration of normal operation. Conversely, requesting a software upgrade is a standard, pre-defined action for obtaining a new version of an application, making it a service request rather than an incident. The misidentification of both elements renders this option incorrect.

A user requests a new laptop (incident) and reports a printer jam (service request)

Why wrong: Both classifications in this option are incorrect. Requesting a new laptop is a standard, pre-defined action to acquire a piece of equipment, which falls under the definition of a service request. In contrast, a printer jam represents an unplanned interruption to the normal operation of a printing service, making it an incident that requires immediate attention to restore functionality.

A user requests access to a database (incident) and reports a network outage (incident)

Why wrong: While reporting a network outage is correctly identified as an incident due to it being an unplanned interruption to service, the classification of a database access request is incorrect. Requesting access to a database is a standard, pre-defined action for obtaining specific permissions or resources, which is a quintessential example of a service request. Therefore, this scenario contains an incorrect classification.

Supplier Management

Why wrong: Supplier Management focuses on establishing and maintaining relationships with third-party vendors to ensure the effective delivery of goods and services. It involves contract negotiation, performance monitoring against service level agreements, and managing the overall supplier lifecycle. This practice does not involve the internal technical investigation of an organization's own network infrastructure for recurring outages, as the team is investigating their internal systems.

Service Desk

Why wrong: The Service Desk serves as the single point of contact for users, primarily responsible for logging incidents, fulfilling service requests, and providing initial support. While they facilitate the reporting and escalation of issues, their core function is not to conduct deep-dive root cause analysis or implement permanent solutions for underlying systemic problems. Their role is to restore service quickly or escalate to appropriate technical teams for resolution.

Incident Management

Why wrong: Incident Management's primary objective is to restore normal service operation as quickly as possible, minimizing the adverse impact on business operations. While it addresses immediate service disruptions, its focus is on rapid restoration, often through temporary workarounds, rather than the detailed investigation into the fundamental causes of recurring issues. The practice prioritizes speed of recovery over comprehensive root cause analysis, which is needed for recurring problems.

A team documents the current process before making changes

Why wrong: This is 'Start where you are'.

A team works in two-week sprints with a review at the end

Why wrong: This is 'Progress iteratively with feedback'.

A team automates repetitive tasks to free up time

Why wrong: This is 'Optimise and automate', not collaboration.

Partners and Suppliers

Why wrong: This dimension focuses on the relationships an organization has with other organizations that are involved in the design, development, delivery, support, and continual improvement of services. The question stem does not provide any indication of issues with external providers or partnerships related to change management. The problem described, concerning internal capabilities or training, does not point to a deficiency in managing external entities, making this dimension unlikely to be the neglected area.

Information and Technology

Why wrong: This dimension includes the information and knowledge needed to deliver and manage services, as well as the technologies and tools required. The question explicitly states that "tools are implemented" to support the change management process. This indicates that the technological aspect of this dimension has been addressed, and there is no suggestion of a lack of necessary information or technological infrastructure that would make this the neglected dimension.

Value Streams and Processes

Why wrong: This dimension describes how the organization creates, delivers, and consumes value through its services. It encompasses the activities, workflows, controls, and procedures that transform inputs into outputs. The question explicitly states that the organization has a "mature change management process," directly indicating that this dimension is well-established and not the neglected area requiring attention.

Focusing only on incident resolution speed

Why wrong: Focusing solely on incident resolution speed, while seemingly beneficial, represents a narrow, sub-optimized approach that neglects the broader dimensions of service quality and value. This singular focus can inadvertently lead to compromises in the quality of resolution, increased operational costs, or a diminished customer experience by ignoring critical aspects like problem management, service availability, or overall customer satisfaction, thereby failing to consider the entire service value system.

Optimizing a single process without considering other processes

Why wrong: Optimizing a single process without considering its interdependencies with other processes within the service value chain is a classic example of sub-optimization, directly contradicting the holistic principle. Such an isolated approach often creates unintended consequences, like bottlenecks, reduced overall efficiency, or degraded end-to-end service performance, because it fails to recognize how changes in one area ripple through the entire system.

Updating a database without assessing the impact on related applications

Why wrong: Updating a foundational component like a database without thoroughly assessing its impact on all related applications, services, and users demonstrates a critical failure to recognize system interconnections. This narrow focus can result in severe service disruptions, data integrity issues, or application malfunctions, directly violating the holistic principle by ignoring how individual IT components collectively contribute to the delivery of value.

Utility

Why wrong: Utility is the functionality offered by a product or service to meet a particular need.

Outcome

Why wrong: Outcome is incorrect because the scenario describes the service’s characteristic of delivering value by enabling desired results *without* the customer managing specific costs and risks. Outcome merely refers to a result for a stakeholder, not the encompassing concept of providing that result whilst also removing burdens. It is tempting as the question explicitly mentions "achieving desired outcomes." This option would be correct if the question focused solely on the ultimate results or benefits a customer experiences from a service.

Warranty

Why wrong: Warranty ensures a product or service meets agreed requirements.

Value Streams and Processes

Why wrong: Processes may exist, but the partner aspect is the issue.

Organizations and People

Why wrong: Internal people may be fine, but the external partner dimension is lacking.

Information and Technology

Why wrong: Technology may be working, but the problem is with the partner relationship.

Utility

Why wrong: Utility is about functionality, not guarantees.

Risk

Why wrong: Risk is a possible event; warranty mitigates risk.

Output

Why wrong: Output is a deliverable.

Progress iteratively with feedback

Why wrong: This principle focuses on delivering improvements in small, manageable steps, allowing for continuous learning and adaptation based on feedback received after each iteration. While vital for the *execution* and refinement of an improvement plan, it does not primarily guide the initial analytical phase of understanding the existing process before any changes are designed or implemented.

Focus on value

Why wrong: This principle ensures that all activities undertaken, including process improvements, directly contribute to the creation of value for stakeholders. While fundamental for setting the *direction* and *priorities* of any change, it does not specifically outline the methodology for conducting an initial analysis of the current state of an existing process to identify improvement areas.

Collaborate and promote visibility

Why wrong: This principle stresses the importance of involving all relevant stakeholders in the improvement process and ensuring transparency of information. While crucial for gaining diverse perspectives, fostering buy-in, and ensuring successful adoption of changes, it does not primarily guide the technical or analytical steps required to assess the current performance or structure of an existing process.

Problem control

Why wrong: Problem control is the subsequent phase in Problem Management, focusing on analyzing identified problems to determine their root cause and developing temporary workarounds. While it involves finding a resolution, the scenario explicitly describes the *detection* of incidents without a known cause, which precedes the detailed analysis and control activities. This phase is initiated *after* a problem has been identified and logged.

Error control

Why wrong: Error control focuses on managing known errors through the lifecycle, including documenting workarounds and initiating resolution via the change enablement practice. This scenario, however, describes incidents with no known cause, which is the trigger for problem identification and analysis—the earlier phase where root cause is sought. Error control would be tempting because it handles incidents once a root cause is documented, but it is not invoked until after a problem has been diagnosed and a known error record exists.

Post-implementation review

Why wrong: A post-implementation review is not a recognized phase within the ITIL Problem Management practice. This activity typically occurs after a change or solution has been deployed, assessing its effectiveness and whether it met its objectives, often as part of the Change Enablement practice or project closure. Problem Management focuses on identifying, diagnosing, and resolving the underlying causes of incidents, not on reviewing the success of implemented solutions in a general sense.