VCP-DCV vSphere Lifecycle Management Practice Question
An administrator is designing a new vSphere environment and wants to minimize manual effort for patching and upgrade. Which lifecycle management approach should they choose for vSphere 8 clusters?
⚠ Common exam trap
The trap is choosing legacy baselines or Update Manager out of familiarity — the exam tests that vLCM with desired-state images is the modern, recommended approach for minimizing manual patching across all vSphere 8 clusters, not just large ones.
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
✓
Enable vLCM for all clusters.
vSphere Lifecycle Manager (vLCM) with desired-state image management is the recommended approach in vSphere 8 for minimizing manual patching and upgrades. Enabling vLCM for all clusters lets administrators define a single image (base ESXi version plus firmware and drivers) and remediate hosts to match it, automating compliance across the cluster. This reduces manual effort compared to legacy baselines.
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 vSphere baselines for granular control.
Why it's wrong here
Baselines patch hosts individually and cannot orchestrate cluster-wide remediation, so they leave manual sequencing and upgrade ordering to the administrator. They suit granular, host-level compliance control. vSphere Lifecycle Manager images manage the whole cluster as one desired-state unit.
- ✓
Enable vLCM for all clusters.
Why this is correct
vLCM applies desired-state images across the cluster, remediating hosts automatically to match the baseline, which directly satisfies the requirement to minimise manual patching and upgrade effort. Unlike baselines that merely report drift, vSphere Lifecycle Manager enforces convergence, so vSphere 8 clusters stay compliant without per-host intervention.
- ✗
Use vSphere Update Manager for standalone hosts.
Why it's wrong here
Update Manager is deprecated in vSphere 8 and manages patching only, not full desired-state lifecycle remediation across the cluster. It is tempting because VUM historically patched standalone hosts, but the stem asks for a vSphere 8 approach minimising manual patching and upgrade effort.
- ✗
Use vLCM only for large clusters with more than 32 hosts.
Why it's wrong here
vLCM is the default lifecycle mechanism for all vSphere 8 clusters regardless of host count, so restricting it to clusters above 32 hosts leaves smaller clusters on manual baselines. The 32-host figure is not a vLCM threshold; it relates to vSphere cluster maximums, which is why the number is tempting.
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.