I85PREP
⌘ K
ITIL 4 SRM study materials
ITIL 4 SRM study resources

ITIL 4 SRM practice questions

One question at a time. Build your ITIL 4 SRM understanding.

First 50 of 199 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Service Request Management practice fundamentals and key concepts

In ITIL 4, what is the primary purpose of the Service Request Management practice?

  1. To identify the root cause of recurring incidents across the technology estate
  2. To support the agreed quality of a service by handling all pre-defined, user-initiated service requests in an effective and user-friendly manner Correct answer.
  3. To plan and manage the full lifecycle of changes to production services
  4. To restore normal service operation as quickly as possible after an unplanned interruption

Explanation

Service Request Management exists to handle pre-defined, user-initiated requests such as password resets, access provisioning, or standard equipment orders. Its emphasis is on effectiveness and a user-friendly experience, because these requests are routine and predictable rather than failures. Incident Management and Change Enablement cover the other scenarios, so the purpose statement is specific to requests.

Question 2Service Request Management practice fundamentals and key concepts

Which statement best describes how a service request is typically characterized?

  1. It is a formal proposal to alter a configuration item with unknown impact
  2. It is always an unplanned event that degrades a live service
  3. It is a normal part of service delivery that is pre-approved and low risk Correct answer.
  4. It is an escalation raised only when a service level target is breached

Explanation

Service requests are normal, pre-defined parts of service delivery, such as information requests, access, or standard changes. Because they are pre-approved and understood, they follow predictable workflows rather than incident triage. This distinguishes them from incidents, which are unplanned disruptions.

Question 3Service Request Management practice fundamentals and key concepts

A user submits a request for a standard software package that appears in the service catalogue with a fixed approval path. Why is this request likely to be handled without formal change authorization?

  1. Because the request was logged outside of business hours
  2. Because the software is already installed on another user's device
  3. Because it is a pre-authorized standard change defined in the catalogue Correct answer.
  4. Because the user has verbally confirmed the business need

Explanation

Standard changes are pre-authorized because their risk and procedure have already been assessed and agreed. When such an item is offered through the service catalogue with a fixed workflow, the request can be fulfilled without a fresh change authorization. The user's verbal confirmation or timing does not remove the need for authorization.

Question 4Service Request Management practice fundamentals and key concepts

What role does the service catalogue play in Service Request Management?

  1. It lists the suppliers contracted to deliver underpinning services
  2. It stores the technical configuration details of each infrastructure component
  3. It records every incident that has affected a configuration item
  4. It defines the requests users can raise, along with their fulfilment workflows and approval steps Correct answer.

Explanation

The service catalogue presents the services and requestable items available to users, and it typically defines how each request is fulfilled, including approvals. It is the user-facing entry point that makes requests predictable. Incident records, configuration details, and supplier lists live in other practices and tools.

Question 5Service Request Management practice fundamentals and key concepts

Which practice is most directly responsible for agreeing and monitoring the targets against which service request fulfilment is measured?

  1. Service Level Management Correct answer.
  2. Service Request Management
  3. Problem Management
  4. Continual Improvement

Explanation

Service Level Management negotiates, agrees, and monitors service levels, including targets for request fulfilment times. Service Request Management executes the fulfilment against those agreed targets. Problem Management and Continual Improvement do not own service level targets.

Question 6Service Request Management practice fundamentals and key concepts

A request is submitted that does not match any item in the service catalogue. What is the most appropriate first step?

  1. Fulfil it immediately because the user has asked for it
  2. Treat it as a new or non-standard request and route it for assessment before fulfilment Correct answer.
  3. Reject it outright because the catalogue is exhaustive
  4. Close it as an incident because it is not catalogued

Explanation

Requests that fall outside the catalogue are not automatically pre-authorized, so they need assessment, possibly through Change Enablement, before fulfilment. Immediate fulfilment bypasses the controls that make catalogued requests safe. Rejecting or misclassifying the request does not serve the user or the organization.

Question 7Service Request Management practice fundamentals and key concepts

