Courseiva

CCNA Vsphere Storage Questions

40 questions · Vsphere Storage topic · All types, answers revealed

Practice these questionsExam hubAll questions
1
MCQeasy

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?

A.64 TB
B.5 TB
C.4 TB
D.2 TB
AnswerB

VMFS5 removed the 2 TB extent limit, so a single extent can span the full underlying LUN. Expanding the datastore to the LUN's full 5 TB capacity requires no additional extents, directly satisfying the constraint of avoiding extra LUNs.

Why this answer

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.

Exam trap

VCP-DCV often tests the difference between the maximum supported VMFS datastore size (64 TB) and the actual expandable size, which is limited by the underlying LUN — candidates frequently pick 64 TB without checking the LUN size.

How to eliminate wrong answers

Option A is wrong because 64 TB is the theoretical maximum VMFS5 datastore size, but it is constrained by the underlying LUN size, which is only 5 TB here. Option C is wrong because 4 TB is not a VMFS5 limit — VMFS5 supports larger than 2 TB with the appropriate block size and is not capped at 4 TB. Option D is wrong because 2 TB is the current size, not the maximum expandable size; the datastore can grow up to the LUN size of 5 TB.

Practice this question →
2
MCQeasy

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

A.8
B.256
C.32
D.4
AnswerC

32 paths is the documented ceiling vSphere supports per single storage device, satisfying the stem's constraint on maximum path count. This limit applies across FC, iSCSI and SAS arrays, where the Pluggable Storage Architecture's path selection modules manage all available routes to a given LUN without exceeding that figure.

Why this answer

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.

Practice this question →
3
Drag & Dropmedium

Place the steps to create a resource pool in a cluster.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

Creating a resource pool in a vSphere cluster involves first initiating the creation by right-clicking the cluster and selecting New Resource Pool, then providing a name, followed by configuring CPU and memory resources including shares, reservation, and limit, optionally enabling expandable reservation, and finally confirming by clicking OK. This sequence ensures all required parameters are set before finalizing the resource pool.

Practice this question →
4
MCQhard

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?

A.The VM is accessible but performance is degraded because the disk group on the failed host is gone.
B.The VM is inaccessible because the lost replica cannot be rebuilt without a replacement host.
C.The VM is inaccessible because the witness component is now the only copy and cannot be used for reads.
D.The VM is fully accessible because it still has one replica and the witness.
AnswerD

With failures-to-tolerate of 1, one surviving replica plus the witness maintains quorum and satisfies the policy, so the object remains accessible. The absent host's lost disk group does not break availability while the remaining replica and witness are reachable.

Why this answer

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.

Exam trap

VCP-DCV often tests vSAN failure tolerance and component states, and candidates may incorrectly assume that loss of a replica makes the VM inaccessible, forgetting that the witness and remaining replica allow continued access.

How to eliminate wrong answers

Option A is wrong because the VM is not just accessible but fully accessible; performance degradation is not inherent when one replica is lost, as the remaining replica can serve reads and writes. Option B is wrong because the VM can be rebuilt later, but it is not inaccessible now; the remaining replica allows access. Option C is wrong because the witness is not a copy of data and cannot be used for reads, but the VM still has a full replica, so it is accessible.

Practice this question →
5
MCQhard

A company is designing a vSphere environment for a critical database application. The storage array supports both Fibre Channel (FC) and iSCSI. The application requires low latency and high IOPS. Which storage protocol and path policy should be recommended?

A.FC with Fixed path policy.
B.FC with Most Recently Used (MRU) path policy.
C.iSCSI with Round Robin path policy.
D.FC with Round Robin path policy.
AnswerD

Fibre Channel provides dedicated, lossless transport with lower latency and higher sustained IOPS than iSCSI over Ethernet. Round Robin spreads I/O across all active paths, maximising throughput and balancing load, which satisfies the database's low-latency, high-IOPS requirement.

Why this answer

FC provides lower latency and higher IOPS than iSCSI due to dedicated hardware and lower protocol overhead, making it ideal for critical database workloads. The Round Robin path policy is recommended for FC with active-active storage arrays because it distributes I/O across all available paths, maximizing throughput and load balancing, which aligns with the requirement for high IOPS.

Exam trap

The trap here is that candidates often assume MRU is the default for FC or that Fixed is sufficient, but the VCP-DCV exam tests the understanding that Round Robin is the recommended path policy for active-active arrays to achieve load balancing and high IOPS, especially for performance-sensitive workloads like databases.

How to eliminate wrong answers

Option A is wrong because the Fixed path policy uses a single preferred path and only switches on failure, which does not optimize for high IOPS or load balancing across multiple paths. Option B is wrong because the Most Recently Used (MRU) path policy is designed for active-passive arrays and can cause path thrashing or suboptimal performance in active-active environments, failing to meet low-latency and high-IOPS needs. Option C is wrong because iSCSI typically incurs higher latency and CPU overhead compared to FC due to TCP/IP processing, making it less suitable for a critical database application requiring low latency and high IOPS.

Practice this question →
6
MCQhard

Refer to the exhibit. An administrator configures a claim rule to use VMW_SATP_ALUA with VMW_PSP_RR and TPGS enabled. After applying the rule, the device shows one active and one standby path. However, the administrator notices that I/O is only sent to the active path. What is the most likely reason?

A.The PSP should be changed to VMW_PSP_MRU to use both paths.
B.The array is not properly configured to present both paths as active/optimized.
C.The claim rule should have used VMW_SATP_DEFAULT_AA instead.
D.The TPGS option should be disabled to force both paths active.
AnswerB

Round robin only distributes I/O across paths the array reports as active/optimised. If the array presents one path as standby rather than both active/optimised, the PSP sends I/O solely to the active path, matching the observed behaviour.

Why this answer

VMW_PSP_RR (Round Robin) with TPGS (Target Port Group Support) enabled only distributes I/O across paths that the array reports as Active/Optimized. If the array presents one path as Active/Optimized and the other as Standby, RR will still send I/O only to the optimized path because ALUA state dictates path usage. The array's target port group configuration must mark both paths as Active/Optimized for RR to load-balance across them.

Exam trap

VCP-DCV often tests the misconception that VMW_PSP_RR always load-balances across all visible paths; in reality, with ALUA and TPGS, RR only uses paths the array marks Active/Optimized, so array-side TPG configuration is the deciding factor.

How to eliminate wrong answers

Option A is wrong because VMW_PSP_MRU (Most Recently Used) does not load-balance across paths; it simply uses the most recently active path and only fails over on path loss, so it would not achieve dual-path I/O. Option C is wrong because VMW_SATP_DEFAULT_AA is for arrays that do not support ALUA and treat all paths as active/active; using it with an ALUA array would ignore the array's asymmetric access states and could cause path thrashing or I/O errors. Option D is wrong because disabling TPGS would prevent ESXi from honoring the array's ALUA target port group states, which is required for correct RR behavior with ALUA arrays; it would not force both paths active.

