A technician is working on a virtual server migration project. The technician has already completed the SOW; however, the servers will not work without a critical network configuration that was…

Question

Options

• AObtain end-user acceptance for the proposed changes and submit a change plan for additional
• BSubmit the changes to the change board for approval.
• CNotify the change team of the changes needed and perform the changes.
• DEscalate to stakeholders and obtain override approval for out-of-scope changes.
• EDocument the changes and perform the work.

• A
  3% (1)
• B
  3% (1)
• C
  9% (3)
• D
  19% (6)
• E
  66% (21)

Explanation

When a configuration is critical and was inadvertently omitted from the original SOW-meaning the project cannot succeed without it-the practical best practice is to document the out-of-scope changes (creating an audit trail and accountability) and then perform the necessary work to complete the project. Submitting to a change board or escalating to stakeholders introduces delays that may be unacceptable when production servers are non-functional. Documentation ensures the deviation is recorded and can be reviewed, satisfying change management requirements without blocking critical work.

No community discussion yet for this question.