How should I use these Configure and Manage vSphere Storage practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

VCP-DCV · topic practice

Configure and Manage vSphere Storage practice questions

Q: Can I practise just Configure and Manage vSphere Storage questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Configure and Manage vSphere Storage domain.

Practise VMware Certified Professional Data Center Virtualization VCP-DCV Configure and Manage vSphere Storage practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: Configure and Manage vSphere Storage

Practice 10 questions Browse domain →

What the exam tests

What to know about Configure and Manage vSphere Storage

Configure and Manage vSphere Storage questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Configure and Manage vSphere Storage exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Configure and Manage vSphere Storage questions

20 questions · select your answer, then reveal the explanation

Question 1hardmultiple choice

Read the full Configure and Manage vSphere Storage explanation →

A vSAN cluster has two fault domains. What is the maximum number of host failures that can be tolerated if the cluster is configured with a storage policy that sets 'Number of failures to tolerate' to 2?

Trap 1: 2

Incorrect. Although FTT=2 is configured, the cluster has only two fault domains. To actually tolerate 2 host failures, you need at least 5 fault domains. With 2 fault domains, the maximum tolerance is 1 host failure.

Trap 2: 3

Incorrect. Three host failures would exceed the capacity of two fault domains, as you can only tolerate at most one failure.

Trap 3: 4

Incorrect. Four host failures is far beyond what two fault domains can handle; you can tolerate at most one failure.

Study all Configure and Manage vSphere Storage common traps →

A
2
Why wrong: Incorrect. Although FTT=2 is configured, the cluster has only two fault domains. To actually tolerate 2 host failures, you need at least 5 fault domains. With 2 fault domains, the maximum tolerance is 1 host failure.
B
1
Correct. With two fault domains, the effective tolerance is limited. The policy of FTT=2 cannot be enforced, so the maximum number of host failures that can be tolerated is 1.
C
3
Why wrong: Incorrect. Three host failures would exceed the capacity of two fault domains, as you can only tolerate at most one failure.
D
4
Why wrong: Incorrect. Four host failures is far beyond what two fault domains can handle; you can tolerate at most one failure.

Full breakdown with real-world context →

Question 2mediummultiple choice

Read the full Configure and Manage vSphere Storage explanation →

An administrator needs to provision an NFS datastore for VMs that require high performance and low latency. The storage array supports multiple NFS versions. Which NFS version should be selected for the best performance?

Trap 1: NFS v2

Incorrect: NFS v2 is obsolete and unsupported in modern vSphere.

Trap 2: NFS v4.0

Incorrect: NFS v4.0 does not include pNFS; v4.1 is preferred.

Trap 3: NFS v3

Incorrect: NFS v3 is less efficient and lacks features like parallel NFS.

Study all Configure and Manage vSphere Storage common traps →

A
NFS v4.1
Correct: NFS v4.1 offers improved performance, compound operations, and pNFS support.
B
NFS v2
Why wrong: Incorrect: NFS v2 is obsolete and unsupported in modern vSphere.
C
NFS v4.0
Why wrong: Incorrect: NFS v4.0 does not include pNFS; v4.1 is preferred.
D
NFS v3
Why wrong: Incorrect: NFS v3 is less efficient and lacks features like parallel NFS.

Full breakdown with real-world context →

Question 3easymultiple choice

Read the full Configure and Manage vSphere Storage explanation →

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?

Trap 1: Move the VM to a cluster with more memory.

Memory does not directly address storage performance.

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

Jumbo frames improve network throughput but are not a mount option.

Trap 3: Increase the size of the NFS datastore to 1 TB.

Datastore size does not affect performance.

Study all Configure and Manage vSphere Storage common traps →

A
Move the VM to a cluster with more memory.
Why wrong: Memory does not directly address storage performance.
B
Enable jumbo frames on the ESXi host's VMkernel adapter for NFS.
Why wrong: Jumbo frames improve network throughput but are not a mount option.
C
Increase the size of the NFS datastore to 1 TB.
Why wrong: Datastore size does not affect performance.
D
Configure the NFS datastore to use vStorage APIs for Array Integration (VAAI).
VAAI offloads storage operations to the array, improving performance.