Practice this question →
7
MCQmedium

Refer to the exhibit. An administrator tries to enable vSAN on a host and receives this error. What is the most likely cause?

A.The vSAN cluster has insufficient hosts (needs at least 2).
B.The host does not have any disks installed.
C.The host has disks but they are not claimed for vSAN or not configured in a disk group.
D.The host's disks are all SSD and vSAN requires HDD for capacity tier.
AnswerC

vSAN requires local disks to be claimed and assigned to a disk group before it can be enabled. Unclaimed or ungrouped disks leave no storage capacity for the vSAN datastore, so the enable operation fails until the administrator creates a disk group.

Why this answer

vSAN requires at least one disk group consisting of one or more capacity disks (and optionally a cache disk). The error indicates that no disk group is present or the disks are not properly claimed.

Practice this question →
8
MCQhard

An administrator notices that a VM with high I/O demands is experiencing performance issues because other VMs on the same datastore are consuming too many I/O operations. Which feature can be used to guarantee a minimum I/O share to this VM?

A.Multipathing policy
B.VM storage policy
C.Storage DRS
D.Storage I/O Control shares
AnswerD

Storage I/O Control shares guarantee a minimum I/O allocation to a virtual machine when the datastore becomes congested, directly addressing contention from other VMs. Shares are applied proportionally during contention, reserving throughput for the high-demand VM.

Why this answer

Storage I/O Control shares allow you to guarantee a minimum I/O share to a VM by assigning shares to its virtual disks. When contention occurs, ESXi enforces these shares to ensure the VM gets its fair share of I/O resources.

Exam trap

VCP-DCV often tests the confusion between Storage DRS (which balances load) and SIOC (which guarantees shares), leading candidates to choose Storage DRS for I/O prioritization.

How to eliminate wrong answers

Option A is wrong because multipathing policy determines how I/O is routed to storage, not how I/O is prioritized among VMs. Option B is wrong because VM storage policy defines storage requirements like RAID or encryption, not I/O prioritization. Option C is wrong because Storage DRS balances storage capacity and I/O load across datastores, but does not guarantee minimum I/O shares to individual VMs.

Practice this question →
9
MCQeasy

Which storage feature in vSphere allows a VM to be migrated from one datastore to another without any downtime?

A.vMotion
B.Distributed Resource Scheduler (DRS)
C.Storage DRS
D.Storage vMotion
AnswerD

Storage vMotion relocates a virtual machine's files between datastores while the VM remains powered on and running, satisfying the no-downtime constraint. Compute vMotion moves the VM between hosts instead, and neither cold nor suspended migration avoids an outage.

Why this answer

Storage vMotion is the correct answer because it enables live migration of a virtual machine's virtual disk files from one datastore to another with zero downtime. It uses a mirrored copy mechanism where the source and destination datastores are synchronized before the VM is switched to the destination, ensuring continuous VM availability.

Exam trap

The trap here is confusing vMotion (host migration) with Storage vMotion (datastore migration), as both are live migration technologies but operate on entirely different resources.

How to eliminate wrong answers

Option A is wrong because vMotion migrates a running VM between ESXi hosts, not between datastores; it moves the VM's memory and CPU state, not its storage. Option B is wrong because Distributed Resource Scheduler (DRS) balances compute resources across hosts by recommending or initiating vMotion migrations, but it does not handle storage migrations. Option C is wrong because Storage DRS provides initial placement and ongoing load balancing of VMs across datastores, but it relies on Storage vMotion to perform the actual migration; Storage DRS itself does not execute the migration.

Practice this question →
10
MCQhard

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

A.The host has not successfully authenticated to the storage on that path.
B.The path is not properly zoned to the storage.
C.The storage array reports that path as non-optimized.
D.The multipathing policy is set to Fixed (VMW_PSP_FIXED).
AnswerC

When an array presents one path as non-optimized, the PSA selects the optimized path as active and places the non-optimized path in standby. This asymmetric logical unit access behaviour explains the standby state without any path failure.

Why this answer

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.

Exam trap

VCP-DCV often tests the distinction between path states (active, standby, dead) and the reasons behind them, and candidates commonly confuse standby with dead or assume it indicates a configuration error rather than an ALUA optimization.

How to eliminate wrong answers

Option A is wrong because authentication failures would typically result in the path being marked as dead or offline, not standby; authentication is handled at the fabric or array level and does not cause a standby state. Option B is wrong because improper zoning would cause the path to be down or not discovered at all, not in a standby state. Option D is wrong because the Fixed policy does not place paths in standby; it uses a single preferred path and leaves others as active but unused, not in standby.

Standby is specifically an ALUA concept.

Practice this question →
11
MCQmedium

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?

A.VASA provider
B.Storage DRS only
C.Storage I/O Control
D.VM storage policy and Storage DRS
AnswerD

Storage DRS automates initial placement and ongoing balancing of VM files across datastores in a datastore cluster, while VM storage policies define the per-VM requirements. Together they let vSphere match each VM to a datastore satisfying its policy, which is precisely the automatic placement behaviour the administrator requires.

Why this answer

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.

Exam trap

VCP-DCV often tests the distinction between capability discovery (VASA), policy definition (VM storage policy), and automated placement (Storage DRS) — candidates frequently pick 'Storage DRS only' and forget that policy enforcement requires an assigned VM storage policy.

How to eliminate wrong answers

Option A is wrong because a VASA provider only exposes array capabilities to vCenter so policies can be created and compliance checked; by itself it does not perform automated placement. Option B is wrong because Storage DRS alone balances by space and I/O metrics but cannot enforce policy-based placement without an assigned VM storage policy. Option C is wrong because Storage I/O Control (SIOC) only manages I/O shares and limits during contention; it has nothing to do with placing VMs on policy-compliant datastores.

Practice this question →
12
MCQmedium

Refer to the exhibit. What does this error indicate?

A.The path is misconfigured.
B.The storage device is not connected.
C.The target LUN is not available.
D.The host's HBA is faulty.
AnswerC

The error arises because the ESXi host cannot reach the specified LUN, so the datastore cannot be mounted or accessed. This typically stems from zoning, masking or array-side presentation problems rather than host configuration, confirming the target LUN is unavailable to the host.

Why this answer

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.

Exam trap

VCP-DCV often tests the distinction between path-level failures (misconfigured path, dead path) and device-level failures (LUN unavailable, PDL) — candidates must recognize that a target LUN unavailable error is a device presentation issue, not a path or HBA issue.

How to eliminate wrong answers

