VCP-DCV vSphere Lifecycle Management Practice Question
A vSphere administrator is trying to create a custom ESXi image for a cluster using vSphere Lifecycle Manager. The cluster contains hosts with a specific hardware that requires a third-party component (e.g., a NIC driver). The administrator adds the component to the image definition in vLCM. However, when applying the image, the component does not get installed on the hosts. What is the likely cause?
⚠ Common exam trap
VCP-DCV often tests whether candidates overlook version compatibility between the component and the ESXi base image, instead blaming ISO mounting, signing, or manual installation — the exam expects you to know that vLCM enforces a compatibility matrix.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The component version is not compatible with the ESXi version in the image.
In vSphere Lifecycle Manager (vLCM), a custom ESXi image is composed of a base ESXi version plus additional components (drivers, firmware). Each component has a compatibility matrix that specifies which ESXi versions it supports. If the component version added to the image definition is not compatible with the ESXi version in the image, vLCM will not install it during remediation — the component is effectively ignored or the image fails validation. This is the most likely cause when a component silently does not get installed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The component version is not compatible with the ESXi version in the image.
Why this is correct
vLCM validates each component against the ESXi base image's acceptance level and version dependencies. A component built for a different ESXi release is silently skipped during remediation, so the NIC driver never installs despite being present in the image definition.
- ✗
The administrator did not mount the component ISO during remediation.
Why it's wrong here
Components are added to the image definition as depot payloads and applied automatically during remediation; mounting an ISO is not part of the vLCM workflow. It is tempting because manual driver installation historically required attaching a vendor ISO, which was the correct approach before image-based cluster management existed.
- ✗
The component is not signed by a trusted certificate authority.
Why it's wrong here
vLCM accepts unsigned or self-signed third-party components provided they are added to the depot and trusted; signing is not the installation gate. Signature verification applies to validating depot integrity. The likely cause is a missing hardware support manager or incompatible component version for the ESXi base image.
- ✗
The component must be installed manually on each host first.
Why it's wrong here
vLCM installs components defined in the image during remediation, so manual per-host installation is unnecessary and would be overwritten. It is tempting because third-party drivers were traditionally installed by hand via esxcli on each host, which was correct for standalone hosts outside a vLCM-managed cluster.
Go deeper
Related to this question
About these practice questions
One of 281 original VCP-DCV practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official VMware exam blueprint
This VCP-DCV practice question is part of Courseiva's free VMware certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the VCP-DCV exam.