ITIL-4-BRM Sample Questions & Answers

A Customer Relationship Management (CRM) system is specifically designed to consolidate all information related to customer/stakeholder interactions. It can centralize contact details, communication history, satisfaction data, service issues, and opportunities into a single record. This directly addresses the problem of fragmented information and enables the comprehensive, holistic reporting the BRM team needs.

The core role of BRM within a value stream is to act as an integrator and orchestrator, ensuring that all contributing practices and departments work together to deliver value to the consumer. In this scenario, the BRM is not performing the technical or legal tasks but is ensuring the end-to-end flow is coherent and meets customer expectations by facilitating communication and coordination, which is a key BRM responsibility.

This statement is false. While BRM is concerned with overall satisfaction, managing day-to-day operational interactions and incidents is the primary purpose of the Service Desk practice. Business Relationship Management focuses on establishing and nurturing relationships at strategic and tactical levels to understand business demand and ensure that the service provider can meet these demands and co-create value.

In the ITIL framework, a 'user' is the role that directly uses a service. The surgeon is the individual actively interacting with the Patient Records Management service to perform their job. The 'customer' defines the requirements for the service (e.g., the Head of Surgery), and the 'sponsor' authorizes the budget for it (e.g., the Hospital Administrator).

This situation describes the 'watermelon effect' where SLAs are green but customer satisfaction is red. This indicates a gap between what is being measured (technical performance) and what actually matters to the business (outcomes). The core BRM activity here is to bridge that gap by reviewing and redefining the SLAs, in collaboration with Service Level Management, to focus on metrics that more accurately reflect business value and outcomes.

Stakeholders with high power and low interest (e.g., a senior executive not directly involved in a project) must be kept satisfied because their power could influence outcomes if they become dissatisfied. The appropriate strategy is to provide them with just enough information to keep them content and confident, without burdening them with details they are not interested in. 'Manage closely' is for high power/high interest, 'Keep informed' is for low power/high interest, and 'Monitor' is for low power/low interest.

A fundamental challenge that BRM aims to overcome is the presence of organizational silos. When the service provider (e.g., IT) and service consumer (e.g., a business department) operate in isolation, they naturally develop their own cultures, goals, and jargon. This leads to a disconnect and a lack of shared understanding of what constitutes 'value', which is a primary barrier to effective relationship management.

A balanced view of BRM performance requires measuring both relationship health (consumer satisfaction) and strategic impact (alignment with business objectives). Satisfaction scores measure the consumer's perception of the service relationship, while the alignment of projects to strategic goals measures the BRM's effectiveness in translating business needs into valuable IT initiatives. The other options focus too narrowly on activity metrics (meetings held) or operational metrics (incidents) that don't capture the strategic value of BRM.

A 'strategic partner' relationship represents the highest level of collaboration. In this model, the service provider is deeply integrated with the consumer's business strategy. They work together proactively to identify opportunities, innovate, and co-create value, often involving shared goals, risks, and rewards. This goes beyond the transactional nature of a commodity supplier or the defined service delivery of a typical service provider.

The LACMT model consists of Lead, Act, Connect, Manage, and Thrive. The 'Thrive' element is focused on strategic partnering activities. This includes shaping business demand, identifying opportunities for value co-creation, and influencing business and IT strategy. Facilitating strategy sessions and enabling new capabilities fall squarely within this strategic, forward-looking 'Thrive' domain.