CompTIA Server+ (SK0-005)Server AdministrationHard
A server administrator is reviewing the current patching strategy for the company's critical production servers. The strategy involves applying all security and critical updates immediately upon release. While this ensures the highest level of security, it has led to several instances of application downtime due to unexpected compatibility issues. Which adjustment to the patching strategy would best balance security with stability for critical production systems?
- AApplying all patches to a test environment first, then to a subset of non-critical production servers, and finally to critical production servers.
- BImplementing a 'skip-patch' policy for any patch that has known issues reported by other organizations.
- CDelaying all patches by at least 6 months to allow for community testing and bug fixes.
- DDisabling automatic updates and applying patches only during major system upgrades.
Show answer & explanationAnswer & explanation
Correct answer: A. Applying all patches to a test environment first, then to a subset of non-critical production servers, and finally to critical production servers.
A phased rollout strategy, starting with testing, then non-critical production, and finally critical production, allows for identification and mitigation of compatibility issues before they impact the most important systems, balancing security with stability.
Why the other options are wrong
- B. While useful, a 'skip-patch' policy is reactive and doesn't proactively test for *unknown* issues specific to the organization's environment.
- C. Delaying all patches by 6 months leaves systems vulnerable for an extended period, which is unacceptable for critical security updates.
- D. Delaying patches until major upgrades significantly increases security vulnerabilities and risk.
Phased Patching Strategy
A phased patching strategy involves deploying patches in stages, typically starting with non-production environments, then to non-critical production systems, and finally to critical production systems, to mitigate risks and ensure stability.
- Reduces risk of production downtime
- Allows for thorough testing of patches
- Balances security needs with stability requirements
Memory trick: Patching: Test, then roll, to keep the servers whole!