A server that has been in production for a year needs to be patched. Management enforces a strict policy to be followed on all production servers. The policy stipulates the following for all change management:

Changes must be reviewed and accepted by a change committee. Changes must be made on development/staging servers two weeks before being made on production servers. Changes must have install and uninstall steps in case of issues. Which of the following are the BEST reasons to have a change management plan in place? (Choose two.)

Question

A server that has been in production for a year needs to be patched. Management enforces a strict policy to be followed on all production servers. The policy stipulates the following for all change management:

Changes must be reviewed and accepted by a change committee. Changes must be made on development/staging servers two weeks before being made on production servers. Changes must have install and uninstall steps in case of issues. Which of the following are the BEST reasons to have a change management plan in place? (Choose two.)

Accepted Answer

A. To keep track of software changes on servers Tracking all software changes - including what was modified, when, and by whom - is a foundational goal of change management, enabling audits, rollbacks via defined uninstall steps, and consistent accountability across all production servers. B. To minimize unapproved outages or downtime By requiring change committee review, staging validation two weeks before production, and documented rollback procedures, change management directly reduces the risk of untested or unauthorized changes causing unplanned service outages.

Answer

C. To enforce all technical personnel do paperwork Generating paperwork is an administrative byproduct of documentation requirements, not a technical or operational objective - the goal is risk reduction, not bureaucratic compliance.

Answer

D. To enable management to track hours worked. Change management does not function as a workforce or time-tracking system; its scope is limited to controlling and documenting modifications to IT infrastructure.

Answer

E. To make sure servers never get rebooted. Preventing all server reboots is not a feasible or intended goal - reboots are often required for patching, and change management governs when and how they are performed, not whether they ever occur.

A server that has been in production for a year needs to be patched. Management enforces a strict policy to be followed on all production servers. The policy stipulates the following for all change…

Question

Options

How the community answered

Why each option

Topics

Community Discussion