VCP-DCV vSphere Lifecycle Management Practice Question
An organization has multiple vSphere clusters with different hardware models. They want a single lifecycle management strategy that minimizes administrative overhead while ensuring all hosts are up-to-date with ESXi and firmware. Which approach should they take?
⚠ Common exam trap
VCP-DCV often tests the confusion between VUM baselines (patch-only) and vLCM images (full desired state including firmware) — candidates who pick baselines miss the firmware requirement.
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 per hardware model and apply to respective clusters.
vLCM cluster images are hardware-model-specific because they bundle the ESXi base image plus OEM firmware and driver add-ons validated for a particular server model. With multiple hardware models, the correct strategy is one image per model, applied to the clusters containing that model. This keeps each image's firmware/driver add-on aligned with the hardware while still centralizing lifecycle management through vLCM.
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 one baseline group per cluster and attach it.
Why it's wrong here
Per-cluster baselines multiply objects to maintain and still leave firmware outside vSphere Lifecycle Manager's image model, so administrative overhead rises rather than falls. Baseline groups suit patching ESXi and drivers on homogeneous clusters, not unified image-and-firmware lifecycle across differing hardware.
- ✗
Use host profiles to enforce firmware settings.
Why it's wrong here
Host profiles enforce configuration compliance, not firmware or ESXi image versions, so they cannot deliver lifecycle remediation. They suit standardising settings like NTP or DNS across hosts; image-based cluster management is required to push ESXi and firmware updates.
- ✗
Use a single cluster image for all clusters.
Why it's wrong here
A single cluster image cannot span different hardware models, because each image pins a specific firmware addon and driver set validated for one server platform. Images suit uniform clusters; heterogeneous hardware requires per-cluster images, defeating the single-strategy goal.
- ✓
Create separate cluster images per hardware model and apply to respective clusters.
Why this is correct
Cluster images are hardware-model-specific, so a single image cannot span differing models. Creating one image per model lets each cluster track its own ESXi and firmware baseline, satisfying the requirement for a unified lifecycle strategy without manual per-host remediation.
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.