Courseiva

ITIL4F Four Dimensions of IT Service Management Practice Question

A mid-sized e-commerce company, ShopFast, operates a 24/7 online store. Their IT service management is based on ITIL 4. Recently, they have been experiencing an increasing number of incidents where customers cannot complete purchases due to payment gateway timeouts. The payment gateway is provided by a third-party vendor, PaySecure. The IT team has checked the internal infrastructure and found no issues; network logs show that requests are reaching PaySecure but responses are delayed. The incident management process is followed, but each incident is handled individually without a systematic approach. The service level agreement (SLA) with PaySecure includes uptime guarantees, but the vendor claims the issue is on ShopFast's side. The IT manager wants to reduce the frequency and impact of these incidents. What is the BEST course of action?

⚠ Common exam trap

A common mix-up: candidates confuse incident management (restoring service quickly) with problem management (preventing recurrence), leading them to choose a reactive option like increasing priority (D) instead of the proactive investigation (A).

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Initiate a problem investigation to identify the root cause and work with PaySecure to implement a permanent solution.

Initiating a problem investigation (Option A) aligns with the ITIL 4 problem management practice, which aims to identify the root cause of recurring incidents. Since the internal infrastructure is healthy and the issue is with a third-party vendor's response delays, a systematic analysis with PaySecure is necessary to uncover the underlying cause (e.g., API timeout thresholds, network latency, or misconfigured retry logic) and implement a permanent fix, reducing incident frequency and impact.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Initiate a problem investigation to identify the root cause and work with PaySecure to implement a permanent solution.

    Why this is correct

    Initiating a problem investigation aligns perfectly with ITIL's Problem Management practice, which aims to identify the underlying root cause of recurring incidents. By systematically analyzing the incidents, ShopFast can pinpoint why the payment gateway issues are happening. Collaborating with PaySecure ensures that any necessary changes, whether in ShopFast's integration or PaySecure's service, are implemented effectively for a permanent resolution, preventing future service disruptions.

  • ✗

    Replace PaySecure with a different payment gateway provider immediately.

    Why it's wrong here

    Replacing a critical service provider like PaySecure immediately is a highly disruptive and risky approach. This action bypasses essential root cause analysis, meaning ShopFast would be acting without understanding if the problem lies with PaySecure, its own systems, or the integration. Such a hasty change introduces significant new integration complexities, potential downtime, and does not guarantee an improved outcome, potentially trading known issues for unknown ones.

  • ✗

    Request PaySecure to improve their service without further analysis.

    Why it's wrong here

    Simply requesting PaySecure to improve their service without conducting a thorough problem investigation is an ineffective and unsubstantiated approach. Without concrete data and identified root causes, ShopFast lacks the evidence to clearly articulate the problem or its origin, making it difficult for PaySecure to act decisively. This approach risks misplacing blame and fails to provide actionable insights for either party to implement a targeted and effective solution.

  • ✗

    Increase the priority of payment-related incidents to ensure faster resolution.

    Why it's wrong here

    Increasing the priority of payment-related incidents is a reactive Incident Management tactic focused solely on minimizing the impact of current service disruptions. While important for immediate service restoration, this action does not address the underlying cause of the recurring payment gateway failures. It merely ensures faster attention to symptoms, leading to an unsustainable cycle of repeated high-priority incidents rather than preventing their occurrence.

About these practice questions

One of 805 original ITIL4F practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This ITIL4F practice question is part of Courseiva's free PeopleCert certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ITIL4F exam.