ITIL 4 MSF study materials
ITIL 4 MSF study resources

ITIL 4 MSF practice questions

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

First 50 of 200 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 1Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

In ITIL 4, which practice owns the day-to-day handling of user-initiated requests such as password resets and standard access provisioning?

  1. Service request management Correct answer.
  2. Incident management
  3. Problem management
  4. Service desk

Explanation

Service request management handles user-initiated requests, many of which are standard and pre-approved, and moves them through a defined workflow. The service desk is the entry point that captures requests, but the practice that structures and fulfils them is service request management.

Question 2Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A service desk analyst receives a call that the payroll application is returning errors for all users. Which practice is primarily engaged to restore the service as quickly as possible?

  1. Capacity and performance management
  2. Incident management Correct answer.
  3. Change enablement
  4. Service level management

Explanation

Incident management is the practice that restores normal service operation as quickly as possible after an unplanned interruption or degradation. Restoring service takes priority over finding the root cause, which is handled later by problem management.

Question 3Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

What distinguishes a 'problem' from an 'incident' in ITIL 4 terminology?

  1. A problem is a cause, or potential cause, of one or more incidents Correct answer.
  2. A problem is a request that requires a formal change record
  3. A problem is any incident that affects more than one user
  4. A problem is an incident that breaches the service level agreement

Explanation

A problem is defined as a cause, or potential cause, of one or more incidents, so it addresses the why rather than the symptom. An incident is the actual unplanned interruption or degradation experienced by users.

Question 4Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which statement best describes the purpose of the service desk practice?

  1. It captures demand for incident resolution and service requests at the point of contact Correct answer.
  2. It authorises changes to production services
  3. It investigates the root cause of recurring failures
  4. It negotiates and agrees service targets with customers

Explanation

The service desk is the single point of contact that captures demand for incident resolution and service requests. It records, triages, and channels work but does not itself negotiate targets, authorise changes, or perform root-cause investigation.

Question 5Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

An organisation wants to reduce the volume of repeat incidents by identifying and removing their underlying causes. Which practice delivers this outcome?

  1. Service request management
  2. Incident management
  3. Continual improvement
  4. Problem management Correct answer.

Explanation

Problem management aims to reduce the likelihood and impact of incidents by identifying actual and potential causes and managing workarounds and known errors. Incident management restores service but does not pursue root causes.

Question 6Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A major incident has been declared. What is the most appropriate immediate focus for the incident management team?

  1. Closing the incident record to keep the backlog low
  2. Raising a change request for a permanent fix before restoring service
  3. Completing a full root-cause analysis before any recovery action
  4. Restoring service within the agreed target and communicating status to stakeholders Correct answer.

Explanation

Incident management prioritises restoring normal service as quickly as possible, and major incidents demand coordinated communication with stakeholders. Root-cause analysis and permanent fixes follow once service is restored.

Question 7Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which is the correct sequence of activities in the incident management workflow?

  1. Log and categorise, resolve, diagnose, prioritise, close
  2. Log and categorise, prioritise, diagnose, escalate if needed, resolve, close Correct answer.
  3. Prioritise, log and categorise, close, resolve, diagnose
  4. Diagnose, close, log and categorise, resolve, escalate

Explanation

Incident management proceeds from logging and categorisation through prioritisation and diagnosis, with escalation when required, then resolution and closure. Logging must precede prioritisation because priority depends on recorded impact and urgency.

Question 8Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

How is incident priority determined in ITIL 4 guidance?

  1. From the number of users in the affected department
  2. From the combination of impact and urgency Correct answer.
  3. From the time remaining before the next service review
  4. From the seniority of the person reporting the incident

Explanation

Priority is derived from impact and urgency, which together indicate how quickly the incident must be resolved. Impact reflects the business effect, while urgency reflects how quickly the business needs resolution.

Question 9Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A user requests a new laptop with a standard build for a new starter. The request matches a pre-approved catalogue item. What is the most efficient handling approach?

  1. Log it as an incident because hardware is missing
  2. Fulfil it through the standard service request workflow without a separate change authorisation Correct answer.
  3. Raise a normal change for the procurement and build
  4. Escalate it to problem management as a known error

