VCP-DCV vSphere Lifecycle Management Practice Test 3 — 15 Questions

Question 1

An administrator is planning to upgrade ESXi hosts using vLCM. Which of the following are prerequisites for using vLCM? (Choose TWO)

Accepted Answer

The hosts must be in a cluster.. Option C is correct because vLCM (vSphere Lifecycle Manager) operates at the cluster level: hosts must be organized into a vSphere cluster, and images/baselines are managed and remediated per cluster rather than per standalone host. Option D is correct because vLCM with desired-state images was introduced in vSphere 7.0, so the managing vCenter Server must be version 7.0 or later to expose the vLCM image-based workflow. Option A is not required, since vLCM can use the vSphere Lifecycle Manager depot (online) or an offline depot/UMDS without every host reaching the internet directly. Option B is not a real prerequisite, as vLCM is included with vCenter licensing rather than needing a separate 'vLCM license'. Option E is not required, because vLCM does not mandate static IP addresses; DHCP-addressed hosts can still be managed and remediated.

Answer

All hosts must be connected to the internet.

Answer

The vCenter must have a valid vLCM license.

Answer

Each host must have a static IP address.

Question 2

An administrator is troubleshooting a failed vLCM remediation. Which two methods can be used to collect diagnostic information? (Choose TWO)

Accepted Answer

Check the vLCM log file at /var/log/vmware/vlcm/vlcm.log on the vCenter Server.. Option C is correct because vLCM (vSphere Lifecycle Manager) writes its operational and remediation diagnostics to /var/log/vmware/vlcm/vlcm.log on the vCenter Server, making it the primary log source for troubleshooting failed remediations. Option D is correct because the vLCM REST API exposes task history and remediation task details, allowing an administrator to query the specific task, its status, and error messages programmatically. Option A is not appropriate because vCenter Server alert logs capture triggered alarms rather than the detailed vLCM remediation diagnostics needed here. Option B is not valid because there is no 'vcli diagnostics' command on vCenter Server; the supported CLI is vSphere Client or the vLCM API, not a vcli diagnostics utility. Option E is incorrect because esxcli system syslog config only manages syslog forwarding configuration on an ESXi host and does not retrieve vLCM remediation diagnostics.

Answer

Review the vCenter Server alert logs.

Answer

Run vcli diagnostics on the vCenter Server.

Answer

Use esxcli system syslog config to check host logs.

Question 3

Refer to the exhibit. What is the cause of the compliance failure?

Accepted Answer

The vLCM depot does not contain the required component.. The compliance failure in vLCM (vSphere Lifecycle Manager) occurs when the desired state image references a component that is not present in the configured depot. vLCM compares the host's current components against the image's component list; if a required component (e.g., a specific driver or firmware) is missing from the depot, the host cannot be remediated and shows as non-compliant. The exhibit likely shows a missing component in the depot, making option C the correct cause.

Answer

The vLCM service is down.

Answer

The host is missing a required driver.

Answer

The host has an incompatible component.

Question 4

Refer to the exhibit. Which hosts are affected by the remediation failure?

Accepted Answer

Only Host3. Based on the exhibit (not shown), the remediation failure affects only Host3. In vLCM, remediation failures are typically host-specific, and the exhibit likely shows that Host1 and Host2 were successfully remediated or are compliant, while Host3 failed due to a specific issue such as a missing add-on or connectivity problem. Therefore, only Host3 is affected.

Answer

Host1 and Host2

Answer

None

Answer

All three hosts

Question 5

Refer to the exhibit. What is the most likely cause of the failure?

Accepted Answer

The vCenter cannot reach the VMware depot.. The exhibit (not shown) likely displays an error indicating that vCenter cannot reach the VMware depot, such as a connection timeout or SSL error when trying to download components. In vLCM, if vCenter cannot access the online depot, it cannot download the required software components, leading to remediation failure. The most likely cause is a network or proxy issue preventing vCenter from reaching the VMware depot.

Answer

The component is already downloaded.

Answer

The vLCM service is not running.

Answer

The component is corrupted.

Question 6

An administrator notices that after applying a baseline to hosts, some hosts fail to reboot properly. What is the most likely cause?

Accepted Answer

Incompatible hardware. When hosts fail to reboot properly after a baseline is applied, the most likely cause is incompatible hardware. vSphere Update Manager (VUM) or vLCM remediations may include firmware or driver updates that are not supported by the host's hardware, causing boot failures.

Answer

Network misconfiguration

Answer

Incorrect BIOS settings

Answer

Insufficient memory

Question 7

A vSphere environment uses vLCM with a desired state model. A host is non-compliant because it has a different firmware version. What is the correct way to remediate?

Accepted Answer

Import a new image with correct firmware. In vLCM's desired-state model, firmware is part of the image definition alongside the ESXi base version and components. To remediate a host that is non-compliant due to a different firmware version, you must update the image definition to include the correct firmware version (via a firmware add-on component) and then remediate the cluster. Importing a new image with the correct firmware is the correct approach.

Answer

Manually update firmware from vendor

Answer

Use a baseline to enforce firmware

Answer

Disable vLCM and use Update Manager

Question 8

A cluster has mixed hardware vendors. The administrator wants to use a single vLCM image specification for all hosts. What is the best approach?

Accepted Answer

Use a generic ESXi image without vendor add-ons. A generic ESXi image without vendor add-ons contains only VMware's base VIBs and is hardware-agnostic, so it can be applied uniformly across hosts from different vendors. Vendor add-ons inject vendor-specific drivers and agents that may conflict or be irrelevant on other vendors' hardware, so omitting them allows a single image spec to work across the mixed cluster.

Answer

Do not use vLCM

Answer

Create a composite image with add-ons for each vendor

