Knowledge + Practice

CCNA vSphere Lifecycle Management Questions

72 questions · vSphere Lifecycle Management · All types, answers revealed

Practice these questions Domain overview All questions

1

MCQhard

Refer to the exhibit. An administrator attempts to apply this cluster image to an ESXi 8.0.1 cluster, but the image validation fails. What is the most likely cause?

A.The 'nmlx5-core' component version is incompatible with the selected ESXi base image.

B.The vendor addon 'VXLAN/5.6.0' is not compatible with ESXi 8.0.1.

C.The firmware section is empty.

D.The 'Intel-i40en' component is missing a critical bug fix.

AnswerB

VXLAN 5.6.0 is designed for ESXi 7.x and is not supported on ESXi 8.0.1.

Why this answer

The vendor addon 'VXLAN/5.6.0' is explicitly listed as incompatible with the ESXi 8.0.1 base image. In vSphere Lifecycle Management, a cluster image consists of an ESXi base image, optional vendor addons, and firmware/driver components. If a vendor addon version is not certified or supported for the selected base image version, image validation will fail.

The error indicates that the VXLAN addon version 5.6.0 does not meet compatibility requirements for ESXi 8.0.1.

Exam trap

The trap here is that candidates often assume validation failures are caused by missing firmware or driver bugs, but vLCM strictly enforces vendor addon compatibility with the base image, and an empty firmware section is permissible.

How to eliminate wrong answers

Option A is wrong because the 'nmlx5-core' component version is not inherently incompatible with the ESXi 8.0.1 base image; the error message specifically points to the vendor addon, not a core driver. Option C is wrong because an empty firmware section does not cause image validation failure; firmware is optional and can be added later via a hardware support manager (HSM) or left empty without blocking validation. Option D is wrong because the 'Intel-i40en' component missing a critical bug fix would not cause a validation failure; missing bug fixes are typically flagged as warnings or non-critical issues, not hard validation errors.

Practice this question →

2

MCQmedium

An administrator wants to use vLCM to manage firmware for a cluster of Dell PowerEdge servers. What is required?

A.Manual download of firmware ISOs

B.Dell OpenManage Enterprise

C.vSphere Update Manager baseline

D.vCenter Server with vLCM and hardware support manager (HSM)

AnswerD

vLCM manages firmware only through a hardware support manager (HSM) plugin, such as Dell's, registered with a vCenter Server. Without both vCenter and the vendor HSM, firmware compliance and remediation for PowerEdge hosts cannot run.

Why this answer

To use vLCM to manage firmware for a cluster of Dell PowerEdge servers, you need vCenter Server with vLCM and a hardware support manager (HSM). The HSM is a vSphere Installation Bundle (VIB) provided by the hardware vendor (in this case, Dell) that integrates with vLCM to provide firmware updates. Dell's HSM is typically delivered as part of the Dell OpenManage integration, but the core requirement is the HSM plugin registered with vLCM.

Exam trap

VCP-DCV often tests the misconception that vLCM can manage firmware without a vendor-provided hardware support manager, or that a standalone tool like OpenManage Enterprise is sufficient, when the HSM integration with vCenter is the actual requirement.

How to eliminate wrong answers

Option A is wrong because manual download of firmware ISOs is the traditional out-of-band method and is not how vLCM manages firmware; vLCM automates firmware updates via the HSM. Option B is wrong because while Dell OpenManage Enterprise may be part of the ecosystem, the specific requirement for vLCM firmware management is the hardware support manager (HSM) integrated with vCenter, not the standalone OpenManage Enterprise appliance. Option C is wrong because vSphere Update Manager baselines are for software updates, not firmware, and vLCM image-based management with an HSM is required for firmware.

Practice this question →

3

Multi-Selectmedium

Which TWO statements accurately describe vSphere Lifecycle Manager (vLCM) image-based management features?

Select 2 answers

A.An image includes ESXi version, firmware/driver version, and additional components.

B.Only vendor-specific images from OEMs are supported.

C.A single vLCM image can be applied to a maximum of 10 hosts in a cluster.

D.Offline bundles can be imported to create a custom image for the cluster.

E.Multiple images can be assigned to different hosts within the same cluster.

AnswersA, D

An image is the declarative desired-state specification for a cluster, bundling the ESXi base version, firmware and driver add-ons, and additional components into one artefact. This satisfies the stem's requirement that image-based management unifies all software layers, rather than patching them separately.

Why this answer

Options A and D are correct. Image-based management in vLCM uses a single image per cluster, which includes ESXi version, firmware/driver versions, and additional components (A). Offline bundles can be imported to create custom images (D).

Option B is incorrect because you can use custom images, not only vendor-specific ones. Option C is incorrect because there is no limit of 10 hosts; a single image applies to all hosts in the cluster. Option E is incorrect because only one image can be assigned per cluster.

Practice this question →

4

MCQeasy

A company manages a vSphere cluster of 200 ESXi hosts using vSphere Lifecycle Manager baselines (baseline-based remediation). They decide to migrate to vLCM image-based management. The administrator selects one host as a reference host, generates a cluster image from it, and attempts to apply the image to the entire cluster. Most hosts remediate successfully, but 20 hosts fail with the error: "Image deployment failed: Error retrieving VIBs from repository." The failed hosts are all from a different hardware vendor than the reference host but are on the vSphere HCL. The administrator confirms that the repository URL is reachable from the failed hosts and that there are no network connectivity issues. What should the administrator do first to resolve the issue?

A.Check the vLCM cluster image for any components specific to the reference host's hardware that are not present in the failed hosts.

B.Reboot the failed hosts and retry the remediation.

C.Verify that the failed hosts have sufficient disk space in the /scratch partition.

D.Manually upload the required VIBs to the local depot on each failed host.

AnswerA

The image likely includes hardware-specific VIBs from the reference host that are incompatible or missing for the other hardware models; removing unnecessary components resolves the issue.

Why this answer

The error 'Error retrieving VIBs from repository' when applying a cluster image generated from a reference host indicates that the image contains hardware-specific VIBs (e.g., drivers, CIM providers) that are present on the reference host but not compatible with the failed hosts from a different hardware vendor. vLCM cluster images are derived from the reference host's software specification, including any vendor-specific components, and when applied to hosts lacking that hardware, the VIB retrieval fails because the repository does not contain matching VIBs for those hosts. The first step is to check the cluster image for such components and remove or replace them with hardware-independent versions to ensure compatibility across the heterogeneous cluster.

Exam trap

The trap here is that candidates often assume network or repository issues are the cause, but the error specifically points to VIB retrieval failure due to incompatible hardware-specific components in the image, not connectivity problems.

How to eliminate wrong answers

Option B is wrong because rebooting the hosts does not address the root cause of missing or incompatible VIBs in the image; it would only retry the same failing operation. Option C is wrong because insufficient disk space in /scratch would typically cause a different error (e.g., 'Insufficient disk space'), not a VIB retrieval failure from a repository, and the administrator already confirmed network connectivity. Option D is wrong because manually uploading VIBs to a local depot is unnecessary and bypasses vLCM's centralized image management; the correct approach is to modify the cluster image to remove hardware-specific components, not to manually stage VIBs on each host.

Practice this question →

5

MCQhard

A company has a vSphere cluster with 10 ESXi hosts managed by vLCM. They use a custom image that includes a third-party network driver. After updating the image to include a new version of the driver, remediation fails on all hosts with the error: 'The software specification contains a VIB that is not compatible with the host platform.' What is the most likely cause?

A.The new driver VIB is not compatible with the ESXi version in the image.

B.The vLCM image depot is corrupted.

C.The hosts have incompatible firmware.

D.The custom image is not signed by VMware.

AnswerA

The VIB compatibility error means the driver targets a different ESXi platform than the image's base version. vLCM validates each VIB against the host's ESXi build, so a driver built for another release fails remediation before installation.

Why this answer

The error 'The software specification contains a VIB that is not compatible with the host platform' indicates that the VIB (vSphere Installation Bundle) in the custom image is not designed to run on the ESXi version specified in the image. vLCM validates VIB compatibility against the ESXi base image version, and a third-party driver VIB must be built for that exact ESXi build. Since the new driver version is incompatible with the ESXi version, remediation fails on all hosts.

Exam trap

The trap here is that candidates often assume the error is about signing or corruption, but vLCM specifically checks VIB-to-platform compatibility at the VIB metadata level, not the image's signature or depot integrity.

How to eliminate wrong answers

Option B is wrong because a corrupted vLCM image depot would typically cause download or checksum errors, not a specific VIB compatibility message. Option C is wrong because incompatible firmware would generate hardware-related errors (e.g., driver/firmware mismatch), not a VIB platform compatibility error. Option D is wrong because vLCM does not require custom images to be signed by VMware; it only validates VIB acceptance levels (e.g., VMwareCertified, PartnerSupported) and host acceptance levels, not a VMware signature on the entire image.

Practice this question →

6

MCQmedium

During a cluster upgrade using vLCM, the pre-check reports that Quick Boot is disabled. How does this affect the upgrade?

A.Quick Boot speeds up reboot

B.No effect

C.Hosts will reboot normally

D.Upgrade will fail

AnswerC

Quick Boot being disabled means the host performs a full BIOS/UEFI POST during reboot rather than skipping hardware initialisation. The vLCM pre-check flags this only as a warning, not a blocker, so remediation proceeds and each host restarts through its normal boot path, satisfying the cluster upgrade without additional configuration.

Why this answer

Quick Boot is a vSphere feature that speeds up host reboots by skipping certain hardware initialization steps, but it is not required for an upgrade. If the vLCM pre-check reports Quick Boot is disabled, the upgrade can still proceed; hosts will simply perform a normal reboot, which takes longer. The pre-check is informational, not a blocker.

Exam trap

The trap is assuming a pre-check warning about Quick Boot is a hard failure; candidates may pick 'upgrade will fail' when in fact it only affects reboot speed and the upgrade proceeds normally.

How to eliminate wrong answers

Option A is wrong because while Quick Boot does speed up reboot, the question asks how its absence affects the upgrade, not what it does. Option B is wrong because there is an effect: the reboot will be a normal, slower reboot rather than a quick one. Option D is wrong because a disabled Quick Boot does not cause the upgrade to fail; it only changes reboot behavior.

Practice this question →

7

MCQeasy

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?

A.Use vSphere baselines for granular control.

B.Enable vLCM for all clusters.

C.Use vSphere Update Manager for standalone hosts.

D.Use vLCM only for large clusters with more than 32 hosts.

AnswerB

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.

Why this answer

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.

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.

How to eliminate wrong answers

Option A is wrong because vSphere baselines are the legacy Update Manager approach that requires more manual baseline/group management and does not provide the desired-state image model of vLCM. Option C is wrong because vSphere Update Manager is the older component superseded by vLCM, and using it for standalone hosts does not address cluster-wide lifecycle automation. Option D is wrong because vLCM is not limited to clusters with more than 32 hosts; it is recommended for all clusters regardless of size, and restricting it to large clusters misses the automation benefit.

Practice this question →

8

MCQhard

During a vLCM health check, an administrator sees that the health status for a cluster is 'Error' with the message: 'Unable to connect to the depot service at https://depot.vmware.com'. The cluster is configured to use the online depot. What is the most likely cause?

A.DNS resolution is failing for the vCenter server.

B.The vCenter server's certificate is expired.

C.A firewall is blocking outbound HTTPS access to the internet.

D.The cluster image has an invalid URL.

AnswerC

Blocked outbound TCP 443 traffic prevents the vLCM depot sync from reaching depot.vmware.com, so the online depot health check fails with a connection error. Since the cluster is configured to use the online depot, no local source exists to fall back on, making firewall filtering of HTTPS the most likely cause.

Why this answer

The most likely cause is that a firewall is blocking outbound HTTPS access to the internet, preventing vCenter from reaching the VMware depot at https://depot.vmware.com. The error message explicitly indicates a connection failure to the depot service, and since the cluster uses the online depot, outbound connectivity is required. Firewall rules blocking port 443 are a common cause in secured environments.

Exam trap

VCP-DCV often tests the difference between connectivity issues and certificate or DNS problems; candidates may jump to certificate expiry because it's a common vCenter issue, but the specific error message points to a network block.

How to eliminate wrong answers

Option A is wrong because DNS resolution failure would typically produce a different error, such as 'Unable to resolve hostname', not a connection error to a specific URL; also, DNS is less likely to be the issue if other services are working. Option B is wrong because an expired vCenter certificate would cause trust or authentication errors, not a failure to connect to an external depot. Option D is wrong because an invalid URL in the cluster image would result in a different error, such as 'Invalid depot URL' or 'Image not found', rather than a connection failure.