Full breakdown with real-world context →

Question 4mediummultiple choice

Read the full Configure and Manage vSphere Storage explanation →

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?

Trap 1: Create a new VM and attach the existing vmdk file.

Creating a new VM and attaching the existing VMDK does not repair the VM’s configuration file (.vmx), which holds the disk’s metadata and connection record; the VM cannot power on because the .vmx still lacks a valid disk reference. This step is tempting because it is the standard recovery method when a VM’s configuration file is lost or corrupted, as it rebuilds the VM object while preserving the disk data.

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

The disk may not appear in the inventory if the descriptor is missing.

Trap 3: Perform a storage vMotion of the VM to another datastore.

Storage vMotion requires the VM to be powered on.

Study all Configure and Manage vSphere Storage common traps →

A
Create a new VM and attach the existing vmdk file.
Why wrong: Creating a new VM and attaching the existing VMDK does not repair the VM’s configuration file (.vmx), which holds the disk’s metadata and connection record; the VM cannot power on because the .vmx still lacks a valid disk reference. This step is tempting because it is the standard recovery method when a VM’s configuration file is lost or corrupted, as it rebuilds the VM object while preserving the disk data.
B
Re-add the virtual disk from the datastore browser to the VM.
Why wrong: The disk may not appear in the inventory if the descriptor is missing.
C
Use the vmkfstools command to re-register the virtual disk.
vmkfstools -i can recreate the descriptor file from the flat vmdk.
D
Perform a storage vMotion of the VM to another datastore.
Why wrong: Storage vMotion requires the VM to be powered on.

Full breakdown with real-world context →

Question 5hardmultiple choice

Read the full Configure and Manage vSphere Storage explanation →

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?

Trap 1: FC with Fixed path policy.

Fixed path policy does not load balance across paths.

Trap 2: FC with Most Recently Used (MRU) path policy.

MRU does not provide load balancing.

Trap 3: iSCSI with Round Robin path policy.

iSCSI has higher latency than FC for critical apps.

Study all Configure and Manage vSphere Storage common traps →

A
FC with Fixed path policy.
Why wrong: Fixed path policy does not load balance across paths.
B
FC with Most Recently Used (MRU) path policy.
Why wrong: MRU does not provide load balancing.
C
iSCSI with Round Robin path policy.
Why wrong: iSCSI has higher latency than FC for critical apps.
D
FC with Round Robin path policy.
FC is low latency; Round Robin balances I/O across paths.

Full breakdown with real-world context →

Question 6mediummulti select

Read the full Configure and Manage vSphere Storage explanation →

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

Trap 1: A dedicated 10 GbE network for vSAN traffic.

While recommended, 1 GbE can be used for vSAN.

Trap 2: All hosts must have identical CPU models.

vSAN does not require identical CPUs.

Trap 3: A shared storage array accessible by all hosts.

vSAN uses local disks, not shared storage.

Study all Configure and Manage vSphere Storage common traps →

A
A dedicated 10 GbE network for vSAN traffic.
Why wrong: While recommended, 1 GbE can be used for vSAN.
B
All hosts must have identical CPU models.
Why wrong: vSAN does not require identical CPUs.
C
Each host must have at least one SSD and one HDD for capacity.
vSAN uses SSD for caching and HDD for capacity.
D
A minimum of 3 ESXi hosts in the cluster.
Standard vSAN requires at least 3 hosts.
E
A shared storage array accessible by all hosts.
Why wrong: vSAN uses local disks, not shared storage.

Full breakdown with real-world context →

Question 7hardmulti select

Read the full Configure and Manage vSphere Storage explanation →

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

Trap 1: The virtual disk must not be attached to a snapshot.

Storage DRS can migrate disks with snapshots.

Trap 2: The storage array must support VAAI.

VAAI is not required for Storage DRS.