Option A is wrong because a misconfigured path would produce a 'path down' or 'dead path' status in the storage adapter view, not a target LUN unavailable error — paths can be down while the LUN remains accessible via other paths. Option B is wrong because a disconnected storage device would typically manifest as all paths down and the device disappearing entirely, often with a 'device is offline' or 'permanently inaccessible' state rather than a target LUN unavailable message. Option D is wrong because a faulty HBA would affect all LUNs presented through that adapter and would surface as adapter-level errors (e.g., link down, hardware failure), not a single LUN unavailability.

Practice this question →
13
MCQhard

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

A.It reduces latency by limiting the number of queued I/Os.
B.It limits the maximum size of read and write operations.
C.It increases throughput by allowing more concurrent I/O operations.
D.It has no effect because NFS 4.1 does not support queue depth adjustments.
AnswerC

MaxQueueDepth defines how many outstanding I/O requests an NFS 4.1 datastore can hold. Raising it lets the host issue more concurrent operations before queuing blocks, so the array sustains higher throughput under load. Latency per operation is unaffected; only parallelism and queue capacity increase.

Why this answer

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.

Exam trap

VCP-DCV often tests the misconception that increasing queue depth always reduces latency, when in fact it primarily aims to increase throughput and can sometimes increase latency if the storage backend cannot handle the additional concurrency.

How to eliminate wrong answers

Option A is wrong because increasing MaxQueueDepth does not reduce latency by limiting queued I/Os; it actually allows more queued I/Os, which can increase latency under certain conditions but aims to improve throughput. Option B is wrong because MaxQueueDepth does not control the size of read/write operations; that is governed by other parameters like rsize/wsize. Option D is wrong because NFS 4.1 does support queue depth adjustments via MaxQueueDepth, and it does have an effect on performance.

Practice this question →
14
MCQmedium

A vSphere administrator needs to increase the size of a VMFS6 datastore that is running low on free space. The underlying LUN has 500 GB of unallocated space. The administrator expands the LUN on the storage array and then rescans the storage adapter. What should the administrator do next to grow the datastore?

A.Use the vSphere Client to increase the datastore capacity.
B.Use the vSphere Client to create a new datastore on the free space and then extend the original datastore.
C.Use the ESXi Shell and run the vmkfstools command to expand the datastore.
D.Use the ESXi Shell and run the partedUtil command to resize the partition.
AnswerA

After expanding the LUN and rescanning, the vSphere Client will show the additional free space on the device. The administrator can then use the 'Increase Datastore Capacity' wizard to expand the VMFS6 datastore into the newly available space. This is the supported method and ensures the file system is grown correctly.

Why this answer

After expanding the LUN and rescanning, the additional space appears as free on the device. The vSphere Client's 'Increase Datastore Capacity' wizard allows you to expand the VMFS6 datastore into that free space. This is the supported and safe method, ensuring the file system is properly grown and the datastore remains consistent.

Exam trap

The trap here is thinking that command-line tools like vmkfstools or partedUtil are needed to expand a VMFS datastore, when the vSphere Client provides a simple wizard.

Practice this question →
15
MCQmedium

Refer to the exhibit. An administrator attempts to add a host to a vSAN cluster and receives this error. Which step should the administrator take to resolve the issue?

A.Reconfigure the vMotion interface (vmk1) to also carry vSAN traffic.
B.Add the host to the cluster without vSAN and enable vSAN later.
C.Create a new VMkernel adapter (vmk3) on the host's network and enable vSAN traffic.
D.Enable vSAN traffic on the existing vmk0 interface.
AnswerC

Creating a dedicated VMkernel adapter with vSAN traffic enabled satisfies the cluster's requirement for a vSAN-capable vmknic on the host. vSAN cannot join a host whose existing adapters lack this service enabled, so adding vmk3 and ticking vSAN traffic provides the necessary network path for cluster communication.

Why this answer

vSAN requires a dedicated VMkernel adapter with the vSAN traffic service enabled, and the error indicates no such adapter exists on the host. Creating a new vmk3 and enabling vSAN traffic on it satisfies the prerequisite without disturbing existing management or vMotion traffic.

Exam trap

The trap is assuming any existing VMkernel adapter can be reused for vSAN; the exam tests whether you know vSAN requires its own dedicated, vSAN-enabled VMkernel interface, not just any vmk.

How to eliminate wrong answers

Option A is wrong because vMotion and vSAN traffic should be separated for performance and isolation; sharing vmk1 does not satisfy vSAN's requirement for a vSAN-enabled VMkernel interface. Option B is wrong because adding the host without vSAN does not resolve the underlying missing VMkernel adapter and defers the problem. Option D is wrong because vmk0 is the management interface, and enabling vSAN on it mixes management and storage traffic, which is not best practice and may not be permitted.

Practice this question →
16
Drag & Dropmedium

Sequence the steps to configure a DRS rule that keeps two VMs on different hosts.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

The correct sequence to configure a DRS rule that keeps two VMs on different hosts is: first access the cluster configuration, then add a new DRS rule, then name the rule, then choose the 'Separate VMs' type to enforce host separation, and finally assign the two VMs. This order ensures that each step logically follows the previous one, adhering to the typical workflow in vSphere where the rule is created before its properties are defined and applied.

Practice this question →
17
MCQmedium

A vSphere administrator is observing that a VM with a 2 TB thin-provisioned virtual disk on a VMFS6 datastore is reporting 1.5 TB of used space inside the guest OS, but the datastore shows only 800 GB consumed by the VM. What is the most likely cause of this discrepancy?

A.The virtual disk needs to be defragmented to reclaim space.
B.The VM has a snapshot that is consolidating, reducing storage usage.
C.The virtual disk is thick-provisioned lazy zeroed, which delays allocation.
D.The virtual disk is thin-provisioned, so only the actual written blocks consume space on the datastore.
AnswerD

Thin provisioning allocates datastore blocks only when the guest actually writes data, so consumed capacity reflects written blocks rather than the guest-reported 1.5 TB. The 800 GB datastore figure is therefore expected, not an error, and matches the thin disk's on-demand allocation behaviour.

Why this answer

The discrepancy is because the virtual disk is thin-provisioned. Thin provisioning means the virtual disk file (VMDK) on the datastore only occupies space for blocks that have been written to by the guest OS, not the full allocated size. The guest OS reports 1.5 TB of used space because it sees the logical file system usage, but the datastore only shows 800 GB consumed because that is the actual physical storage used by the written blocks.

Exam trap

The trap here is that candidates may confuse guest OS reported usage with datastore consumption, not realizing that thin provisioning only allocates storage for blocks actually written, leading them to incorrectly suspect snapshots or defragmentation issues.

How to eliminate wrong answers