Practice this question →

9

MCQeasy

A vSphere administrator is asked to choose a lifecycle management approach for a new cluster of 100 hosts. The cluster will use vSAN and will be updated frequently. The administrator wants to minimize manual intervention and ensure consistency. Which approach should be recommended?

A.Manually update each host with the latest ESXi ISO.

B.Use vSphere Update Manager with baseline groups for updates.

C.Use vSphere Lifecycle Manager with baseline-based management.

D.Use vSphere Lifecycle Manager with image-based management.

AnswerD

Image-based management in vSphere Lifecycle Manager defines a desired-state software image per cluster, so all 100 hosts converge to one specification, including firmware and drivers. This satisfies the frequent-update and consistency constraints, and vSAN clusters are validated against the image, minimising manual intervention across hosts.

Why this answer

vSphere Lifecycle Manager (vLCM) with image-based management uses a declarative desired-state model where the entire cluster is managed from a single software image that includes ESXi base image, drivers, and firmware. This is the recommended approach for vSAN clusters because it ensures consistency across all hosts and integrates with vSAN's hardware compatibility checks, minimizing manual intervention.

Exam trap

The trap is assuming that baseline-based management is still the recommended approach — many candidates pick VUM or vLCM baselines out of familiarity, but image-based vLCM is the modern, declarative method required for consistent vSAN firmware/driver management.

How to eliminate wrong answers

Option A is wrong because manually updating 100 hosts with ISOs is error-prone, time-consuming, and does not ensure consistency or firmware/driver alignment. Option B is wrong because vSphere Update Manager (VUM) with baselines is the legacy approach and does not manage firmware or drivers as part of a unified image, and VUM has been deprecated in favor of vLCM. Option C is wrong because vLCM baseline-based management still uses the older baseline model and does not provide the declarative image-based consistency that vSAN clusters benefit from.

Practice this question →

10

MCQhard

An administrator attempts to export a vLCM image but gets an error: 'Export image operation is not supported for this image'. What could be the reason?

A.The vLCM database is corrupt.

B.The image contains a custom component.

C.The image is too large.

D.The vCenter version does not support export.

AnswerB

vLCM image export is blocked when the image includes a custom component, because such components cannot be represented in the exportable image specification. Removing the custom component or using a base image allows export to succeed.

Why this answer

vLCM image export is only supported for images composed entirely of components available in the VMware depot (base image plus standard add-ons). When an image includes a custom component — for example, an OEM or third-party VIB added outside the standard depot — vCenter cannot serialize that image for export, so it returns 'Export image operation is not supported for this image'. Removing the custom component or rebuilding the image from depot-only components resolves the error.

Exam trap

VCP-DCV often tests whether candidates blame infrastructure-level causes (corruption, size, version) for an error that is actually caused by the content of the image itself — specifically a non-depot custom component.

How to eliminate wrong answers

Option A is wrong because a corrupt vLCM database would produce broad, systemic failures across image management, not a targeted 'not supported for this image' message tied to a specific image. Option C is wrong because image size is not a gating factor for export; vLCM does not reject exports based on size thresholds. Option D is wrong because export is a supported vLCM feature in the relevant vCenter versions — the error is image-specific, not version-specific.

Practice this question →

11

Multi-Selecteasy

An organization wants to use vLCM for lifecycle management. Which three components can be managed using vLCM images? (Choose THREE)

Select 3 answers

A.ESXi version

B.vCenter Server version

C.Add-ons like drivers

D.Firmware for supported hardware

E.VMware Tools

AnswersA, C, D

ESXi version is a core component of a vLCM image, satisfying the requirement to manage host firmware and software as a single desired-state baseline. Images bundle the ESXi base image with vendor add-ons, so the hypervisor version itself is directly declared and remediated through the cluster image, not managed separately.

Why this answer

Option A (ESXi version) is correct because a vLCM image is fundamentally a declarative specification of the ESXi base image, which defines the exact ESXi version and build to be installed on hosts. Option C (Add-ons like drivers) is correct because vLCM images include add-on components such as async drivers, vendor add-ons, and components that are layered on top of the base ESXi image. Option D (Firmware for supported hardware) is correct because vLCM integrates with Hardware Support Managers (HSMs) from OEMs to include firmware and driver updates for supported servers in the image, enabling firmware compliance alongside software.

Option B (vCenter Server version) is not managed by vLCM images; vCenter Server is upgraded separately via VAMI or the CLI installer. Option E (VMware Tools) is not part of a vLCM image; it is managed per-VM through vSphere Lifecycle Manager baselines or VM hardware settings, not as an image component.

Exam trap

VCP-DCV often tests the boundary of vLCM scope — candidates confuse host-image components (ESXi, add-ons, firmware) with adjacent lifecycle items like vCenter, VMware Tools, or vSAN disk firmware, which are managed separately.

Practice this question →

12

MCQeasy

A vSphere administrator is using vSphere Lifecycle Manager to manage a cluster. The cluster's desired image includes a specific ESXi base image and several components. After adding a new host to the cluster, the administrator notices that the host is non-compliant. What is the most efficient way to bring the host into compliance with the cluster's desired image?

A.Use vSphere Update Manager to create a baseline and remediate the host.

B.Manually install the same ESXi version and components on the host using an ISO image.

C.Remove the host from the cluster and re-add it after installing the correct image.

D.Use vSphere Lifecycle Manager to remediate the host.

AnswerD

vLCM can remediate individual hosts or entire clusters to bring them into compliance with the desired image. Remediation automatically installs the required ESXi version and components, ensuring the host matches the cluster's image. This is the most efficient and consistent method, as it leverages vLCM's automation and validation. Therefore, using vLCM to remediate the host is the correct approach.

Why this answer

vSphere Lifecycle Manager is designed to automate host remediation to match the cluster's desired image. Remediating the host will apply the correct ESXi base image and components, ensuring compliance. This is the most efficient and consistent method, avoiding manual errors and downtime associated with other approaches.

Exam trap

The trap here is confusing vLCM with the legacy vSphere Update Manager baseline approach, leading to the selection of baseline remediation instead of image-based remediation.

Practice this question →

13

MCQeasy

A company plans to upgrade the ESXi hosts in their vSphere cluster from version 7.0 Update 3 to 8.0 Update 1 using vSphere Lifecycle Manager (vLCM). The cluster currently uses baseline-based management. What is the recommended approach to prepare for this upgrade?

A.Migrate the cluster to image-based management.

B.Manually upgrade each host using an ISO file.

C.Create a new baseline group and attach it to the cluster.

D.Use vMotion to migrate all VMs to another cluster before upgrading.

AnswerA

vLCM image-based management is the prerequisite for declarative firmware and driver add-on upgrades to ESXi 8.0 Update 1; baselines cannot manage firmware. Migrating the cluster first lets a single desired-state image drive the whole upgrade.

Why this answer

vSphere Lifecycle Manager (vLCM) image-based management is the recommended approach for upgrading to vSphere 8.0 Update 1 because it provides a declarative, desired-state model for the entire cluster, including firmware and drivers via Hardware Support Manager. Baseline-based management is legacy and does not support the full vLCM feature set in 8.0. Migrating the cluster to image-based management before the upgrade ensures a clean, supported path.

Exam trap

VCP-DCV often tests the distinction between baseline-based and image-based management — candidates must know that image-based is the recommended model for vSphere 8 and that baselines are legacy.

How to eliminate wrong answers

Option B is wrong because manually upgrading each host with an ISO bypasses vLCM entirely, is error-prone, and does not leverage the cluster-aware orchestration vLCM provides. Option C is wrong because creating a new baseline group keeps the cluster on baseline-based management, which is the legacy model being deprecated in favor of image-based management in vSphere 8. Option D is wrong because vMotion to another cluster is a workload evacuation step, not an upgrade preparation step — it does not address the management model change required.

Practice this question →

14

MCQmedium

A company has a vLCM-managed cluster with a desired image that includes ESXi 8.0 U1 and multiple VIBs. After remediating, one host fails with an error: 'Failed to retrieve VIBs from depot'. What is the most likely cause?

A.The cluster has a baseline attached that conflicts with the desired image.

B.The image validation failed due to incompatible VIBs.

C.The host firmware is not compatible with the selected VIBs.

D.The vCenter Server does not have internet access to the VMware depot.

AnswerD

The error indicates vLCM cannot pull VIB payloads from the depot. If the vCenter Server lacks internet access to the VMware depot and no local depot or proxy is configured, retrieval fails during remediation, matching the stem's post-remediation host error.

Why this answer

The error 'Failed to retrieve VIBs from depot' indicates that vCenter Server cannot reach the depot from which the VIBs are sourced. In a vLCM-managed cluster using a desired image, the image specification includes VIBs that may be hosted on the VMware online depot or a local depot. If vCenter Server lacks internet access to the VMware depot, it cannot download the required VIBs, causing the remediation to fail.

This is the most likely cause because the error is specifically about retrieval, not validation or compatibility.

Exam trap

The trap here is that candidates often confuse a depot retrieval failure with image validation or compatibility issues, but the error message explicitly points to a network or depot accessibility problem, not a VIB-level conflict.

How to eliminate wrong answers

Option A is wrong because vLCM-managed clusters use desired images, not baselines; if a baseline were attached, it would conflict at the cluster level, but the error message points to depot retrieval, not a baseline conflict. Option B is wrong because image validation errors (e.g., incompatible VIBs) would produce a different error, such as 'Image compliance check failed' or 'VIB dependency error', not a depot retrieval failure. Option C is wrong because host firmware incompatibility would manifest as a hardware compatibility error during remediation, not a failure to retrieve VIBs from a depot.

Practice this question →

15

MCQmedium

An administrator manages a vSphere 8 cluster with vSphere Lifecycle Manager (vLCM) using a single image. The cluster contains hosts from two different server vendors. The administrator attempts to add a firmware add-on to the image but receives an error that the add-on is not compatible with all hosts. What is the most likely cause?

A.The hosts are not in maintenance mode, so vLCM cannot validate the firmware add-on.

B.The cluster uses a single image, but the firmware add-on is only supported on one of the server vendor models.

C.The firmware add-on requires vSphere Lifecycle Manager to be in 'baseline' mode instead of 'image' mode.

D.The firmware add-on is not included in the vLCM depot and must be downloaded from the vendor's website.

AnswerB

A single vLCM image requires all hosts to be compatible with every component, including firmware add-ons. If the add-on only supports one vendor's hardware, vLCM will flag it as incompatible with the other hosts, preventing the image from being applied uniformly.

Why this answer

vLCM images must be compatible with every host in the cluster. Firmware add-ons are hardware-specific; if they do not support all server models present, the image cannot be uniformly applied. The correct answer identifies the vendor-specific limitation as the cause of the incompatibility.

Exam trap

The trap here is assuming that any firmware add-on can be applied cluster-wide without checking per-host hardware compatibility.

Practice this question →

16

MCQhard

An administrator is using vSphere Lifecycle Manager to manage a cluster with a single image. The cluster has a hardware support manager (HSM) configured. During remediation, the task fails on one host with the error: 'Host firmware update failed: Unable to contact BMC.' What is the most likely cause of this error?

A.The HSM is not registered correctly in vCenter Server.

B.The host's BMC network settings are misconfigured or the BMC is unreachable.

C.The host is not compatible with the firmware add-on in the desired image.

D.The host's BMC firmware is outdated and does not support the update method used by the HSM.

AnswerB

The error 'Unable to contact BMC' directly indicates that the HSM cannot reach the BMC. This could be due to incorrect IP configuration, network isolation, or BMC being down. Since it affects one host, it's likely a host-specific BMC connectivity issue. Checking BMC network settings and reachability is the correct troubleshooting step.

Why this answer

The error 'Unable to contact BMC' indicates a communication failure between the Hardware Support Manager and the host's baseboard management controller. This is typically caused by network misconfiguration, incorrect credentials, or the BMC being offline. Since it affects a single host, it's a host-specific issue.

Verifying BMC network settings and connectivity resolves the problem.

Exam trap

The trap here is interpreting the error as a compatibility or HSM registration issue, when it specifically points to BMC connectivity for that host.

Practice this question →

17

MCQhard

An administrator is using vSphere Lifecycle Manager (vLCM) to manage a cluster with an image. During remediation, the task fails with the error: 'Cannot remediate host because it is not compliant with the image.' The administrator checks the image and sees that it includes a firmware add-on. The hosts are from different hardware vendors. What is the most likely cause of the failure?

A.The firmware add-on is not compatible with all host models in the cluster.

B.The hosts do not have enough free disk space to stage the firmware update.

C.The ESXi base image version is too old for the firmware add-on.

