5V0-22.23 · Question #33
A vSAN administrator has a vSAN cluster that is using vSphere Lifecycle Manager (vLCM) to manage hypervisor, server drivers, and firmware. All hosts in the cluster are compliant according to the…
The correct answer is B. Add an individual component to the vLCM image that has the updated NIC driver. vSphere Lifecycle Manager (vLCM) manages hosts using a single image composed of a base ESXi version, optional Vendor Add-ons, and individual components - and individual components can be added to override or supplement what the Vendor Add-on provides, making B the correct…
Question
A vSAN administrator has a vSAN cluster that is using vSphere Lifecycle Manager (vLCM) to manage hypervisor, server drivers, and firmware. All hosts in the cluster are compliant according to the vLCM image. A 10GB NIC on the servers is experiencing issues, and the vSAN administrator determines a new network driver will resolve the problem. Unfortunately, the required NIC driver is a newer version compared to the driver provided by the most recent Vendor Add-on. Which action should the vSAN administrator take to ensure the latest network driver is installed on the NIC before remediation?
Options
- AMake sure the vLCM image is configured to use the most recent version of the Vendor Add-on
- BAdd an individual component to the vLCM image that has the updated NIC driver
- CRemove the Vendor Add-on from the vLCM image, and then manually install the network driver
- DModify the vLCM image to omit the NIC Driver, and then manually update the servers with the
How the community answered
(32 responses)- A9% (3)
- B81% (26)
- C3% (1)
- D6% (2)
Explanation
vSphere Lifecycle Manager (vLCM) manages hosts using a single image composed of a base ESXi version, optional Vendor Add-ons, and individual components - and individual components can be added to override or supplement what the Vendor Add-on provides, making B the correct action. Since the required NIC driver is newer than what the latest Vendor Add-on offers, adding it as a standalone component to the image allows vLCM to install the specific driver version during remediation while keeping everything else managed consistently.
Why the distractors are wrong:
- A is wrong because using the most recent Vendor Add-on still won't include the newer driver - the problem explicitly states the driver exceeds what the latest add-on provides.
- C is wrong because removing the Vendor Add-on and manually installing drivers defeats the purpose of vLCM image-based management and would leave hosts unmanaged for that component.
- D is wrong for the same reason - manually patching servers outside of vLCM breaks the single-image compliance model and is an anti-pattern for vLCM-managed clusters.
Memory tip: Think of vLCM image layers as a hierarchy - base image → Vendor Add-on → individual components - where individual components sit at the top and win over what the Vendor Add-on provides, letting you surgically override a single driver without abandoning the managed framework.
Topics
Community Discussion
No community discussion yet for this question.