VCP-DCV Practice Test 2 — 30 Questions

Question 1

An administrator is planning a vCenter Server deployment for a large environment with 15 ESXi hosts and 300 VMs. The environment requires high availability for vCenter Server. Which deployment topology should the administrator choose?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

A VCSA configured with vCenter HA (active-passive).. vCenter HA (active-passive) is the native, supported high-availability solution for VCSA, providing automatic failover between an active, passive, and witness node. For a large environment (15 hosts, 300 VMs) requiring vCenter HA, this topology ensures minimal downtime and is the recommended approach in modern vSphere versions.

Answer

A Windows vCenter Server with a mirrored SQL database.

Answer

A single VCSA with an embedded database.

Answer

A VCSA deployed with an external Platform Services Controller.

Question 2

A vSphere administrator is deploying VMs on a vSAN cluster with 6 hosts. Each host has two disk groups, each with one cache SSD and four capacity SSDs. The administrator applies a storage policy using RAID 5 erasure coding with Number of failures to tolerate set to 1. After some time, the administrator notices that several VMs are showing compliance status as 'Non-compliant'. Investigating further, the administrator finds that on one host, the cache SSD of the first disk group has failed. The capacity SSDs in that disk group are still functional. The vSAN cluster still has sufficient overall capacity and the health service shows no other issues. What is the most likely reason for the VMs' non-compliance?

Accepted Answer

The failed cache device makes the entire disk group unavailable, so components on that disk group are inaccessible.. A failed cache device renders the entire disk group non-operational; any VM components on that disk group become inaccessible, causing non-compliance. Option A is incorrect because cache capacity is not a compliance factor. Option B is incorrect because loss of a single cache device does not remove a fault domain. Option C is incorrect because the number of hosts with cache devices is still sufficient.

Answer

The failed cache device reduces the overall cache capacity, causing the policy to be violated.

Answer

The vSAN cluster has lost a fault domain due to the failed cache device.

Answer

The RAID 5 policy requires a minimum of 4 hosts with cache devices, and now only 5 are available.

Question 3

An administrator notices that HTTP connections to the ESXi host are timing out frequently. Based on the exhibit, which configuration change would most likely resolve the issue?

Accepted Answer

Increase maxKeepAliveTimeout to a higher value, such as 180. Increasing maxKeepAliveTimeout to a higher value, such as 180, would most likely resolve the issue of HTTP connections timing out frequently. The maxKeepAliveTimeout setting controls how long the ESXi host's reverse proxy (rhttpproxy) keeps an HTTP connection open for keep-alive requests. If it is too low, connections may time out prematurely, causing frequent timeouts. Increasing it allows longer-lived connections.

Answer

Restart the rhttpproxy service

Answer

Set useProxy to true and specify a proxy server

Answer

Set maxKeepAliveTimeout to 0 to disable keepalive

Question 4

Sequence the steps to configure a VM to use a static IP address via vSphere's customization specification.

Accepted Answer

Initiate customization, then select or create a customization specification, then configure the IP settings within the specification, then apply the customization, then power on the VM.. The correct sequence ensures that the VM receives the static IP configuration during the first boot after customization. Initiating the customization opens the wizard, selecting or creating a spec defines the settings, configuring IP within the spec sets the static address, applying saves the configuration, and powering on triggers the OS customization process.

Answer

Initiate customization, then configure IP settings, then select or create a customization specification, then apply, then power on.

Answer

Power on the VM, then initiate customization, then select or create a specification, then configure IP, then apply.

Answer

Initiate customization, then select or create a specification, then apply, then configure IP, then power on.

Question 5

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

Accepted Answer

vCenter Server with vLCM and hardware support manager (HSM). 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.

Answer

Manual download of firmware ISOs

Answer

Dell OpenManage Enterprise

Answer

vSphere Update Manager baseline

Question 6

A large financial institution runs a vSphere 7.0 environment with 100 ESXi hosts and 2,000 VMs. The security team has identified that several VMs are vulnerable to a critical side-channel attack that requires disabling hyperthreading on the ESXi hosts. The administrator needs to implement a solution that minimizes performance impact while ensuring compliance. The environment uses DRS clusters with varying workloads: some VMs are CPU-intensive (financial modeling) and others are memory-bound (database servers). The administrator cannot afford to take hosts offline for maintenance during business hours. The change must be implemented within 48 hours. Which course of action should the administrator take?

Accepted Answer

Place each host in maintenance mode individually, disable hyperthreading in the host BIOS, reboot the host, and then move to the next host. Rebalance VMs after all hosts are updated.. Disabling hyperthreading to mitigate side-channel attacks (e.g., L1TF or MDS) requires a host BIOS change, which necessitates a reboot. The only supported method in vSphere 7.0 is to place each host into maintenance mode, change the BIOS setting, reboot, and then repeat for all hosts. This approach minimizes performance impact by allowing VMs to be migrated via vMotion and avoids simultaneous downtime, meeting the 48-hour requirement without taking all hosts offline during business hours.

Answer

Use a vSphere DRS rule to disable hyperthreading for all VMs in the cluster, avoiding the need to modify host BIOS.

Answer

Delay the change and schedule a maintenance window for the next month when business impact is lower.

Answer

Disable hyperthreading on all hosts simultaneously using a vSphere Cluster feature, then reboot all hosts at once during off-peak hours.

Question 7

After upgrading the physical switches, the LAG (Link Aggregation Group) on a VDS does not come up. The VDS LAG configuration shows LACP active mode. The physical switch ports are configured with LACP active mode as well. What is the most likely cause?

Accepted Answer

The physical switch ports are not in a port-channel. For a VDS LAG in LACP active mode to come up, the physical switch ports must be configured as a port-channel (LAG) with LACP enabled. If the switch ports are left as individual access ports without a port-channel, the ESXi host's LACP PDUs are not matched to a LAG on the switch side, and the LAG never forms. This is the most common cause after a switch upgrade where the port-channel configuration was not reapplied.

Answer

The physical switch uses a different LACP system priority

Answer

The ESXi hosts have different LAG IDs

Answer

The VDS LAG hashing algorithm is set to IP hash

Question 8

Refer to the exhibit. The vSphere administrator observes that vm1 has a %RDY value of 20.5. What is the most likely cause of this high ready time?

Accepted Answer

The host's physical CPUs are overcommitted. %RDY (ready time) measures the percentage of time a VM's virtual CPUs are ready to run but cannot be scheduled onto a physical CPU because the host's pCPUs are busy. A sustained value of 20.5% indicates significant CPU contention, meaning the host's physical cores are overcommitted relative to the total vCPU demand of all powered-on VMs. This is a classic symptom of CPU over-subscription on the ESXi host.

Answer

The VM is experiencing network packet loss

Answer

The VM's virtual disk is causing I/O latency

Answer

Insufficient memory is allocated to vm1

Question 9

Which feature allows a VM to use storage directly from the host's local disks, pooled across a cluster?

Accepted Answer

vSAN. vSAN is VMware's software-defined storage solution that pools local disks (SSDs/HDDs) from ESXi hosts across a cluster into a shared datastore. It allows VMs to use storage directly from host local disks, aggregated and presented as a single distributed datastore. This matches the requirement exactly.

Answer

VMFS

Answer

vFlash

Answer

NFS

Question 10

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?

Accepted Answer

vSphere Lifecycle Manager (vLCM) with a single image. 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.

Answer

vSphere Update Manager (VUM)

Answer

Host Profiles

Answer

Quick Boot

Question 11

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 12

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 13

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 14

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 15

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 16

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 17

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 18

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 19

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 20

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).