VCP-DCV vSphere Lifecycle Management Practice Question
A vSphere administrator manages a cluster of 50 ESXi hosts using vLCM with image-based management. The cluster includes hosts from two different hardware vendors. The administrator needs to ensure firmware updates are consistently applied across all hosts. What is the best practice for this scenario?
⚠ Common exam trap
VCP-DCV often tests the misconception that a single vLCM cluster image can include firmware for multiple hardware vendors, confusing the desired-state model with legacy baseline groups that could be combined.
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 separate cluster images for each hardware vendor and apply to respective hosts.
In vLCM image-based management, a cluster image is a single desired-state specification that includes ESXi base image, vendor add-ons, and firmware add-ons. Firmware add-ons are hardware-vendor-specific (e.g., Dell, HPE, Lenovo), so a single image cannot contain firmware components for two different vendors. The correct best practice is to create separate cluster images per hardware vendor, each containing the appropriate vendor add-on and firmware add-on, and apply them to the respective hosts. This ensures consistent firmware updates while respecting vendor-specific packaging.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use baseline groups to manage firmware separately.
Why it's wrong here
Baseline groups manage ESXi software and add-on components, not firmware, so they cannot deliver the vendor firmware payloads this scenario requires. They are tempting because baselines remain the mechanism for host patching outside image-based clusters, where per-host remediation is genuinely needed.
- ✗
Create a single cluster image that includes firmware for both vendors.
Why it's wrong here
A single cluster image cannot embed firmware for two hardware vendors; firmware components are vendor- and model-specific, so the image fails validation or omits one vendor's hosts. One image is tempting because it works cleanly in single-vendor clusters, where all hosts share identical firmware components.
- ✓
Create separate cluster images for each hardware vendor and apply to respective hosts.
Why this is correct
Separate cluster images per vendor satisfy the stem's mixed-hardware constraint, because a vLCM image bundles vendor-specific firmware add-ons that only apply to matching hardware. A single image spanning both vendors would fail validation or skip firmware components, so splitting images ensures consistent firmware delivery across all 50 hosts.
- ✗
Manually update firmware using vendor tools, then use vLCM for ESXi updates.
Why it's wrong here
Manual vendor-tool firmware updates break the image's single declarative source, so drift between hosts is undetectable and unrepeatable at 50-host scale. Vendor tools are tempting when a host sits outside vLCM, or when firmware must be flashed before the host can be added to the 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.