D.The vLCM depot is not synchronized with the latest firmware packages.

AnswerA

Firmware add-ons are vendor-specific and model-specific. If the cluster contains hosts from different hardware vendors or models, a single firmware add-on may not support all of them. vLCM will flag hosts that cannot apply the firmware add-on as non-compliant. This is the most likely cause of the remediation failure.

Why this answer

Firmware add-ons in vLCM are specific to hardware vendors and models. When a cluster contains hosts from different vendors, a single firmware add-on cannot apply to all hosts. vLCM will mark hosts that are incompatible with the add-on as non-compliant, causing remediation to fail. The administrator should either use separate clusters per hardware type or remove the firmware add-on and manage firmware separately.

Exam trap

The trap here is assuming that any firmware add-on can be applied to any host, but firmware add-ons are hardware-specific and require homogeneous hardware within the cluster.

Practice this question →

18

MCQeasy

Based on the exhibit, if a host in the cluster has a network card that is not on the vSphere Compatibility Guide, what will happen during remediation?

A.The host will automatically update its drivers to become compatible.

B.A warning will be generated but remediation proceeds.

C.The remediation will fail for that host.

D.The host will be skipped with a warning.

AnswerC

vSphere Lifecycle Manager validates every host's hardware against the vSphere Compatibility Guide before applying an image. A network card absent from that guide fails the hardware compatibility check, so remediation aborts on that host rather than proceeding.

Why this answer

During remediation (e.g., vSphere Lifecycle Manager or Update Manager), if a host has a network card not on the vSphere Compatibility Guide, the remediation will fail for that host. vSphere validates hardware compatibility before applying updates; an incompatible device causes the host to be placed in a failed state for that remediation task.

Exam trap

VCP-DCV often tests the difference between a warning and a failure during remediation; candidates may assume the host is skipped or that drivers auto-update, but incompatible hardware causes an outright failure.

How to eliminate wrong answers

Option A is wrong because drivers are not automatically updated to achieve compatibility; hardware must be listed on the Compatibility Guide, and remediation does not install unsupported drivers. Option B is wrong because it is not merely a warning; the remediation fails for that host. Option D is wrong because the host is not simply skipped with a warning; the remediation attempt fails, and the host remains non-compliant.

Practice this question →

19

MCQmedium

An administrator is using vSphere Lifecycle Manager (vLCM) to manage a vSphere 8 cluster. The cluster's desired image includes a specific ESXi base image and an OEM add-on. During remediation, the administrator wants to minimize the impact on running workloads. Which vLCM feature should be configured to control the number of hosts remediated in parallel?

A.vSphere High Availability (HA) admission control

B.Remediation parallelization

C.Host remediation timeout

D.Distributed Resource Scheduler (DRS) automation level

AnswerB

vLCM allows administrators to set the maximum number of hosts that can be remediated concurrently. This setting, often called remediation parallelization, helps control the impact on cluster capacity and ensures that enough resources remain available for running workloads during the update process.

Why this answer

Remediation parallelization in vLCM lets administrators specify the maximum number of hosts that can be remediated simultaneously. This directly controls the impact on cluster capacity and workload performance during updates. The other options are related to resource management but do not set the concurrency level for remediation.

Exam trap

The trap here is confusing DRS or HA settings with the vLCM-specific parallelization control that actually limits concurrent host remediation.

Practice this question →

20

MCQmedium

A vSphere administrator manages a cluster of eight ESXi hosts with vSphere Lifecycle Manager. The cluster's desired image specifies a firmware add-on that must be applied to all hosts. During remediation, the administrator notices that the firmware update is not being applied to any host. The hosts are otherwise compliant with the ESXi base image and other components. What is the most likely reason for the firmware not being applied?

A.The firmware add-on is included in the image but the hosts do not have the required vSphere Installation Bundles (VIBs) installed.

B.The ESXi hosts are in maintenance mode, preventing firmware updates from being applied.

C.The hardware support manager (HSM) is not configured or is unable to communicate with the firmware management interface.

D.The firmware add-on is not compatible with the current ESXi version and was skipped.

AnswerC

vLCM relies on a hardware support manager to apply firmware updates. If the HSM is not registered, is misconfigured, or cannot reach the out-of-band management interface (e.g., iDRAC, iLO), firmware updates will not be applied. The hosts may still be compliant with software components because those are handled by vLCM directly. Thus, the missing HSM configuration or connectivity is the most likely cause.

Why this answer

Firmware updates in vLCM are applied via a hardware support manager, which communicates with the server's out-of-band management controller. If the HSM is not properly configured or lacks network connectivity, firmware updates will not occur even if the software components are compliant. This is a common oversight when setting up vLCM with firmware add-ons.

Exam trap

The trap here is assuming that firmware updates are delivered as VIBs and thus part of the regular image compliance, rather than requiring a separate hardware support manager.

Practice this question →

21

MCQhard

A vSphere administrator manages a vLCM cluster with a desired image. The administrator needs to update the ESXi base image to a newer version. The cluster contains hosts with different CPU generations. What should the administrator verify before updating the base image?

A.That all hosts have the same amount of memory installed.

B.That the cluster has vSphere DRS enabled in fully automated mode.

C.That all hosts are using the same storage adapter model.

D.That the newer ESXi version supports all CPU generations present in the cluster.

AnswerD

ESXi versions have specific CPU compatibility requirements. If the newer base image does not support an older CPU generation, hosts with that CPU cannot be upgraded and will become non-compliant. Verifying CPU support ensures a successful remediation across all hosts in the cluster.

Why this answer

Before updating the ESXi base image, the administrator must ensure the newer version supports all CPU generations in the cluster. ESXi releases have specific CPU compatibility requirements, and unsupported CPUs will block remediation. Verifying this prevents failed upgrades and ensures all hosts can run the new base image.

Exam trap

The trap here is focusing on uniform hardware like memory or storage adapters, when the actual compatibility concern for a base image update is CPU generation support.

Practice this question →

22

MCQmedium

An administrator is using vSphere Lifecycle Manager (vLCM) to manage a cluster with an image. The administrator wants to add a custom VIB from a third-party vendor to the image. What must be done first?

A.Create a baseline containing the VIB and attach it to the cluster alongside the image.

B.Use vSphere Client to upload the VIB to each host's /tmp directory and reboot.

C.Import the VIB into the vLCM depot and add it as a component to the image.

D.Install the VIB manually on each host using esxcli, then remediate the cluster.

AnswerC

Custom VIBs must be added to the vLCM depot before they can be included in an image. The administrator imports the VIB into the depot, then adds it as a component to the desired image. This ensures the VIB is available for remediation and compliance checks. This is the correct first step to include third-party software in an image.

Why this answer

To include a custom VIB in a vLCM image, the VIB must first be imported into the vLCM depot. Once in the depot, it can be added as a component to the image. This ensures that the VIB is part of the desired state and will be applied during remediation.

Manual installation or baselines are not appropriate when the cluster is image-managed.

Exam trap

The trap here is thinking that manually installing a VIB or using a baseline is sufficient, but vLCM images require components to be in the depot to be part of the image.

Practice this question →

23

MCQhard

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?

A.Create one baseline group per cluster and attach it.

B.Use host profiles to enforce firmware settings.

C.Use a single cluster image for all clusters.

D.Create separate cluster images per hardware model and apply to respective clusters.

AnswerD

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.

Why this answer

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.

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.

How to eliminate wrong answers

Option A is wrong because baseline groups are the legacy VUM (vSphere Update Manager) approach — they manage patches/VIBs but do not deliver firmware or a full desired-state image, so they do not meet the 'ESXi and firmware' requirement. Option B is wrong because host profiles enforce configuration (settings) compliance, not firmware or ESXi version updates. Option C is wrong because a single image cannot contain firmware/driver add-ons for multiple different hardware models — the OEM add-on is model-specific, so one image would fail compatibility on at least one model.

Practice this question →

24

Multi-Selectmedium

Which THREE are valid components of a vLCM single image? (Choose three.)

Select 3 answers

A.Virtual machine hardware versions

B.Additional VIBs and components

C.ESXi version and build number

D.vCenter Server version

E.Firmware and driver versions

AnswersB, C, E

A vLCM single image is composed of the base ESXi image plus additional VIBs and components layered onto it. This component layer lets administrators add third-party drivers or vendor agents while retaining one managed specification.

Why this answer

In vSphere Lifecycle Manager (vLCM), a single image is a declarative, cluster-level software specification that includes the ESXi base image (the ESXi version and build number, option C), additional VIBs and components layered on top of that base image (option B), and the firmware and driver add-ons delivered through hardware support managers (option E). Option C is correct because the base image defines the exact ESXi version and build the hosts will run. Option B is correct because components and additional VIBs are explicitly part of the image payload beyond the base ESXi image.

Option E is correct because firmware and driver versions are managed as part of the image via firmware add-ons and hardware support managers. Option A is not part of a vLCM image, since VM hardware versions are per-VM settings unrelated to host image management. Option D is not part of a vLCM image, because vCenter Server version is managed separately from the ESXi cluster image.

Exam trap

The trap here is that candidates often confuse the components of a vLCM single image with other vSphere lifecycle management concepts, such as VM hardware versions or vCenter Server version, which are not part of the ESXi host image specification.

Practice this question →

25

MCQmedium

A vSphere administrator is planning to upgrade a vSphere 7.0 U2 cluster to vSphere 8.0 U1. The cluster is managed by a vCenter Server 7.0 U2. The administrator wants to use vSphere Lifecycle Manager (vLCM) to manage the upgrade. What must the administrator do first?

A.Enable vLCM on the cluster and set the desired image to ESXi 8.0 U1.

B.Upgrade vCenter Server to version 8.0 U1.

C.Upgrade one ESXi host to 8.0 U1 manually to test compatibility.

D.Create a baseline for ESXi 8.0 U1 in vLCM.

AnswerB

vLCM image management requires the managing vCenter Server to run the same or newer version than the target ESXi release. Upgrading vCenter Server to 8.0 U1 first satisfies that dependency, enabling the cluster upgrade to 8.0 U1.

Why this answer

vLCM relies on the vCenter Server to orchestrate and push images to ESXi hosts. Since the vCenter Server version must be equal to or higher than the target ESXi version, upgrading vCenter Server to 8.0 U1 first is a prerequisite. Without this, vLCM cannot manage the ESXi 8.0 U1 image because the older vCenter lacks the necessary APIs and compatibility.

Exam trap

The trap here is that candidates often assume vLCM can be configured independently of vCenter version, or they confuse vLCM's image-based approach with the older baseline-based method, leading them to select options that involve baselines or direct host upgrades.

How to eliminate wrong answers

Option A is wrong because enabling vLCM and setting the desired image to ESXi 8.0 U1 is not possible until vCenter Server is upgraded; vLCM cannot manage an ESXi version newer than the vCenter version. Option C is wrong because manually upgrading a host to 8.0 U1 before upgrading vCenter would break management connectivity, as vCenter 7.0 U2 cannot manage ESXi 8.0 U1 hosts. Option D is wrong because vLCM uses images, not baselines; baselines are a feature of the older Update Manager (UM) workflow, not vLCM.

Practice this question →

26

MCQhard

A vSphere administrator is managing a vLCM cluster with a desired image that includes a custom partner add-on. During remediation, one host fails with the error: 'Failed to apply image. Cannot find VIB required by add-on.' The administrator verifies that the add-on is present in the image and that the host is compatible. What is the most likely cause of this error?

A.The custom add-on is not signed by VMware and is therefore rejected during remediation.

B.The host's software depot is not synchronized with the vCenter Server depot, causing the VIB to be unavailable.

C.The host's ESXi version is too new for the custom add-on to be installed.

D.The custom add-on depends on a VIB that is not included in the desired image or is not available in the depot.

AnswerD

Custom add-ons may have dependencies on other VIBs. If those dependency VIBs are not part of the desired image or are not present in the configured depot, vLCM cannot resolve them during remediation, resulting in the error. The administrator should verify the add-on's dependencies and ensure all required VIBs are included in the image or available in the depot.

Why this answer

Custom add-ons often have dependencies on other VIBs. If those dependency VIBs are not included in the desired image or are not available in the depot used by vLCM, remediation will fail with an error about missing VIBs. The administrator must ensure all required VIBs are included in the image or available in the depot.

Exam trap

The trap here is assuming that the add-on itself is self-contained and that any missing VIB error indicates a problem with the add-on rather than its dependencies.

Practice this question →

27

MCQmedium

An administrator sees that a vLCM remediation task for a host has failed with the error: 'The VIB is incompatible with the host's base image.' The host is using a custom image that includes a third-party driver. What is the most likely cause?

