Input from other Service Management processes is required to keep the IT service continuity plan current Which process has the most to contribute?

Question

Options

• AChange management
• BAvailability management
• CFinancial management for IT services
• DProblem management

• A
  73% (22)
• B
  13% (4)
• C
  3% (1)
• D
  10% (3)

Explanation

Change Management (A) is correct because every approved change to IT infrastructure, configurations, or services can render an existing continuity plan inaccurate or unworkable - recovery procedures may reference systems, topologies, or capabilities that no longer exist. Since Change Management acts as the mandatory gateway for all significant changes to the IT environment, it naturally generates the most frequent and impactful input needed to keep continuity plans aligned with reality.

Availability Management (B) is closely related but focuses on keeping services running under normal conditions, not recovering from major disruptions - it contributes some input but plays a supporting, not primary, role. Financial Management (C) handles budgeting and charging for IT services; it rarely generates information that directly affects how continuity plans are structured or updated. Problem Management (D) can surface vulnerabilities that inform continuity planning, but it doesn't systematically trigger plan updates the way Change Management does.

Memory tip: Think "Change breaks Continuity plans" - whenever something changes in your IT environment (hardware, software, architecture), your disaster recovery and continuity procedures must be reviewed. Change Management owns that change pipeline, so it owns the continuity plan update trigger.

No community discussion yet for this question.