VCP-DCV Configure and Manage vSphere Storage — Timed 30 Questions

Question 1

An administrator notices that a VM with a 500 GB virtual disk stored on an NFS datastore is performing poorly during backup operations. The NFS datastore is mounted with default settings. Which change will most likely improve performance?

30 minute time limit — choose an answer to begin.

Accepted Answer

Configure the NFS datastore to use vStorage APIs for Array Integration (VAAI).. VAAI for NFS offloads storage operations like hardware-assisted locking and full-file/clone operations to the NAS array, reducing CPU overhead on the ESXi host and improving performance during backup-intensive tasks. Since the NFS datastore is mounted with default settings, VAAI is not automatically enabled and must be explicitly configured to leverage array-based primitives.

Answer

Move the VM to a cluster with more memory.

Answer

Enable jumbo frames on the ESXi host's VMkernel adapter for NFS.

Answer

Increase the size of the NFS datastore to 1 TB.

Question 2

A vSphere administrator is troubleshooting a VM that has been disconnected from its virtual disk. The VM's virtual disk file (vmdk) is still present on the datastore, but the VM cannot be powered on. Which step should the administrator take first to resolve the issue?

Accepted Answer

Use the vmkfstools command to re-register the virtual disk.. When a VM is disconnected from its virtual disk but the .vmdk file remains on the datastore, the issue is often a corrupt or missing disk descriptor file. The vmkfstools command with the -fix option can repair the descriptor file, re-establishing the connection between the VM and its virtual disk without requiring VM recreation or manual re-attachment.

Answer

Create a new VM and attach the existing vmdk file.

Answer

Re-add the virtual disk from the datastore browser to the VM.

Answer

Perform a storage vMotion of the VM to another datastore.

Question 3

A vSphere administrator is planning to configure VMware vSAN. Which TWO requirements must be met for a vSAN cluster?

Accepted Answer

Each host must have at least one SSD and one HDD for capacity.. VSAN requires at least one SSD (or NVMe) for the cache tier and one HDD (or SSD) for the capacity tier on each host to form a disk group. This hybrid or all-flash configuration is fundamental to vSAN's storage architecture, where the cache tier accelerates writes and reads, while the capacity tier provides persistent storage.

Answer

A dedicated 10 GbE network for vSAN traffic.

Answer

All hosts must have identical CPU models.

Answer

A shared storage array accessible by all hosts.

Question 4

An administrator is configuring Storage DRS on a datastore cluster. Which THREE conditions must be met for Storage DRS to migrate virtual disks?

Accepted Answer

The source and destination datastores must be part of the same datastore cluster.. Storage DRS operates within a single datastore cluster, which is a collection of datastores that share resources and are managed as a single entity. For Storage DRS to migrate virtual disks via Storage vMotion, both the source and destination datastores must be members of the same datastore cluster; cross-cluster migrations are not supported by Storage DRS.

Answer

The virtual disk must not be attached to a snapshot.

Answer

The storage array must support VAAI.

Question 5

An administrator needs to expand a VMFS6 datastore that is currently 2 TB in size. The LUN presented to the ESXi host has been expanded to 3 TB from the storage array. Which command should the administrator use to extend the datastore?

Accepted Answer

vmkfstools --growfs /vmfs/devices/disks/naa.60050768018603e1b800000000000001. The correct command is `vmkfstools --growfs` because it is the only VMware-supported method to expand a VMFS6 datastore after the underlying LUN has been resized. This command grows the file system to use the newly available unpartitioned space on the device, without requiring a new partition. The `--growfs` option specifically targets the VMFS file system, not the partition, which is essential for VMFS6 datastores.

Answer

esxcli storage vmfs extend -l naa.60050768018603e1b800000000000001

Answer

esxcli storage vmfs grow -l naa.60050768018603e1b800000000000001

Answer

vmkfstools --extend /vmfs/devices/disks/naa.60050768018603e1b800000000000001

Question 6

An administrator runs vmkfstools on a VMFS datastore and receives the output shown. The datastore is backed by a single LUN from a SAN array. What is the most likely explanation for the multiple extents shown?

Accepted Answer

The datastore was expanded by adding an extent from the same LUN.. When a VMFS datastore is expanded using the same LUN, vmkfstools can show multiple extents because the additional space is added as a separate extent on the same physical LUN. This is a common practice to grow a datastore without reprovisioning a new LUN, and the output reflects the original and expanded extents both pointing to the same LUN identifier.

Answer

The LUN was presented to the host with multiple paths, and each path is treated as a separate extent.

Answer

The datastore is a VMFS6 datastore with three logical volumes aggregated into one namespace.

Answer

The virtual machine has a large VMDK file that spans multiple extents due to VMFS6 sub-block allocation.

Question 7

Which THREE actions can be performed on a VMFS datastore without unmounting it or putting the ESXi host into maintenance mode?

Accepted Answer