Why should Service Request Management workflows be automated where possible?

  1. To eliminate the need for any human approval in all request types
  2. To remove the requirement to record requests in the service management tool
  3. To guarantee that no request will ever breach its service level target
  4. To make fulfilment faster, consistent, and more user-friendly while freeing staff for complex work Correct answer.

Explanation

Automation supports the practice's aim of effective and user-friendly fulfilment by standardizing routine steps and reducing wait times. It does not remove the need for governance or records, nor can it guarantee service level outcomes. Human approval remains necessary where the workflow requires it.

Question 8Service Request Management practice fundamentals and key concepts

Which metric best reflects the user experience dimension of Service Request Management?

  1. The percentage of changes rejected by the change advisory board
  2. The count of major incidents closed in the period
  3. User satisfaction with the ease and speed of request fulfilment Correct answer.
  4. The number of configuration items recorded in the CMDB

Explanation

Because the practice emphasizes a user-friendly experience, satisfaction with ease and speed of fulfilment is a direct measure of that goal. CMDB counts, major incident closures, and change rejections measure other practices. Selecting experience-oriented metrics keeps measurement aligned to the practice's purpose.

Question 9Service Request Management practice fundamentals and key concepts

How does Service Request Management interact with the 'service desk' as a practice?

  1. The service desk replaces Service Request Management entirely in small organizations
  2. The service desk owns the approval of all standard changes across the organization
  3. The service desk is responsible for root cause analysis of request failures
  4. The service desk is the primary user contact point where many requests are captured and tracked Correct answer.

Explanation

The service desk is the user-facing channel through which requests are often captured, communicated, and tracked. It supports Service Request Management rather than replacing it, since the practice defines workflows and governance. Approvals and root cause analysis sit with other roles and practices.

Question 10Service Request Management practice fundamentals and key concepts

A user requests a status update on an open request. Which practice activity does this best represent?

  1. Capacity and performance management
  2. Communication and user engagement within request handling Correct answer.
  3. Change scheduling and deployment
  4. Problem identification and error control

Explanation

Keeping users informed about the progress of their requests is part of the communication and engagement that underpins good request handling. It is not a problem, change, or capacity activity. Transparent status communication directly supports the user-friendly aim of the practice.

Question 11Service Request Management practice fundamentals and key concepts

What is the most appropriate way to handle a request that requires approval from a line manager?

  1. Ask the user to obtain approval informally and confirm verbally later
  2. Build the approval step into the request workflow so it is triggered and recorded automatically Correct answer.
  3. Skip approval because the request appears routine
  4. Escalate the request as an incident until approval is obtained

Explanation

Approvals should be part of the defined workflow so they are triggered consistently and leave an auditable record. Informal or skipped approvals undermine governance and traceability. Treating the request as an incident misclassifies it and does not resolve the approval need.

Question 12Service Request Management practice fundamentals and key concepts

Which pair of practices most closely collaborate to ensure a request for a new starter's equipment is fulfilled correctly?

  1. Incident Management and Availability Management
  2. Continual Improvement and Measurement and Reporting
  3. Problem Management and Capacity Management
  4. Service Request Management and Service Catalogue Management Correct answer.

Explanation

The request is defined and offered through the service catalogue, and Service Request Management executes its fulfilment. The other pairs address different concerns such as root cause, capacity, or measurement. Collaboration between these two practices makes the request predictable and available to users.

Question 13Service Request Management practice fundamentals and key concepts

Why is it important that service requests are logged even when they are fulfilled instantly?

  1. Logging is required only for requests that breach their target
  2. Logging automatically approves the request for future use
  3. Logging prevents users from submitting duplicate requests
  4. Logging provides a record for audit, trend analysis, and continual improvement Correct answer.

Explanation

Every request should be recorded so the organization can demonstrate what was delivered, spot demand patterns, and improve the workflow. Logging is not conditional on a breach, and it does not by itself prevent duplicates or grant future approval. The record is the basis for measurement and improvement.

Question 14Service Request Management practice fundamentals and key concepts

A request type generates high volumes of manual handling and frequent user complaints about delays. Which action best reflects Continual Improvement applied to Service Request Management?

  1. Add more approval layers to slow the process and increase control
  2. Analyze the workflow, automate or simplify steps, and measure the effect on fulfilment time Correct answer.
  3. Close the request type to reduce demand on the team
  4. Reclassify all such requests as incidents to reset their targets