A.The third-party driver should be removed from the image.

B.The VIB version is not compatible with the ESXi version in the image.

C.The VIB is missing from the cluster image.

D.The administrator should ignore the error and proceed.

AnswerB

A VIB built against a different ESXi base version cannot be added to the image, since vLCM validates each VIB against the base image's ESXi build. The third-party driver's version targets an incompatible ESXi release.

Why this answer

The error 'The VIB is incompatible with the host's base image' specifically indicates that the VIB's compatibility metadata does not match the ESXi base image version. vLCM validates each VIB against the base image's ESXi version and will reject any VIB whose acceptance level or version constraints are not satisfied. Since the host uses a custom image with a third-party driver, the most likely cause is that the driver VIB was built for a different ESXi version than the one in the image.

Exam trap

VCP-DCV often tests the misconception that any VIB can be added to any image, but vLCM enforces strict version compatibility between VIBs and the base image.

How to eliminate wrong answers

Option A is wrong because removing the third-party driver would eliminate the custom functionality and is not the root cause; the error is about version incompatibility, not the presence of the driver. Option C is wrong because if the VIB were missing from the cluster image, the remediation would not attempt to install it and would not produce this specific incompatibility error. Option D is wrong because ignoring the error would leave the host in a non-compliant state and could cause instability or failure of the third-party driver.

Practice this question →

28

Drag & Dropmedium

Arrange the steps to convert a virtual machine to a template.

Drag or tap steps into the slots.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

To convert a VM to a template in vSphere, you must first power off the VM, then right-click it and select Convert to Template, confirm the operation, wait for the task to finish, and finally verify the template in the inventory. This ensures the VM is not in use and the conversion process is properly executed.

Practice this question →

29

MCQeasy

A customer wants to ensure that all hosts in a cluster run the same ESXi version and firmware. Which vSphere feature should they use?

A.vSphere Update Manager (VUM)

B.vSphere Lifecycle Manager (vLCM)

C.Host Profiles

D.vSphere Replication

AnswerB

vSphere Lifecycle Manager manages hosts through a desired-state image containing both ESXi base version and firmware add-ons, so remediating the cluster converges every host to identical software and firmware. Traditional baselines handle patches and upgrades but cannot enforce firmware consistency across hosts.

Why this answer

vSphere Lifecycle Manager (vLCM) manages a cluster against a single desired image that includes both the ESXi base image and firmware/add-ons, ensuring all hosts converge to the same ESXi version and firmware. This desired-state model is exactly what the customer needs to guarantee uniformity across the cluster.

Exam trap

VCP-DCV often tests the distinction between vLCM (image-based, includes firmware) and VUM (baseline-based, ESXi patches only), and the misconception that Host Profiles manage ESXi versions or firmware.

How to eliminate wrong answers

Option A is wrong because vSphere Update Manager (VUM) is the legacy baseline-based patching tool; it manages ESXi patches and some add-ons but does not manage firmware as part of a unified image, so it cannot guarantee identical firmware across hosts. Option C is wrong because Host Profiles enforce configuration consistency (networking, security, storage settings) but do not manage ESXi version or firmware updates. Option D is wrong because vSphere Replication is a disaster-recovery feature for replicating VMs between sites, unrelated to host version/firmware consistency.

Practice this question →

30

MCQmedium

A vLCM image is configured, but remediation fails with error: 'Image compliance check failed. Host does not have required add-on.' What should the administrator check first?

A.That the vCenter Service is running.

B.That the add-on is downloaded in the vLCM depot.

C.That the host has sufficient memory for the add-on.

D.That the host has internet access to download the add-on.

AnswerB

The error states the host lacks a required add-on, so the add-on component must exist in the vLCM depot before remediation can apply it. Verifying it is downloaded and available ensures the image can be composed and remediated successfully.

Why this answer

The error 'Image compliance check failed. Host does not have required add-on' indicates that the vLCM image includes an add-on component that is not present on the host. The first thing to check is whether that add-on is available in the vLCM depot, because if it is not downloaded, vLCM cannot apply it to the host.

Ensuring the add-on is in the depot is a prerequisite for successful remediation.

Exam trap

VCP-DCV often tests the assumption that the host needs internet access to download add-ons, but in vLCM, the vCenter server manages the depot, so the host does not require direct internet access.

How to eliminate wrong answers

Option A is wrong because the vCenter Service running is unrelated to the specific error about a missing add-on; if vCenter were down, you would not see this error. Option C is wrong because insufficient memory would typically cause a different error, not a missing add-on. Option D is wrong because the host does not download add-ons directly from the internet; vLCM uses the depot configured in vCenter, so internet access on the host is not required.

Practice this question →

31

MCQhard

An organization wants to upgrade ESXi hosts from 7.0 to 8.0 using vLCM. They have a cluster with mixed hardware (different NICs and HBAs). What is the best practice?

A.Create a custom image that includes all necessary drivers and add-ons for the mixed hardware.

B.Use vSphere Update Manager baselines instead of vLCM.

C.Use a single image with the latest ESXi version and no add-ons.

D.Upgrade hosts manually by booting from installation media.

AnswerA

A custom image built in vLCM bundles the specific NIC and HBA drivers plus add-ons required by the differing hardware, so every host in the mixed cluster remediates to one consistent, compatible image rather than failing validation against a vendor base image.

Why this answer

vLCM image-based management requires a single desired-state image per cluster, and that image must contain every driver, add-on, and component needed by all hosts in the cluster. With mixed hardware (different NICs and HBAs), the vendor add-on or custom image must bundle the appropriate async drivers so each host can boot and function after remediation. Creating a custom image that includes all necessary drivers and add-ons ensures the desired state is valid for every host, which is the documented best practice for heterogeneous clusters.

Exam trap

VCP-DCV often tests the misconception that a single vanilla ESXi image is sufficient for any cluster, ignoring that async drivers for NICs and HBAs must be included via vendor add-ons or custom images in vLCM.

How to eliminate wrong answers

Option B is wrong because vSphere Update Manager baselines are the legacy baseline-based approach and do not provide the desired-state image consistency the organization wants; vLCM supersedes UMB in vSphere 8. Option C is wrong because a single image with no add-ons will lack the async NIC/HBA drivers required by the mixed hardware, causing hosts to fail remediation or lose connectivity. Option D is wrong because manual installation media upgrades bypass vLCM entirely, defeating the purpose of using desired-state image management and introducing configuration drift.

Practice this question →

32

MCQeasy

An administrator needs to apply a security patch to a vLCM-managed cluster. The patch is available as an ESXi image in the vSphere Lifecycle Manager depot. What is the correct procedure?

A.Create a new desired state image with the patch, validate, and remediate the cluster.

B.Attach a patch baseline to the cluster and remediate.

C.Export the current image, add the patch, and import it to the cluster.

D.Use Quick Boot to apply the patch to each host individually.

AnswerA

vLCM manages hosts through a desired-state image rather than baselines. Adding the patch means editing the image to include the updated ESXi base image, validating it against the cluster, then remediating so each host converges to that declared state, satisfying the depot-sourced patch requirement.

Why this answer

In a vLCM-managed cluster, the correct procedure to apply a security patch is to create a new desired state image that includes the patch from the vSphere Lifecycle Manager depot, validate the image against the cluster's hardware and software compatibility, and then remediate the cluster. This ensures all hosts are updated to the exact same image specification, maintaining consistency and compliance with the desired state.

Exam trap

The trap here is confusing vLCM's image-based management with the legacy baseline-based patching method, leading candidates to incorrectly select attaching a patch baseline (Option B) instead of creating a new desired state image.

How to eliminate wrong answers

Option B is wrong because attaching a patch baseline is a legacy approach used with baseline-based updates, not supported in vLCM-managed clusters which use image-based management. Option C is wrong because exporting the current image, adding the patch, and importing it is not a supported workflow; vLCM requires creating a new desired state image from the depot, not manual image manipulation. Option D is wrong because Quick Boot is a feature to reduce reboot time during remediation, not a method to apply patches individually; vLCM applies updates to all hosts in the cluster via a single remediation operation.

Practice this question →

33

MCQhard

A vSphere administrator is troubleshooting a failed remediation attempt on an ESXi host in a cluster managed by vLCM. The image compliance status shows 'Non-Compliant'. The host is in maintenance mode. The administrator sees the following error: 'Failed to apply the software specification. Reason: The host's firmware version is incompatible with the selected ESXi image.' What is the most likely cause?

A.The hardware support manager (HSM) is not configured or the firmware baseline is outdated.

B.The host must be taken out of maintenance mode for the remediation to proceed.

C.The ESXi 8.0 image has deprecated certain drivers that are still in use.

D.The vLCM image is corrupted and needs to be re-imported.

AnswerA

vLCM compares host firmware against the hardware support manager's baseline during remediation. Without a configured HSM or with an outdated firmware baseline, the image's required firmware level cannot be validated or applied, producing the incompatibility error.

Why this answer

The error indicates that the host's firmware version is incompatible with the selected ESXi image. In vLCM, hardware compatibility is managed by the Hardware Support Manager (HSM), which provides firmware baselines. If the HSM is not configured or the firmware baseline is outdated, vLCM cannot validate or update the firmware to match the ESXi image requirements, leading to a 'Non-Compliant' status and remediation failure.

This is the most likely cause because the error directly points to firmware incompatibility, not driver issues or image corruption.

Exam trap

The trap here is that candidates may confuse firmware incompatibility with driver deprecation (Option C) or assume the host must be in maintenance mode (Option B), but the error message explicitly points to firmware version mismatch, which is managed by the HSM.

How to eliminate wrong answers

Option B is wrong because the host is already in maintenance mode, which is a prerequisite for remediation; taking it out of maintenance mode would not resolve the firmware incompatibility error. Option C is wrong because the error specifically mentions firmware version incompatibility, not deprecated drivers; while driver deprecation could cause issues, it would typically result in a different error message about missing or unsupported drivers. Option D is wrong because a corrupted vLCM image would likely produce a different error, such as 'Image import failed' or 'Invalid image', not a firmware version incompatibility error.

Practice this question →

34

MCQmedium

A vSphere administrator manages a vLCM cluster with a desired image. The administrator wants to add a new vendor add-on to the image. Before applying the change, the administrator needs to understand the impact. What happens when a vendor add-on is added to the desired image?

A.The cluster becomes non-compliant, and remediation is required to apply the add-on to all hosts.

B.The add-on is applied only to the host that is currently in maintenance mode.

C.The add-on is stored in the vLCM depot but not applied until the next ESXi upgrade.

D.The add-on is automatically installed on all hosts without remediation.

AnswerA

Adding a vendor add-on changes the desired image, so hosts no longer match it. vLCM marks the cluster as non-compliant. Remediation applies the new add-on to each host. This is the expected behavior when modifying the desired image, and it ensures all hosts receive the updated software consistently.

Why this answer

When a vendor add-on is added to the desired image, the cluster's target state changes. Hosts no longer match the desired image and are marked non-compliant. Remediation is required to apply the add-on to all hosts.

This ensures consistent software across the cluster and is the standard vLCM workflow.

Exam trap

The trap here is assuming the add-on is applied automatically or deferred, when in fact the cluster becomes non-compliant and requires remediation.

Practice this question →

35

Multi-Selecteasy

Which two are benefits of using vLCM over legacy baseline-based patching? (Choose two.)

Select 2 answers

A.Support for heterogeneous cluster configurations.

B.No requirement to put hosts in maintenance mode.

C.Real-time compliance monitoring of all hosts.

D.Built-in integration with vRealize Automation.

E.Single image management for cluster consistency.

AnswersC, E

vLCM continuously reconciles desired-state images against each host, reporting drift as it occurs rather than only at scheduled baseline scans. This satisfies the stem's compliance-monitoring benefit, since legacy baselines surface compliance solely during remediation runs, leaving drift undetected between scans.

Why this answer

Option C is correct because vLCM (vSphere Lifecycle Manager) continuously and automatically checks each host in the cluster against the desired image and reports drift in real time, unlike legacy baselines that require manual compliance scans. Option E is correct because vLCM manages the entire cluster from a single desired-state image (base ESXi image plus firmware add-ons and components), ensuring every host is identical and consistent, whereas baselines apply separate patch/extension baselines per host. Option A is not a vLCM benefit since vLCM requires homogeneous clusters with identical hardware and image, and heterogeneous configurations are actually a limitation.

Option B is incorrect because remediation with vLCM still requires hosts to enter maintenance mode (or use the quick-boot/stateless options) just as with baselines. Option D is incorrect because vLCM does not provide built-in integration with vRealize Automation; that is not a documented vLCM capability.

Practice this question →

36

MCQeasy