Study all Configure and Manage vSphere Storage common traps →

A
The source and destination datastores must be part of the same datastore cluster.
Storage DRS operates within a datastore cluster.
B
The ESXi host must have a valid Storage vMotion license.
Storage vMotion is required for migration.
C
The virtual disk must not be attached to a snapshot.
Why wrong: Storage DRS can migrate disks with snapshots.
D
The storage array must support VAAI.
Why wrong: VAAI is not required for Storage DRS.
E
The virtual machine must be powered on.
Storage DRS migrates disks only for powered on VMs.

Full breakdown with real-world context →

Question 8easymultiple choice

Read the full Configure and Manage vSphere Storage explanation →

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

Trap 1: vMotion

vMotion migrates running VMs between hosts, not storage.

Trap 2: Distributed Resource Scheduler (DRS)

DRS balances compute resources.

Trap 3: Storage DRS

Storage DRS automates migrations but is not the underlying technology.

Study all Configure and Manage vSphere Storage common traps →

A
vMotion
Why wrong: vMotion migrates running VMs between hosts, not storage.
B
Distributed Resource Scheduler (DRS)
Why wrong: DRS balances compute resources.
C
Storage DRS
Why wrong: Storage DRS automates migrations but is not the underlying technology.
D
Storage vMotion
Storage vMotion migrates virtual disks with zero downtime.

Full breakdown with real-world context →

Question 9mediummultiple choice

Read the full Configure and Manage vSphere Storage explanation →

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?

Trap 1: The virtual disk needs to be defragmented to reclaim space.

Defragmentation does not affect datastore allocation.

Trap 2: The VM has a snapshot that is consolidating, reducing storage usage.

Snapshots increase storage usage, not decrease.

Trap 3: The virtual disk is thick-provisioned lazy zeroed, which delays…

Thick lazy zeroed still allocates all space at creation.

Study all Configure and Manage vSphere Storage common traps →

A
The virtual disk needs to be defragmented to reclaim space.
Why wrong: Defragmentation does not affect datastore allocation.
B
The VM has a snapshot that is consolidating, reducing storage usage.
Why wrong: Snapshots increase storage usage, not decrease.
C
The virtual disk is thick-provisioned lazy zeroed, which delays allocation.
Why wrong: Thick lazy zeroed still allocates all space at creation.
D
The virtual disk is thin-provisioned, so only the actual written blocks consume space on the datastore.
Thin provisioning allocates space as data is written.

Full breakdown with real-world context →

Question 10easymultiple choice

Read the full Configure and Manage vSphere Storage explanation →

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?

Trap 1: esxcli storage vmfs extend -l naa.60050768018603e1b800000000000001

The correct esxcli command is 'storage vmfs extend' but with different syntax.

Trap 2: esxcli storage vmfs grow -l naa.60050768018603e1b800000000000001

'grow' is not a valid esxcli command.

Trap 3: vmkfstools --extend…

--extend is not a valid option; use --growfs.

Study all Configure and Manage vSphere Storage common traps →

A
esxcli storage vmfs extend -l naa.60050768018603e1b800000000000001
Why wrong: The correct esxcli command is 'storage vmfs extend' but with different syntax.
B
esxcli storage vmfs grow -l naa.60050768018603e1b800000000000001
Why wrong: 'grow' is not a valid esxcli command.
C
vmkfstools --extend /vmfs/devices/disks/naa.60050768018603e1b800000000000001
Why wrong: --extend is not a valid option; use --growfs.
D
vmkfstools --growfs /vmfs/devices/disks/naa.60050768018603e1b800000000000001
This command extends the VMFS datastore to the full LUN size.

Full breakdown with real-world context →

Question 11hardmultiple choice

Read the full Configure and Manage vSphere Storage explanation →

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?

Trap 1: The CHAP secret is not set on the failing hosts.

The hosts have one-way CHAP, so secret is set.

Trap 2: The iSCSI target name is incorrect on the failing hosts.

Target name is likely correct because connection attempt is made.

