Which NCPI management technique specifically addresses the challenge of maintaining spare equipment at compatible firmware revision levels to avoid downtime?

Question

Options

• AChange management
• BCapacity management
• CReliability management
• DAvailability management

• A
  86% (24)
• B
  4% (1)
• C
  7% (2)
• D
  4% (1)

Explanation

Change management is correct because it governs the controlled process of tracking and coordinating modifications across your infrastructure - including ensuring that spare/replacement equipment mirrors the firmware revision of the live equipment it may replace. If a spare sits on a shelf running an older firmware version incompatible with the current environment, a hot-swap could cause immediate downtime; change management prevents this by requiring spares to be updated in lockstep with production changes.

• Capacity management (B) is wrong because it focuses on planning and allocating physical resources (power, cooling, rack space) to meet current and future demand - not on version control of components.
• Reliability management (C) is wrong because it addresses mean-time-between-failure, redundancy design, and component quality to reduce the probability of failure - not firmware revision alignment.
• Availability management (D) is wrong because it focuses on meeting uptime SLAs and minimizing recovery time after a failure - it measures outcomes, whereas change management controls the process that keeps spares ready.

Memory tip: Whenever you see "revision," "version," or "firmware level" in an NCPI question, map it to Change - because changes (including firmware updates) must be tracked and applied consistently to both active and spare equipment.

No community discussion yet for this question.