VCP-DCV Configure and Manage vSphere Storage Practice Test 6 — 15 Questions

Question 1

What is the default block size of a VMFS5 datastore?

Accepted Answer

1 MB. The default block size of a VMFS5 datastore is 1 MB. VMFS5 introduced a unified 1 MB block size that supports large files up to 2 TB minus 512 bytes, eliminating the need for multiple block sizes. This default applies to all VMFS5 datastores unless upgraded from VMFS3.

Answer

8 MB

Answer

2 MB

Answer

4 MB

Question 2

An administrator needs to migrate a VM from a VMFS5 datastore to a vSAN datastore while preserving the storage policy. Which migration method should be used?

Accepted Answer

Storage vMotion. Storage vMotion migrates a VM's virtual disks from one datastore to another while the VM remains powered on, and it preserves the VM's storage policy (e.g., vSAN storage policy). It is the correct method for moving a VM between datastores without downtime.

Answer

Cold migration

Answer

Clone

Answer

vMotion

Question 3

A vSphere cluster has multiple storage arrays with different capabilities. The administrator wants to automatically place VMs on datastores that match their storage policy. What is required?

Accepted Answer

VM storage policy and Storage DRS. Storage DRS automates initial placement and ongoing balancing of VMs across datastores in a datastore cluster, but it only honors storage requirements when a VM storage policy is assigned. The VM storage policy expresses capabilities such as RAID level, replication, or tier (e.g., gold/silver/bronze), and Storage DRS uses those policy requirements to select a compatible datastore. Therefore both a VM storage policy and Storage DRS are required to automatically place VMs on datastores matching their policy.

Answer

VASA provider

Answer

Storage DRS only

Answer

Storage I/O Control

Question 4

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 5

Refer to the exhibit. What is the most likely reason the second path is in standby state?

Accepted Answer

The storage array reports that path as non-optimized.. In an ALUA (Asymmetric Logical Unit Access) environment, a storage array designates each path as either optimized (active) or non-optimized (standby). When the array reports a path as non-optimized, ESXi places that path in a standby state and routes I/O through the optimized path. This is the expected behavior for arrays that support ALUA and is the most likely reason the second path shows as standby.

Answer

The host has not successfully authenticated to the storage on that path.

Answer

The path is not properly zoned to the storage.

Answer

The multipathing policy is set to Fixed (VMW_PSP_FIXED).

Question 6

Refer to the exhibit. What does this error indicate?

Accepted Answer

The target LUN is not available.. In VMware vSphere, an error indicating the target LUN is unavailable typically appears when an ESXi host cannot access a presented storage device — for example, the LUN has been unpresented from the storage array, masked incorrectly in the SAN fabric, or the datastore is in an 'inaccessible' state. The exhibit error (commonly 'The target LUN is not available' or a similar vSphere Client message) points to the LUN no longer being visible to the host, not to a path or HBA fault.

Answer

The path is misconfigured.

Answer

The storage device is not connected.

Answer

The host's HBA is faulty.

Question 7

An administrator needs to create a datastore cluster for a set of VMs that require high availability. The VMs should be automatically balanced across datastores based on I/O latency. Which feature must be enabled on the datastore cluster?

Accepted Answer

Storage DRS with I/O metric enabled.. Storage DRS with the I/O metric enabled uses datastore latency and I/O load (via SIOC) to make initial placement and ongoing balancing decisions, which is exactly what is needed to balance VMs across datastores based on I/O latency. Enabling the I/O metric is the specific setting that activates latency-aware recommendations.

Answer

Storage I/O Control (SIOC) on each datastore.

Answer

vSphere HA for the datastore cluster.

Answer

Storage DRS without I/O metric, using space only.

Question 8

An administrator needs to expand a VMFS5 datastore that is currently 2 TB in size. The underlying LUN is 5 TB. What is the maximum size the datastore can be expanded to without involving additional LUNs?

Accepted Answer

5 TB. VMFS5 supports datastore sizes up to 64 TB, but the datastore cannot exceed the size of its underlying LUN. Since the LUN is 5 TB, the maximum the datastore can be expanded to without adding LUNs is 5 TB.

Answer

64 TB

Answer

4 TB

Answer

2 TB

Question 9

A vSphere administrator is planning a Storage DRS implementation for a datastore cluster containing multiple VMFS datastores. The VMs have various I/O patterns. Some VMs should always remain together on the same datastore. Which configuration should be used?

Accepted Answer

Create a VM-to-VM affinity rule in the datastore cluster.. Storage DRS supports VM-to-VM affinity rules within a datastore cluster, which ensure that specified VMs are always placed on the same datastore. This is the correct configuration when VMs must remain together, such as for application clusters that require shared storage locality or licensing constraints. The rule is enforced during initial placement and during Storage DRS migrations.

Answer

Set individual datastore affinity rules on each host.

Answer

Apply Storage I/O Control with high shares to the VMs.

Answer

Create a VM-to-VM anti-affinity rule in the datastore cluster.

Question 10

An administrator is configuring multipathing for a Fibre Channel storage array. The administrator wants to maximize throughput by using all available paths. Which path selection policy should be chosen?

Accepted Answer