Option A is wrong because defragmentation reorganizes data within the guest OS but does not reclaim space on the datastore for thin-provisioned disks; it may even increase fragmentation of the underlying VMDK. Option B is wrong because a consolidating snapshot would temporarily increase storage usage, not decrease it, and the scenario describes a lower datastore consumption, not higher. Option C is wrong because a thick-provisioned lazy zeroed disk allocates all space at creation (2 TB) and does not show only 800 GB consumed; it would show the full 2 TB allocated on the datastore regardless of guest usage.

Practice this question →
18
MCQeasy

A vSphere administrator needs to create a VMFS6 datastore on a new 4 TB LUN presented to an ESXi 7.0 host. The LUN is not yet formatted. Which method should the administrator use to create the datastore?

A.Use the ESXi Shell and run the partedUtil command to create a GPT partition.
B.Use the ESXi Shell and run the vmkfstools command to format the LUN.
C.Use the vSphere Client to add storage and select VMFS6.
D.Use the vSphere Client to create an NFS datastore and then convert it to VMFS6.
AnswerC

The vSphere Client provides a guided workflow to create a VMFS6 datastore on an unformatted LUN. This is the standard and recommended method for ESXi 7.0, as it automatically applies the correct partition layout and block size. It ensures compatibility and proper alignment without manual intervention.

Why this answer

The vSphere Client provides a straightforward wizard to create a VMFS6 datastore on an unformatted LUN. This method ensures correct partitioning, alignment, and registration with the ESXi host. It is the supported and recommended approach for ESXi 7.0, avoiding manual errors and ensuring compatibility.

Exam trap

The trap here is assuming that command-line tools like vmkfstools or partedUtil are required for creating VMFS datastores, when the vSphere Client is the standard method.

Practice this question →
19
MCQeasy

A vSphere administrator needs to present a new Fibre Channel LUN to an ESXi host. The LUN is already zoned and visible to the host's HBA. Which action should the administrator take to make the datastore available for use?

A.Rescan the storage adapter in the vSphere Client.
B.Create a new datastore and select the LUN from the list.
C.Reboot the ESXi host to detect the new LUN.
D.Run the esxcli storage core adapter rescan command from the host's DCUI.
AnswerA

After zoning and presenting a new LUN, the ESXi host must rescan its storage adapters to detect the new device. This can be done via the vSphere Client by selecting the host, going to Configure > Storage Adapters, and clicking Rescan. The rescan discovers new LUNs and makes them available for creating a datastore. Without a rescan, the host will not see the LUN.

Why this answer

To make a newly presented Fibre Channel LUN available, the administrator must rescan the storage adapter on the ESXi host. This can be done through the vSphere Client by navigating to the host's Storage Adapters and initiating a rescan. Once the rescan completes, the LUN appears and can be used to create a datastore.

Creating the datastore without a rescan will not work because the LUN is not yet detected.

Exam trap

The trap here is assuming that creating a datastore will automatically detect the new LUN, when a rescan is required first.

Practice this question →
20
MCQeasy

An ESXi host is connected to an iSCSI storage array using software iSCSI initiator. The administrator has configured two NICs for iSCSI traffic. During setup, the administrator selects 'Round Robin' as the path policy for the storage device. What is the benefit of this path policy?

A.It uses a single path until failure, then switches to another
B.It minimizes latency by always using the path with lowest latency
C.It load balances I/O across all active paths
D.It provides the highest performance for all workloads
AnswerC

Round Robin cycles I/O across every active path to the device, distributing load rather than using one path. With two iSCSI NICs configured, this policy uses both paths simultaneously, improving throughput and balancing traffic, unlike Fixed or Most Recently Used.

Why this answer

Round Robin is a VMware PSA (Pluggable Storage Architecture) path selection policy that actively distributes I/O across all active paths to a given device in a rotating fashion. With two iSCSI NICs configured, Round Robin sends commands down both paths, increasing aggregate throughput and utilizing both NICs simultaneously. This is the defining benefit of Round Robin compared to failover-only policies.

Exam trap

VCP-DCV often tests the confusion between path selection policies — candidates mix up Fixed (single path until failover), Round Robin (load balance across active paths), and Latency (prefer lowest-latency path), and pick the one that sounds most 'optimal' rather than the one matching the described behavior.

How to eliminate wrong answers

Option A is wrong because 'uses a single path until failure, then switches' describes the Fixed path policy, not Round Robin. Option B is wrong because 'always using the path with lowest latency' describes the Latency-based path policy (introduced in vSphere 6.5), which measures path latency and prefers the lowest. Option D is wrong because 'highest performance for all workloads' is an overgeneralization — Round Robin improves aggregate throughput but can actually reduce performance for workloads that benefit from path affinity or that are sensitive to out-of-order completion, and it is not universally the highest-performing policy.

Practice this question →
21
MCQeasy

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?

A.Storage I/O Control (SIOC) on each datastore.
B.vSphere HA for the datastore cluster.
C.Storage DRS without I/O metric, using space only.
D.Storage DRS with I/O metric enabled.
AnswerD

Storage DRS with the I/O metric enabled satisfies the I/O latency balancing requirement: Storage DRS migrates VM disks between datastores in the cluster, and enabling the I/O metric makes it use observed latency and throughput, not just capacity, when generating migration recommendations.

Why this answer

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.

Exam trap

The trap is conflating SIOC with Storage DRS — candidates pick SIOC because it deals with I/O latency, but SIOC only prioritizes and measures I/O; it is Storage DRS with the I/O metric that actually balances VMs across datastores.

How to eliminate wrong answers

Option A is wrong because SIOC alone provides I/O prioritization and latency stats but does not perform automated cross-datastore balancing — that is Storage DRS's job. Option B is wrong because vSphere HA is a compute-cluster availability feature for VM restart on host failure, not a datastore-cluster balancing feature. Option C is wrong because Storage DRS without the I/O metric balances only on space utilization, ignoring I/O latency entirely.

Practice this question →
22
MCQeasy

What is the default block size of a VMFS5 datastore?

A.1 MB
B.8 MB
C.2 MB
D.4 MB
AnswerA

VMFS5 uses a 1 MB file block size by default, replacing the 1 MB to 8 MB range available in VMFS3. This uniform block size supports volumes up to 64 TB and individual files up to 62 TB, satisfying the datastore capacity and large virtual disk requirements in the scenario.

Why this answer

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.

Exam trap

VCP-DCV often tests the difference between VMFS3 and VMFS5 block sizes; candidates may remember VMFS3's 8 MB default or confuse it with VMFS5's 1 MB default.

How to eliminate wrong answers

Option B is wrong because 8 MB was a possible block size in VMFS3, not the default for VMFS5. Option C is wrong because 2 MB was not a standard VMFS block size; VMFS3 offered 1, 2, 4, and 8 MB, but VMFS5 uses 1 MB. Option D is wrong because 4 MB was a VMFS3 block size option, not the VMFS5 default.