Trap 3: The storage array is configured to use only one-way CHAP.

If array used one-way, mutual would fail, but mutual works.

Study all Configure and Manage vSphere Storage common traps →

A
The CHAP secret is not set on the failing hosts.
Why wrong: The hosts have one-way CHAP, so secret is set.
B
The storage array requires mutual CHAP, but the failing hosts are configured for one-way CHAP.
Mutual CHAP requires both sides to authenticate.
C
The iSCSI target name is incorrect on the failing hosts.
Why wrong: Target name is likely correct because connection attempt is made.
D
The storage array is configured to use only one-way CHAP.
Why wrong: If array used one-way, mutual would fail, but mutual works.

Full breakdown with real-world context →

Question 12mediummultiple choice

Read the full Configure and Manage vSphere Storage explanation →

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?

Trap 1: Add a vSphere Flash Read Cache to the VM.

Adds cost and may require additional licensing.

Trap 2: Upgrade the Fibre Channel infrastructure to 16 Gbps.

Costly and may not be necessary if paths are underutilized.

Trap 3: Convert the virtual disk to thin provisioning to reduce I/O.

Thin provisioning does not improve performance.

Study all Configure and Manage vSphere Storage common traps →

A
Change the path selection policy to Round Robin on the ESXi host.
Utilizes multiple paths, reducing latency.
B
Add a vSphere Flash Read Cache to the VM.
Why wrong: Adds cost and may require additional licensing.
C
Upgrade the Fibre Channel infrastructure to 16 Gbps.
Why wrong: Costly and may not be necessary if paths are underutilized.
D
Convert the virtual disk to thin provisioning to reduce I/O.
Why wrong: Thin provisioning does not improve performance.

Full breakdown with real-world context →

Question 13mediummultiple choice

Read the full Configure and Manage vSphere Storage explanation →

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?

Exhibit

Refer to the exhibit.

vmkfstools -P -v10 /vmfs/volumes/datastore1/vm1/vm1.vmdk

Output:
DISKOPEN: /vmfs/devices/disks/naa.6000c29a1b2c3d4e:1: Size 17179869184 (512 bytes sectors)
DISKOPEN: /vmfs/devices/disks/naa.6000c29a1b2c3d4e:2: Size 8589934592 (512 bytes sectors)
DISKOPEN: /vmfs/devices/disks/naa.6000c29a1b2c3d4e:3: Size 4294967296 (512 bytes sectors)
vmfs version: 6.82
capacity: 17179869184 (16.0 GB)
format: 3 (vmfs6)
number of extents: 3

Trap 1: The LUN was presented to the host with multiple paths, and each…

Multiple paths to the same LUN do not create separate extents; they appear as the same device with multiple paths.

Trap 2: The datastore is a VMFS6 datastore with three logical volumes…

VMFS6 does not aggregate logical volumes; extents are from the same physical LUN.

Trap 3: The virtual machine has a large VMDK file that spans multiple…

Large VMDK files are stored as a single file on VMFS6; sub-blocks are for small files, not extents.

Study all Configure and Manage vSphere Storage common traps →

A
The LUN was presented to the host with multiple paths, and each path is treated as a separate extent.
Why wrong: Multiple paths to the same LUN do not create separate extents; they appear as the same device with multiple paths.
B
The datastore was expanded by adding an extent from the same LUN.
When expanding a VMFS datastore, the system can add extents from the same LUN, leading to multiple extents as shown.
C
The datastore is a VMFS6 datastore with three logical volumes aggregated into one namespace.
Why wrong: VMFS6 does not aggregate logical volumes; extents are from the same physical LUN.
D
The virtual machine has a large VMDK file that spans multiple extents due to VMFS6 sub-block allocation.
Why wrong: Large VMDK files are stored as a single file on VMFS6; sub-blocks are for small files, not extents.

Full breakdown with real-world context →

Question 14hardmulti select

Read the full Configure and Manage vSphere Storage explanation →

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

Trap 1: Upgrade the datastore from VMFS5 to VMFS6.

