VCP-DCV Practice Test 6 — 10 Questions

Question 1

A storage administrator is planning a vSAN stretched cluster for a remote office. The cluster must support stretching across two sites for disaster avoidance. Which two prerequisites must be met? (Choose two.)

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

Accepted Answer

The network latency between sites must be less than 5 ms round-trip.. Correct options A and C: Each site must have a minimum of two hosts (C) and network latency between sites must be less than 5 ms round-trip (A). Option B is incorrect because the witness host must be placed at a third site, not the primary. Option D is incorrect because hosts can use multiple network adapters for vSAN traffic; a single adapter is not required. Option E is incorrect because a vSAN stretched cluster typically uses two fault domains (one per site) plus a witness, not four.

Answer

The witness host must be placed at the primary site.

Answer

All hosts must be configured with a single network adapter for vSAN traffic.

Answer

A vSAN stretched cluster requires a minimum of four fault domains.

Question 2

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

Accepted Answer

Stage and remediate. The correct answers are C, D, and E. vSphere Lifecycle Manager (vLCM) supports three standard remediation methods: staging updates and then remediating (Stage and remediate), remediating immediately without staging (Remediate immediately), and scheduling remediation for a later time (Schedule remediation). 'Auto update' and 'Push from vCenter' are not valid vLCM remediation methods. Auto update is not a feature of vLCM, and push-based remediation is not how vLCM operates; vLCM uses a desired-state model.

Answer

Auto update

Answer

Push from vCenter

Question 3

A vSphere administrator configures a VVol datastore on a Pure Storage array. The administrator creates a storage policy with a custom tag. After attaching the policy to a VM, the VM remains uncompliant. What is the most likely cause?

Accepted Answer

The storage array does not support the capability specified in the policy.. VVol storage policies rely on capabilities advertised by the array through VASA. If the array does not support the specific capability or tag used in the policy, the VM will be uncompliant. Option A is correct because the custom tag in the storage policy is not supported by the Pure Storage array. Option B is incorrect: VVol datastores require VASA certification; if the array were not VASA-compliant, it could not host a VVol datastore at all. Option C is incorrect because Storage DRS is unrelated to VVol policy compliance. Option D is incorrect because VVol datastores can use either iSCSI or NFS protocols, and the protocol does not affect compliance.

Answer

The storage array is not VASA-compliant.

Answer

The datastore cluster is not configured for Storage DRS.

Answer

The VVol datastore is using NFS protocol instead of iSCSI.

Question 4

Refer to the exhibit. An administrator runs the 'esxcli storage core device list' command and sees the output. The storage array is an active-passive array with ALUA. The current path selection policy is set to Fixed with no preferred path. What is the consequence of this configuration?

Accepted Answer

I/O may be sent to a non-optimized path, causing higher latency. With an active-passive ALUA array, the Fixed path selection policy without a preferred path means the host may not switch to the optimized active path for a given LUN. Since no preferred path is set, the host can select any available path, potentially sending I/O through a non-optimized passive path. This results in higher latency as the array must redirect I/O through the partner controller. Option C correctly identifies this consequence. Option A is incorrect because Fixed policy does not load-balance; it uses a single path unless it fails. Option B is wrong because ALUA is supported and the host can use multiple paths but only one is active. Option D is irrelevant as VMDKs can be used on any path.

Answer

The I/O is load-balanced across all four paths

Answer

ALUA is not supported, so the host will use only one path

Answer

The device cannot be used for VMDKs, only for RDM

Question 5

Refer to the exhibit. An administrator observes high latency on a VMFS datastore. Based on the vdbench and esxtop output, which component is most likely causing the latency?

Accepted Answer

The virtual machine or application is causing high latency due to inefficient I/O patterns.. The esxtop output shows KAVG (kernel latency) of 2.5 ms and GAVG (guest latency) of 8.2 ms. The total latency (QAVG) is 10.7 ms, but the reported datastore latency is 12 ms. The high GAVG relative to KAVG indicates latency at the guest/application level, not at the storage array. The vdbench test shows 12 ms average latency, which matches the guest-level latency. The issue is likely due to application I/O patterns or queue depth, not the storage backend.

Answer

The storage array is overloaded, causing high queue depth (DAQLEN=32).

Answer

The VMFS datastore is fragmented, causing increased seek times.

Answer

The ESXi host's HBA queue depth is insufficient, causing queuing on the host.

Question 6