Explanation

Continual Improvement uses analysis and measurement to remove waste and improve outcomes, which here means simplifying or automating the workflow. Closing the request type or reclassifying requests avoids the problem rather than solving it. Adding approval layers typically worsens delays.

Question 15Service Request Management practice fundamentals and key concepts

Which statement correctly distinguishes a service request from an incident?

  1. A service request is always urgent; an incident is always routine
  2. A service request requires root cause analysis; an incident requires only fulfilment
  3. A service request is raised by staff; an incident is raised only by customers
  4. A service request is a planned, pre-defined need; an incident is an unplanned disruption to a service Correct answer.

Explanation

The core distinction is planned versus unplanned: requests are normal, pre-defined needs, while incidents are unplanned disruptions. Urgency, root cause analysis, and the identity of the raiser do not define the boundary. Both can be raised by any user of the service.

Question 16Service Request Management practice fundamentals and key concepts

What does 'pre-defined' mean in the context of a service request?

  1. The request can only be submitted at predefined times of day
  2. The request type has an agreed description, workflow, and fulfilment steps before it is submitted Correct answer.
  3. The request has already been fulfilled before the user asks
  4. The request must be approved by the service desk before it is logged

Explanation

Pre-defined means the request type is understood in advance, with an agreed description, approval path, and fulfilment steps. This is what allows routine requests to be handled consistently and often automatically. It does not refer to prior fulfilment, pre-logging approval, or submission timing.

Question 17Service Request Management practice fundamentals and key concepts

A team wants to reduce the time users spend waiting for simple access requests. Which approach aligns best with Service Request Management principles?

  1. Require every access request to be reviewed by a senior manager
  2. Route all access requests through the major incident process
  3. Offer self-service with automated fulfilment for low-risk, well-understood access requests Correct answer.
  4. Remove access requests from the service catalogue to reduce visibility

Explanation

Self-service and automation suit low-risk, well-understood requests and reduce waiting while keeping control. Senior review for every request adds delay without proportionate benefit. Major incident routing and removing catalogue visibility both work against the practice's aims.

Question 18Service Request Management practice fundamentals and key concepts

Which outcome most clearly indicates that Service Request Management is performing well?

  1. Every request is handled by a senior manager for oversight
  2. All requests are fulfilled without any record being created
  3. Users can find and raise requests easily, and fulfilment meets agreed expectations Correct answer.
  4. The number of logged requests falls to zero across all channels

Explanation

Good performance means requests are easy to raise and are fulfilled as agreed, reflecting both effectiveness and user-friendliness. Zero logged requests would suggest demand is being hidden, not that the practice is healthy. Senior handling of everything and unrecorded fulfilment both undermine the practice.

Question 19Service Request Management practice fundamentals and key concepts

How should Service Request Management treat a request that has been raised but cannot be fulfilled because a dependency is unavailable?

  1. Delete the request so the user can resubmit later
  2. Keep the request open, communicate the status to the user, and manage it against its target Correct answer.
  3. Convert the request into a problem record for root cause analysis
  4. Close the request as fulfilled to protect the fulfilment metric

Explanation

An unfulfilled request remains open and should be tracked, with the user informed of the delay and the target managed. Closing it as fulfilled or deleting it falsifies records and hides demand. A single dependency delay does not by itself warrant a problem record.

Question 20Service Request Management practice fundamentals and key concepts

Which statement about the scope of Service Request Management is correct?

  1. It covers only requests submitted by external customers
  2. It covers only requests raised outside normal service hours
  3. It covers only requests that require a formal change advisory board decision
  4. It covers requests from users for information, access, standard changes, and other pre-defined items Correct answer.

Explanation

The practice spans the range of pre-defined, user-initiated requests, including information, access, and standard changes. It is not limited by who raises the request, whether a change board is involved, or the time of submission. This broad scope is what makes it a distinct practice.

Question 21Service Request Management practice fundamentals and key concepts

