Security software was accidentally uninstalled from all servers in the environment. After requesting the same version of the software be reinstalled, the security analyst learns that a change…

Question

Options

• AOwners can be notified a change is being made and can monitor it for performance impact.
• BA risk assessment can be performed to determine if the software is needed.
• CEnd users can be aware of the scope of the change.
• DA rollback plan can be implemented in case the software breaks an application.

• A
  81% (22)
• B
  4% (1)
• C
  11% (3)
• D
  4% (1)

Explanation

The best reason to follow the change management process in this scenario is so that owners and stakeholders can be formally notified that a change is being made and can actively monitor their systems for any performance impact or unexpected behavior during and after the reinstallation. Change management ensures visibility, accountability, and coordination across teams. Performing a risk assessment to determine if the software is needed (B) is not the primary driver here - the software's necessity is already known. End users typically do not need to be informed of server-side security software changes (C). A rollback plan (D) is a component of change management, but the question asks for the best reason to follow the process in this specific scenario, which is stakeholder notification and performance monitoring.

No community discussion yet for this question.