Missing VIB in vLCM Image — Depot URL and Acceptance Level Checks
A vSphere administrator is managing a cluster with vLCM and receives a notification that a new ESXi patch is available. The administrator updates the desired image to include the patch and attempts to remediate, but the remediation fails with 'Cannot retrieve software depots'. What could be the issue?
⚠ Common exam trap
Many exam-takers confuse a depot retrieval failure with a host communication issue or image validation problem, but the specific error message directly points to the depot URL being inaccessible, not to host connectivity or dependency checks.
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
✓
The software depot URL in the image is incorrect or unreachable.
The error 'Cannot retrieve software depots' indicates that vLCM is unable to reach the software depot URL specified in the desired image. This typically occurs when the URL is incorrect, the depot server is down, or network/firewall rules block access to the depot. Since the administrator updated the image and remediation fails at the depot retrieval stage, the most direct cause is an unreachable or misconfigured depot URL.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The software depot URL in the image is incorrect or unreachable.
Why this is correct
An unreachable or malformed depot URL prevents vLCM from downloading the patch payloads referenced by the desired image, so remediation aborts before any host enters maintenance mode. The error text names the depot retrieval stage specifically, making connectivity or URL accuracy the constraint that must be satisfied first.
- ✗
The hosts cannot communicate with the vCenter Server.
Why it's wrong here
Loss of vCenter connectivity would break all vLCM operations, yet the administrator successfully edited the desired image; depot retrieval failure points to unreachable or invalid depot URLs, proxy or certificate problems. This option would be correct if hosts lost management-plane connectivity to vCenter entirely.
- ✗
The image validation failed due to missing dependencies.
Why it's wrong here
Image validation checks dependency and signature consistency within a depot; it does not contact the depot server, so a validation failure would report unmet dependencies, not retrieval failure. Validation is the right concern when a manually assembled image references VIBs absent from the configured depot.
- ✗
The desired image was not saved after adding the patch.
Why it's wrong here
An unsaved desired image would leave remediation running against the previous image, producing no change or a compliance mismatch rather than a depot retrieval error. Saving is the correct step when you want edits to persist before scheduling remediation, but it does not govern depot connectivity.
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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.