Practice this question →
23
MCQeasy

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?

A.Fixed (VMW_PSP_FIXED)
B.Most Recently Used (VMW_PSP_MRU)
C.Vendor-specific (VMW_PSP_FIXED_AP)
D.Round Robin (VMW_PSP_RR)
AnswerD

Round Robin (VMW_PSP_RR) satisfies the requirement to use all available paths by rotating I/O across every active path in the set, rather than confining traffic to a single preferred path. This maximises aggregate throughput for the Fibre Channel array, since each path carries a share of the load concurrently.

Why this answer

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.

Exam trap

VCP-DCV often tests the misconception that MRU or Fixed can load balance, but only Round Robin actively distributes I/O across all paths for throughput.

How to eliminate wrong answers

Option A is wrong because Fixed (VMW_PSP_FIXED) uses only the single preferred path and does not utilize other available paths unless the preferred path fails, so it cannot maximize throughput. Option B is wrong because Most Recently Used (VMW_PSP_MRU) uses only one path at a time (the most recently used) and switches only upon path failure, not for load balancing. Option C is wrong because Vendor-specific (VMW_PSP_FIXED_AP) is a policy that uses a fixed path with array-specific failover behavior, not active load balancing across all paths.

Practice this question →
24
MCQmedium

A company runs a critical SQL Server VM on vSphere 7.0. The VM has a single 300 GB virtual disk on a VMFS6 datastore backed by a SAN with 8 Gbps Fibre Channel. The VM is configured with 16 vCPUs and 64 GB RAM. Recently, users have reported slow query performance. The administrator checks the datastore performance and sees average latency of 15 ms with peaks of 50 ms during business hours. The storage array has multiple paths to the ESXi host, and the current path policy is Fixed with a single active path. The administrator wants to improve storage performance with minimal cost. Which action should the administrator take first?

A.Change the path selection policy to Round Robin on the ESXi host.
B.Add a vSphere Flash Read Cache to the VM.
C.Upgrade the Fibre Channel infrastructure to 16 Gbps.
D.Convert the virtual disk to thin provisioning to reduce I/O.
AnswerA

Round Robin spreads I/O across all active Fibre Channel paths, using the array's available bandwidth instead of one path. With Fixed policy, a single path bottlenecks at 15–50 ms latency, so this change is free and immediate.

Why this answer

The current Fixed path policy with a single active path underutilizes the available storage bandwidth, causing high latency during peak I/O. Changing to Round Robin (RR) distributes I/O across all available paths, reducing queue depth on any single path and lowering latency without any hardware cost. This is the most immediate and cost-effective fix for the observed performance issue.

Exam trap

The trap here is that candidates may assume hardware upgrades (like faster Fibre Channel) are the only solution to high latency, overlooking the fact that a misconfigured path policy can cause a single path to become a bottleneck even when multiple paths exist.

How to eliminate wrong answers

Option B is wrong because vSphere Flash Read Cache is deprecated in vSphere 7.0 and only accelerates read operations, not writes; the SQL Server workload likely involves significant write I/O, and adding it would not address the path-level bottleneck. Option C is wrong because upgrading the Fibre Channel infrastructure to 16 Gbps is a costly hardware change that does not fix the root cause—the single active path policy—and may not reduce latency if the bottleneck is path saturation rather than link speed. Option D is wrong because converting to thin provisioning does not improve I/O performance; it can actually increase latency due to on-demand allocation overhead and does not affect the path selection or queue depth issue.

Practice this question →
25
MCQeasy

A vSphere administrator needs to add a new VMFS6 datastore to an ESXi 7.0 host. The storage array has presented a 2 TB LUN to the host. The administrator wants to ensure the datastore uses the entire LUN and is aligned correctly. Which action should the administrator take?

A.Use the ESXi Shell to run partedUtil to create a GPT partition and then format it with vmkfstools.
B.Use the vSphere Client to create a new VMFS6 datastore but specify a smaller extent to leave room for snapshots.
C.Use the vSphere Client to create a new VMFS6 datastore and manually set the partition alignment to 64 KB for performance.
D.Use the vSphere Client to create a new VMFS6 datastore and select the entire LUN as the extent.
AnswerD

Creating a VMFS6 datastore through the vSphere Client automatically handles partition alignment and uses the entire LUN if selected. VMFS6 supports large volumes and automatically aligns partitions to the recommended 1 MB boundary. This is the simplest and most reliable method to ensure correct alignment and full LUN utilization without manual partitioning.

Why this answer

The vSphere Client's datastore creation wizard automatically aligns VMFS6 partitions to the optimal 1 MB boundary and uses the entire LUN when selected. This ensures correct alignment and full capacity utilization without manual intervention. Manual partitioning or leaving unallocated space is unnecessary and can introduce errors.

Exam trap

The trap here is thinking that manual partitioning or leaving unallocated space is required for alignment or snapshot space, when the vSphere Client handles alignment automatically.

Practice this question →
26
MCQmedium

An administrator is configuring a vSAN cluster with all-flash capacity. The cluster uses RAID-5 erasure coding with a policy of 'Number of failures to tolerate = 1' (PFTT=1). The administrator wants to minimize storage overhead while ensuring availability. Which vSAN storage policy setting should be used?

A.Set 'Primary level of failures to tolerate' to 1 and 'Primary level of failures to tolerate method' to 'RAID-1 (Mirroring)'
B.Set 'Primary level of failures to tolerate' to 2 and 'Primary level of failures to tolerate method' to 'RAID-6 (Erasure Coding)'
C.Set 'Primary level of failures to tolerate' to 1 and 'Primary level of failures to tolerate method' to 'RAID-5 (Erasure Coding)'
D.Set 'Primary level of failures to tolerate' to 0
AnswerC

RAID-5 erasure coding with PFTT=1 delivers roughly 1.33x overhead versus 2x for RAID-1 mirroring, satisfying the all-flash minimum-overhead constraint while still tolerating one host failure. The policy must explicitly select the RAID-5 method, not RAID-1.

Why this answer

For an all-flash vSAN cluster with PFTT=1, RAID-5 erasure coding provides the lowest storage overhead (approximately 1.33x) while still tolerating one failure. Setting the primary level of failures to tolerate to 1 and the method to RAID-5 (Erasure Coding) achieves the administrator's goal of minimizing overhead while maintaining availability.

Exam trap

VCP-DCV often tests whether candidates know the minimum host requirements and overhead ratios for vSAN RAID-5 vs RAID-6, and candidates frequently pick RAID-1 assuming it is always the most efficient or forget that erasure coding requires all-flash.

How to eliminate wrong answers

