Sign in
Home/VMware/VMware HCI Master Specialist (5V0-21.21)/Free questions

VMware HCI Master Specialist (5V0-21.21) — Free Practice Questions

10 free sample questions from a bank of 95, with the correct answers and explanations. No signup required — start practising right now.

1In a stretched vSAN cluster, how is Read Locality established after fail over to the secondary site?
  • 100% of the reads comes from vSAN hosts on the local site
  • 50% of the reads comes from vSAN hosts on the local site
  • 100% of the reads comes from vSAN hosts on the remote site
  • 50% of the reads comes from vSAN hosts on the remote site
Answer: A

The short version

A — Read locality re-establishes to the surviving site. After failover to the secondary site, VMs read 100% from local hosts there.

Key concepts in this question

  • Read Locality: preferring local-site reads in a stretched cluster
  • Failover: VMs restart or continue on the secondary site
  • Stretched cluster sites: preferred, secondary, and witness roles

Why A is correct

In a stretched vSAN cluster, read locality means reads are served from the site where the VM is running. After failover to the secondary site, the VM's active site becomes the secondary site, so 100% of reads come from vSAN hosts on that local site. This avoids unnecessary cross-site read traffic and restores expected latency.

Why the others are wrong

  • B. 50% local implies round-robin reads across sites, which defeats read locality.
  • C. 100% remote means reading from the old site, the opposite of locality after failover.
  • D. 50% remote still sends half the reads across the inter-site link, so locality is not established.

5V0-2121 exam tip

Failover moves locality with the VM — think local reads follow the running site.

2During a maintenance action on a vSAN node, a vSAN administrator noticed that the default repair delay time is about to be reached. Which two commands must be run to extend the time? (Choose two.)
  • /etc/init.d/vsanmgmtd restart
  • esxcli system settings advanced set -o /VSAN/ClomRepairDelay -i 50
  • esxcli system settings advanced set -o /VSAN/ClomRepairDelay -i 80
  • /etc/init.d/clomd restart
  • /etc/init.d/vsanobserver restart
Answer: C, D

The short version

CD — Extend ClomRepairDelay then restart clomd. Setting the delay to 80 minutes and restarting clomd applies the longer window.

Key concepts in this question

  • ClomRepairDelay: timer before absent components are rebuilt
  • clomd: cluster-level object manager daemon that enforces the timer
  • Maintenance window: needing more than the default 60 minutes

Why CD is correct

The repair delay is controlled by the advanced setting /VSAN/ClomRepairDelay, and increasing it to 80 extends the window before rebuild starts. The clomd service must be restarted for the new delay value to take effect on that host. Together these two steps safely postpone resync during maintenance.

Why the others are wrong

  • A. Restarting vsanmgmtd affects management and health service, not the repair timer.
  • B. Setting the value to 50 shortens the delay below default instead of extending it.
  • E. Restarting vsanobserver only affects stats collection, not repair behavior.

5V0-2121 exam tip

Delay plus clomd — remember 60 default, set higher with esxcli and restart clomd.

3A write intensive application has been deployed recently into an All-flash 4-node vSAN cluster. Each node has one disk group with the following configuration: • 1 x 400 GB SSD for Cache • 4 x 3.84 TB SSD for Capacity After the deployment, the administrator notices that the overall workload performance is degraded and observes a low-write, buffer-free percentage. Which action should be taken to remediate this issue?
  • Adding a second cache disk to the existing disk group
  • Replacing the cache disk in the existing disk group with a larger one
  • Enabling automatic rebalance from the vSAN services advanced options
  • Increasing the number of capacity disks in the existing disk group
Answer: B

The short version

Keep B: all-flash write-buffer exhaustion needs a larger cache device because a second cache disk per group is impossible.

Key concepts in this question

All-flash write buffer, OSA disk-group ratio 1 cache to 1 group, cache-to-capacity ratio.

Why B is correct

B is correct because 100 percent of the all-flash cache is the write buffer and replacing it with a larger device directly grows buffer capacity and endurance; docs cap the group at one cache device.