Remove the datastore from the host's inventory.. Removing a datastore from the host's inventory simply detaches the datastore object from the ESXi host's configuration without affecting the underlying LUN or requiring the host to enter maintenance mode. This operation only modifies the host's metadata, not the storage device itself, so it can be performed while VMs are running on other datastores.

Answer

Upgrade the datastore from VMFS5 to VMFS6.

Answer

Add a new extent to the datastore from a different LUN.

Question 8

Match each VMware acronym to its full name.

Accepted Answer

ESXi: VMware ESXi is a bare-metal hypervisor.. Common VMware acronyms and their expansions.

Answer

ESXi: VMware vCenter Server is a centralized management platform.

Answer

vSphere: VMware VMFS is a clustered file system.

Question 9

Match each vSphere object to its maximum supported size (vSphere 7).

Accepted Answer

Virtual machine - max vCPUs per VM: 256. Correct matches: VM max vCPUs 256, VM max memory 6 TB, datastore max size 64 TB, cluster max hosts 64. Common confusions include lower values from previous versions.

Answer

Virtual machine - max vCPUs per VM: 128

Answer

Datastore - max size: 32 TB

Question 10

A vSphere administrator has a VMFS6 datastore that is running low on space. The storage array has additional unallocated LUNs. The administrator attaches a new 2 TB LUN to the ESXi host. What is the correct procedure to increase the datastore capacity?

Accepted Answer

Use the 'Increase datastore capacity' wizard to add the LUN as an extent. The correct procedure is to use the 'Increase datastore capacity' wizard to add the new LUN as an extent to the existing VMFS6 datastore. VMFS6 supports online extension, allowing the datastore to be expanded without unmounting or disrupting running VMs. Option B is incorrect because unmounting and extending the partition is unnecessary; VMFS6 handles this dynamically. Option C is incorrect because recreating the datastore with a larger block size is disruptive and not required—adding an extent achieves the capacity increase. Option D is incorrect because creating a new datastore and migrating VMs is unnecessary and adds complexity; the existing datastore can be extended seamlessly.

Answer

Unmount the datastore, expand the VMFS partition, then remount

Answer

Recreate the datastore with a larger block size and restore from backup

Answer

Create a new datastore on the LUN and use Storage vMotion to migrate VMs

Question 11

An administrator has configured Storage DRS on a cluster of datastores. The cluster includes both NFS and VMFS datastores. The administrator notices that Storage DRS recommendations are not being generated for some datastores. What is the most likely cause?

Accepted Answer

NFS datastores are not supported by Storage DRS. Storage DRS does not support NFS datastores unless they are on a NAS array that supports VAAI for storage offload operations. In this scenario, the cluster includes both NFS and VMFS datastores, but Storage DRS recommendations are not generated for some datastores. The most likely cause is that those datastores are NFS and do not meet the requirements for Storage DRS. Option B (space utilization below threshold) is incorrect because Storage DRS would still generate recommendations when space utilization is below the threshold, just perhaps less frequently. Option C (datastores part of a vSAN cluster) is incorrect because vSAN uses its own distributed resource scheduler, not Storage DRS, and would not be included in the cluster. Option D (I/O metrics not enabled) is incorrect because if I/O metrics were not enabled, recommendations based on I/O latency would not be generated, but recommendations based on space utilization would still be generated; however, the question states recommendations are not being generated for some datastores, which points to the NFS incompatibility.

Answer

The datastore space utilization is below the threshold

Answer

The datastores are part of a vSAN cluster

Answer

I/O metrics are not enabled for the Storage DRS cluster

Question 12

A company is implementing VMware vVols with a VASA provider from a major storage vendor. The environment includes multiple ESXi hosts and a vCenter Server. After binding a virtual machine to a vVol, the administrator notices that the VM cannot power on. The storage status shows 'Not mounted'. What is the most likely cause?

Accepted Answer

The VASA provider is not registered on the ESXi host where the VM is being powered on. vVols require storage container binding per host. If the VASA provider is not properly registered on that host, the vVol cannot be mounted. Option A is correct. Option B (vCenter Server not connected) does not prevent direct mount if the host has the provider. Option C (protocol endpoint not reachable) would affect all VMs. Option D (storage policy) would affect placement, not power-on.

Answer

The vCenter Server is not connected to the VASA provider

Answer

The protocol endpoint is not reachable from the ESXi host

Answer

The storage policy does not include the correct capability

Question 13

An administrator is troubleshooting performance issues on a VMFS datastore hosting SQL Server VMs. Storage I/O Control (SIOC) is enabled, but the administrator notices that congestion is detected but no throttling is applied. What could be the reason?

Accepted Answer

The SIOC congestion threshold is set too high. The SIOC congestion threshold is set too high, meaning that although congestion is detected, the threshold for applying throttling has not been reached. SIOC uses a congestion threshold (default 30ms) to determine when to throttle I/O. If the threshold is set too high, SIOC may detect congestion but not apply throttling because the latency has not exceeded the threshold. The administrator should lower the threshold to enable throttling.

Answer

The datastore is deduplicated

Answer

SIOC is disabled on the datastore

Answer