Option A is wrong because RAID-1 mirroring with PFTT=1 requires 2x storage overhead, which does not minimize storage consumption compared to RAID-5. Option B is wrong because PFTT=2 with RAID-6 requires a minimum of 6 hosts and incurs higher overhead (approximately 1.5x), and the question specifies PFTT=1. Option D is wrong because PFTT=0 provides no redundancy at all, violating the availability requirement.

Practice this question →
27
MCQhard

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?

A.Enable the array's QoS policy and configure the datastore for VAAI.
B.Change the PSP to Most Recently Used (MRU) to reduce path thrashing.
C.Increase the Round Robin IOPS limit to 10000.
D.Change the SATP to VMW_SATP_DEFAULT_AA and reconfigure the iSCSI initiator.
AnswerC

Raising the Round Robin IOPS limit to 10000 lets the PSP switch paths more frequently, spreading I/O across all active-active array ports instead of saturating one path for 1000 IOPS. Since VMW_SATP_ALUA reports every path active, the current limit concentrates load, causing the latency variance observed.

Why this answer

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.

Exam trap

The trap here is that candidates often assume a higher IOPS limit will cause more path switching and latency, when in fact the opposite is true—a low IOPS limit causes thrashing, and increasing it stabilizes performance on active-active arrays.

How to eliminate wrong answers

Option A is wrong because enabling QoS on the array does not directly address path switching behavior, and VAAI is a storage offload feature that does not resolve high latency from path thrashing. Option B is wrong because changing the PSP to MRU would use only one active path, negating the benefits of the active-active array and likely worsening performance for high-I/O VMs. Option D is wrong because VMW_SATP_DEFAULT_AA is a legacy SATP for active-active arrays without ALUA, and changing to it would break the ALUA path selection logic, potentially causing incorrect path states or failover issues.

Practice this question →
28
MCQhard

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?

A.Create a VM-to-VM affinity rule in the datastore cluster.
B.Set individual datastore affinity rules on each host.
C.Apply Storage I/O Control with high shares to the VMs.
D.Create a VM-to-VM anti-affinity rule in the datastore cluster.
AnswerA

VM-to-VM affinity rules keep specified virtual machines together on the same datastore within the datastore cluster. This satisfies the requirement that certain VMs must always remain co-located, which Storage DRS would otherwise separate during automated migrations.

Why this answer

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.

Exam trap

VCP-DCV often tests the confusion between compute-level DRS rules (host affinity) and storage-level DRS rules (datastore affinity), causing candidates to select host-based options for a storage placement requirement.

How to eliminate wrong answers

Option B is wrong because datastore affinity rules are configured at the datastore cluster level, not per host; host-level rules govern compute placement (vSphere DRS), not storage placement. Option C is wrong because Storage I/O Control with high shares prioritizes I/O throughput for specific VMs but does not control which datastore they reside on, so it cannot keep VMs together. Option D is wrong because a VM-to-VM anti-affinity rule does the opposite — it forces VMs onto separate datastores, which directly contradicts the requirement that they remain together.

Practice this question →
29
MCQeasy

An ESXi host has an NFS datastore mounted from a NAS array. The administrator wants to enable hardware acceleration (VAAI) for the datastore. Which requirement must be met?

A.The NAS array must present the LUN as an iSCSI target
B.The datastore must be formatted as VMFS6
C.The ESXi host must have a software FCoE adapter configured
D.The NAS array must support NFSv3 and VAAI primitives
AnswerD

NFS VAAI hardware acceleration relies on the NAS array implementing the NFSv3 primitives, specifically `SEXCL` (space reservation), `FILESIZE`, and `FULLFILE`, which ESXi offloads to the array. The datastore must be mounted over NFSv3, since these primitives are not defined for NFSv4.1, satisfying the stem's hardware acceleration requirement.

Why this answer

VAAI (vStorage APIs for Array Integration) for NFS requires the NAS array to support NFSv3 and the specific VAAI primitives for NFS, such as Full File Clone, Fast File Clone, Reserve Space, and Extended Statistics. ESXi detects these primitives via the array's NFSv3 protocol extensions and enables hardware acceleration for operations like clone and snapshot. Without array support for these primitives, VAAI cannot be enabled.

Exam trap

VCP-DCV often tests the confusion between block VAAI (which requires VMFS and array support for primitives like ATS, XCOPY, WRITE SAME) and NFS VAAI (which requires NFSv3 and array support for Full File Clone, Reserve Space, etc.) — candidates pick VMFS6 or iSCSI answers that apply to block storage, not NFS.

How to eliminate wrong answers

Option A is wrong because presenting the LUN as an iSCSI target changes the datastore from NFS to block (VMFS), which is a different protocol and not the NFS VAAI scenario described. Option B is wrong because VMFS6 is a block-based filesystem for iSCSI/FC datastores, not for NFS datastores — NFS datastores are not formatted as VMFS. Option C is wrong because a software FCoE adapter is for Fibre Channel over Ethernet block storage, unrelated to NFS VAAI.

Practice this question →
30
MCQhard

A vSphere environment uses an iSCSI storage array with multiple targets. The administrator configures CHAP authentication but some hosts fail to connect. The working hosts are configured with mutual CHAP, while the failing hosts use only one-way CHAP. What is the most likely reason for the failures?

A.The CHAP secret is not set on the failing hosts.
B.The storage array requires mutual CHAP, but the failing hosts are configured for one-way CHAP.
C.The iSCSI target name is incorrect on the failing hosts.
D.The storage array is configured to use only one-way CHAP.
AnswerB

Mutual CHAP requires authentication in both directions: the host authenticates to the target and the target authenticates to the host. The working hosts supply both sets of credentials, whereas one-way CHAP sends only the initiator's credentials, so the array's reverse challenge fails.

Why this answer

Mutual CHAP requires the target to authenticate the initiator and the initiator to authenticate the target. If the storage array is configured to require mutual CHAP, hosts using only one-way CHAP will fail to complete the authentication handshake. The working hosts are configured with mutual CHAP, confirming the array enforces mutual authentication.

Exam trap

The trap here is that candidates assume CHAP configuration is binary (enabled or disabled) and overlook the distinction between one-way and mutual CHAP, leading them to incorrectly select a missing secret or target name issue.

How to eliminate wrong answers

Option A is wrong because the failing hosts are configured with one-way CHAP, which still requires a CHAP secret; the issue is not the absence of a secret but the authentication direction. Option C is wrong because an incorrect iSCSI target name would cause all hosts to fail, not just those using one-way CHAP, and the working hosts connect successfully. Option D is wrong because if the array used only one-way CHAP, the hosts configured with mutual CHAP would fail, but they are working, so the array must require mutual CHAP.

Practice this question →
31
MCQmedium

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?

A.Cold migration
B.Clone
C.Storage vMotion
D.vMotion
AnswerC

