Relationship and Resolution Processes Flashcards

A service provider is holding regular meetings with a key customer to review service performance, discuss upcoming business needs, and gauge overall satisfaction. According to ISO 20000, which process is primarily responsible for these activities?

Answer: Business Relationship Management

Business Relationship Management is the process responsible for establishing and maintaining a good relationship between the service provider and the customer. This includes understanding the customer's business, holding service reviews, and managing satisfaction to ensure services remain aligned with business needs.

A user reports that they are unable to access a critical application, which is preventing them from performing their job duties. According to ISO 20000, how should this be classified and handled?

Answer: As an Incident, representing an unplanned interruption to a service that must be restored as quickly as possible.

An incident is defined as an unplanned interruption to a service or a reduction in the quality of a service. The user's inability to access a critical application fits this definition, and the primary goal of the Incident Management process is to restore normal service operation as quickly as possible to minimize business impact.

To ensure that a Service Level Agreement (SLA) with a customer can be met, the service provider documents an agreement with an internal IT department that provides a component of the service. What is this internal agreement commonly called?

Answer: Operational Level Agreement (OLA)

An Operational Level Agreement (OLA) is an agreement between a service provider and another part of the same organization that assists with the provision of services. It defines the internal responsibilities and timeframes required to meet the targets in the customer-facing SLA.

Which of the following is a primary objective of the Problem Management process within the ISO 20000 framework?

Answer: To minimize the adverse impact of incidents and problems by preventing them from occurring.

The primary objective of Problem Management is to manage the lifecycle of all problems, from identification to eradication. A key part of this is preventing incidents from happening in the first place and minimizing the impact of incidents that cannot be prevented. This involves performing root cause analysis on reactive problems and proactively identifying and addressing potential issues.

A service provider uses a third-party cloud vendor for data storage. To comply with ISO 20000, what is the primary purpose of the Supplier Management process in this context?

Answer: To ensure the cloud vendor's performance meets the agreed-upon targets in the contract, which in turn supports the SLAs with customers.

The Supplier Management process aims to ensure that all suppliers and their services are managed to support the agreed-upon service levels provided to customers. This includes negotiating contracts (or Underpinning Contracts), monitoring supplier performance against targets, and ensuring they meet their contractual obligations.

A service desk has noticed a recurring pattern of incidents related to a specific software application, all logged with the same error code after a recent update. While Incident Management resolves each user's issue with a workaround, the underlying fault persists. According to ISO 20000, which two processes must work closely together to address this situation for the long term?

Answer: Incident Management and Problem Management

Incident Management's goal is to restore service quickly, often using workarounds. When incidents recur, it indicates an underlying problem. The Problem Management process is responsible for investigating the root cause of these recurring incidents and finding a permanent solution. A strong relationship and information flow between these two processes are critical for long-term service stability.