Explanation

Pre-approved catalogue items are handled through the service request management workflow, which is designed for low-risk, repeatable requests. Because the item is already authorised in the catalogue, a separate change record is not required.

Question 10Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

What is the key difference between a workaround and a permanent fix in problem management?

  1. A workaround permanently removes the root cause
  2. A workaround is recorded as a change and requires CAB approval
  3. A workaround is only used for service requests
  4. A workaround reduces or eliminates the impact while the root cause remains unresolved Correct answer.

Explanation

A workaround reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available. The root cause remains until a permanent fix is identified and implemented.

Question 11Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

An incident is resolved by a first-line analyst using a documented workaround from the known error database. What should happen next?

  1. The known error record is updated and the problem record remains open until a permanent fix is found Correct answer.
  2. The problem record is closed because the user is working again
  3. The workaround is deleted to prevent reuse
  4. The incident is reclassified as a service request

Explanation

Applying a workaround restores service but does not eliminate the root cause, so the problem record stays open until a permanent resolution is implemented. The known error record should be updated with what was learned.

Question 12Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which practice ensures that changes to services are assessed, authorised, and scheduled in a controlled way?

  1. Service configuration management
  2. Deployment management
  3. Release management
  4. Change enablement Correct answer.

Explanation

Change enablement maximises the number of successful service and product changes by assessing risk, authorising changes, and managing the change schedule. Release and deployment practices move changes into live use but do not authorise them.

Question 13Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A change is low-risk, well-understood, and follows a documented procedure that has been pre-authorised. Which change type does this describe?

  1. Standard change Correct answer.
  2. Emergency change
  3. Normal change
  4. Major change

Explanation

A standard change is a low-risk, pre-authorised change that follows a defined procedure and does not require individual authorisation each time. Normal and emergency changes require assessment and authorisation per instance.

Question 14Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

What is the primary purpose of a configuration management database (CMDB) within service configuration management?

  1. To schedule staff shifts for the service desk
  2. To hold configuration records and the relationships between configuration items Correct answer.
  3. To capture customer satisfaction survey results
  4. To store the full text of all resolved incidents

Explanation

The CMDB stores configuration records for configuration items and the relationships between them, supporting impact analysis and other practices. It is not a repository for incident text, survey data, or rosters.

Question 15Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A service desk analyst cannot resolve an incident within the agreed time and lacks the authority or knowledge to proceed. What is the appropriate action?

  1. Escalate the incident to the next support level with the information gathered so far Correct answer.
  2. Reclassify the incident as a problem and stop work
  3. Wait until the user calls again before taking any action
  4. Close the incident and ask the user to call back later

Explanation

Functional escalation moves an incident to a team with greater expertise or authority when the current level cannot resolve it. The record should carry the diagnostic information already gathered so effort is not repeated.

Question 16Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which statement accurately describes the relationship between incident management and problem management?

  1. Both practices exist only to fulfil standard service requests
  2. Incident management restores service, while problem management investigates causes that incidents reveal Correct answer.
  3. Incident management owns the change schedule that problem management uses
  4. Problem management restores service, while incident management investigates causes

Explanation

Incident management focuses on restoring service quickly, and problem management uses incident data to find and remove underlying causes. The two practices cooperate, but their objectives and timescales differ.

Question 17Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

What is the main benefit of resolving a high proportion of incidents at first line?

  1. Elimination of the need for problem management
  2. Removal of the need for a known error database
  3. Faster restoration for users and lower overall cost of support Correct answer.
  4. Guaranteed compliance with all service level targets

Explanation

First-line resolution restores service sooner for users and reduces the cost of escalating work to more specialised teams. It does not remove the need for problem management or guarantee every service level target.