The host has exceeded the maximum number of concurrent I/Os

Question 14

An administrator is configuring persistent memory (PMem) for a critical database VM. The host has 512 GB of Intel Optane PMem. The VM must be able to vMotion while PMem is used. Which configuration meets this requirement?

Accepted Answer

Add a vPMem device to the VM and ensure the destination host has compatible PMem. To use PMem with a VM and still allow vMotion, you must add a virtual PMem (vPMem) device to the VM and ensure the destination host has compatible PMem. vPMem devices are backed by the host's PMem and are migrated as part of the VM's configuration, provided the destination host has PMem with compatible characteristics. This is the supported configuration for vMotion with PMem.

Answer

Use NVDIMM labels and create a datastore for PMem

Answer

Configure the VM to use PMem in hardware passthrough mode

Answer

Emulate PMem using SSD-backed virtual disks

Question 15

Which TWO statements are true regarding vSAN deduplication and compression?

Accepted Answer

They are disabled by default on new vSAN clusters. Option B is correct because vSAN deduplication and compression are disabled by default when a new vSAN cluster is created; an administrator must explicitly enable them in the cluster's vSAN services settings. Option D is correct because deduplication and compression require an all-flash vSAN configuration (flash cache and flash capacity devices); they cannot be enabled on hybrid clusters. Option A is incorrect because deduplication and compression are enabled at the cluster level, not per-disk-group or per-VM, so the statement as worded is not one of the two true answers. Option C is incorrect because deduplication and compression work with RAID-1, RAID-5, and RAID-6 storage policies, not only RAID-1. Option E is incorrect because in vSAN, compression cannot be enabled independently of deduplication; enabling deduplication and compression is a single combined cluster-level setting.

Answer

They are enabled at the vSAN cluster level

Answer

They can only be used with RAID-1 mirroring policies

Answer

Compression can be enabled independently of deduplication

Question 16

Which TWO conditions require increasing the VMFS heap size on an ESXi host?

Accepted Answer

The host is connected to many VMFS datastores (e.g., 64). Option A is correct because the VMFS heap is consumed per open VMFS volume, so a host connected to many VMFS datastores (for example, 64) can exhaust the default heap and requires increasing it. Option D is correct because the heap is also consumed by open files on VMFS volumes, and running more than 500 virtual machines on a host generates enough open VMDK files to exceed the default heap. Option B is incorrect because a VMDK larger than 2 TB affects datastore/file format limits, not the VMFS heap size. Option C is incorrect because vSAN uses its own object storage stack rather than the VMFS heap. Option E is incorrect because snapshots are additional files on a datastore but do not by themselves drive the documented heap-sizing thresholds.

Answer

A virtual machine has a VMDK larger than 2 TB

Answer

The host is part of a vSAN cluster

Answer

The host has many snapshots per virtual machine

Question 17

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 18

Refer to the exhibit. An administrator checks the vSAN cluster health and sees the above output. The cluster has been running for months. What is the most likely cause of the degraded objects?

Accepted Answer

A disk failure occurred and components are being rebuilt. In a vSAN cluster, when a disk fails, the components stored on that disk become absent, and vSAN immediately begins rebuilding those components onto remaining healthy disks to restore the specified storage policy compliance. The exhibit shows degraded objects with 'reduced availability' or active rebuild activity, which is the classic signature of a disk failure triggering component rebuild. Because the cluster has been stable for months, a sudden change in object health points to a hardware event rather than a policy change or capacity issue.

Answer

A storage policy was changed to increase redundancy

Answer

A disk group is full and needs capacity expansion

Answer

A network partition between hosts

Question 19

Refer to the exhibit. An administrator runs the 'vmkfstools -P -v 10' command on a datastore. What is the total capacity of the datastore?

Accepted Answer

3 TB. The vmkfstools -P -v 10 command displays the datastore's extent information. The output shows two extents: one with 1,048,576 blocks and another with 2,097,152 blocks, both using a 1 MB block size. Total blocks = 1,048,576 + 2,097,152 = 3,145,728 blocks. Since each block is 1 MB, total capacity = 3,145,728 MB = 3,072 GB = 3 TB. Therefore, option C (3 TB) is correct. Option A (2.5 TB) and Option B (2 TB) are incorrect; Option D (1 TB) matches only the smaller extent.

Answer

2.5 TB

Answer

2 TB

Answer

1 TB

Question 20

An administrator attempts to expand a VMFS datastore by increasing the LUN size, but the expand option is grayed out. What could be the reason?

Accepted Answer

The LUN is shared with another datastore. The expand option is grayed out because the LUN is shared with another datastore. In VMFS, a single LUN can only host one VMFS datastore. If the LUN is already presented to another host or used by another datastore (e.g., a second VMFS partition), the datastore cannot be expanded because the underlying LUN is not exclusively owned by this datastore. This is a common configuration error where the LUN is incorrectly zoned or masked, leading to the expand option being disabled.

Answer

The datastore is using block size 2 MB

Answer

The host is not rescanned

Answer

The datastore is on a RDM