Why does Service Request Management rely on clearly defined request models?

  1. Request models guarantee that every request will be approved automatically
  2. Request models allow each handler to design a unique approach for every request
  3. Request models remove the need to record the outcome of a request
  4. Request models standardize steps, roles, and timescales so similar requests are handled consistently Correct answer.

Explanation

A request model defines the agreed steps, responsibilities, and timescales for a request type, which enables consistency and measurement. It does not permit ad hoc handling, remove records, or guarantee approval. Consistency is the key benefit that supports both quality and user experience.

Question 22Service Request Management practice fundamentals and key concepts

A request workflow includes a step where a specialist team must confirm technical feasibility. What is the best way to represent this in the practice?

  1. As a defined fulfilment task with an owner and expected timescale in the request model Correct answer.
  2. As an unrecorded conversation between handlers
  3. As a separate incident raised against the specialist team
  4. As an optional step left to the requester to chase

Explanation

Feasibility confirmation is part of fulfilment and should appear in the request model with a named owner and timescale. Leaving it optional or unrecorded makes the workflow unpredictable and untraceable. Raising an incident against a team misuses the incident process.

Question 23Service Request Management practice fundamentals and key concepts

Which practice is most likely to supply the knowledge articles that let users resolve simple requests themselves?

  1. Capacity Management acting alone
  2. Service Desk and Service Request Management working together with Knowledge Management Correct answer.
  3. Problem Management acting alone
  4. Supplier Management acting alone

Explanation

Self-help content is created through Knowledge Management and surfaced by the service desk and request workflows. Capacity, Problem, and Supplier Management do not primarily own user-facing knowledge articles. Collaboration across these practices makes self-service effective.

Question 24Service Request Management practice fundamentals and key concepts

What is the best justification for measuring request fulfilment against agreed timescales rather than only counting closed requests?

  1. Timescale measurement reflects whether the service meets user expectations, while volume alone does not Correct answer.
  2. Counting closed requests always overstates user satisfaction
  3. Volume measurement is prohibited by the practice
  4. Timescales are the only data the tool can capture

Explanation

Measuring against agreed timescales shows whether expectations are being met, which is central to the practice's purpose. Volume is useful for demand analysis but says nothing about quality of fulfilment. The other options misstate the practice's guidance or the capability of tools.

Question 25Service Request Management practice fundamentals and key concepts

How does Service Request Management support the 'optimize and automate' dimension of service management?

  1. By eliminating all human roles from the organization
  2. By removing the need for a service catalogue
  3. By replacing Incident Management in all circumstances
  4. By streamlining and automating routine request workflows to improve efficiency and user experience Correct answer.

Explanation

Optimize and automate means improving workflows before automating them, which is exactly what well-run request handling does. It does not eliminate human roles, remove the catalogue, or replace Incident Management. The practice demonstrates the dimension through efficient, standardized fulfilment.

Question 26Service Request Management practice fundamentals and key concepts

In Service Request Management, what is the primary purpose of a request model?

  1. To document the technical design of the service that fulfils the request
  2. To record the identity of the approver who authorised a request
  3. To calculate the cost of fulfilling a request for chargeback purposes
  4. To define the agreed steps, roles, and timescales for handling a specific type of request Correct answer.

Explanation

A request model is a pre-defined, agreed approach for handling a particular type of service request. It specifies the activities, responsibilities, and target timescales so that requests of that type are handled consistently and efficiently.

Question 27Service Request Management practice fundamentals and key concepts

Which statement best describes how Service Request Management differs from Incident Management?

  1. Service Request Management deals only with requests from external customers, while Incident Management deals only with internal staff
  2. Service Request Management focuses on agreed, pre-defined user requests, while Incident Management focuses on restoring service after unplanned disruption Correct answer.
  3. Service Request Management owns the problem lifecycle, while Incident Management owns the change lifecycle
  4. Service Request Management restores normal service after disruption, while Incident Management handles planned changes

Explanation

Service requests are user-initiated, pre-defined requests that are part of normal service delivery, such as access or information requests. Incidents are unplanned interruptions or degradations of service that must be resolved to restore normal operation.

Question 28Service Request Management practice fundamentals and key concepts