Question 18Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A problem has been diagnosed and a permanent fix identified, but implementing it requires modifying a live production service. How should this be handled?

  1. The problem manager applies the fix directly without any authorisation
  2. The fix is deferred until the next incident occurs
  3. The fix is implemented through change enablement so risk is assessed and authorised Correct answer.
  4. The fix is logged as a service request and fulfilled by the service desk

Explanation

Implementing a permanent fix alters a live service, so it must pass through change enablement for risk assessment, authorisation, and scheduling. Problem management identifies the fix but does not bypass change control.

Question 19Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which activity belongs to the 'resolve' stage rather than the 'diagnose' stage of incident handling?

  1. Reviewing recent changes for a likely cause
  2. Applying the identified recovery action and confirming the user can work again Correct answer.
  3. Gathering symptoms and establishing the extent of the failure
  4. Identifying which component is failing

Explanation

Diagnosis establishes what is wrong and why, while resolution applies the recovery action and confirms service is restored. Symptom gathering, component identification, and change review are diagnostic activities.

Question 20Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

An organisation defines a 'known error' record. Which content is essential to that record?

  1. A description of the problem and the workaround, where one exists Correct answer.
  2. The purchase order number for replacement hardware
  3. The customer satisfaction score for the last survey
  4. The name of the user who first reported the symptom

Explanation

A known error record documents a problem that has a documented root cause and a workaround, enabling faster future diagnosis and restoration. Reporter identity, procurement references, and survey scores are not defining content.

Question 21Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A service desk is designing its channels so that users can log incidents by phone, chat, portal, and email, with consistent recording regardless of channel. Which principle should guide this design?

  1. Each channel should maintain its own separate queue and records
  2. All channels should feed a single point of contact with consistent logging and ownership Correct answer.
  3. Channels should be added without updating the knowledge base
  4. Only telephone contact should be supported for incidents

Explanation

The service desk acts as a single point of contact, so requests and incidents from every channel should be captured consistently with clear ownership. Fragmented queues undermine visibility, reporting, and user experience.

Question 22Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Analysis shows that a small number of recurring incidents account for a large share of service desk effort. Which approach best reflects ITIL 4 guidance for addressing this?

  1. Convert the recurring incidents into standard changes without analysis
  2. Suppress the recurring incidents from reporting to reduce visible volumes
  3. Increase first-line headcount to absorb the recurring volume indefinitely
  4. Prioritise problem management effort on the high-impact recurring incidents and track the reduction in repeat incidents Correct answer.

Explanation

Problem management should be prioritised using impact, urgency, and recurrence so effort targets the causes that matter most, with metrics showing reduced repeat incidents. Absorbing or hiding the volume leaves the cause in place.

Question 23Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A major incident review finds that responders lacked a current support matrix and wasted time finding the right team. Which improvement most directly strengthens incident management?

  1. Remove escalation paths to simplify the process
  2. Increase the number of severity levels to twelve
  3. Require all incidents to be resolved by problem management
  4. Maintain and publish an up-to-date escalation and support matrix used during major incidents Correct answer.

Explanation

Clear, current escalation paths and responsibilities let responders engage the right team quickly during major incidents. Removing paths, over-complicating severity levels, or rerouting all work adds delay rather than reducing it.

Question 24Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which pair of metrics best indicates whether problem management is delivering value?

  1. Number of changes rejected and number of releases deployed
  2. Reduction in the number and impact of recurring incidents, and the proportion of problems with a permanent resolution Correct answer.
  3. Number of calls answered per hour and average call duration
  4. Number of catalogue items published and portal logins

Explanation

Problem management value is shown by fewer and less impactful recurring incidents and by progress from workaround to permanent resolution. Call handling, change, release, and catalogue metrics measure other practices.

Question 25Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A service request workflow repeatedly stalls because approvals are sought from managers who are often unavailable. Which redesign best aligns with service request management principles?

  1. Route all stalled requests to problem management for investigation
  2. Remove the catalogue and handle every request as a normal change
  3. Pre-authorise low-risk catalogue items and reserve individual approval for higher-risk requests Correct answer.
  4. Require two manager approvals for every request to improve control

Explanation