A vSphere administrator is responsible for a vLCM-managed cluster. The administrator needs to check whether the cluster's hosts match the desired image before performing remediation. Which vLCM feature provides this information?

A.Remediation pre-check

B.Hardware compatibility list (HCL) validation

C.Compliance check

D.Image export

AnswerC

The compliance check compares each host's current software and firmware against the desired image. It reports whether hosts are compliant or non-compliant and provides details on any discrepancies. This is the correct feature for verifying host alignment with the desired image before remediation.

Why this answer

The compliance check in vLCM compares each host's current state to the cluster's desired image and reports compliance status. It is the standard way to verify whether hosts match the desired image before remediation. Other features like pre-checks or HCL validation serve different purposes.

Exam trap

The trap here is confusing the compliance check with the remediation pre-check, which is a later step in the remediation workflow.

Practice this question →

37

MCQhard

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?

A.Use baseline groups to manage firmware separately.

B.Create a single cluster image that includes firmware for both vendors.

C.Create separate cluster images for each hardware vendor and apply to respective hosts.

D.Manually update firmware using vendor tools, then use vLCM for ESXi updates.

AnswerC

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.

Why this answer

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.

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.

How to eliminate wrong answers

Option A is wrong because baseline groups are a legacy vSphere Update Manager (VUM) construct, not part of vLCM image-based management; using them would abandon the desired-state model and not meet the requirement for consistent firmware updates via vLCM. Option B is wrong because a single cluster image cannot include firmware for both vendors—firmware add-ons are vendor-specific and mutually exclusive; attempting to combine them would cause validation errors or apply incorrect firmware. Option D is wrong because manual firmware updates via vendor tools break the vLCM desired-state model, introduce drift, and do not provide the consistent, automated firmware compliance that vLCM image-based management is designed to deliver.

Practice this question →

38

MCQmedium

A company has multiple clusters with different hardware. They want to create separate vLCM images for each cluster. What is the best practice?

A.Create a single image that includes all possible components.

B.Use baseline groups instead of images.

C.Create separate images for each cluster tailored to their hardware.

D.Use Auto Deploy with a single image.

AnswerC

Hardware-specific firmware add-ons cannot be shared across dissimilar hosts, so a single image would flag mismatches. Creating one image per cluster, tailored to its hardware, keeps each cluster compliant and is the documented vLCM best practice.

Why this answer

vLCM (vSphere Lifecycle Manager) images are cluster-scoped and must match the hardware compatibility of the hosts in that cluster. Because the company has multiple clusters with different hardware, the best practice is to create a separate image per cluster, tailoring the firmware add-on, driver add-on, and ESXi base image to that cluster's specific server models. This ensures HCL compliance and avoids remediation failures caused by incompatible drivers.

Exam trap

VCP-DCV often tests the misconception that a single vLCM image can serve heterogeneous clusters, or that baseline groups are still the recommended approach — candidates must recognize that image-based management is cluster-scoped and hardware-specific.

How to eliminate wrong answers

Option A is wrong because a single image containing all possible components would include drivers and firmware for hardware not present in each cluster, causing HCL violations and remediation errors — vLCM images are validated against the actual host hardware. Option B is wrong because baseline groups are the legacy vSphere Update Manager (VUM) approach; vLCM image-based management is the modern replacement and the question explicitly states image-based management is in use. Option D is wrong because Auto Deploy is a stateless provisioning mechanism, not an image management strategy, and a single image across heterogeneous hardware would fail HCL checks.

Practice this question →

39

MCQeasy

During a vLCM remediation, one host fails with error 'Could not complete the operation due to a network error'. What is the first troubleshooting step?

A.Reset the vLCM image.

B.Check network connectivity between vCenter and the host.

C.Restart the vLCM service.

D.Reboot the host.

AnswerB

The error explicitly cites a network problem, so verifying connectivity between vCenter and the ESXi host is the logical first step. Remediation depends on that channel, and a dropped or blocked connection would halt the operation before any configuration issue matters.

Why this answer

The error 'Could not complete the operation due to a network error' during vLCM remediation indicates that vCenter Server lost communication with the ESXi host mid-operation. Since vLCM remediation pushes an image payload from vCenter to the host over the management network, the first logical step is to verify that vCenter can reach the host on the management VMkernel interface (typically port 443 and 902). Confirming connectivity rules out transient network issues before touching the vLCM image or host state.

Exam trap

VCP-DCV often tests whether candidates jump to remediation actions (reset image, restart service, reboot) instead of performing basic connectivity troubleshooting first when the error message explicitly names a network condition.

How to eliminate wrong answers

Option A is wrong because resetting the vLCM image discards the desired-state configuration and does not address the underlying connectivity failure that produced the error. Option C is wrong because restarting the vLCM service on vCenter does not fix a network path problem between vCenter and the host, and would only be relevant if the service itself were hung. Option D is wrong because rebooting the host is a disruptive action that should never be the first step when the error explicitly points to a network condition.

Practice this question →

40

Multi-Selecteasy

An administrator is managing a vSphere cluster with vSphere Lifecycle Manager baselines. Which THREE are valid baseline types? (Choose three.)

Select 3 answers

A.Patch baseline

B.Firmware baseline

C.Upgrade baseline

D.Critical Hosts baseline

E.Extension baseline

AnswersA, C, E

Patch baselines are a valid vSphere Lifecycle Manager baseline type, grouping ESXi patches and updates for remediation across hosts. They satisfy the stem's requirement by letting administrators scan and remediate clusters against curated patch collections, distinct from upgrade and extension baselines, which handle version upgrades and additional components respectively.

Why this answer

In vSphere Lifecycle Manager, baselines are categorized into three valid types: Patch, Upgrade, and Extension. Option A (Patch baseline) is correct because patch baselines contain a collection of patches (VIBs) that can be applied to hosts to update or remediate them without changing the major ESXi version. Option C (Upgrade baseline) is correct because upgrade baselines contain an ESXi image that upgrades hosts to a new major version (for example, from ESXi 7 to ESXi 8).

Option E (Extension baseline) is correct because extension baselines contain additional VIBs, such as third-party drivers or custom extensions, that are not part of the standard patch or upgrade process. Option B (Firmware baseline) is not a valid baseline type in vSphere Lifecycle Manager baselines; firmware updates are handled through firmware add-ons in desired-state images, not baselines. Option D (Critical Hosts baseline) is not a valid baseline type; there is no such baseline category in vSphere Lifecycle Manager.

Exam trap

VCP-DCV often tests the boundary between baseline types and image-based management, tricking candidates into selecting 'firmware baseline' because firmware is a real vLCM concept — but it belongs to images, not baselines.

Practice this question →

41

MCQhard

A vSphere administrator is using vSphere Lifecycle Manager (vLCM) to manage a cluster with a single image. After a recent hardware upgrade, one host in the cluster has a new network adapter that is not listed in the vSphere Compatibility Guide for the current ESXi version. The administrator attempts to remediate the cluster. What will happen?

A.The remediation will succeed, but the network adapter will be disabled until a compatible driver is installed.

B.The remediation will proceed, but the host will be marked as non-compliant after the update.

C.The remediation will succeed, and vLCM will automatically download and install the required driver from the internet.

D.The remediation will fail with an error indicating that the host hardware is not compatible with the image.

AnswerD

vLCM validates the desired image against each host's hardware compatibility. If a network adapter is not on the vSphere Compatibility Guide for the target ESXi version, the host fails the compatibility check, and remediation cannot proceed. The error will explicitly state the incompatibility.

Why this answer

vLCM enforces hardware compatibility before remediation. A network adapter not on the vSphere Compatibility Guide for the target ESXi version causes the host to be non-compliant, and remediation fails with a compatibility error. The correct answer reflects this pre-check behavior.

Exam trap

The trap here is thinking that vLCM will attempt remediation and then report issues, rather than blocking the update upfront due to hardware incompatibility.

Practice this question →

42

Matchingmedium

Match each vSphere security feature to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Virtual Trusted Platform Module for VM encryption

Restricts direct root access to ESXi

Single sign-on authentication for vSphere

Replaces default certificates with custom ones

Encrypts vMotion traffic between hosts

Why these pairings

The correct matches are: ESXi Firewall controls network traffic, VM Encryption encrypts VM files, and vTPM provides virtual TPM. Common confusions involve swapping these definitions.

Practice this question →

43

MCQhard

Based on the exhibit, what is the most likely cause of the remediation failure?

A.The local depot is not configured.

B.The DNS server is unable to resolve depot.vmware.com.

C.The vLCM service is not running on vCenter.

D.A firewall is blocking outbound HTTPS traffic to the internet.

AnswerD

vSphere Lifecycle Manager pulls firmware and software payloads from online depots over HTTPS. If outbound HTTPS to the internet is blocked, remediation cannot download the components, so the task fails while hardware compatibility checks may still pass.

Why this answer

A firewall blocking outbound HTTPS traffic to the internet would cause a connection timeout when vSphere Lifecycle Manager (vLCM) tries to reach the public VMware depot. This matches the error shown in the exhibit. Option A is incorrect because the local depot is not the source of the timeout; the issue is with external connectivity.

Option B is incorrect because a DNS resolution failure would typically produce a 'Name or service not known' error, not a timeout. Option C is incorrect because if the vLCM service were not running, the error would likely indicate a service unavailability, not a network timeout.

Practice this question →

44

MCQhard

A company uses vSphere 7 with vLCM. They want to update hosts in a cluster with a new ESXi version. The cluster has mixed hardware. What is the recommended method?

A.Use vSphere Update Manager baseline

B.Manually upload ISO to each host

C.Use cluster image management

D.Use Auto Deploy

AnswerC

Cluster image management applies a single desired-state image across all hosts, letting vLCM remediate each host to the target ESXi version while validating against its specific hardware. This handles mixed hardware without per-host baselines, which is the recommended vSphere 7 approach.

Why this answer

For a vSphere 7 cluster with mixed hardware managed by vLCM, the recommended method to update ESXi is cluster image management. vLCM's cluster image is a single desired-state image that includes the ESXi base version plus vendor add-ons and firmware/driver add-ons, and it handles hardware diversity by letting you include the appropriate vendor add-ons for each host model.

Exam trap

VCP-DCV often tests the distinction between the legacy VUM baseline model and the vLCM image model — candidates who default to 'baseline' answers miss that vLCM clusters use cluster images, not baselines.

How to eliminate wrong answers

Option A is wrong because vSphere Update Manager baselines are the legacy (pre-vLCM) approach and do not provide the desired-state image model that vLCM uses; baselines are still supported but not the recommended method for vLCM-managed clusters. Option B is wrong because manually uploading an ISO to each host is error-prone, does not scale, and bypasses vLCM's compliance tracking entirely. Option D is wrong because Auto Deploy is a stateless provisioning mechanism for booting ESXi hosts from images, not the update method for an existing vLCM cluster with mixed hardware.

Practice this question →

45

MCQeasy

What is the purpose of the 'Export System Logs' option in vSphere Lifecycle Manager?

A.Collect logs for troubleshooting

B.Create a recovery image

C.Back up configuration

D.Transfer logs to vCenter

AnswerA

Export System Logs bundles vSphere Lifecycle Manager and related service logs into a downloadable archive, giving support and administrators the diagnostic evidence needed to troubleshoot remediation, compliance, or sync failures without manually gathering files from each component.

Why this answer

The 'Export System Logs' option in vSphere Lifecycle Manager (vLCM) is designed to gather diagnostic information from the vLCM components, including the vLCM service logs, image depot logs, and related vCenter Server logs. This bundled log archive is used by VMware support and administrators to troubleshoot issues such as image compliance failures, remediation errors, or depot synchronization problems. It does not create backups or recovery images; it is purely a diagnostic tool.

Exam trap

VCP-DCV often tests the distinction between diagnostic and backup/recovery functions, so candidates may confuse 'Export System Logs' with configuration backup or image export features.

How to eliminate wrong answers

Option B is wrong because creating a recovery image is not the purpose of exporting logs; recovery images are typically created via backup solutions or vSphere Replication, not vLCM. Option C is wrong because backing up configuration involves exporting vCenter configuration data (e.g., via VAMI or vSphere Client), not system logs. Option D is wrong because transferring logs to vCenter is not the primary goal; logs are exported to a local file or a remote syslog server, not specifically to vCenter, and vLCM already runs on vCenter.

Practice this question →

46

MCQhard

An administrator is using vSphere Lifecycle Manager (vLCM) to manage a cluster with a single image. The image includes a base ESXi image and a vendor add-on. During remediation, the task fails with the error: 'Cannot remediate host because the desired image contains a component that is not compatible with the host.' Which action should the administrator take first to resolve this issue?

