VCP-DCV Practice Test 5 — 10 Questions

Question 1

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

Accepted Answer

Patch baseline. 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.

Answer

Firmware baseline

Answer

Critical Hosts baseline

Question 2

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?

Accepted Answer

The VIB version is not compatible with the ESXi version in the image.. 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.

Answer

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

Answer

The VIB is missing from the cluster image.

Answer

The administrator should ignore the error and proceed.

Question 3

A vSphere administrator wants to prevent users in a custom role from powering off virtual machines that have Fault Tolerance enabled. Which privilege must be removed from the custom role?

Accepted Answer

VirtualMachine.Interrupt.PowerOff. The privilege VirtualMachine.Interrupt.PowerOff directly controls the ability to power off a virtual machine, including those with Fault Tolerance enabled. Removing this privilege from a custom role prevents users from performing a power-off operation on any VM, including FT-protected ones. Other privileges like Suspend, Reset, or PowerOn do not govern the power-off action, so they are irrelevant to this requirement.

Answer

VirtualMachine.State.Suspend

Answer

VirtualMachine.Interrupt.Reset

Answer

VirtualMachine.Interrupt.PowerOn

Question 4

An administrator configures a VDS with two uplinks and sets the load balancing policy to 'Route based on IP hash'. What additional configuration is required on the physical switches to ensure proper traffic distribution?

Accepted Answer

Configure a static EtherChannel.. 'Route based on IP hash' on a vSphere Distributed Switch requires the physical switch ports to be configured as a static EtherChannel (or equivalent LAG). IP hash uses a hash of source and destination IPs to select an uplink, and the physical switch must treat the uplinks as a single logical link so return traffic flows correctly.

Answer

Use individual ports with no aggregation.

Answer

Set port security to allow multiple MAC addresses.

Answer

Enable Link Aggregation Control Protocol (LACP).

Question 5

An administrator notices that a virtual machine on an NFS datastore is experiencing intermittent performance degradation. The ESXi hosts are connected to the NFS server via a 10 GbE network. The administrator uses esxtop and sees high average latency on the storage device, but the NFS server reports low latency. What is the most likely cause?

Accepted Answer

Network congestion is causing TCP retransmissions. The most likely cause is network congestion causing TCP retransmissions. When the ESXi host sees high average latency on the NFS datastore but the NFS server reports low latency, it indicates that the delay is occurring in the network path between the host and the server, not on the server itself. TCP retransmissions due to network congestion would cause the host to experience higher latency than the server, matching the symptoms.

Answer

Jumbo frames are enabled on the ESXi hosts but not on the NFS server

Answer

The NFS server is performing data deduplication on the datastore

Answer

The NFS datastore is mounted with read-only permissions

Question 6

Refer to the exhibit. An ESXi 7.0 host is being configured for vSphere Trust Authority. The administrator runs the command shown and gets the output. What does this indicate?

Accepted Answer

The host does not have a TPM 2.0 chip, so vSphere Trust Authority cannot be used.. The output shows 'No TPM device found', which indicates that the ESXi 7.0 host does not have a TPM 2.0 chip installed or it is not detected by the system. vSphere Trust Authority (vTA) requires a TPM 2.0 chip on each ESXi host to establish hardware-based attestation and secure the trusted infrastructure. Without a TPM 2.0, the host cannot participate in vTA, making option C correct.

Answer

The TPM 2.0 device is present but not accessible.

Answer

The command is incorrect; the correct command is 'esxcli system visorfs tpm list'.

Answer

The host has a TPM 2.0 chip but it is not supported by ESXi.

Question 7

What is the maximum number of paths that vSphere supports for a single storage device?

Accepted Answer

32. vSphere supports up to 32 paths per storage device. 4 paths is common for some arrays, 8 is typical but not the maximum, and 256 is too high.

Answer

8

Answer

256

Answer

4

Question 8

An administrator observes that a VM with 4 vCPUs running on a host with hyperthreading enabled shows high %CSTP (co-stop) values in esxtop. What is a likely cause?

Accepted Answer

The VM has CPU affinity configured forcing vCPUs to specific pCPUs.. High %CSTP (co-stop) in esxtop indicates that the VM's vCPUs are waiting for each other to be co-scheduled on physical CPUs. CPU affinity forcing vCPUs to specific pCPUs can restrict the scheduler's ability to co-schedule all vCPUs simultaneously, leading to co-stop. This is a likely cause when a VM has multiple vCPUs and affinity constraints.

Answer

The VM's memory reservation is too high.

Answer

The host has deep C-states enabled causing CPU idle savings.

Answer

The host memory is overcommitted causing swapping.

Question 9

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?

Accepted Answer

Check the vLCM cluster image for any components specific to the reference host's hardware that are not present in the failed hosts.. 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.

Answer

Reboot the failed hosts and retry the remediation.

Answer

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

Answer

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

Question 10

A company is implementing vSphere 7.0 and wants to encrypt all vMotion traffic between ESXi hosts in a cluster. The cluster is not using any other encryption features. What is the minimum requirement to enable vMotion encryption?

Accepted Answer

The ESXi hosts must have a host profile applied with encryption enabled.. In vSphere 7.0, enabling vMotion encryption does not require Active Directory, a Key Management Server, Enhanced vMotion Compatibility (EVC), or host profiles. The minimum requirement is simply to configure the vMotion encryption policy on each ESXi host (set to 'Required' or 'Opportunistic'). No additional infrastructure or profiles are needed.

Answer

A VM Encryption Key Management Server must be configured.

Answer

The ESXi hosts must be joined to an Active Directory domain.

Answer

The cluster must be configured with Enhanced vMotion Compatibility (EVC).