Upgrading VMFS version requires the datastore to be in maintenance mode.

Trap 2: Add a new extent to the datastore from a different LUN.

Adding a new extent requires the datastore to be unmounted.

Study all Configure and Manage vSphere Storage common traps →

A
Remove the datastore from the host's inventory.
Removing from inventory is possible if no VMs are registered on it.
B
Upgrade the datastore from VMFS5 to VMFS6.
Why wrong: Upgrading VMFS version requires the datastore to be in maintenance mode.
C
Add a new extent to the datastore from a different LUN.
Why wrong: Adding a new extent requires the datastore to be unmounted.
D
Increase the size of the datastore by expanding an existing extent.
Expanding an existing extent can be done online.
E
Rename the datastore.
Renaming is a simple metadata change that can be done online.

Full breakdown with real-world context →

Question 15easymultiple choice

Read the full Configure and Manage vSphere Storage explanation →

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?

Trap 1: Reboot the affected ESXi host.

Rebooting is unnecessary and disruptive.

Trap 2: Change the multipathing policy on the affected host to Round Robin.

The issue is path availability, not policy.

Trap 3: Unmount the datastore from the affected host and then remount it.

Unmounting may cause issues with VMs on that host and is not needed.

Study all Configure and Manage vSphere Storage common traps →

A
Perform a storage rescan on the affected host.
Rescanning refreshes the list of paths and resolves transient path issues.
B
Reboot the affected ESXi host.
Why wrong: Rebooting is unnecessary and disruptive.
C
Change the multipathing policy on the affected host to Round Robin.
Why wrong: The issue is path availability, not policy.
D
Unmount the datastore from the affected host and then remount it.
Why wrong: Unmounting may cause issues with VMs on that host and is not needed.

Full breakdown with real-world context →

Question 16mediumdrag order

Read the full Configure and Manage vSphere Storage explanation →

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

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: Access cluster configuration, then add a new DRS rule, then select…

This is incorrect because the rule name is typically required before or right after selecting the type, not after assigning VMs. In many interfaces, naming comes earlier in the wizard to identify the rule before other selections.

Trap 2: Access cluster configuration, then provide a name for the rule,…

This is incorrect because you cannot name a rule before it is created (added). The rule must first be initiated as a new object before any properties like name can be set.

Trap 3: Access cluster configuration, then add a new DRS rule, then assign…

This is incorrect because the type (Separate VMs) must be chosen before assigning VMs, as the type determines how VMs are selected. Also, naming should be done early to avoid confusion.

Study all Configure and Manage vSphere Storage common traps →

A
Access cluster configuration, then add a new DRS rule, then provide a name for the rule, then select 'Separate VMs' as the type, then assign the two VMs.
This is the correct order because in vSphere, when creating a DRS rule to keep VMs on separate hosts, you first access the cluster settings, add a new rule, name it, choose the 'Separate VMs' type to enforce host separation, and finally assign the VMs. Following this sequence ensures the rule is properly configured.
B
Access cluster configuration, then add a new DRS rule, then select 'Separate VMs' as the type, then assign the two VMs, then provide a name for the rule.
Why wrong: This is incorrect because the rule name is typically required before or right after selecting the type, not after assigning VMs. In many interfaces, naming comes earlier in the wizard to identify the rule before other selections.
C
Access cluster configuration, then provide a name for the rule, then add a new DRS rule, then select 'Separate VMs' as the type, then assign the two VMs.
Why wrong: This is incorrect because you cannot name a rule before it is created (added). The rule must first be initiated as a new object before any properties like name can be set.
D
Access cluster configuration, then add a new DRS rule, then assign the two VMs, then provide a name for the rule, then select 'Separate VMs' as the type.
Why wrong: This is incorrect because the type (Separate VMs) must be chosen before assigning VMs, as the type determines how VMs are selected. Also, naming should be done early to avoid confusion.

Full breakdown with real-world context →

Question 17mediumdrag order