Service request management should streamline fulfilment of standard, pre-approved items while keeping proportionate control for higher-risk requests. Adding approvals to everything increases delay without improving risk management.

Question 26Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

In ITIL 4, which practice owns the responsibility for understanding the needs of users and ensuring that the service provider is able to meet those needs across all engagement channels?

  1. Incident management
  2. Relationship management
  3. Service desk Correct answer.
  4. Service request management

Explanation

The service desk practice is defined as the practice that captures demand for incident resolution and service requests, acting as the single point of contact between the service provider and users. It focuses on understanding user needs and translating them into appropriate engagement channels and support capability.

Question 27Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A service desk wants to record every interaction in a consistent way regardless of channel, so that reporting is comparable. Which design consideration from the service desk practice best supports this?

  1. Offering more channels than competitors
  2. Routing all contacts to a single senior analyst
  3. Removing self-service to force human contact
  4. Standardising data capture and taxonomy across all channels Correct answer.

Explanation

The service desk practice emphasises consistent data capture and a common taxonomy so that contacts from different channels can be compared, analysed and reported. Channel variety only delivers value when the underlying record structure is consistent.

Question 28Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which statement best describes the purpose of the incident management practice in ITIL 4?

  1. To ensure that all user requests are approved by the correct budget holder
  2. To maintain accurate records of configuration items and their relationships
  3. To minimise the negative impact of incidents by restoring normal service operation as quickly as possible Correct answer.
  4. To maximise the number of changes deployed per release

Explanation

Incident management exists to reduce the adverse impact of incidents on the organisation by returning service to its normal operating state as quickly as practicable. It is not concerned with change volume, budget approval or asset records.

Question 29Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

An analyst receives a report that a payroll service is unavailable for all users. The analyst confirms the impact, logs the incident and assigns a priority. Which activity should follow next in the incident workflow?

  1. Formal problem investigation and root cause analysis
  2. Closure with a customer satisfaction survey
  3. Diagnosis and, where possible, resolution of the incident Correct answer.
  4. Immediate escalation to the change advisory board

Explanation

After logging and prioritising, incident handling proceeds to diagnosis and resolution, using known error information and support tools where available. Problem investigation and change authorisation happen only if the incident cannot be resolved and requires them.

Question 30Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which practice is responsible for managing the full lifecycle of service requests, including their logging, approval and fulfilment?

  1. Service level management
  2. Service request management Correct answer.
  3. Incident management
  4. Problem management

Explanation

Service request management supports the agreed quality of a service by handling all pre-defined, user-initiated service requests in an effective and user-friendly manner. It covers logging, approval, fulfilment and closure of those requests.

Question 31Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A service request for access to a finance reporting tool requires approval from the data owner, who is on leave for two weeks. What is the most appropriate design improvement for the service request management practice?

  1. Cancel the request and ask the user to reapply later
  2. Route all such requests to the service desk manager for personal approval
  3. Convert the request into an incident so it is handled faster
  4. Define pre-authorised approval rules and delegation so that requests do not stall Correct answer.

Explanation

Service request management should design request models that include clear approval rules, delegation and pre-authorisation so fulfilment is not blocked by individual availability. This keeps requests predictable and efficient.

Question 32Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

In ITIL 4, what is the main purpose of the problem management practice?

  1. To provide a single point of contact for users reporting issues
  2. To define and monitor agreed service levels with customers
  3. To authorise and schedule changes to production services
  4. To reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents Correct answer.

Explanation

Problem management aims to reduce the likelihood and impact of incidents by identifying actual and potential causes, and by managing workarounds and known errors. It addresses causes rather than individual symptoms.

Question 33Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which three phases make up the problem management workflow in ITIL 4?

  1. Plan, do, check
  2. Problem identification, problem control, error control Correct answer.
  3. Log, escalate, close
  4. Detect, restore, review

Explanation

ITIL 4 describes problem management as comprising problem identification, problem control and error control. Identification detects problems, control investigates and analyses them, and error control manages known errors and their workarounds.

