Examkin

Question

Difficulty: Very hardConfiguration and Change Management

An enterprise network engineering team is preparing a formal Request for Change (RFC) to modify core switch configurations and re-architect VLAN trunking across multiple datacenters. To adhere strictly to enterprise configuration and change management standards, which of the following components MUST be included within the submitted RFC prior to presenting it to the Change Advisory Board (CAB) for evaluation? (Select TWO.)

  1. A detailed rollback plan specifying precise abort triggers and step-by-step restoration proceduresAnswer
  2. A comprehensive risk and impact assessment outlining potential service disruptions and mitigation controlsAnswer
  3. C
    Implementation of the configuration changes on a live production switch to establish a baseline prior to CAB review
  4. D
    A full system recovery strategy relying solely on incremental backup files without validating baseline state

Answer

The Request for Change (RFC) must include a detailed rollback plan with explicit abort triggers and a comprehensive risk and impact assessment detailing service exposure.
A formal Request for Change (RFC) requires both a comprehensive risk and impact assessment to evaluate business risk and a detailed rollback procedure specifying exact conditions under which the change must be aborted and reverted.

Step-by-Step Solution

1
Analyze RFC documentation requirements
Identify mandatory sections required prior to CAB submission, including impact scope, business justification, maintenance window parameters, and contingency planning.
An RFC must provide complete visibility into the risk exposure and operational safety nets of a proposed network change.
2
Evaluate risk and impact assessment necessity
Confirm that an impact analysis evaluates how the change affects dependent applications, network links, and business operations during and after maintenance.
CAB members rely on risk assessments to approve scheduling windows and assess organizational risk.
3
Evaluate rollback plan necessity
Confirm that a rollback plan defines precise quantitative criteria (e.g., latency spikes, packet loss thresholds) for aborting the deployment and restoring original state.
Without a validated rollback plan, unforeseen errors in production could lead to prolonged unrecoverable outages.

Key Concept

Request for Change (RFC) Mandatory Components
Rate this question

Topics

Configuration and Change Management

More questions from this topic