A.Remove the incompatible component from the image and remediate again.

B.Update the host's firmware to the latest version and retry remediation.

C.Remove the host from the cluster and add it back.

D.Check the vSphere Compatibility Guide for the component's supported hardware and ESXi versions.

AnswerD

The error indicates a compatibility issue. The first step is to verify whether the component is supported on the host's hardware and ESXi version. The vSphere Compatibility Guide provides this information. This helps determine if the component can be used or if an alternative is needed.

Why this answer

When vLCM remediation fails due to an incompatible component, the administrator must first determine why the component is incompatible. The vSphere Compatibility Guide lists supported hardware, drivers, and ESXi versions for components. Checking it helps identify if the component is supported on the host or if an update or alternative is needed.

This systematic approach avoids unnecessary changes.

Exam trap

The trap here is jumping to remove the component or update firmware without first verifying compatibility, which could lead to further issues or not resolve the root cause.

Practice this question →

47

MCQeasy

A company plans to deploy a new homogeneous cluster with vSphere 8. They want to use vLCM to simplify lifecycle management. What is the recommended approach for maintaining the ESXi hosts?

A.Define a single cluster image and apply it to all hosts.

B.Manually upgrade each host via ISO and then import into vLCM.

C.Use vSphere baselines to manage patches.

D.Create separate images for each host based on its hardware.

AnswerA

A single cluster image satisfies the homogeneous hardware constraint, letting vLCM manage every host against one desired-state specification. Because all hosts share identical components, firmware and driver add-ons apply uniformly, avoiding per-host baselines. vLCM then remediates drift automatically, keeping the whole cluster compliant with the image.

Why this answer

vLCM (vSphere Lifecycle Manager) uses a desired-state model where a single cluster image defines the ESXi base image, vendor add-on, and firmware. Applying one image to all hosts in a homogeneous cluster ensures consistency and simplifies patching and upgrades.

Exam trap

VCP-DCV often tests vLCM vs VUM baselines — candidates pick 'baselines' because they are familiar with older vSphere versions, missing that vLCM image-based management is the recommended approach for vSphere 8 homogeneous clusters.

How to eliminate wrong answers

Option B is wrong because manually upgrading each host via ISO defeats the purpose of vLCM and introduces drift; vLCM is designed to manage the entire lifecycle from a single image. Option C is wrong because vSphere baselines are the legacy vSphere Update Manager (VUM) approach; vLCM replaces baselines with images for image-managed clusters. Option D is wrong because creating separate images per host based on hardware contradicts the 'homogeneous cluster' premise and increases management overhead; vLCM images are per-cluster, not per-host.

Practice this question →

48

MCQeasy

What is the purpose of the vLCM hardware compatibility check?

A.Verify ESXi build

B.Check storage performance

C.Check if hardware is on HCL

D.Validate network drivers

AnswerC

vLCM's hardware compatibility check validates each host's CPU, storage controllers, NICs and drivers against the VMware Compatibility Guide, confirming the hardware appears on the HCL for the intended ESXi version. This satisfies the stem's requirement by preventing remediation of clusters containing unsupported components, which would otherwise fail during firmware or driver updates.

Why this answer

The vLCM hardware compatibility check validates that the host's physical hardware (CPU, storage controllers, NICs, HBAs) is listed on the VMware Hardware Compatibility List (HCL) for the target ESXi version. This ensures the image being applied is supported on that hardware, preventing unsupported configurations that could cause instability or void support.

Exam trap

VCP-DCV often tests whether candidates confuse the HCL check (hardware compatibility) with driver validation or build verification — the HCL check is specifically about whether the physical hardware is certified for the ESXi version.

How to eliminate wrong answers

Option A is wrong because verifying the ESXi build is a version/compliance check, not a hardware compatibility check — vLCM already knows the build from the image spec. Option B is wrong because storage performance benchmarking is not part of vLCM; that would be handled by tools like HCIBench or vSAN Performance Diagnostics. Option D is wrong because validating network drivers is a subset of driver/firmware compliance, but the HCL check is broader — it covers all hardware components against VMware's compatibility database, not just network drivers.

Practice this question →

49

MCQeasy

A vSphere administrator needs to apply a critical ESXi security patch to a cluster of 10 hosts. The cluster is managed by vLCM using image-based management. What is the correct procedure to apply the patch?

A.Create a new baseline group with the patch and attach it to the cluster.

B.Update the cluster image to include the patched version and remediate the cluster.

C.Manually update each host using the patch's ISO.

D.Use vCenter Update Manager to push the patch as a baseline.

AnswerB

Updating the cluster image to include the patched ESXi version, then remediating the cluster, satisfies image-based management's requirement that desired state be declared at cluster level. vLCM compares each host against the image and applies only the delta, patching all 10 hosts consistently without per-host baselines.

Why this answer

In vLCM image-based management, patches are applied by updating the cluster's image to a newer ESXi base image version that includes the patch, then remediating the cluster. vLCM computes the difference between the current host state and the desired image state and applies only the necessary changes, rolling through hosts per the remediation settings (e.g., maintenance mode, DRS). This is the correct image-based workflow.

Exam trap

VCP-DCV often tests the confusion between legacy VUM baselines and modern vLCM images — candidates who default to 'create a baseline' miss that image-based clusters require updating the image itself, not attaching a baseline.

How to eliminate wrong answers

Option A is wrong because baselines and baseline groups belong to the legacy VUM workflow, not image-based management — vLCM images do not use baselines. Option C is wrong because manually applying an ISO bypasses vLCM entirely, breaks the desired-state model, and is not the correct procedure in an image-managed cluster. Option D is wrong because vCenter Update Manager (the legacy VUM) is not used for image-based clusters; vLCM is the integrated replacement, and pushing a baseline contradicts the image-based model.

Practice this question →

50

MCQeasy

A company wants to minimize downtime during an ESXi upgrade from 7.0 to 8.0 on a vSAN cluster. What is the best approach?

A.Upgrade all hosts simultaneously to complete faster.

B.Upgrade vCenter Server first, then upgrade all hosts at once.

C.Place each host in maintenance mode, evacuate vSAN data, upgrade, and rejoin the cluster.

D.Use Quick Boot feature to speed up the upgrade process.

AnswerC

Maintenance mode with full data evacuation maintains vSAN availability throughout the upgrade, satisfying the no-downtime constraint. Each host's data is migrated to remaining cluster members before remediation, and the host rejoins once upgraded, avoiding any storage outage.

Why this answer

The correct approach is to place each host in maintenance mode, evacuate vSAN data, upgrade, and rejoin the cluster. This ensures vSAN data availability and cluster quorum are maintained throughout the upgrade, minimizing downtime. vSAN requires that data be migrated off a host before it enters maintenance mode with 'Ensure Accessibility' or 'Full Data Migration' to preserve policy compliance.

Exam trap

VCP-DCV often tests the misconception that upgrading all hosts simultaneously is faster and acceptable, but candidates must remember that vSAN requires data evacuation and quorum maintenance to avoid downtime.

How to eliminate wrong answers

Option A is wrong because upgrading all hosts simultaneously would cause a complete vSAN outage and data unavailability, as no hosts would be available to serve storage. Option B is wrong because upgrading vCenter first is necessary but upgrading all hosts at once still causes a full outage; vCenter upgrade alone does not address host upgrade sequencing. Option D is wrong because Quick Boot only speeds up the reboot phase of an upgrade but does not evacuate vSAN data or maintain availability; it is not a substitute for proper maintenance mode evacuation.

Practice this question →

51

MCQhard

An administrator is troubleshooting a failed vSphere Lifecycle Manager remediation operation on a cluster. The error message in the vLCM UI states: 'Hardware Compliance Check failed: The ESXi host does not meet the hardware requirements for the selected image.' The administrator verifies that the host is in the vSphere Hardware Compatibility List (HCL) for the ESXi version. What additional step should the administrator take to resolve this issue?

A.Remove the host from the cluster and re-add it after a clean installation.

B.Use the vSphere Client to export the host's hardware compatibility report.

C.Update the vLCM hardware compatibility plug-in to the latest version.

D.Manually add the host's hardware to the vCenter server's HCL database.

AnswerC

The hardware compatibility check is performed by the vLCM hardware compatibility plug-in, which holds its own HCL data separate from the web HCL. An outdated plug-in can misreport a supported host as incompatible, so updating it refreshes that data.

Why this answer

The error indicates that vLCM's hardware compatibility check failed even though the host is on the HCL. This often occurs when the vLCM hardware compatibility plug-in (provided by the hardware vendor) is outdated or not installed, preventing vLCM from correctly assessing the host's hardware against the desired image. Updating the plug-in to the latest version ensures accurate compliance checks.

Exam trap

The trap is assuming that HCL listing alone guarantees vLCM compliance — candidates may overlook that the hardware compatibility plug-in must be current for vLCM to correctly evaluate the host.

How to eliminate wrong answers

Option A is wrong because removing and re-adding the host does not address the underlying plug-in issue and would cause unnecessary downtime. Option B is wrong because exporting a hardware compatibility report is a diagnostic step, not a resolution; it does not fix the compliance check failure. Option D is wrong because administrators cannot manually add hardware to vCenter's HCL database; the HCL is maintained by VMware and vendors, and vLCM relies on vendor-provided plug-ins for hardware compatibility data.

Practice this question →

52

MCQmedium

A vSphere administrator manages a cluster of six ESXi 8.0 hosts with vSphere Lifecycle Manager. The cluster's desired image specifies an ESXi base image and two add-ons: a vendor NIC driver add-on and a storage add-on. During a remediation pre-check, one host reports a hardware compatibility warning: its NIC firmware is older than the minimum version required by the vendor NIC driver add-on. The administrator wants to resolve the warning without removing the add-on from the image. Which action should the administrator take?

A.Put the host into maintenance mode and then run remediation with the option to skip hardware compatibility checks.

B.Update the host's NIC firmware to the minimum version required by the vendor add-on, then remediate the cluster again.

C.Remove the vendor NIC driver add-on from the desired image and add it back after remediation completes.

D.Replace the vendor NIC driver add-on with a generic ESXi base image driver and remediate the cluster.

AnswerB

vLCM validates hardware firmware against the requirements of vendor add-ons in the desired image. The warning indicates a firmware version mismatch, not a missing add-on. Updating the NIC firmware to the required level satisfies the add-on's dependency, and the cluster can then remediate successfully while keeping the desired image unchanged.

Why this answer

The warning is caused by host NIC firmware being older than the minimum version required by the vendor add-on in the desired image. vLCM checks firmware compatibility as part of remediation pre-checks. Updating the firmware to the required level resolves the warning while preserving the desired image and its add-ons, allowing remediation to proceed normally.

Exam trap

The trap here is assuming the warning can be bypassed or that the add-on must be removed, when the actual fix is updating the host firmware to meet the add-on's requirement.

Practice this question →

53

MCQmedium

After adding a new ESXi host to a vLCM-managed cluster, the compliance status shows 'Non-Compliant'. All other hosts in the cluster are compliant. The cluster uses a custom image. Which is the most likely cause of the non-compliance?

A.The cluster image has not been exported to the host.

B.The host profile is not attached to the host.

C.The cluster image is corrupted.

D.The host's software inventory differs from the cluster image.

AnswerD

A newly added host retains its original software inventory, so any divergence from the cluster image's specified components, drivers or firmware triggers Non-Compliant status. vLCM compares each host's actual software against the image's desired state; because the other hosts already match, only this host's differing inventory explains the result.

Why this answer

In vSphere Lifecycle Manager (vLCM), a cluster image defines the exact desired software specification (ESXi base image, firmware add-ons, and components) for all hosts. When a new host is added, vLCM compares its actual software inventory against the cluster image. If any installed VIB, driver, or component version differs from the image, the host is marked Non-Compliant.

Since all other hosts are compliant, the cluster image itself is valid and properly applied; the new host simply hasn't been remediated to match the image yet. Therefore, the most likely cause is that the host's software inventory differs from the cluster image.

Exam trap

VCP-DCV often tests the misconception that adding a host to a vLCM cluster automatically makes it compliant, when in fact the host must be remediated to match the cluster image.

How to eliminate wrong answers

Option A is wrong because vLCM does not 'export' cluster images to hosts; it applies the image during remediation, and the image is already defined at the cluster level. Option B is wrong because host profiles are a separate feature used with vSphere Configuration Profiles or legacy host profiles, not the primary compliance mechanism for vLCM cluster images. Option C is wrong because if the cluster image were corrupted, all hosts in the cluster would likely show non-compliance, not just the newly added host.

Practice this question →

54

MCQeasy

