Change, Capacity, and Continuity
- Explain safe network change and operational resilience
- Apply the idea to evidence from a realistic technology scenario
- Justify a decision using security, reliability, cost, and user impact
Change, Capacity, and Continuity
A change plan states purpose, scope, prerequisites, validation, communication, maintenance window, and rollback. Capacity planning uses growth and peak demand rather than averages alone. Continuity planning identifies critical services and acceptable recovery targets.
Decision lens
Strong technical decisions connect evidence → mechanism → impact → response. Identify what the evidence shows, explain the system behavior that produced it, state the likely effect on people or data, and choose a response that addresses the cause without creating unnecessary disruption.
A firmware update is scheduled during registration with no backup configuration or rollback procedure.
- 1.The timing creates unnecessary business impact.
- 2.Save and verify current configuration and software.
- 3.Test compatibility and define success checks.
- 4.Move to an approved window and prepare rollback plus stakeholder communication.
What should a rollback plan specify?
Which response best demonstrates complete reasoning about safe network change and operational resilience?
For a scenario about safe network change and operational resilience, identify the decisive evidence before naming a response. A defensible conclusion here is: A technically valid update is still a poor operational change when timing, validation, and recovery are missing.
Answer the 2 checkpoints as you read.
Sign in to save your progress