Round Robin (VMW_PSP_RR). Round Robin (VMW_PSP_RR) is the only path selection policy that actively distributes I/O across all available paths to a given device in a round-robin fashion, thereby maximizing throughput by utilizing all paths simultaneously. It is the default PSP for most block storage arrays in ESXi and is recommended for active-active arrays. By cycling through each path, it avoids saturating a single path and can significantly improve performance. This aligns with the administrator's goal of using all available paths to maximize throughput.

Answer

Fixed (VMW_PSP_FIXED)

Answer

Most Recently Used (VMW_PSP_MRU)

Answer

Vendor-specific (VMW_PSP_FIXED_AP)

Question 11

A company has a vSphere cluster consisting of 8 ESXi hosts connected to a single Fibre Channel SAN array. They use VMFS6 datastores to store virtual machine files. The storage administrator has scheduled a firmware upgrade for the SAN array that requires a controller reboot. This will cause a temporary loss of connectivity to one LUN (datastore) for approximately 5 minutes. The datastore hosts 15 production VMs, including critical database servers. The cluster has sufficient spare capacity on other datastores, but the VMs are large (each about 200 GB). The vSphere administrator must ensure that these VMs remain available during the upgrade. The cluster has vSphere HA enabled with default settings. What should the administrator do to meet the requirement?

Accepted Answer

Use Storage vMotion to migrate all VMs on the affected datastores to a healthy datastore before the upgrade.. Storage vMotion migrates the VMs' files to a different datastore while they remain powered on, so when the affected LUN goes offline for the controller reboot the VMs are no longer dependent on it and stay available. This directly addresses the requirement of continuous availability during a planned 5-minute storage outage. The other options either don't move the VMs off the impacted datastore or address unrelated concerns (HA admission control, host maintenance, I/O prioritization).

Answer

Configure a vSphere HA admission control policy to reserve resources in case of host failure.

Answer

Place all ESXi hosts into maintenance mode.

Answer

Enable Storage I/O Control on the affected datastore to manage I/O during the upgrade.

Question 12

An administrator manages a vSAN cluster with 5 ESXi hosts in a single failure domain. The cluster uses vSAN version 8 and is configured with a single disk group per host. A storage policy is applied to a group of VMs with 'Number of failures to tolerate = 1' and 'Primary level of failures = Host'. One host experiences a catastrophic hardware failure and is now marked as 'Absent' in the vSAN cluster. The administrator checks the vSAN health and finds that the affected host's disk group is completely lost. One of the VMs from that group previously had two replicas on different hosts and a witness component on a third host. The VM is still powered on, and the administrator sees that one replica was on the failed host. The other replica and witness are on surviving hosts. What is the current state of this VM regarding data accessibility?

Accepted Answer

The VM is fully accessible because it still has one replica and the witness.. With 'Number of failures to tolerate = 1' and 'Primary level of failures = Host', vSAN ensures that a VM has at least one full replica and a witness when one host fails. The VM still has one replica and the witness on surviving hosts, so it remains fully accessible. The witness acts as a tiebreaker for quorum but does not store VM data; the remaining replica provides data access.

Answer

The VM is accessible but performance is degraded because the disk group on the failed host is gone.

Answer

The VM is inaccessible because the lost replica cannot be rebuilt without a replacement host.

Answer

The VM is inaccessible because the witness component is now the only copy and cannot be used for reads.

Question 13

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 14

A company has a vSphere 7.0 cluster with 6 ESXi hosts connected to a Dell EMC PowerStore array using iSCSI. They are using VMFS6 datastores. After a recent firmware upgrade on the array, they notice that performance on one datastore has degraded significantly. The datastore is used by several high-I/O VMs. The administrator runs 'esxcli storage core path list' and sees that all paths to that datastore are active but with varying latency. The PSP is set to Round Robin with IOPS limit of 1000. The SATP is VMW_SATP_ALUA. The storage administrator confirms that the array is in active-active mode. What should the administrator do to improve performance?

Accepted Answer

Increase the Round Robin IOPS limit to 10000.. The Round Robin PSP with an IOPS limit of 1000 is causing the ESXi host to switch paths too frequently, which can lead to higher latency due to path thrashing and suboptimal use of the array's active-active ALUA mode. Increasing the Round Robin IOPS limit to 10000 reduces the frequency of path switches, allowing each path to handle more I/Os before switching, which improves performance for high-I/O workloads on VMFS6 datastores.

Answer

Enable the array's QoS policy and configure the datastore for VAAI.

Answer

Change the PSP to Most Recently Used (MRU) to reduce path thrashing.

Answer

Change the SATP to VMW_SATP_DEFAULT_AA and reconfigure the iSCSI initiator.

Question 15

Refer to the exhibit. An administrator increased the MaxQueueDepth parameter for an NFS 4.1 datastore. Which effect does this change have on performance?

Accepted Answer

It increases throughput by allowing more concurrent I/O operations.. MaxQueueDepth on an NFS 4.1 datastore controls the maximum number of outstanding I/O operations that can be queued to the NFS server. Increasing this value allows more concurrent I/O requests to be in flight, which can improve throughput by keeping the storage pipeline fuller and reducing idle time waiting for responses. This is especially beneficial for workloads with many parallel I/O streams, as it enables better utilization of network and storage resources.

Answer

It reduces latency by limiting the number of queued I/Os.

Answer

It limits the maximum size of read and write operations.

Answer

It has no effect because NFS 4.1 does not support queue depth adjustments.