Question 34Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A known error has been documented but no permanent fix is yet available. What is the appropriate treatment of the related incidents while the error remains open?

  1. Reopen each incident as a new problem record
  2. Suspend all related services until a fix is delivered
  3. Apply the documented workaround and link incidents to the known error Correct answer.
  4. Escalate every occurrence directly to the change advisory board

Explanation

Where a known error exists, the documented workaround should be applied to restore service, and incidents should be linked to the known error so that frequency and impact can be tracked. This is the essence of error control.

Question 35Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which practice ensures that risks are properly assessed, authorising changes and managing the change schedule in ITIL 4?

  1. Change enablement Correct answer.
  2. Service configuration management
  3. Release management
  4. Deployment management

Explanation

Change enablement maximises the number of successful service and product changes by ensuring risks are properly assessed, authorising changes, and managing the change schedule. It is the authority for whether a change proceeds.

Question 36Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A change has been assessed as low risk and follows a documented, pre-authorised procedure. Which change enablement concept allows it to proceed without individual authorisation each time?

  1. Standard change Correct answer.
  2. Emergency change
  3. Normal change
  4. Major change

Explanation

A standard change is a low-risk, pre-authorised change that follows a defined procedure and does not require individual authorisation on each occasion. This allows routine work to flow without unnecessary change authority involvement.

Question 37Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which statement best describes the purpose of the service configuration management practice?

  1. To negotiate service level targets with customers and report against them
  2. To manage the pipeline of work items through to completion
  3. To restore normal service operation after an unplanned interruption
  4. To ensure that accurate and reliable information about the configuration of services and the configuration items that support them is available when and where it is needed Correct answer.

Explanation

Service configuration management ensures accurate and reliable configuration information, including configuration items and their relationships, is available when and where needed. This supports other practices such as incident, problem and change management.

Question 38Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A configuration management database shows that a server supports three applications, but an incident investigation reveals it supports five. What is the most significant consequence for the incident management practice?

  1. Impact assessment during incidents may be wrong, leading to delayed or misdirected resolution Correct answer.
  2. Incident priority will automatically be recalculated correctly
  3. Service level agreements will be renegotiated
  4. The change schedule will be automatically updated

Explanation

Accurate configuration information underpins impact assessment and the identification of affected users and services during incidents. If relationships are wrong, responders may underestimate impact and involve the wrong teams, slowing resolution.

Question 39Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

In ITIL 4, which practice is described as the entry point and single point of contact for the service provider with all of its users?

  1. Supplier management
  2. Service level management
  3. Continual improvement
  4. Service desk Correct answer.

Explanation

The service desk practice is described as the entry point and single point of contact for the service provider with all of its users. It captures demand and coordinates resolution and fulfilment activities.

Question 40Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which metric pair most directly indicates whether a service desk is meeting its objective of restoring service quickly?

  1. Number of suppliers onboarded and supplier satisfaction
  2. Mean time to restore service and percentage of incidents resolved at first line Correct answer.
  3. Number of changes deployed and number of releases
  4. Number of improvements logged and number of audits completed

Explanation

Mean time to restore service reflects how quickly normal operation is recovered, while the proportion of incidents resolved at first line reflects the desk's capability to resolve without onward escalation. Together they indicate service desk effectiveness.

Question 41Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which practice provides the framework for negotiating, agreeing and monitoring service levels between the provider and its customers?

  1. Relationship management
  2. Incident management
  3. Service level management Correct answer.
  4. Service request management

Explanation

Service level management sets clear business-based targets for service levels and ensures delivery against them through measurement and reporting. It is the practice that formalises agreed service commitments.

Question 42Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A service desk analyst needs to escalate an incident to a technical team but does not know which team owns the affected component. Which practice should provide this information?

  1. Supplier management, through contract records
  2. Continual improvement, through improvement registers
  3. Service configuration management, through recorded relationships between configuration items and support groups Correct answer.
  4. Service request management, through the request catalogue

Explanation

Service configuration management maintains configuration items and their relationships, which can include ownership and support group information. This allows incidents to be routed to the correct resolving team quickly.

