SK0-005 · Question #48
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…
The correct answer is A. To keep track of software changes on servers B. To minimize unapproved outages or downtime. A change management plan is crucial for tracking all software changes on servers and for minimizing unapproved outages or downtime by enforcing structured review, testing, and rollback procedures.
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.)
Options
- ATo keep track of software changes on servers
- BTo minimize unapproved outages or downtime
- CTo enforce all technical personnel do paperwork
- DTo enable management to track hours worked.
- ETo make sure servers never get rebooted.
How the community answered
(51 responses)- A92% (47)
- C2% (1)
- D4% (2)
- E2% (1)
Why each option
A change management plan is crucial for tracking all software changes on servers and for minimizing unapproved outages or downtime by enforcing structured review, testing, and rollback procedures.
A primary reason for change management is to provide a comprehensive record of all modifications made to server software and configurations, which is essential for auditing, compliance, and effective troubleshooting.
By mandating careful review, testing in staging environments, and clearly defined install/uninstall steps, change management significantly reduces the risk of unexpected service disruptions and outages caused by ill-conceived or untested changes.
While change management involves documentation, its main purpose is to manage risk and ensure stability, not merely to enforce paperwork on technical personnel.
Tracking hours worked is related to project management or human resources, not a core objective of IT change management itself.
It is unrealistic to expect servers to never be rebooted, as patches and maintenance often require restarts; change management aims to manage these reboots safely, not to prevent them entirely.
Concept tested: IT change management principles
Topics
Community Discussion
No community discussion yet for this question.