VCP-DCV vSphere Lifecycle Management Practice Question
An organization wants to upgrade ESXi hosts from 7.0 to 8.0 using vLCM. They have a cluster with mixed hardware (different NICs and HBAs). What is the best practice?
⚠ Common exam trap
VCP-DCV often tests the misconception that a single vanilla ESXi image is sufficient for any cluster, ignoring that async drivers for NICs and HBAs must be included via vendor add-ons or custom images in vLCM.
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
✓
Create a custom image that includes all necessary drivers and add-ons for the mixed hardware.
vLCM image-based management requires a single desired-state image per cluster, and that image must contain every driver, add-on, and component needed by all hosts in the cluster. With mixed hardware (different NICs and HBAs), the vendor add-on or custom image must bundle the appropriate async drivers so each host can boot and function after remediation. Creating a custom image that includes all necessary drivers and add-ons ensures the desired state is valid for every host, which is the documented best practice for heterogeneous clusters.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a custom image that includes all necessary drivers and add-ons for the mixed hardware.
Why this is correct
A custom image built in vLCM bundles the specific NIC and HBA drivers plus add-ons required by the differing hardware, so every host in the mixed cluster remediates to one consistent, compatible image rather than failing validation against a vendor base image.
- ✗
Use vSphere Update Manager baselines instead of vLCM.
Why it's wrong here
vSphere Update Manager baselines manage ESXi patching and upgrades but do not perform desired-state firmware and driver remediation across heterogeneous hosts. It is tempting because baselines are the legacy upgrade mechanism, yet vLCM is specifically designed to reconcile mixed NIC and HBA hardware by adding vendor add-ons to the image.
- ✗
Use a single image with the latest ESXi version and no add-ons.
Why it's wrong here
A single image without vendor add-ons omits the NIC and HBA drivers that mixed hardware requires, so hosts may lose connectivity or fail to boot after remediation. It is tempting because a minimal image reduces conflicts, but vLCM images must include the appropriate vendor add-ons for each hardware variant in the cluster.
- ✗
Upgrade hosts manually by booting from installation media.
Why it's wrong here
Booting each host from installation media performs a manual, destructive reinstall that wipes configuration and cannot coordinate firmware or driver consistency across mixed hardware. It is tempting as a fallback when automated tooling fails, but vLCM is precisely the supported path for orchestrating cluster-wide upgrades with vendor add-ons.
Go deeper
Related to this question
About these practice questions
This VCP-DCV question is part of Courseiva's 281-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.