A vSphere administrator manages a cluster that is currently using vSphere Lifecycle Manager (vLCM) images. The administrator needs to make the cluster use a baseline-based remediation approach instead. Which action should the administrator take?

A.Deactivate the image from the cluster, then attach baselines and remediate.

B.Remediate the cluster with a baseline while the image remains active.

C.Create a new baseline and attach it to the cluster, then remediate.

D.Delete the cluster from vCenter and recreate it without vLCM.

AnswerA

To switch from image-based to baseline-based management, the administrator must deactivate the image on the cluster. This removes the desired image and allows baselines to be attached. After deactivation, the cluster can be managed with baselines and remediated accordingly. This is the correct procedure to change the cluster's lifecycle management approach.

Why this answer

A cluster managed by vLCM images cannot simultaneously use baselines. To switch to baseline-based remediation, the administrator must deactivate the image on the cluster. This action removes the image-based desired state and enables baseline attachment.

After deactivation, baselines can be attached and remediation performed. This is the supported method to change the management approach without recreating the cluster.

Exam trap

The trap here is assuming that baselines can be attached to a cluster that is already managed by an image, but vLCM enforces mutual exclusivity between images and baselines.

Practice this question →

55

MCQhard

A vSphere administrator is trying to create a custom ESXi image for a cluster using vSphere Lifecycle Manager. The cluster contains hosts with a specific hardware that requires a third-party component (e.g., a NIC driver). The administrator adds the component to the image definition in vLCM. However, when applying the image, the component does not get installed on the hosts. What is the likely cause?

A.The component version is not compatible with the ESXi version in the image.

B.The administrator did not mount the component ISO during remediation.

C.The component is not signed by a trusted certificate authority.

D.The component must be installed manually on each host first.

AnswerA

vLCM validates each component against the ESXi base image's acceptance level and version dependencies. A component built for a different ESXi release is silently skipped during remediation, so the NIC driver never installs despite being present in the image definition.

Why this answer

In vSphere Lifecycle Manager (vLCM), a custom ESXi image is composed of a base ESXi version plus additional components (drivers, firmware). Each component has a compatibility matrix that specifies which ESXi versions it supports. If the component version added to the image definition is not compatible with the ESXi version in the image, vLCM will not install it during remediation — the component is effectively ignored or the image fails validation.

This is the most likely cause when a component silently does not get installed.

Exam trap

VCP-DCV often tests whether candidates overlook version compatibility between the component and the ESXi base image, instead blaming ISO mounting, signing, or manual installation — the exam expects you to know that vLCM enforces a compatibility matrix.

How to eliminate wrong answers

Option B is wrong because vLCM does not require mounting a component ISO during remediation — components are added to the image definition and vLCM handles delivery. Option C is wrong because while component signing is important, an untrusted signature would typically produce a validation error, not a silent non-installation; the more common cause is version incompatibility. Option D is wrong because vLCM is designed to install components automatically as part of the image; manual installation defeats the purpose of the desired-state model.

Practice this question →

56

Multi-Selecthard

An administrator is managing a vSphere 8 cluster with vSphere Lifecycle Manager (vLCM) using a single image. The cluster's desired image includes an ESXi base image and a vendor add-on. The administrator needs to add a custom VIB that is not part of any depot. Which two steps are required to include this custom VIB in the vLCM image? (Choose two.)

Select 2 answers

A.Upload the custom VIB to a local depot or a web server accessible by vLCM.

B.Manually install the custom VIB on each host using ESXCLI before remediation.

C.Add the custom VIB to the cluster's desired image using the 'Add Component' option.

D.Convert the custom VIB to a firmware add-on.

E.Disable image compliance checks to allow unsigned VIBs.

AnswersA, C

vLCM can only use software from configured depots. To include a custom VIB, it must be added to a depot that vLCM can access. This can be a local depot on the vCenter Server or a web server hosting an offline depot. Without this step, the VIB will not appear in the image customization options.

Why this answer

To include a custom VIB in a vLCM image, the VIB must first be made available in a depot that vLCM can access, such as a local or web-based depot. Then, it can be added as a component to the cluster's desired image. Manual installation or disabling checks are not valid approaches.

Exam trap

The trap here is thinking that manually installing the VIB on hosts or disabling compliance checks will make it part of the vLCM image, when in fact the VIB must be in a depot and added as a component.

Practice this question →

57

Drag & Dropmedium

Place the steps to create a new standard virtual switch in vSphere in order.

Drag or tap steps into the slots.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

The correct sequence for creating a new standard virtual switch in vSphere is: select a host, access its networking settings, click Add Networking, choose the connection type (e.g., Virtual Machine), and finally create and configure the new standard switch. This order ensures you follow the wizard's logical steps and avoid errors.

Practice this question →

58

MCQmedium

An administrator manages a cluster of 10 identical ESXi hosts using vLCM with image-based management. After importing a new hardware support package (HSP) and applying a new image specification, 5 hosts report non-compliant with the error 'Firmware version not supported'. The compliant hosts and non-compliant hosts are from the same vendor model. What is the most likely cause?

A.The image specification was applied only to the compliant hosts.

B.The non-compliant hosts have a different manufacturer than the compliant ones.

C.The vLCM service failed to download the HSP to the non-compliant hosts.

D.The firmware version on the non-compliant hosts is newer than what the hardware support package supports.

AnswerD

An HSP bundles validated firmware baselines per server model. Hosts already flashed beyond that validated version fail the image compliance check with 'Firmware version not supported', since vLCM cannot downgrade or match them to the package's supported firmware level.

Why this answer

The error 'Firmware version not supported' in vLCM image-based management indicates that the HSP (Hardware Support Package) included in the image specification does not support the firmware version currently running on the non-compliant hosts. HSPs are vendor-provided bundles that define supported firmware/driver combinations for specific hardware models. If the hosts have a newer firmware version than what the HSP was validated against, vLCM flags them as non-compliant because the HSP cannot guarantee compatibility.

Since all hosts are the same vendor model, the difference must be in firmware version, not hardware model or image application.

Exam trap

VCP-DCV often tests the distinction between image application errors and firmware compatibility errors, tricking candidates into choosing options about image distribution or hardware differences when the real issue is firmware version mismatch with the HSP.

How to eliminate wrong answers

Option A is wrong because if the image specification were applied only to the compliant hosts, the non-compliant hosts would not be evaluated against the new image at all, and they would not report a firmware version error; they would simply remain at their previous compliance state. Option B is wrong because the scenario explicitly states all hosts are from the same vendor model, so a different manufacturer is impossible. Option C is wrong because a failure to download the HSP would typically result in a download or connectivity error, not a 'Firmware version not supported' error; the HSP is already imported and applied, and the error specifically points to firmware incompatibility.

Practice this question →

59

Matchingmedium

Match each vSphere storage concept to its definition.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Cluster file system for VM storage

Network file system protocol for VM storage

Block storage protocol over IP networks

Raw device mapping for direct LUN access

Hyper-converged storage from local disks

Why these pairings

Correct matches: VMFS is a cluster file system for block storage; NFS is a network file system for NAS; vSAN aggregates local disks for shared storage; VVols enable VM-level storage management. Common confusions: mixing VMFS and vSAN definitions, or swapping NFS and VMFS.

Practice this question →

60

MCQeasy

An administrator wants to stage updates to reduce downtime during remediation of a vLCM-managed cluster. What should they configure?

A.Enable 'Stage remediation' in the cluster image configuration.

B.Enable 'Quick Boot' to speed up reboots.

C.Configure the cluster to use a rolling schedule.

D.Create multiple host images for each host.

AnswerA

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.

Why this answer

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.

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.

How to eliminate wrong answers

Option B is wrong because Quick Boot speeds up the reboot itself by skipping certain firmware/hardware initialization, but it does not stage updates or reduce the time spent downloading and preparing payloads — it addresses a different phase. Option C is wrong because a rolling schedule controls the order and concurrency of remediation across hosts, not the staging of update payloads; it reduces risk but not the per-host downtime from downloading. Option D is wrong because creating multiple host images per host defeats the purpose of vLCM's desired-state model and does not stage updates — it fragments management and does not reduce remediation downtime.

Practice this question →

61

Multi-Selecthard

A vSphere administrator is managing a vLCM cluster with a desired image. The administrator needs to update the ESXi base image to a newer version. Before initiating remediation, the administrator wants to validate the image to ensure it is compatible with all hosts in the cluster. Which two actions should the administrator take to validate the image? (Choose two.)

Select 2 answers

A.Manually compare the image's VIB list with each host's installed VIBs.

B.Use the 'Validate Image' feature in the vLCM interface.

C.Run the 'Check Compliance' operation on the cluster.

D.Export the image to an ISO and test it on a standalone host.

E.Check the vSphere Compatibility Guide for the ESXi version.

AnswersB, C

vLCM provides a 'Validate Image' function that checks the desired image for internal consistency, such as missing VIBs, dependency conflicts, and compatibility with the cluster's hosts. It performs a pre-check to ensure the image is valid and can be remediated. This feature is specifically designed to validate the image before applying it. Hence, this action is correct.

Why this answer

To validate a desired image before remediation, the administrator should use vLCM's 'Check Compliance' operation and the 'Validate Image' feature. These tools automatically check for compatibility, dependencies, and potential issues with the hosts, ensuring a smooth remediation process.

Exam trap

The trap here is assuming that manual checks or external documentation can substitute for vLCM's built-in validation, which is specifically designed to catch image and host compatibility issues.

Practice this question →

62

MCQmedium

A vSphere administrator is planning to upgrade a vSphere 7.0 U3 cluster to vSphere 8.0. The cluster currently uses vSphere Lifecycle Manager (vLCM) with a single image. After the upgrade, the administrator wants to ensure that all ESXi hosts apply firmware updates from a hardware support manager (HSM) integrated with vLCM. Which step must the administrator take before starting the cluster upgrade?

A.Disable vLCM and use baseline-based remediation for the upgrade.

B.Create separate baselines for ESXi and firmware and attach them to the cluster.

C.Remove the HSM integration because vLCM cannot apply firmware updates.

D.Ensure the desired ESXi version and firmware component are specified in the vLCM image.

AnswerD

vLCM only applies firmware through the hardware support manager when the firmware component is declared in the cluster image. Specifying both the target ESXi version and firmware component in that image before upgrading ensures hosts apply HSM-delivered firmware, satisfying the stated requirement.

Why this answer

VLCM with a single image can include both the ESXi version and firmware components from an integrated hardware support manager (HSM). By specifying the desired ESXi version and firmware component in the vLCM image, the administrator ensures that during the cluster upgrade, vLCM will apply the firmware updates provided by the HSM as part of the image-based remediation process. This is the required step before starting the upgrade to vSphere 8.0.

Exam trap

The trap here is that candidates may think vLCM cannot handle firmware updates or that separate baselines are needed, when in fact vLCM's single-image approach with HSM integration is designed to manage both ESXi and firmware updates together.

How to eliminate wrong answers

Option A is wrong because disabling vLCM and reverting to baseline-based remediation would lose the single-image management and HSM integration capabilities, which are key to applying firmware updates in a unified manner. Option B is wrong because vLCM with a single image does not use separate baselines for ESXi and firmware; instead, it uses a single image that includes both components, and attaching separate baselines would conflict with the image-based approach. Option C is wrong because vLCM can apply firmware updates when integrated with an HSM, and removing the HSM would prevent firmware updates from being applied during the upgrade.

Practice this question →

63

MCQeasy

A vSphere administrator wants to ensure that all ESXi hosts in a cluster boot from a consistent set of software packages, including firmware and drivers. Which vSphere feature should be used to achieve this?

A.vSphere Update Manager (VUM)

B.vSphere Lifecycle Manager (vLCM) with a single image

C.Host Profiles

D.Quick Boot

AnswerB

vLCM with a single image defines one desired-state image per cluster, containing the ESXi base image plus firmware and driver add-ons from the HSM. Remediation enforces that exact image on every host, satisfying the requirement for a consistent set of software packages.

Why this answer

vSphere Lifecycle Manager (vLCM) with a single image is the correct choice because it allows the administrator to define a complete software specification—including ESXi version, firmware, drivers, and add-ons—as a single desired state image. When applied to a cluster, vLCM ensures every ESXi host boots from exactly the same set of software packages, eliminating drift and guaranteeing consistency across all hosts.

Exam trap

The trap here is that candidates often confuse Host Profiles (which manage configuration settings) with image-based lifecycle management, not realizing that Host Profiles cannot enforce firmware or driver versions, while vLCM with a single image provides a holistic, boot-level software consistency.

How to eliminate wrong answers