A user submits a request for a standard software package through the self-service portal. The request matches a published request model. What is the most appropriate next action?

  1. Escalate it to the change advisory board for approval
  2. Reject it and ask the user to raise a problem record
  3. Route it through the pre-defined request model workflow for fulfilment Correct answer.
  4. Log it as an incident because the user cannot proceed without the software

Explanation

When a request matches an existing request model, it should be handled through that model's workflow. This ensures consistent, efficient fulfilment using the agreed steps and timescales.

Question 29Service Request Management practice fundamentals and key concepts

Why should Service Request Management define and agree service levels for request fulfilment?

  1. To provide a basis for measuring performance and managing user expectations Correct answer.
  2. To eliminate the need for any approval steps in request workflows
  3. To guarantee that every request will be fulfilled within one hour
  4. To ensure that all requests are fulfilled by the service desk without specialist involvement

Explanation

Agreed service levels set expectations for how quickly and reliably requests will be handled. They also provide a measurable target against which the performance of Service Request Management can be assessed and improved.

Question 30Service Request Management practice fundamentals and key concepts

A request for a new laptop has been approved and is waiting for the device to be delivered by a supplier. How should Service Request Management handle this situation?

  1. Cancel the request and ask the user to resubmit when stock is available
  2. Keep the request open with a status that reflects the dependency and communicate the expected date to the user Correct answer.
  3. Close the request because the approval step is complete
  4. Mark the request as an incident because the user is without a device

Explanation

The request remains open until fulfilment is complete. Its status should reflect that it is waiting on a dependency, and the user should be kept informed of progress and expected timescales.

Question 31Service Request Management practice fundamentals and key concepts

Which practice is most directly responsible for providing the self-help articles that allow users to resolve simple service requests without contacting the service desk?

  1. Continual Improvement
  2. Capacity and Performance Management
  3. Supplier Management
  4. Knowledge Management Correct answer.

Explanation

Knowledge Management creates and maintains the articles and guidance that enable users to resolve simple requests through self-service. Service Request Management relies on this knowledge to support efficient fulfilment.

Question 32Service Request Management practice fundamentals and key concepts

What is the main benefit of automating a service request workflow?

  1. It reduces manual effort and improves consistency and speed of fulfilment Correct answer.
  2. It removes the need to record the request in the system
  3. It eliminates the need for any human involvement in fulfilment
  4. It guarantees that the request will never be rejected

Explanation

Automation streamlines repetitive steps, reduces errors, and speeds up fulfilment while maintaining a consistent process. It supports efficient use of resources and a better user experience.

Question 33Service Request Management practice fundamentals and key concepts

A user raises a request for a type that has never been handled before and does not match any existing request model. What is the most appropriate first step?

  1. Log it and route it for assessment to determine whether a new request model is needed Correct answer.
  2. Fulfil it informally and record the details later
  3. Reject it because it is not in the service catalogue
  4. Assign it to the problem management team for root cause analysis

Explanation

New request types should be logged and assessed so that an appropriate handling approach can be defined. This may lead to the creation of a new request model to handle similar requests consistently in future.

Question 34Service Request Management practice fundamentals and key concepts

Which two practices are most likely to collaborate to ensure that a service request requiring a change to an IT system is fulfilled correctly?

  1. Service Request Management and Workforce Management
  2. Service Request Management and Relationship Management
  3. Service Request Management and Financial Management
  4. Service Request Management and Change Enablement Correct answer.

Explanation

When fulfilling a request requires a change to an IT system, Service Request Management must work with Change Enablement to ensure the change is assessed, authorised, and scheduled appropriately.

Question 35Service Request Management practice fundamentals and key concepts

Which metric best indicates that Service Request Management is delivering a good user experience?

  1. The average time taken to approve a request
  2. The percentage of requests fulfilled within agreed timescales Correct answer.
  3. The total number of request models defined
  4. The number of requests logged per agent per day

Explanation

Fulfilment within agreed timescales directly reflects how well user expectations are met. It is a key indicator of the user experience and the effectiveness of the practice.

Question 36Service Request Management practice fundamentals and key concepts

What is the most appropriate way to handle a service request that requires approval from a line manager?

  1. Escalate the request to the change advisory board
  2. Reject the request because approval is required
  3. Fulfil the request immediately and seek approval afterwards
  4. Include an approval step in the request model and route it to the line manager Correct answer.

