CAS-002 · Question #3
Several critical servers are unresponsive after an update was installed. Other computers that have not yet received the same update are operational, but are vulnerable to certain buffer overflow…
The correct answer is D. Distributed patch management system where all updates are tested in a lab environment. Testing patches in a lab environment before deploying to production minimizes downtime by catching problematic updates before they affect operational systems.
Question
Several critical servers are unresponsive after an update was installed. Other computers that have not yet received the same update are operational, but are vulnerable to certain buffer overflow attacks. The security administrator is required to ensure all systems have the latest updates while minimizing any downtime. Which of the following is the BEST risk mitigation strategy to use to ensure a system is properly updated and operational?
Options
- ADistributed patch management system where all systems in production are patched as
- BCentral patch management system where all systems in production are patched by
- CCentral patch management system where all updates are tested in a lab environment after
- DDistributed patch management system where all updates are tested in a lab environment
How the community answered
(38 responses)- A11% (4)
- B3% (1)
- C8% (3)
- D79% (30)
Why each option
Testing patches in a lab environment before deploying to production minimizes downtime by catching problematic updates before they affect operational systems.
Patching all production systems simultaneously without prior lab testing is the scenario that caused the outage described; it maximizes exposure and downtime risk.
A centralized system that patches all production systems directly also skips the lab validation step, repeating the same risky process that caused the initial failure.
Testing in a lab environment after deploying to production reverses the correct order; issues are discovered only after production systems are already impacted.
A distributed patch management system that first tests all updates in a lab environment replicates the production configuration to validate patch stability and compatibility before any production system is touched. This approach minimizes downtime by identifying breaking changes - such as the server crash described - in an isolated environment. Distribution also reduces the risk of a single point of failure in the patching infrastructure itself.
Concept tested: Patch management lab testing before production deployment
Source: https://learn.microsoft.com/en-us/windows/deployment/update/waas-manage-updates-wsus
Topics
Community Discussion
No community discussion yet for this question.