Option A is wrong because vSphere Update Manager (VUM) applies updates and patches but does not enforce a single, unified image that includes firmware and driver baselines across all hosts; it operates on individual baselines and can leave hosts with different software combinations. Option C is wrong because Host Profiles capture host-level configuration settings (e.g., networking, storage, security) but do not manage firmware or driver versions; they are not designed to control the boot-time software package set. Option D is wrong because Quick Boot is a feature that reduces reboot time during updates by skipping hardware reinitialization; it has no role in ensuring consistent software packages across hosts.

Practice this question →

64

MCQmedium

An administrator sees the above error in the vLCM remediation history. What is the most likely cause?

A.The desired image validation failed before remediation.

B.The host's acceptance level does not allow the VIB.

C.The host firmware is incompatible with the VIB.

D.The vCenter Server cannot reach the VMware depot.

AnswerD

The vLCM remediation history error indicates the vCenter Server failed to download metadata or payloads from the VMware depot, confirming a connectivity fault rather than a host-side configuration issue. This satisfies the stem's constraint: remediation requires the vCenter Server to reach the online depot, so blocked outbound HTTPS access is the most likely cause.

Why this answer

The error shown in the vLCM remediation history indicates a failure to download the desired image components. vLCM relies on the vCenter Server to fetch VIBs and software depots from the VMware online depot (or a local depot). If the vCenter Server cannot reach the VMware depot due to network issues, proxy misconfiguration, or firewall blocks (e.g., port 443 to *.vmware.com), the remediation will fail with a download error, not a validation or acceptance-level error.

Exam trap

The trap here is that candidates often confuse a depot connectivity error with a VIB acceptance-level or validation error, because all can prevent remediation, but only the depot error manifests as a download failure in the remediation history.

How to eliminate wrong answers

Option A is wrong because a validation failure would produce a specific error message about image compliance or component mismatch, not a download failure. Option B is wrong because an acceptance-level mismatch would generate a host-level error during VIB installation, not a depot connectivity issue. Option C is wrong because firmware incompatibility is checked during hardware compatibility validation, not during depot download, and would produce a different error related to hardware support.

Practice this question →

65

MCQeasy

An administrator wants to use vLCM to manage a cluster with 10 ESXi hosts. After enabling vLCM, what is the first step to ensure all hosts are running the same desired image?

A.Define a desired state image for the cluster.

B.Remediate the cluster immediately to apply the default image.

C.Place all hosts into maintenance mode.

D.Create a host upgrade baseline and attach it to the cluster.

AnswerA

Defining a desired-state image establishes the cluster's target software specification, which vLCM then remediates each host against. This directly satisfies the stem's requirement to bring all ten ESXi hosts to a consistent image, since vLCM compares each host's current state to the image and flags drift for remediation.

Why this answer

With vLCM, the first step after enabling it on a cluster is to define a desired state image. This image specifies the exact ESXi version, firmware, and driver versions that all hosts in the cluster must match. Without defining this image, vLCM has no target configuration to validate or enforce against the hosts.

Exam trap

The trap here is that candidates often confuse vLCM's image-based approach with the legacy baseline-based workflow from Update Manager, leading them to select option D, or they assume remediation can proceed without first defining a desired state image.

How to eliminate wrong answers

Option B is wrong because remediating the cluster immediately would apply a default image that does not exist; vLCM requires an explicit desired state image to be defined before any remediation can occur. Option C is wrong because placing hosts into maintenance mode is a prerequisite for remediation, not the first step after enabling vLCM; the image must be defined first. Option D is wrong because vLCM does not use host upgrade baselines; baselines are a legacy Update Manager concept, and vLCM uses images and image-based clusters instead.

Practice this question →

66

MCQmedium

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?

A.The software depot URL in the image is incorrect or unreachable.

B.The hosts cannot communicate with the vCenter Server.

C.The image validation failed due to missing dependencies.

D.The desired image was not saved after adding the patch.

AnswerA

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.

Why this answer

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.

Exam trap

The trap here is that candidates may 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.

How to eliminate wrong answers

Option B is wrong because if hosts cannot communicate with vCenter Server, the remediation would likely fail with a different error, such as 'Host connection lost' or 'Cannot communicate with host', not a depot retrieval error. Option C is wrong because image validation failures due to missing dependencies produce errors like 'Missing dependency' or 'Conflicting packages', not 'Cannot retrieve software depots'. Option D is wrong because if the desired image was not saved, the patch would not be included in the image, but the remediation would either proceed without the patch or fail with a different error; the depot retrieval error is unrelated to saving the image.

Practice this question →

67

MCQmedium

An administrator manages a vSphere 8 cluster that is currently using vSphere Lifecycle Manager (vLCM) with a single image. The cluster contains hosts from two different server vendors. The administrator needs to add a firmware add-on to the image to ensure firmware compliance. Which vLCM component must be present in the image to enable firmware updates?

A.Vendor add-on

B.Hardware Support Manager (HSM)

C.Component

D.Base ESXi image

AnswerB

Hardware Support Manager is a vLCM component that enables firmware updates for hosts. It is required in the desired image to manage firmware and drivers. Without HSM, firmware remediation is not possible. This is correct because HSM provides the necessary integration with hardware vendors to apply firmware updates during remediation.

Why this answer

Firmware updates in vLCM are performed through the Hardware Support Manager (HSM), which must be included in the desired image. The HSM integrates with vendor tools to apply firmware updates during remediation. Without HSM, the image can still update ESXi software but cannot manage firmware, so the administrator must ensure HSM is present to meet the requirement.

Exam trap

The trap here is assuming that a vendor add-on or base image automatically includes firmware management, when actually a separate Hardware Support Manager component is required.

Practice this question →

68

MCQeasy

An administrator is planning to decommission a vSphere cluster that currently uses baseline-based lifecycle management. They want to adopt image-based management for a new cluster. Which action must be taken to ensure a clean migration?

A.Manually recreate the baselines as images in the new cluster.

B.Assign host profiles to the new cluster to enforce configuration.

C.Export the existing baseline group and import it into the new cluster.

D.Create a new cluster with image-based management.

AnswerD

Creating a separate cluster lets vLCM manage hosts through a single desired-state image, avoiding the baseline-to-image conversion conflicts that arise when both methods coexist on the same cluster. This satisfies the clean migration constraint by keeping legacy baseline assignments isolated from the new image-based lifecycle management.

Why this answer

Image-based lifecycle management in vSphere Lifecycle Manager (vLCM) is a cluster-level construct; a cluster is either baseline-based or image-based, and you cannot convert an existing baseline-managed cluster in place. To adopt image-based management, you must create a new cluster configured for image-based management and then move hosts into it.

Exam trap

The trap is assuming baselines can be converted or exported into images; the exam tests whether you know that image-based management requires a new cluster because the two modes are mutually exclusive at the cluster level.

How to eliminate wrong answers

Option A is wrong because baselines and images are fundamentally different constructs — baselines are collections of patches/VIBs applied to hosts, while images are declarative desired-state specifications for an entire cluster, so you cannot simply recreate baselines as images. Option B is wrong because host profiles enforce configuration compliance and are orthogonal to lifecycle management; assigning them does not migrate a cluster from baseline to image-based management. Option C is wrong because baseline groups cannot be exported and imported as images; the data models are incompatible and vLCM does not provide such a conversion path.

Practice this question →

69

Multi-Selectmedium

An administrator is planning to migrate from legacy baselines to vLCM for a cluster. Which TWO statements are true about vLCM?

Select 2 answers

A.vLCM allows individual host remediation for flexibility.

B.vLCM uses a desired state image to manage host configurations.

C.vLCM supports different images for different hosts in the same cluster.

D.vLCM can integrate with Hardware Support Manager for firmware updates.

E.vLCM uses baseline groups to apply updates.

AnswersB, D

vLCM replaces per-host baselines with a single desired-state image declared for the whole cluster. Hosts are remediated to match that image, so this statement accurately describes vLCM's core model and satisfies the stem's migration-planning question.

Why this answer

Option B is correct because vLCM (vSphere Lifecycle Manager) operates on a desired-state image model, where an administrator defines a single image (base ESXi version plus components and firmware add-ons) that the cluster's hosts are remediated to match. Option D is correct because vLCM integrates with a Hardware Support Manager (HSM) provided by OEM vendors, enabling firmware updates to be delivered alongside ESXi and driver updates through the same image. Option A is not correct because vLCM enforces a cluster-wide image, so remediation is applied at the cluster level rather than allowing per-host flexibility as legacy baselines did.

Option C is not correct because all hosts in a vLCM-managed cluster must conform to the same desired-state image; different images per host are not supported within one cluster. Option E is not correct because baseline groups are a feature of legacy vSphere Update Manager baselines, not vLCM, which replaces baselines with images.

Exam trap

The trap here is that candidates confuse vLCM's cluster-wide image with the older baseline-based approach, mistakenly thinking vLCM supports per-host flexibility or baseline groups, when in fact it enforces a single desired state image for the entire cluster.

Practice this question →

70

MCQmedium

An administrator notices that after applying a vLCM image to a cluster, some hosts fail compliance with error: 'Host does not have required add-on'. What is the most likely cause?

A.The add-on is not present in the vLCM depot.

B.The vCenter license does not include vLCM.

C.The host is not in maintenance mode during the check.

D.The host does not have internet access to download the add-on.

AnswerA

An add-on compliance failure means the desired image references an add-on component that the vLCM depot cannot resolve, so hosts report it as missing. Adding the required add-on to the depot, or removing it from the image specification, restores compliance.

Why this answer

vLCM image compliance checks compare the host's installed software against the desired image, including base image, components, and add-ons. The error 'Host does not have required add-on' means the image references an add-on (e.g., a vendor add-on like NSX or a custom add-on) that is not available in the configured depot. Without the add-on in the depot, vLCM cannot remediate the host to match the image.

Exam trap

VCP-DCV often tests the misconception that compliance errors relate to maintenance mode or licensing, when the specific 'required add-on' message points to depot content availability.

How to eliminate wrong answers

Option B is wrong because vLCM is included in all vSphere editions that support it (Enterprise Plus and above); a license issue would produce a different error, not a missing add-on. Option C is wrong because maintenance mode is required for remediation, not for compliance checking — compliance can be evaluated while the host is running. Option D is wrong because hosts do not download add-ons directly from the internet; vLCM uses the depot configured in vCenter (online or offline), so internet access on the host is irrelevant.

Practice this question →

71

MCQmedium

Refer to the exhibit. What is the cause of the non-compliance?

A.The host has an outdated firmware version

B.The compliance scan failed

C.The host's hardware is not supported

D.The host is running an older ESXi version than desired

AnswerD

Compliance against a desired-state baseline fails when the host's actual ESXi build does not match the specified target version. Running an older ESXi version than the image requires is precisely the drift that marks the host non-compliant.

Why this answer

In vSphere Lifecycle Manager (vLCM) image-based compliance, a host is marked non-compliant when its installed ESXi version does not match the version specified in the desired image. The exhibit shows a version mismatch between the host's current ESXi build and the target image, which is the direct cause of non-compliance. Firmware, scan failures, and hardware support are separate checks that would produce different error indicators.

Exam trap

The trap is conflating firmware compliance with ESXi version compliance — candidates see 'non-compliant' and pick firmware, but the exhibit's version mismatch specifically points to an older ESXi build.

How to eliminate wrong answers

Option A is wrong because outdated firmware is reported under the firmware add-on compliance check, not as a general ESXi version non-compliance, and the exhibit points to a version delta. Option B is wrong because a failed compliance scan produces a 'scan error' or 'unknown' state, not a definitive non-compliant result with a version mismatch. Option C is wrong because unsupported hardware would prevent the host from being added to the cluster or image at all, rather than showing a version-based non-compliance.

Practice this question →

72

MCQeasy

A vSphere administrator is using vSphere Lifecycle Manager (vLCM) to manage an ESXi cluster. The administrator wants to check the compliance status of the cluster against the desired image without making any changes. Which vLCM operation should the administrator perform?

A.Scan

B.Export

C.Remediate

D.Import

AnswerA

Scanning checks each host's current state against the desired image and reports compliance without applying any changes. It is a read-only operation that provides the compliance status. This is exactly what the administrator needs to verify compliance without modifying hosts.

Why this answer

The Scan operation in vLCM evaluates each host's software and firmware against the desired image and produces a compliance status without making changes. Remediation would apply updates, while import and export deal with image management rather than compliance checking. Therefore, scanning is the correct operation to assess compliance safely.

Exam trap

The trap here is confusing scanning with remediation; scanning only reports compliance, while remediation actually applies the desired state.

Practice this question →

Ready to test yourself?

Try a timed practice session using only vSphere Lifecycle Management questions.

Start 20-question session