Storage vMotion relocates a VM's virtual disks between datastores while the VM runs, and it carries the assigned VM storage policy to the destination. That satisfies the requirement to move from VMFS5 to vSAN without reconfiguring the policy manually.

Why this answer

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.

Exam trap

The trap is confusing vMotion (compute migration between hosts) with Storage vMotion (datastore migration) — candidates pick vMotion because it sounds like the general migration tool, missing that storage movement requires Storage vMotion.

How to eliminate wrong answers

Option A is wrong because cold migration requires the VM to be powered off, causing downtime, and is unnecessary when Storage vMotion can do it live. Option B is wrong because Clone creates a copy of the VM rather than migrating the original, leaving the source VM in place and potentially duplicating the storage policy assignment. Option D is wrong because vMotion migrates the VM's compute state (CPU/memory) between hosts, not its storage — it does not move virtual disks between datastores.

Practice this question →
32
MCQmedium

An administrator is configuring a vSAN cluster with a storage policy that uses RAID-5 erasure coding. The cluster has 6 hosts, each contributing capacity. The administrator sets the policy to 'Number of failures to tolerate' = 1. What is the minimum number of hosts required for this policy to be compliant?

A.6 hosts
B.4 hosts
C.5 hosts
D.3 hosts
AnswerB

RAID-5 erasure coding with FTT=1 requires a minimum of 4 hosts. This configuration stripes data and parity across 4 hosts, allowing the cluster to tolerate one host failure while maintaining data availability. With 4 hosts, the policy can be satisfied. Using more hosts increases resilience and performance, but 4 is the minimum for this specific policy.

Why this answer

For a vSAN storage policy using RAID-5 erasure coding with 'Number of failures to tolerate' set to 1, the minimum number of hosts required is 4. RAID-5 distributes data and parity across at least 4 fault domains (hosts), allowing the cluster to tolerate one host failure. With fewer than 4 hosts, the policy cannot be satisfied, and VMs would be non-compliant.

Exam trap

The trap here is confusing RAID-5 with RAID-1, where RAID-1 with FTT=1 requires only 3 hosts, but RAID-5 requires 4.

Practice this question →
33
Multi-Selecthard

Which THREE components are required to configure Storage DRS affinity and anti-affinity rules?

Select 3 answers
A.A resource pool
B.Datastores
C.An ESXi host
D.Virtual machines
E.A datastore cluster
AnswersB, D, E

Datastores are the actual storage backing devices that affinity and anti-affinity rules reference. Each rule specifies which virtual machines should or should not reside together on the same datastore, so at least two datastores within the cluster are needed to make placement decisions meaningful.

Why this answer

Storage DRS affinity and anti-affinity rules are configured at the datastore-cluster level, so option E (a datastore cluster) is required because it provides the boundary within which the rules are defined and enforced. Option B (datastores) is correct because the rules themselves specify which datastores within that cluster the virtual machines should be kept together on (affinity) or kept apart from (anti-affinity). Option D (virtual machines) is correct because the rules are applied to VM-to-datastore relationships, meaning the VMs are the objects whose placement is being constrained.

Option A (a resource pool) is not required, since resource pools govern CPU and memory allocation, not datastore placement. Option C (an ESXi host) is not required as a rule component, because Storage DRS rules operate on datastores and VMs within a datastore cluster rather than being defined per host.

Exam trap

The trap is confusing compute-layer objects (resource pools, ESXi hosts) with storage-layer objects — candidates who think 'affinity' always involves hosts or resource pools pick the wrong components.

Practice this question →
34
MCQhard

An administrator is troubleshooting a VMFS6 datastore that has become inaccessible after a storage array controller failover. The ESXi host logs show multiple 'Lost access to volume' errors. The administrator verifies that the array is presenting the LUN to the host, but the datastore remains unavailable. Which step should the administrator take first to resolve the issue?

A.Unmount and delete the VMFS datastore, then recreate it and restore from backup.
B.Rescan the storage adapter to discover the LUN and restore access.
C.Check the VMFS metadata and run vmfsanalyzer to determine if the datastore is corrupt.
D.Verify that the host can see the LUN and check for permanent device loss (PDL) or all paths down (APD) conditions.
AnswerD

After a controller failover, the host may experience APD or PDL. APD occurs when all paths to a device become unavailable, while PDL indicates the device is permanently gone. Checking for these conditions helps determine the appropriate recovery action, such as re-establishing paths or rebooting the host. This is the first step to diagnose the issue.

Why this answer

When a VMFS datastore becomes inaccessible after a controller failover, the host may have lost all paths to the storage. This can trigger an APD or PDL condition. The administrator should first verify whether the LUN is visible and check for these conditions.

Depending on the state, the host may need to be rebooted or paths may need to be re-established. This approach avoids unnecessary data loss.

Exam trap

The trap here is jumping to conclusions about datastore corruption or immediately rescanning without first determining whether the issue is an APD/PDL condition, which requires different remediation.

Practice this question →
35
MCQeasy

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

A.VMFS
B.vFlash
C.NFS
D.vSAN
AnswerD

vSAN aggregates local disks attached to each ESXi host into a shared distributed datastore, presenting pooled capacity and performance across the cluster. This lets VMs consume storage from hosts' local devices rather than requiring external shared arrays, which is the feature described.

Why this answer

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.

Exam trap

The trap is confusing vSAN with vFlash or VMFS: candidates may think vFlash pools local storage, but vFlash is only a caching mechanism, while vSAN is the actual pooling technology for local disks across a cluster.

How to eliminate wrong answers

Option A is wrong because VMFS is a clustered file system for shared storage (SAN/NFS), not a pooling mechanism for local disks across a cluster. Option B is wrong because vFlash uses local SSD as a read cache for VMs, but it does not pool storage across hosts. Option C is wrong because NFS is a network file system protocol for accessing remote storage, not a way to pool local disks.

Practice this question →
36
MCQmedium

An administrator is designing a vSAN cluster with 6 hosts. The cluster will run production workloads that require high availability. The administrator wants to minimize storage overhead while ensuring data can survive a single host failure. Which storage policy setting should be used?

A.RAID-5 with Number of Failures to Tolerate = 1
B.RAID-6 with Number of Failures to Tolerate = 2
C.RAID-0 with Number of Failures to Tolerate = 0
D.RAID-1 with Number of Failures to Tolerate = 1
AnswerA

RAID-5 erasure coding in vSAN provides fault tolerance for one host failure with less storage overhead than RAID-1. It requires a minimum of 4 hosts and uses parity to reconstruct data. For a 6-host cluster, RAID-5 offers a good balance of availability and capacity efficiency, making it ideal for production workloads.

Why this answer