Answer

Use separate images per vendor

Question 9

A vSphere 8 environment uses vLCM. An administrator wants to enable Quick Boot during remediation. What is the prerequisite?

Accepted Answer

ESXi hosts must be version 7.0 or later. Quick Boot is a vSphere 7.0 and later feature that allows ESXi hosts to skip the full BIOS POST and firmware initialization during reboot, dramatically reducing remediation time. vLCM leverages this capability only when the host runs ESXi 7.0 or later, because the underlying Quick Boot API and boot process optimizations were introduced in that release. Therefore, the prerequisite is that ESXi hosts must be version 7.0 or later.

Answer

BIOS must support UEFI

Answer

Hosts must be in a cluster with DRS enabled

Answer

vCenter Server must be updated

Question 10

Which TWO conditions are required to use vLCM for firmware management? (Select TWO.)

Accepted Answer

Hardware support manager (HSM) installed for each vendor. Option A is correct because vLCM firmware management relies on a vendor-provided Hardware Support Manager (HSM) plugin, installed per vendor, that integrates with vCenter to deliver and apply firmware updates to the hosts. Option E is correct because the cluster must have vLCM (vSphere Lifecycle Manager) enabled as its image-based management method; firmware management is a capability of the vLCM desired-state image, so a cluster still using baselines cannot use it. Option B is not required as stated, since vLCM firmware management is available in vSphere 7.0 and later but the question asks for conditions specific to firmware management rather than a version floor, and vCenter 7.0 alone is not the gating condition. Option C is not required because vLCM images can include hardware support for mixed hardware as long as the HSM covers the vendors and models present. Option D is not required because vLCM firmware remediation does not depend on DRS being in fully automated mode.

Answer

vCenter Server 7.0 or later

Answer

All hosts in the cluster must be identical hardware

Answer

Hosts must be in a fully automated DRS cluster

Question 11

Which THREE are valid methods to remediate ESXi hosts using vSphere Lifecycle Manager? (Select THREE.)

Accepted Answer

Stage and remediate. Option C (Stage and remediate) is valid because vSphere Lifecycle Manager allows you to first stage the desired ESXi image or baseline to the host, then remediate during a maintenance window, minimizing downtime. Option D (Remediate immediately) is valid because vLCM can apply the image or baseline to the host right away, which is the default remediation action when you do not stage first. Option E (Schedule remediation) is valid because vLCM supports scheduling remediation tasks at a chosen date and time, letting you control when hosts enter maintenance mode and are updated. Options A (Auto update) and B (Push from vCenter) are not recognized remediation methods in vSphere Lifecycle Manager; remediation is initiated from vCenter but 'push from vCenter' is not a distinct vLCM remediation mode, and vLCM does not provide an 'auto update' remediation option.

Answer

Auto update

Answer

Push from vCenter

Question 12

Which TWO components are part of a vLCM cluster image? (Select TWO.)

Accepted Answer

ESXi version. A vLCM cluster image is composed of the ESXi base image, which specifies the ESXi version (option B), and one or more vendor add-ons (option C), which bundle OEM drivers, tools, and firmware components supplied by the hardware vendor. The ESXi version defines the core hypervisor build, while the vendor add-on layers vendor-specific packages on top of that base image, and together these are the two required building blocks of a cluster image in vSphere Lifecycle Manager. Firmware and drivers add-on (option A) is not a separate image component; firmware is delivered through the hardware support manager and drivers come via vendor add-ons. vCenter Server version (option D) is irrelevant because vLCM manages ESXi hosts, not the vCenter appliance itself. Baseline groups (option E) belong to the legacy Update Manager baseline-based remediation model, not to the image-based vLCM workflow.

Answer

Firmware and drivers add-on

Answer

vCenter Server version

Answer

Baseline group

Question 13

Refer to the exhibit. Why did the remediation fail?

Accepted Answer

The host was not in maintenance mode. vSphere Lifecycle Manager (and legacy Update Manager) requires a host to be placed in maintenance mode before remediation can proceed, because patching or upgrading requires the host to evacuate its running workloads and reboot. If the host is not in maintenance mode, the remediation task fails with an error indicating the host is not in the required state. The exhibit (implied) shows this failure condition.

Answer

The host was in maintenance mode

Answer

The host failed to connect to vCenter

Answer

The host had VMs running

Question 14

Refer to the exhibit. What does this output indicate?

Accepted Answer

The host has been upgraded to ESXi 8.0.0, but the previous profile remains. The exhibit (not shown) likely displays an ESXi host with an upgraded version (8.0.0) and a previous profile still listed, indicating that the host was upgraded but the old profile remains in the boot configuration. This is a common scenario after an upgrade where the previous image profile is retained for rollback purposes.

Answer

The host has two ESXi installations and can boot into either

Answer

The host's profile is corrupted

Answer

The host is running both versions simultaneously

Question 15

A vSphere administrator is planning to upgrade ESXi hosts in a cluster from version 7.0 to 8.0 using vSphere Lifecycle Manager. The cluster currently uses a baseline-based upgrade. The administrator wants to leverage a desired state image for better consistency. What is the first step to transition from baseline-based to image-based management?

Accepted Answer

Detach all baselines from the cluster in turn.. The first step to transition a cluster from baseline-based to image-based management in vSphere Lifecycle Manager is to detach all baselines from the cluster. vLCM requires that a cluster be managed by either baselines or a single image, not both. Detaching baselines removes the baseline-based configuration and allows the administrator to then create and apply a desired-state image. This is the documented prerequisite before enabling image-based management.

Answer

Export the cluster's baseline compliance report.

Answer

Create a new cluster image from the vSphere Lifecycle Manager image catalog.

Answer

Delete all existing baselines and baseline groups.