Question 43Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which statement best captures the relationship between the 'monitor' and 'support and fulfil' activities in the service value chain context of this domain?

  1. Monitoring is performed exclusively by the service desk
  2. Monitoring is only performed after all incidents are closed
  3. Support and fulfilment activities replace the need for monitoring
  4. Monitoring detects conditions and events that trigger support and fulfilment activities Correct answer.

Explanation

Monitoring detects events and conditions such as failures or threshold breaches, which then trigger support and fulfil activities such as incident handling or request fulfilment. Detection and response are linked but distinct.

Question 44Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

An event indicates that disk usage on a production server has crossed a defined threshold but service is not yet affected. How should this event be handled?

  1. Raise a major incident immediately
  2. Treat it as a warning that may require action before it becomes an incident Correct answer.
  3. Close it without action because users are unaffected
  4. Log it as a service request for a new server

Explanation

Events that breach thresholds but have not yet affected service are typically warnings that prompt investigation or proactive action. Escalating to a major incident is premature and would distort priority and reporting.

Question 45Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which practice manages the relationship between the organisation and its suppliers, including their performance and contracts?

  1. Service level management
  2. Supplier management Correct answer.
  3. Incident management
  4. Change enablement

Explanation

Supplier management ensures that the organisation's suppliers and their performance are managed appropriately to support the seamless provision of quality products and services. It covers contracts, performance and relationships with third parties.

Question 46Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A recurring incident affects a supplier-provided component, and the supplier's response times are consistently below the agreed contract. Which combination of practices should be engaged?

  1. Change enablement and release management only
  2. Continual improvement and relationship management only
  3. Problem management to investigate the recurring cause and supplier management to address the supplier's performance Correct answer.
  4. Service request management and service level management only

Explanation

Recurring incidents point to an underlying problem that problem management should investigate, while poor supplier performance falls within supplier management. Addressing both the cause and the contractual performance is necessary.

Question 47Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

Which activity is most characteristic of the 'support and fulfil' area rather than the 'monitor' area?

  1. Recording the availability of a network link
  2. Correlating events from multiple monitoring tools
  3. Fulfilling a user's request for a software licence Correct answer.
  4. Detecting a threshold breach through automated tooling

Explanation

Support and fulfil activities include handling incidents and fulfilling service requests on behalf of users. Detecting, correlating and recording events are monitoring activities.

Question 48Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A service desk is deciding how to handle a high volume of password reset requests. Which approach best reflects good service request management design?

  1. Treat each password reset as a problem record
  2. Reject the requests and instruct users to remember passwords
  3. Create a standard, automated request model with appropriate identity verification Correct answer.
  4. Handle each request manually to retain personal contact

Explanation

Service request management favours pre-defined request models, and routine low-risk requests such as password resets are ideal candidates for automation with adequate identity verification. This reduces cost and improves speed and consistency.

Question 49Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

A major incident has been resolved and normal service restored. Which activity should occur before the incident record is formally closed?

  1. Deletion of all related event records
  2. Confirmation with the user that service is restored and that the record is accurate Correct answer.
  3. Immediate implementation of a permanent fix through an emergency change
  4. Reclassification of the incident as a service request

Explanation

Incident closure requires confirmation that the user considers the incident resolved and that the record captures the necessary detail. Permanent fixes go through change enablement separately and are not a precondition for closure.

Question 50Monitor, Support and Fulfil (syllabus domains not enumerated in the cited source)

An organisation wants to reduce the number of incidents caused by repeated misconfiguration of a widely used application. Which practice combination is most directly relevant to preventing recurrence?

  1. Supplier management and relationship management
  2. Continual improvement and service level management
  3. Service request management and service desk
  4. Problem management to identify the cause and change enablement to control the corrective change Correct answer.

Explanation

Problem management identifies and analyses the underlying cause of recurring incidents, and change enablement ensures that the corrective change is assessed, authorised and scheduled safely. Together they prevent recurrence rather than repeatedly restoring service.