For a 6-host vSAN cluster requiring tolerance of one host failure with minimized overhead, RAID-5 erasure coding is the best choice. It provides the necessary fault tolerance while using less capacity than RAID-1 mirroring. RAID-6 would offer additional protection but at higher overhead, and RAID-0 offers no redundancy.

Exam trap

The trap here is assuming that RAID-1 is always the default for high availability, but RAID-5 can provide similar fault tolerance with less overhead in clusters of sufficient size.

Practice this question →
37
MCQmedium

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?

A.Use Storage vMotion to migrate all VMs on the affected datastores to a healthy datastore before the upgrade.
B.Configure a vSphere HA admission control policy to reserve resources in case of host failure.
C.Place all ESXi hosts into maintenance mode.
D.Enable Storage I/O Control on the affected datastore to manage I/O during the upgrade.
AnswerA

Storage vMotion relocates the running VMs' files to a healthy datastore, so the five-minute LUN loss never affects them. vSphere HA default settings would only restart VMs after an APD timeout, causing downtime, so proactive migration satisfies the availability requirement.

Why this answer

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

Exam trap

VCP-DCV often tests the confusion between host-level availability (HA, maintenance mode) and storage-level availability (Storage vMotion, datastore evacuation) — candidates pick HA admission control thinking it protects against storage loss.

How to eliminate wrong answers

Option B is wrong because vSphere HA admission control reserves capacity for host failures; it does nothing to protect VMs from a datastore/LUN becoming temporarily unavailable, and the VMs would still lose access to their files. Option C is wrong because putting hosts into maintenance mode would evacuate or power off VMs, causing an outage rather than preventing one, and it doesn't relocate storage. Option D is wrong because Storage I/O Control only manages I/O contention/prioritization on a datastore; it cannot keep VMs running when the LUN is offline and provides no availability during a controller reboot.

Practice this question →
38
MCQeasy

A company uses vSphere 7.0 with two ESXi hosts in a cluster. All virtual machines (VMs) are stored on a VMFS6 datastore backed by a single LUN from a mid-range SAN. The LUN is presented to both hosts and both hosts have identical multipathing configuration. Recently, an administrator noticed that one host shows the datastore as "Inactive" while the other host can access it normally. The administrator verifies that both hosts have connectivity to the SAN, the LUN is visible to both hosts, and the storage array reports the LUN as online. The administrator wants to restore access to the datastore on the affected host without disrupting VMs running on the other host. Which action should the administrator take?

A.Perform a storage rescan on the affected host.
B.Reboot the affected ESXi host.
C.Change the multipathing policy on the affected host to Round Robin.
D.Unmount the datastore from the affected host and then remount it.
AnswerA

A rescan refreshes the affected host's storage adapter and VMFS volume inventory, re-establishing the datastore path without touching the host that still has working access. Because the SAN LUN is online and visible, rescanning is the non-disruptive remedy.

Why this answer

The datastore showing as 'Inactive' on one host while remaining accessible on the other indicates a path failure or a transient storage connectivity issue at the host level, not a permanent problem with the LUN or array. Performing a storage rescan on the affected host forces the ESXi host to re-evaluate all storage paths and re-register the datastore, restoring access without impacting VMs on the other host. This is the safest and least disruptive action because it does not require a reboot, multipathing policy change, or unmounting the datastore.

Exam trap

The trap here is that candidates may assume an 'Inactive' datastore requires a disruptive action like a reboot or unmount, when in fact a simple storage rescan is the standard VMware-recommended first step to re-establish path connectivity without affecting running VMs.

How to eliminate wrong answers

Option B is wrong because rebooting the affected host would cause unnecessary downtime for any VMs running on that host and is not required to fix a simple path visibility issue; a rescan is sufficient. Option C is wrong because changing the multipathing policy to Round Robin addresses load balancing across multiple active paths, but the problem here is that the datastore is 'Inactive' (all paths are dead or not claimed), not that the current policy is suboptimal; changing the policy will not re-establish connectivity. Option D is wrong because unmounting and remounting the datastore is a more invasive operation that could disrupt VMs on the affected host if any are present, and it does not address the underlying path issue; a rescan is the correct first step to re-discover the LUN.

Practice this question →
39
MCQhard

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?

A.The failed cache device reduces the overall cache capacity, causing the policy to be violated.
B.The vSAN cluster has lost a fault domain due to the failed cache device.
C.The RAID 5 policy requires a minimum of 4 hosts with cache devices, and now only 5 are available.
D.The failed cache device makes the entire disk group unavailable, so components on that disk group are inaccessible.
AnswerD

In vSAN, the cache tier is a single point of failure for its disk group. Losing the cache SSD renders the whole disk group inaccessible, so components stored on its capacity SSDs become absent, driving VMs non-compliant despite the cluster retaining sufficient capacity elsewhere.

Why this answer

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.

Practice this question →
40
MCQhard

A company is deploying a high-performance database workload on vSphere. The storage array supports NVMe over RDMA (NVMe-oF) and iSCSI. The workload requires extremely low latency and high IOPS. The network is dedicated 25 Gbps Ethernet with RoCE v2 support. Which storage protocol should be recommended, and why?

A.NFS, because it supports advanced features like Storage DRS
B.NVMe over RDMA, because it provides direct memory access and lower CPU overhead
C.Fibre Channel, because it is the fastest protocol available
D.iSCSI, because it is simpler to configure and does not require RDMA support
AnswerB

NVMe over RDMA performs direct memory access between host and array, bypassing much of the TCP/IP stack. On the dedicated 25 Gbps RoCE v2 fabric this cuts CPU overhead and latency, meeting the workload's extremely low latency and high IOPS requirement.

Why this answer

NVMe over RDMA (NVMe-oF with RoCE v2) provides direct memory access between the host and storage target, bypassing much of the TCP/IP stack and dramatically reducing CPU overhead and latency. For a high-IOPS, low-latency database workload on a dedicated 25 Gbps RoCE-capable network, this is the optimal choice. It leverages the existing RDMA fabric to deliver near-local NVMe performance.

Exam trap

VCP-DCV often tests the assumption that Fibre Channel is always the fastest option; candidates must recognize that NVMe over RDMA can surpass FC in latency and CPU efficiency when the fabric supports it.

How to eliminate wrong answers

Option A is wrong because NFS is a file-level protocol with higher latency and does not provide the block-level, low-latency access a high-performance database requires; Storage DRS is a vSphere feature unrelated to protocol speed. Option C is wrong because Fibre Channel, while fast and mature, is not inherently faster than NVMe-oF and would require separate FC HBAs and switching, ignoring the available 25 Gbps RoCE infrastructure. Option D is wrong because iSCSI runs over TCP and lacks RDMA's direct memory access, resulting in higher CPU utilization and latency — the opposite of what the workload demands.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Vsphere Storage questions.

Start 20-question session