Why the others are wrong

  • A. Wrong because adding a second cache disk to the existing disk group violates the 1:1 cache-to-group rule and is architecturally impossible.
  • B. Correct: larger cache device remediates low buffer-free percentage.
  • C. Wrong because automatic rebalance distributes capacity, it does not grow the write buffer.
  • D. Wrong because adding capacity disks grows capacity, not write-buffer size.

5V0-2121 exam tip

One cache per disk group always; low buffer-free means grow the cache device, never add a second cache to the same group.

4An administrator wants to deploy a desktop and application virtualization solution on top of vSAN. Which VMware product should the administrator install?
  • VMware Dynamic Environment Manager
  • VMware Horizon Apps
  • VMware Workspace One Access
  • VMware Horizon
Answer: D

The short version

D -- desktop and app virtualization on vSAN means VMware Horizon.

Key concepts in this question

  • Horizon delivers virtual desktops and applications.
  • The other options are accessory or identity products, not the VDI platform.

Why D is correct

Horizon is the VMware product for deploying desktop and application virtualization on top of vSAN storage.

Why the others are wrong

  • A. Dynamic Environment Manager handles user environment settings, not desktop delivery.
  • B. Horizon Apps is not the platform name for the full solution.
  • C. Workspace One Access provides identity brokering, not desktops.

vSAN exam tip

Desktops plus apps on vSAN equals Horizon.

5An administrator has been tasked with enabling encryption for existing virtual machines on a vSAN cluster. Which three prerequisites must be satisfied before completing the task? (Choose three.)
  • Create an encryption storage policy
  • Enable Data-In-Transit encryption first
  • Enable that the virtual machines are powered on
  • Verify if a role with privilege ג€Cryptographic operations.Encrypt newג€ is assigned
  • Verify if a role with privilege ג€Cryptographic operations.Migrateג€ is assigned
  • Establish a trusted connection with the KMS
Answer: A, D, F

The short version

ADF — Encryption needs KMS trust, encryption policy, and Encrypt-new privilege. The VM must be powered off, not powered on, and Data-In-Transit encryption is not a prerequisite.

Key concepts in this question

  • KMS trust: vCenter must establish a trusted connection with a Key Management Server before encrypting VMs.
  • Encryption storage policy: an SPBM policy with encryption enabled is required to apply encryption to existing VMs.
  • Encrypt-new privilege: Cryptographic operations.Encrypt new is the required privilege, not Migrate.

Why ADF is correct

A is correct because an encryption storage policy must exist before existing VMs can be encrypted. D is correct because VMware requires the Cryptographic operations.Encrypt new privilege to encrypt an existing VM. F is correct because a trusted KMS connection must be established first so keys can be issued and retrieved.

Why the others are wrong

  • B. Data-In-Transit encryption is a separate vSAN feature and is not a prerequisite for VM encryption.
  • C. The VM must be powered off to encrypt it; requiring it to be powered on contradicts the docs.
  • E. Cryptographic operations.Migrate is for migrating encrypted VMs, not for enabling encryption on existing VMs.

5V0-2121 exam tip

Remember: KMS trust + encryption policy + powered-off VM + Encrypt new.

6Upon checking the latency goal under vSAN performance diagnostics, the vSAN Administrator sees this message displayed: The increase in latency in the vSAN stack might be beyond expected limits. Which two root causes can be identified to help remediate the issue? (Choose two.)
  • vSAN VMKemel portgroup is configured with the ג€Route based on IP hashג€ teaming policy
  • vSAN encryption is enabled
  • Large packet losses and retransmissions on the network layer
  • Incorrect sizing of the disk groups capacity disks
  • One or more disk groups are congested
Answer: C, E

The short version

CE — Network loss and congested disk groups raise latency. Packet loss with retransmits and disk-group congestion explain the warning.

Key concepts in this question

  • vSAN latency: time spent in network plus storage stack
  • Packet loss: retransmissions that inflate network latency
  • Congestion: overloaded disk groups queuing IO

Why CE is correct

