In an IaaS environment, which patch-management approach should be used after CAB approval?

In an IaaS environment, which patch-management approach should be used after CAB approval?

• A. Using a patch management system, identify the hypervisor type, select a group of hypervisors to patch, and perform a rolling application of patches
• B. Using a patch management system, identify the guests that require patching, and apply the patches
• C. Using a patch management system, identify the applications needing the patch, select the required application in a patch management console, and apply the patches
• D. Using a patch management system, identify the services that require patching, and apply the patches

Answer: (A)

Rolling patching of the hypervisor layer across the cluster after CAB approval is the best approach in an IaaS environment. The hypervisor hosts underpin all virtual machines, so updates at this level must be done in a controlled, staged way to keep workloads available. By identifying the hypervisor type, grouping hosts with the same version, and patching one group at a time, you maintain capacity on the remaining hosts while patches are applied. This minimizes downtime, enables validation on a subset first, and aligns with change-management approvals. Patching guests or applications is still necessary, but it doesn’t address the risk at the virtualization layer across the infrastructure, and patching services is too vague to specify how to safely roll out hypervisor updates.

Rolling patching of the hypervisor layer across the cluster after CAB approval is the best approach in an IaaS environment. The hypervisor hosts underpin all virtual machines, so updates at this level must be done in a controlled, staged way to keep workloads available. By identifying the hypervisor type, grouping hosts with the same version, and patching one group at a time, you maintain capacity on the remaining hosts while patches are applied. This minimizes downtime, enables validation on a subset first, and aligns with change-management approvals. Patching guests or applications is still necessary, but it doesn’t address the risk at the virtualization layer across the infrastructure, and patching services is too vague to specify how to safely roll out hypervisor updates.