Read the full Configure and Manage vSphere Storage explanation →

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

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: Right-click cluster, select New Resource Pool, set CPU and memory…

This is incorrect because you must name the resource pool before configuring resources, as the name is a required parameter that identifies the pool.

Trap 2: Right-click cluster, select New Resource Pool, name the resource…

This is incorrect because the expandable reservation option is part of the resource configuration and must be set before confirming the creation, as it cannot be changed after clicking OK without editing the resource pool.

Trap 3: Right-click cluster, select New Resource Pool, name the resource…

This is incorrect because the expandable reservation option is a setting within the resource configuration, and it is typically set after specifying the resource limits and reservations, not before.

Study all Configure and Manage vSphere Storage common traps →

A
Right-click cluster, select New Resource Pool, name the resource pool, set CPU and memory resources (shares, reservation, limit), configure expandable reservation (optional), click OK.
This is the correct order because you must first initiate creation, then provide a name, then configure resources, optionally set expandable reservation, and finally confirm.
B
Right-click cluster, select New Resource Pool, set CPU and memory resources (shares, reservation, limit), name the resource pool, configure expandable reservation (optional), click OK.
Why wrong: This is incorrect because you must name the resource pool before configuring resources, as the name is a required parameter that identifies the pool.
C
Right-click cluster, select New Resource Pool, name the resource pool, set CPU and memory resources (shares, reservation, limit), click OK, configure expandable reservation (optional).
Why wrong: This is incorrect because the expandable reservation option is part of the resource configuration and must be set before confirming the creation, as it cannot be changed after clicking OK without editing the resource pool.
D
Right-click cluster, select New Resource Pool, name the resource pool, configure expandable reservation (optional), set CPU and memory resources (shares, reservation, limit), click OK.
Why wrong: This is incorrect because the expandable reservation option is a setting within the resource configuration, and it is typically set after specifying the resource limits and reservations, not before.

Full breakdown with real-world context →

Question 18mediummatching

Read the full Configure and Manage vSphere Storage explanation →

Match each VMware acronym to its full name.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Virtual Distributed Switch

Virtual Standard Switch

vSphere Installation Bundle

vSphere Storage APIs for Array Integration

vSphere APIs for Storage Awareness

Trap 1: ESXi: VMware vCenter Server is a centralized management platform.

Incorrect. This definition actually describes vCenter Server, not ESXi.

Trap 2: vSphere: VMware VMFS is a clustered file system.

Incorrect. This definition actually describes VMFS, not vSphere.

Study all Configure and Manage vSphere Storage common traps →

A
ESXi: VMware ESXi is a bare-metal hypervisor.
Correct. ESXi stands for Elastic Sky X integrated and is a bare-metal hypervisor.
B
vCenter: VMware vCenter Server is a centralized management platform.
Correct. vCenter Server is the central management platform for vSphere.
C
vSphere: VMware vSphere is a suite of virtualization products.
Correct. vSphere is VMware's virtualization platform comprising ESXi and vCenter.
D
VMFS: VMware VMFS is a clustered file system.
Correct. VMFS is a clustered file system optimized for virtual machines.
E
ESXi: VMware vCenter Server is a centralized management platform.
Why wrong: Incorrect. This definition actually describes vCenter Server, not ESXi.
F
vSphere: VMware VMFS is a clustered file system.
Why wrong: Incorrect. This definition actually describes VMFS, not vSphere.

Full breakdown with real-world context →

Question 19mediummatching

Read the full Configure and Manage vSphere Storage explanation →

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

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

62 TB

256

6 TB

1024

Trap 1: Virtual machine - max vCPUs per VM: 128

Incorrect — the maximum vCPUs per VM in vSphere 7 is 256, not 128.

Trap 2: Datastore - max size: 32 TB

Incorrect — the maximum datastore size in vSphere 7 is 64 TB, not 32 TB.

Study all Configure and Manage vSphere Storage common traps →

