VCP-DCV vSphere Lifecycle Management Practice Question
An administrator wants to stage updates to reduce downtime during remediation of a vLCM-managed cluster. What should they configure?
⚠ Common exam trap
VCP-DCV often tests the confusion between staging (pre-downloading payloads) and scheduling/concurrency (rolling remediation) or Quick Boot (faster reboot) — candidates must match the feature to the specific downtime-reduction goal.
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 'Stage remediation' in the cluster image configuration.
vLCM's 'Stage remediation' option pre-downloads and stages the update payload on each host before remediation begins, so the actual remediation step only needs to apply the staged bits and reboot. This shortens the per-host maintenance window and reduces the risk of remediation failing due to download issues during the change window.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable 'Stage remediation' in the cluster image configuration.
Why this is correct
Enabling 'Stage remediation' in the cluster image configuration lets vLCM pre-download and stage all payloads to each host before any maintenance window, so remediation itself only applies the staged updates. This directly satisfies the stem's requirement to reduce downtime during remediation of the vLCM-managed cluster.
- ✗
Enable 'Quick Boot' to speed up reboots.
Why it's wrong here
Quick Boot shortens individual host reboot time but does not stage updates; remediation still applies to hosts sequentially with full downtime per host. It is tempting because faster reboots appear to reduce outage windows, and Quick Boot is genuinely useful for routine maintenance reboots, not vLCM staging.
- ✗
Configure the cluster to use a rolling schedule.
Why it's wrong here
A rolling schedule sequences remediation across hosts but does not stage updates beforehand; each host still enters maintenance and reboots during the window. It is tempting because rolling remediation sounds like staged delivery, and it is correct for limiting concurrent host disruption, not for pre-staging payloads.
- ✗
Create multiple host images for each host.
Why it's wrong here
Per-host images fragment the cluster's desired-state baseline, so vLCM cannot remediate consistently and drift detection breaks. It is tempting because host-level customisation feels like control, and separate images are legitimate for heterogeneous hardware profiles, not for staging cluster remediation.
Visual reference
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.