Which process aims to prevent incidents resulting from changes to the IT infrastructure?

Question

Options

• AAvailability Management
• BChange Management
• CIncident Management
• DProblem Management

• A
  5% (3)
• B
  81% (47)
• C
  3% (2)
• D
  10% (6)

Explanation

Change Management is the process explicitly designed to control modifications to the IT infrastructure in a way that minimizes the risk of disruption. Its core goal is to ensure every change is assessed, approved, and implemented in a controlled manner - directly targeting the prevention of change-induced incidents.

Why the distractors are wrong:

• A. Availability Management focuses on ensuring services meet agreed uptime targets; it monitors and plans for availability but does not govern how changes are made.
• C. Incident Management is reactive - it restores service after an incident has already occurred, not before.
• D. Problem Management identifies root causes of recurring incidents to prevent future ones, but it addresses existing problems rather than controlling incoming changes.

Memory tip: Think of Change Management as the "gatekeeper" - every change must pass through it before touching production. If a change skips the gate, incidents follow. The other three processes deal with availability targets, active outages, and root causes - none of which involve approving changes before they happen.

No community discussion yet for this question.