CV0-002 · Question #419
A non-critical vulnerability has been identified by a Linux vendor, who has released a patch and recommends that it be applied immediately. Which of the following is the BEST plan for the cloud…
The correct answer is D. Deploy the patch to the development and QA environments and request a functional test review. Even for a non-critical vulnerability with a vendor-recommended patch, the best plan is to test the patch thoroughly in non-production environments before deploying it to production systems.
Question
A non-critical vulnerability has been identified by a Linux vendor, who has released a patch and recommends that it be applied immediately. Which of the following is the BEST plan for the cloud administrator to install the patch?
Options
- ASchedule an emergency maintenance window and deploy the patch to servers in production.
- BDeploy the patch to the failover cluster and force a failover to the patched environment.
- CDeploy the patch to half of the servers in production and monitor for any issues.
- DDeploy the patch to the development and QA environments and request a functional test review.
How the community answered
(41 responses)- A10% (4)
- B15% (6)
- C5% (2)
- D71% (29)
Why each option
Even for a non-critical vulnerability with a vendor-recommended patch, the best plan is to test the patch thoroughly in non-production environments before deploying it to production systems.
Scheduling an emergency maintenance window and deploying directly to production, even with a vendor recommendation, bypasses crucial testing stages and risks introducing new issues into the live environment without prior validation.
Deploying to a failover cluster and forcing a failover without prior testing in a non-production environment still carries the risk of introducing an untested patch to a live system that then becomes primary, potentially causing service disruption.
Deploying to half of the production servers, though a form of canary deployment, is still a direct deployment to production without prior validation in a dedicated test environment, which is too risky for initial patch deployment.
The BEST plan for a non-critical vulnerability patch is to first deploy it to non-production environments like development and QA. This allows for thorough testing and functional review to identify any potential regressions or adverse effects before the patch is introduced to critical production systems, minimizing risk.
Concept tested: Patch management strategy, change management
Source: https://learn.microsoft.com/en-us/windows-server/get-started/patch-management-best-practices
Topics
Community Discussion
No community discussion yet for this question.