Explanation

Approval requirements should be built into the request model so that the request is routed to the appropriate approver. This ensures the request is authorised before fulfilment proceeds.

Question 37Service Request Management practice fundamentals and key concepts

A service request has been raised but cannot be fulfilled because a dependent task in another team is delayed. What is the best way to manage this?

  1. Reclassify the request as an incident to expedite the dependent task
  2. Cancel the request and log a problem record for the delay
  3. Close the request and ask the user to raise a new one when the dependency is resolved
  4. Keep the request open, update its status to reflect the dependency, and communicate with the user Correct answer.

Explanation

The request should remain open and its status should accurately reflect that it is waiting on a dependency. Keeping the user informed helps manage expectations and maintains trust.

Question 38Service Request Management practice fundamentals and key concepts

Why is it important that Service Request Management captures and analyses data on request volumes and fulfilment performance?

  1. To justify reducing the number of service desk staff
  2. To identify opportunities for improvement, such as new request models or automation Correct answer.
  3. To ensure that all requests are handled by a single team
  4. To eliminate the need for user feedback

Explanation

Analysing request data reveals trends, bottlenecks, and high-volume request types that may benefit from standardisation or automation. This supports continual improvement of the practice and the services it supports.

Question 39Service Request Management practice fundamentals and key concepts

Which statement best describes the relationship between Service Request Management and the service catalogue?

  1. The service catalogue lists only incidents that have been resolved
  2. Service Request Management is independent of the service catalogue
  3. Service Request Management uses the service catalogue to identify what users can request and how it will be fulfilled Correct answer.
  4. The service catalogue is maintained by Service Request Management alone

Explanation

The service catalogue provides information about available services and requestable items. Service Request Management relies on it to determine what can be requested and to route requests to the appropriate fulfilment model.

Question 40Service Request Management practice fundamentals and key concepts

A service desk analyst receives a request that has been logged but whose fulfilment depends on a task assigned to a specialist team in another department. Under Service Request Management, which action best reflects the practice's guidance on coordinating fulfilment?

  1. Track the request as a single unit of work with defined ownership and status, escalating when agreed timescales are at risk Correct answer.
  2. Close the request at the service desk and ask the user to raise a separate request directly with the specialist team
  3. Reclassify the request as an incident so that the specialist team is obliged to respond within incident targets
  4. Log the dependent task as a problem so that root cause analysis can determine why the specialist team is slow

Explanation

Service Request Management treats a request as a unit of work that is owned, tracked and reported on from submission to completion, even when fulfilment involves several teams. Because request models define the tasks, owners and timescales, the practice can monitor progress and escalate when targets are threatened rather than fragmenting the request. Keeping ownership and status visible is what allows fulfilment to be measured against agreed service levels.

Question 41Service Request Management value streams, processes, and people (roles and competencies)

In ITIL 4 service request management, what is the primary purpose of a service request value stream?

  1. To handle a user's request for something the service offers, such as information or access Correct answer.
  2. To negotiate and agree service level targets with customers
  3. To investigate the root cause of recurring incidents
  4. To restore a failed component to its normal operating state

Explanation

Service request management supports the agreed, predefined handling of user-initiated requests for standard service offerings. Restoration of failed components belongs to incident management, and root-cause investigation belongs to problem management.

Question 42Service Request Management value streams, processes, and people (roles and competencies)

Which statement best describes how service requests differ from incidents in ITIL 4?

  1. A request must be raised through a change request, while an incident is logged directly
  2. A request is a normal part of service consumption, while an incident is an unplanned interruption or degradation Correct answer.
  3. A request is always more urgent than an incident
  4. A request is handled only by technical specialists, while an incident is handled by the service desk

Explanation

ITIL 4 frames a service request as a user's normal request for something the service provides, whereas an incident is an unplanned interruption to or reduction in quality of a service. Urgency, routing and authorisation do not define the distinction.

Question 43Service Request Management value streams, processes, and people (roles and competencies)