Large packet losses force retransmissions on the vSAN network, which directly increases observed latency in performance diagnostics. Congested disk groups queue backend IO and add storage-layer latency, so remediation focuses on network health and congestion. These are the two classic root causes called out by vSAN diagnostics.

Why the others are wrong

  • A. Route based on IP hash teaming affects load distribution, not this latency warning.
  • B. Encryption adds CPU overhead but is not flagged as the cause of this stack latency increase.
  • D. Capacity-disk sizing affects usable space, not transient latency and congestion.

5V0-2121 exam tip

Latency high — check network loss first, then disk-group congestion.

7An architect is designing for a production vSAN cluster, and the customer introduced these requirements related to File Services: ✑ A minimum of 12 files shares. ✑ 30TB NFS capacity to mount workload VMs. What should be the architect's recommendations?
  • Point out the risks regarding putting the hosts in maintenance mode in terms of FSVM.
  • Confirm on all of the requirements and move forward with the physical design.
  • Raise concerns regarding support when running VMs on an NFS share as risk.
  • Highlight the required number of nodes required for the vSAN cluster as a constraint.
Answer: C

The short version

C — Warn against running VMs on vSAN File Service NFS. NFS shares are for file workloads, not VM hosting.

Key concepts in this question

  • vSAN File Services: NFS and SMB shares from vSAN
  • NFS for VMs: unsupported or discouraged design pattern
  • Design risk: architect must call out constraint

Why C is correct

vSAN File Service NFS is designed for file shares, and running production workload VMs on those NFS mounts is not a supported or recommended pattern. The architect should therefore raise this as a risk rather than confirming the design as-is. The correct action is to flag the workload placement concern and propose block or vSAN datastore alternatives.

Why the others are wrong

  • A. Maintenance-mode FSVM behavior is secondary and misses the main workload-placement risk.
  • B. Confirming all requirements ignores the VM-on-NFS support problem.
  • D. Node count is not the blocking issue when the access method itself is unsuitable.

5V0-2121 exam tip

File shares are files — never design VMs to run on vSAN NFS.

8An administrator has received an alert indicating that a single capacity device is close to failing within the production vSAN Cluster. The administrator must now complete preemptive maintenance on the vSAN Cluster without impacting the availability of workloads or vSAN File Services. The following information is known about the vSAN Cluster: ✑ vSAN 7.x Cluster ✑ vSAN node count: 8 ✑ De-Duplication and Compression: Enabled. ✑ Encryption: Disabled Current Utilization: 45% ✑ Disk Groups: 2 ✑ Devices per node: 2 x 400 GB SSD, 6 x 1.8 TB SSD Which three steps should the administrator take to successfully complete the task? (Choose three.)
VMware HCI Master Specialist (5V0-21.21) question 8
  • Remove the affected Disk Group from the vSAN Cluster, and choose Full Data Migration.
  • Replace the failed disk with a storage device that is identical in class and capacity.
  • Remove the affected Disk Group from the vSAN Cluster, and choose No Data Migration.
  • Replace the failed disk with a storage device that is identical in class but smaller in capacity.
  • Put the affected vSAN host into maintenance mode to physically replace the storage device.
  • Remove the affected Disk from the Disk Group, and choose Full Data Migration.
Answer: A, B, E

The short version

ABE — Evacuate the disk group, use identical disk, use maintenance mode. Deduplication forces disk-group level work plus safe replacement.

Key concepts in this question

  • Deduplication and Compression: applied at disk-group granularity
  • Full Data Migration: evacuates data before removal
  • Identical device: same class and capacity for replacement

Why ABE is correct

With deduplication enabled, an entire disk group must be removed with Full Data Migration because dedup scope spans the group. The replacement disk must be identical in class and capacity to keep the group balanced and supported. Placing the host in maintenance mode allows safe physical replacement without workload or File Service impact.

Why the others are wrong

  • C. No Data Migration would leave data at risk and violate availability requirements.
  • D. A smaller-capacity device is unsupported and can break disk-group uniformity.
  • F. Removing only the disk is insufficient when deduplication requires whole-group evacuation.

