When presented with a server issue, how should an action plan for resolution be formulated?

Question

Options

• ABased on the most recent server trends
• BBy randomly replacing server components
• CAccording to the severity and impact of the issue
• DSolely based on the aesthetics of the solution

• B
  3% (1)
• C
  95% (36)
• D
  3% (1)

Explanation

Formulating an action plan according to severity and impact (C) ensures resources are allocated efficiently - critical outages affecting many users demand immediate escalation, while minor issues can follow standard procedures. Option A fails because trends describe patterns over time, not the specific nature of the current incident. Option B is dangerous and wasteful, as randomly swapping components could worsen the problem and introduces unnecessary downtime. Option D is irrelevant to technical resolution - aesthetics have no bearing on fixing infrastructure failures.

Memory tip: Think "triage first" - just like emergency rooms prioritize patients by urgency, IT incident response prioritizes by severity (how bad?) and impact (how many affected?). That framing maps directly to option C.

No community discussion yet for this question.