A service desk analyst receives a request for a standard software licence. Which action best reflects the request management practice's guidance on predefined request models?

  1. Pass the request to problem management for root-cause analysis
  2. Raise an emergency change so the licence can be approved quickly
  3. Log the request as an incident and close it once the user is contacted
  4. Follow the agreed workflow for that request type, including its approvals and fulfilment steps Correct answer.

Explanation

Predefined request models capture the steps, approvals and responsibilities for a common request type so it can be handled consistently and efficiently. Emergency change, problem management and incident closure do not match the nature of a standard request.

Question 44Service Request Management value streams, processes, and people (roles and competencies)

Which role is typically accountable for the overall performance and continual improvement of the service request management practice?

  1. The service request management practice owner Correct answer.
  2. The end user raising the request
  3. The supplier delivering the requested component
  4. The change advisory board chair

Explanation

A practice owner is accountable for the practice's effectiveness, its value streams and its continual improvement. Users, suppliers and the change advisory board participate in or govern specific activities but do not own the practice.

Question 45Service Request Management value streams, processes, and people (roles and competencies)

What is the main benefit of automating a high-volume, low-risk service request such as a password reset?

  1. It removes the need for any request model or workflow
  2. It reduces lead time and frees service desk capacity for complex work Correct answer.
  3. It eliminates the need to record the request in the system
  4. It transfers accountability for the request to the user

Explanation

Automation of standard, well-understood requests shortens fulfilment time and allows staff to focus on more complex interactions. It does not remove the need for request models, records, or clear accountability.

Question 46Service Request Management value streams, processes, and people (roles and competencies)

Which competency is most important for a service desk agent handling a wide range of user requests?

  1. Deep specialist knowledge of a single technology platform
  2. Authority to approve all financial expenditure requested by users
  3. Skill in writing detailed root-cause analysis reports
  4. Effective communication and the ability to classify and route requests accurately Correct answer.

Explanation

Front-line request handling depends on clear communication and correct classification so requests reach the right workflow or team. Narrow specialist depth, financial authority and root-cause writing are not the core competencies for this role.

Question 47Service Request Management value streams, processes, and people (roles and competencies)

A user submits a request that is not part of the published service catalogue. What is the most appropriate first step?

  1. Reject it without explanation because it is not catalogued
  2. Clarify the need with the user and determine whether an existing offering or a separate change process applies Correct answer.
  3. Log it as a major incident to escalate visibility
  4. Fulfil it immediately to maintain customer satisfaction

Explanation

Requests outside the catalogue need clarification to see whether an existing offering satisfies the need or whether a change or other process is required. Immediate fulfilment bypasses governance, and silent rejection or major incident escalation misuses other practices.

Question 48Service Request Management value streams, processes, and people (roles and competencies)

Why should service request management capture user satisfaction feedback after fulfilment?

  1. To replace the need for service level reporting
  2. To satisfy a legal requirement in every jurisdiction
  3. To determine which users should be denied future requests
  4. To provide evidence for the continual improvement of request models and the user experience Correct answer.

Explanation

Feedback reveals friction in request models and the user experience, feeding continual improvement. It complements rather than replaces service level reporting and has no role in denying service or meeting a universal legal duty.

Question 49Service Request Management value streams, processes, and people (roles and competencies)

A request model for new-starter IT setup includes steps for account creation, hardware allocation and manager approval. Which element of the model determines the order in which these steps occur?

  1. The knowledge article template
  2. The escalation policy
  3. The service level target
  4. The workflow or sequence of activities Correct answer.

Explanation

A request model defines the workflow, meaning the sequence of activities, dependencies and decision points for that request type. Escalation policy, service level targets and article templates are related but do not define step order.

Question 50Service Request Management value streams, processes, and people (roles and competencies)

During fulfilment of an access request, an agent discovers the requested role grants access to regulated data requiring additional approval. What should the agent do?

  1. Apply the model's additional approval step before provisioning access Correct answer.
  2. Grant the access and note the issue afterwards
  3. Escalate to problem management for a root-cause investigation
  4. Close the request and ask the user to resubmit next quarter

Explanation

Request models should include decision points and approvals for exceptions such as regulated data. Pausing to obtain the required approval preserves compliance, whereas granting first, closing, or misrouting to problem management does not.