nerdexam
CompTIA

CV0-003 · Question #310

In a private cloud environment, which of the following is the BEST way to update 20 VMs with the same patch that has been regression tested and approved for rollout?

The correct answer is D. Install the patch on as many VMs as possible during the next maintenance window.. When a patch is already regression tested and approved, the correct practice in a private cloud is to deploy it during a scheduled maintenance window to ensure change control and minimize production disruption.

Operations

Question

In a private cloud environment, which of the following is the BEST way to update 20 VMs with the same patch that has been regression tested and approved for rollout?

Options

  • AAutomate the distribution of the patch and use an orchestration tool to roll it out.
  • BRoll out the patch manually to the 20 VMs and reboot the system.
  • CDeploy the patch to ten VMs for testing and then install it on the remaining VMs.
  • DInstall the patch on as many VMs as possible during the next maintenance window.

How the community answered

(21 responses)
  • A
    5% (1)
  • C
    5% (1)
  • D
    90% (19)

Why each option

When a patch is already regression tested and approved, the correct practice in a private cloud is to deploy it during a scheduled maintenance window to ensure change control and minimize production disruption.

AAutomate the distribution of the patch and use an orchestration tool to roll it out.

Automating distribution via an orchestration tool without scheduling it during a maintenance window bypasses change control practices and risks disrupting production workloads at an uncontrolled time.

BRoll out the patch manually to the 20 VMs and reboot the system.

Manually patching 20 VMs is time-consuming, inconsistent, and error-prone compared to a structured maintenance window approach.

CDeploy the patch to ten VMs for testing and then install it on the remaining VMs.

The patch has already been regression tested and approved for rollout, so deploying to only half the VMs for additional testing is redundant and unnecessarily delays full remediation.

DInstall the patch on as many VMs as possible during the next maintenance window.Correct

Because the patch is already regression tested and approved for rollout, no additional validation is needed before deployment. Applying it to as many VMs as possible during a scheduled maintenance window follows standard change management governance for private cloud environments. The maintenance window ensures patching happens at a controlled, low-impact time without disrupting active workloads.

Concept tested: Private cloud patch management using scheduled maintenance windows

Source: https://learn.microsoft.com/en-us/mem/configmgr/sum/deploy-use/deploy-software-updates

Topics

#patch management#private cloud#orchestration#maintenance window

Community Discussion

No community discussion yet for this question.

Full CV0-003 Practice