ITIL4-CDS Create, Deliver and Support Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Increase the database pool limit without investigating the root cause

  Why it's wrong here

  Simply increasing the pool limit acts as a temporary patch that may mask a deeper performance issue. Without investigating why connections are being exhausted, the underlying problem—such as connection leaks or inefficient queries—remains, likely leading to another failure even with a larger limit in place.

• ✓

  Restore service and perform a root cause analysis to prevent recurrence

  Why this is correct

  Restoring service is the primary goal to minimize user impact. However, CDS emphasizes the importance of learning from incidents. By performing a root cause analysis, the team identifies the source of the exhaustion, allowing them to implement a sustainable fix that improves long-term service reliability and performance.

• ✗

  Restart the database server to clear the connection pool immediately

  Why it's wrong here

  Restarting the database is a reactive measure that clears current connections but does not solve the underlying defect. If the application logic continues to exhaust connections, the problem will return shortly after the restart. This approach fails to address the root cause and provides only temporary relief.

• ✗

  Wait for the automated retry mechanism to succeed eventually

  Why it's wrong here

  Depending on automated retries when the system is already at capacity can exacerbate the issue by increasing traffic. If the pool is exhausted, retries will likely fail repeatedly. Proactive intervention is required to stabilize the environment rather than relying on a mechanism that has already failed three times.