A global company manages multiple vSphere clusters across different data centers. They have a standard operating procedure to upgrade ESXi hosts every two years. The vSphere administrator is planning the upgrade of a critical production cluster that runs a mix of VMs, including some latency-sensitive applications. The cluster consists of 20 ESXi 7.0 Update 3 hosts managed by vLCM with a single image. The target is ESXi 8.0 Update 1. The administrator wants to minimize downtime and ensure rollback capability. The company has a hardware support manager (HSM) integrated with vLCM. After staging the new image, the administrator remediates the cluster. During the remediation of the first host, the host fails to reboot after applying the image and becomes unresponsive. What is the most likely cause of this failure?

Accepted Answer

The hardware support manager (HSM) did not deploy the correct firmware version for the host.. The most likely cause is that the hardware support manager (HSM) deployed an incorrect firmware version for the host during the vLCM remediation. vLCM integrates with HSM to automatically update firmware as part of the image-based lifecycle, and if the firmware is incompatible with ESXi 8.0 Update 1, the host can fail to reboot and become unresponsive. This is a known risk when upgrading across major ESXi versions, as hardware firmware requirements often change.

Answer

The vCenter Server version is not compatible with ESXi 8.0 Update 1.

Answer

The host was not placed in maintenance mode before remediation.

Answer

The vLCM single image is corrupted and was applied incorrectly.

Question 7

Refer to the exhibit. An administrator attempts to reclaim unused space on a VMFS datastore using esxcli storage vmfs unmap, but the command fails. Based on the logs and documentation, what is the most likely cause?

Accepted Answer

The storage LUN is thick-provisioned and does not support UNMAP.. The vmkernel log shows the UNMAP command failed with ILLEGAL REQUEST, sense 0x5 0x20 0x0, which indicates an invalid command. The vendor documentation states that UNMAP is only supported when thin provisioning is enabled on the LUN. The LUN is likely thick-provisioned, so the array rejects the UNMAP command.

Answer

The reclaim-unit parameter is set too low, causing the array to reject the command.

Answer

The ESXi host does not have sufficient permissions to issue UNMAP commands.

Answer

The VMFS datastore is not formatted with a supported block size.

Question 8

Refer to the exhibit. An administrator checks the status of a distributed switch port and sees no errors or drops. However, virtual machines on this port cannot communicate with the default gateway at 192.168.200.1. What is the most likely cause?

Accepted Answer

The port is configured with Allowed VLANs 100, 200, 300, which is a trunk configuration, but the virtual machine expects an access port on VLAN 200.. The exhibit shows the port has Allowed VLANs: 100, 200, 300. This is unusual because a port should typically be assigned to a single VLAN (access port) or carry multiple VLANs (trunk port). If the port is set to allow multiple VLANs but the virtual machine expects a specific VLAN, packets may be misconfigured. However, the most likely cause is that the port is configured as a trunk port (allows multiple VLANs) when it should be an access port for VLAN 200. This can cause the virtual machine to receive traffic from other VLANs or not tag its own traffic correctly.

Answer

The port has no allowed MAC addresses, which may cause filtering.

Answer

The MTU is set to 1500, which is standard and should work fine.

Answer

The link speed is 10 Gbps, which is sufficient.

Question 9

Refer to the exhibit. An administrator configured beacon probing for network failure detection on the Production port group. However, virtual machines are experiencing intermittent connectivity. What is the most likely reason?

Accepted Answer

There are only two uplinks, and beacon probing requires at least three uplinks.. Beacon probing requires at least three uplinks to function correctly. The exhibit shows only two uplinks (vmnic1 and vmnic2) are active. With two uplinks, beacon probing cannot reliably detect failures because there are not enough beacons to determine which link is down. This can cause false positives and connectivity issues.

Answer

The VLAN ID 200 is not allowed on the physical switch trunks.

Answer

The DVS version 7.0.0 does not support beacon probing.

Answer

The load balancing policy is set to Route based on IP hash, which is incompatible with beacon probing.

Question 10

Match each vSphere networking component to its description.

Accepted Answer

vSphere Distributed Switch: A centralized virtual switch that spans multiple ESXi hosts and provides consistent networking configuration.. Key vSphere networking components: Distributed Switch (centralized, multi-host), Standard Switch (per-host), Port Group (logical grouping). Common confusion is mixing the switch types.

Answer

vSphere Distributed Switch: A host-level virtual switch that does not support centralized management.

Answer

vSphere Standard Switch: A virtual switch that spans multiple hosts and provides consistent configuration across a cluster.

Answer

Port Group: A physical network interface that connects a host to the physical network.