5V0-2121 exam tip

Dedup on means disk-group surgery — full evacuation plus identical disk.

9A 30-minute power maintenance window has been approved on Sunday. Due to a delay, the maintenance took 20 minutes longer to finish. During this time, the vSAN administrator noticed that one of the clusters nodes was affected by a power shortage, as it was connected to an affected power source. The default vSAN storage policy has been applied. What will be the status of the vSAN objects on the affected host immediately after it is recovered?
  • The cluster will be partitioned and the vSAN host will need to be rejoined.
  • A rebuild of the affected objects will occur.
  • All objects will remain accessible.
  • All objects on the affected host will be lost.
Answer: C

The short version

C -- 50-minute outage is still inside the 60-minute CLOM repair delay, so objects stay accessible.

Key concepts in this question

  • Absent vs degraded components and the 60-minute repair delay timer.
  • Default vSAN policy keeps quorum when the host returns before the delay expires.

Why C is correct

Total downtime is 30 plus 20 equals 50 minutes, under the 60-minute delay, so vSAN has not started a rebuild and objects remain accessible, though non-compliant, once the host is back.

Why the others are wrong

  • A. No partition rejoin is needed for a transient outage under the delay timer.
  • B. No rebuild occurs because the delay had not expired.
  • D. Components are absent, not permanently lost, so nothing is discarded.

vSAN exam tip

Absent under 60 minutes means accessible but non-compliant; rebuild starts only after the delay expires.

10Due to the success of the recently deployed developer-only private cloud solution, a company has a new requirement to at least double the usable capacity in their all-flash vSAN cluster. The vSAN cluster is deployed into a co-located datacenter that is owned by a third-party hosting company. The hosting company charges a fixed monthly cost for rack space and power consumption. The service owner has been given a limited budget for additional hardware purchases, but not for on-going co-location costs. The current vSAN cluster has the following configuration: ✑ 10 vSAN Nodes with 2 CPUs (20 cores), 512 GB RAM ✑ 1 Disk Group per vSAN node - 1 x 400 GB - 4 x 1.8 TB ✑ De-duplication and Compression is enabled. ✑ vSAN Capacity is currently: - Total: 72 TB - Usable: ~40 TB (FTT1/RAID1) and ~60 TB (FTT1/RAID5). As a result of any action taken, the service owner would like to ensure that overall availability of the vSAN cluster is increased. Which two recommendations meet the requirement to increase capacity while maintaining service availability? (Choose two.)
  • Install an additional 400 GB SSD and 4 x 1.8 TB SSDs per vSAN node.
  • Update the existing Disk Group, and claim the newly installed drives for each node.
  • Create a new Disk Group, and claim the newly installed cache and capacity SSD drives for each node.
  • Install an additional 3 x 1.8 TB SSDs per vSAN node.
  • Replace existing SSDs with an 800 GB SSD and 4 x 3.8 TB SSDs per vSAN node.
Answer: A, C

The short version

AC — Add cache plus capacity disks and create a new disk group. That doubles capacity without new racks or power.

Key concepts in this question

  • Disk groups: cache plus capacity scaling unit
  • Colocation cost: fixed rack and power budget
  • New disk group: required when adding new cache

Why AC is correct

Adding a matching cache SSD plus capacity SSDs to each node increases raw capacity within the same rack footprint, respecting the hosting cost constraint. A new cache device cannot join an existing disk group, so a new disk group must be created and claimed. This combination roughly doubles usable capacity under the existing FTT policies.

Why the others are wrong

  • B. Updating the existing disk group cannot absorb a new cache disk, so it fails.
  • D. Adding only three capacity disks without cache is unbalanced and will not double capacity.
  • E. Replacing all SSDs with larger ones is costly and requires heavy data movement, violating budget intent.

5V0-2121 exam tip

New cache means new disk group — scale capacity inside the same racks.

Want the full bank of 95 questions for VMware HCI Master Specialist (5V0-21.21)? See all practice exams.