Examkin

Question

Difficulty: HardConfiguration and Change Management

A network engineering team is drafting a Request for Change (RFC) to deploy automated configuration management scripts across enterprise cloud interconnect routers. Which TWO of the following operational elements must be formally documented within the RFC prior to submitting it to the Change Advisory Board (CAB) for approval?

  1. A detailed risk assessment and impact analysis identifying business dependencies and potential service disruptions during execution.Answer
  2. A comprehensive backout plan detailing specific rollback steps and quantifiable metric thresholds that trigger execution if testing fails.Answer
  3. C
    Results from deploying and executing the script on production routers prior to CAB review to prove script functionality.
  4. D
    A disaster recovery workflow that restores only the most recent incremental configuration file directly without applying the base baseline image.

Answer

The correct elements required in the RFC are a comprehensive risk assessment/impact analysis and a detailed backout plan with predefined rollback triggers.
A formal Request for Change (RFC) submitted to a Change Advisory Board (CAB) must include a thorough risk assessment and impact analysis to quantify potential business disruptions, as well as a rollback plan with explicit metric thresholds defining when to abort and revert the deployment. These components ensure organizational oversight and risk mitigation before production execution.

Step-by-Step Solution

1
Analyze the mandatory components of an enterprise Request for Change (RFC) intended for Change Advisory Board (CAB) evaluation.
Identified that RFCs require risk identification, impact scope, scheduled maintenance windows, sandbox validation, and rollback strategies.
CAB approval relies on understanding business risks and operational recovery procedures before authorizing changes to production systems.
2
Evaluate the risk mitigation and rollback strategy requirement.
Determined that defining specific impact metrics and rollback trigger points ensures clear decision-making during maintenance windows.
Without predefined threshold triggers, engineers might delay rolling back a failed deployment, worsening downtime.
3
Identify operational flaws in distractor options.
Recognized that testing directly in production violates troubleshooting and change management sequencing, and restoring incremental backups out of sequence creates configuration corruption.
Production testing introduces unapproved risk, and incremental restoration requires full baseline restoration first.

Key Concept

RFC Documentation and CAB Approval Requirements
Rate this question

Topics

Configuration and Change Management

More questions from this topic