SK0-004 · Question #403
A server administrator is notified of an OS hot fix for a production server. Which of the following BEST represent how the hot fix should be applied? (Choose two.)
The correct answer is A. The hot fix should be applied after testing in a non-production environment C. The hot fix should be applied after following proper change management procedures. Hot fixes for production servers must be tested in a non-production environment first and applied through formal change management to reduce the risk of service disruption.
Question
A server administrator is notified of an OS hot fix for a production server. Which of the following BEST represent how the hot fix should be applied? (Choose two.)
Options
- AThe hot fix should be applied after testing in a non-production environment
- BThe hot fix should be applied when it is released from the vendor
- CThe hot fix should be applied after following proper change management procedures
- DThe hot fix should be applied after testing in a production environment
- EThe hot fix should be applied once it has been superseded
How the community answered
(14 responses)- A79% (11)
- D7% (1)
- E14% (2)
Why each option
Hot fixes for production servers must be tested in a non-production environment first and applied through formal change management to reduce the risk of service disruption.
Testing in a non-production environment first validates that the hot fix does not introduce instability, compatibility issues, or unexpected behavior before it affects live systems. This step is critical in patch management because hot fixes can conflict with existing software configurations, and discovering issues in production can lead to costly downtime.
Applying a hot fix immediately upon vendor release bypasses required testing and change approval processes, creating unnecessary risk to production stability.
Change management procedures require that any modification to a production system go through a formal approval, scheduling, and documentation process before implementation. Following these procedures ensures the hot fix is applied during a scheduled maintenance window, with a tested rollback plan in place and all stakeholders informed.
Testing in a production environment puts live services and data at risk and violates standard IT change management practices.
Waiting until a hot fix is superseded leaves the system exposed to the vulnerability the fix addresses for an unnecessarily long period.
Concept tested: Patch management and change control for production servers
Source: https://csrc.nist.gov/pubs/sp/800/40/r4/final
Topics
Community Discussion
No community discussion yet for this question.