A
Virtual machine - max vCPUs per VM: 256
vSphere 7 supports up to 256 virtual CPUs per virtual machine.
B
Virtual machine - max memory per VM: 6 TB
vSphere 7 supports up to 6 TB of memory per virtual machine.
C
Datastore - max size: 64 TB
VMFS6 datastores in vSphere 7 support a maximum size of 64 TB.
D
Cluster - max hosts: 64
A vSphere cluster can contain up to 64 hosts in vSphere 7.
E
Virtual machine - max vCPUs per VM: 128
Why wrong: Incorrect — the maximum vCPUs per VM in vSphere 7 is 256, not 128.
F
Datastore - max size: 32 TB
Why wrong: Incorrect — the maximum datastore size in vSphere 7 is 64 TB, not 32 TB.

Full breakdown with real-world context →

Question 20mediummultiple choice

Read the full Configure and Manage vSphere Storage explanation →

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?

Trap 1: Set 'Primary level of failures to tolerate' to 1 and 'Primary level…

Mirroring uses more capacity than erasure coding.

Trap 2: Set 'Primary level of failures to tolerate' to 2 and 'Primary level…

RAID-6 provides higher tolerance but more overhead, not minimal for PFTT=1.

Trap 3: Set 'Primary level of failures to tolerate' to 0

No redundancy means no protection against failures.

Study all Configure and Manage vSphere Storage common traps →

A
Set 'Primary level of failures to tolerate' to 1 and 'Primary level of failures to tolerate method' to 'RAID-1 (Mirroring)'
Why wrong: Mirroring uses more capacity than erasure coding.
B
Set 'Primary level of failures to tolerate' to 2 and 'Primary level of failures to tolerate method' to 'RAID-6 (Erasure Coding)'
Why wrong: RAID-6 provides higher tolerance but more overhead, not minimal for PFTT=1.
C
Set 'Primary level of failures to tolerate' to 1 and 'Primary level of failures to tolerate method' to 'RAID-5 (Erasure Coding)'
RAID-5 with PFTT=1 provides efficient capacity usage and fault tolerance.
D
Set 'Primary level of failures to tolerate' to 0
Why wrong: No redundancy means no protection against failures.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Configure and Manage vSphere Storage sessions

Start a Configure and Manage vSphere Storage only practice session

Every question in these sessions is drawn from the Configure and Manage vSphere Storage domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Configure and Manage vSphere Storage questions →Mixed VCP-DCV session

Frequently asked questions

What does the VCP-DCV exam test about Configure and Manage vSphere Storage?: Configure and Manage vSphere Storage questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Configure and Manage vSphere Storage questions in a focused session?: Yes — the session launcher on this page draws every question from the Configure and Manage vSphere Storage domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other VCP-DCV topics?: Use the topic links above to move to related areas, or go back to the VCP-DCV question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the VCP-DCV exam covers. They are not copied from any real exam or dump site.

Configure and Manage vSphere Storage only

10 questions 20 questions 30 questions 50 questions

Mixed VCP-DCV session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All VCP-DCV questions Configure and Manage vSphere Storage domain overview VCP-DCV exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Configure and Manage vSphere Storage practice questions

What to know about Configure and Manage vSphere Storage

Common Configure and Manage vSphere Storage exam traps

Configure and Manage vSphere Storage questions

A vSAN cluster has two fault domains. What is the maximum number of host failures that can be tolerated if the cluster is configured with a storage policy that sets 'Number of failures to tolerate' to 2?

An administrator needs to provision an NFS datastore for VMs that require high performance and low latency. The storage array supports multiple NFS versions. Which NFS version should be selected for the best performance?

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?

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?

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 vSphere administrator is planning to configure VMware vSAN. Which TWO requirements must be met for a vSAN cluster?

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

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

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?

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?

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?

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?

Exhibit

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

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

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

Match each VMware acronym to its full name.

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

Track your progress over time

Start a Configure and Manage vSphere Storage only practice session

Related VCP-DCV topic practice pages

vSphere Architecture, Products and Solutions practice questions

Configure and Manage vSphere Networking practice questions