VCP-DCV Practice Test 37 — 15 Questions

Question 1

A vSphere administrator manages a cluster for a VDI workload using VMware Horizon. Each virtual desktop runs a GPU-intensive application and is assigned a vGPU profile (profile: grid_m60-1q) with 4 vCPUs and 8 GB RAM. The ESXi hosts are equipped with NVIDIA M60 GPUs (each host has 2 GPUs, each with 2 physical GPUs? Actually M60 has 2 GPUs on one card, but let's keep generic). The administrator receives complaints of poor graphics performance and high latency. The administrator runs esxtop and observes that the total CPU utilization for the hosts is low (average 30%), but the GPU memory utilization is consistently above 95%, and the vGPU scheduler reports high 'GPU mem' wait times. The number of VMs per host is within the GPU profile limits. What is the most effective way to improve performance?

Accepted Answer

Upgrade the hosts to support GPUs with larger memory capacity or add additional GPUs to each host.. The bottleneck is GPU memory, not CPU. The most effective solution is to upgrade to GPUs with higher memory capacity or add more GPUs. Option D directly addresses this. Option A would increase GPU memory per VM but reduce the total number of VMs, possibly not needed. Option B might not help. Option C could reduce GPU load but at the cost of user experience.

Answer

Change the vGPU profile to a larger profile (e.g., grid_m60-2q) for all VMs.

Answer

Increase the CPU reservation for each VDI VM.

Answer

Reduce the number of vCPUs per VM from 4 to 2.

Question 2

A small financial services company runs a critical trading application on a single vSphere host with two NUMA nodes (each with 8 cores). The VM is configured with 12 vCPUs and 64 GB memory. The application is not yet live, but load testing shows that CPU performance is satisfactory, but memory bandwidth is lower than expected. The application is known to benefit from fast memory access within a single NUMA domain. The administrator notices that the VM's memory is spread across both NUMA nodes. The administrator wants to force the VM to use only one NUMA node to maximize performance. However, the VM requires 12 vCPUs, which exceeds the 8 physical cores per node. What is the best course of action to improve memory bandwidth for this VM?

Accepted Answer

Keep the vCPU count at 12 but configure a NUMA Affinity to prefer the first NUMA node, and accept some cross-node memory access.. Option C is correct: Using NUMA affinity to prefer one node keeps most memory local, but vCPU count exceeds core count, so some vCPUs will still run on the second node. However, memory can be allocated from the preferred node as much as possible, reducing cross-node latency. Option A is wrong because reducing vCPUs may affect application performance. Option B is wrong because CPU affinity to only one node would starve vCPUs as there are only 8 cores, causing high ready time. Option D is wrong; Hyper-Threading does not change physical core count; 12 vCPUs still exceed 8 cores per node, and HT does not enable single-node placement.

Answer

Enable Hyper-Threading and reassign vCPUs to 12, and the VM will automatically run within one NUMA node.

Answer

Keep the vCPU count at 12 but set CPU affinity to the first NUMA node only, leaving the second node unused.

Answer

Reduce the number of vCPUs to 8 to fit within one NUMA node, and keep the same memory size.

Question 3

A managed hosting provider uses vSphere 7 with vSAN to run customer VMs. One customer's VM is a SQL Server database with 8 vCPUs and 128 GB RAM. The administrator notices that the VM's performance during peak hours is poor, with high disk latency and occasional disconnects. The cluster has 4 hosts, each with 10 cores (HT enabled) and 256 GB RAM. vSAN is configured with a hybrid disk group (SSD cache, HDD capacity) per host. The VM's storage policy is set to 'Performance' with RAID-1 mirroring (2 copies). The administrator runs esxtop and sees high %DAVG (device average latency) for the VM's vmdk. The observed latency averages 30 ms, but spikes to 100 ms. The host where the VM is running has relatively low CPU and memory usage, and the vSAN cache is not full. Which of the following is the most likely root cause and recommended solution?

Accepted Answer

Cause: vSAN disk group has a single SSD cache leading to high latency during heavy writes. Solution: Convert to all-flash vSAN.. Option C is correct. The high spike latency suggests that the SSD cache is being overwhelmed during write bursts. All-flash vSAN eliminates the HDD tier bottleneck. Option A is wrong; the cache is not full, so adding capacity won't help write bursts; the issue is write buffer exhaustion. Option B is wrong; memory ballooning would cause swapping but not high device latency. Option D is wrong; contention is not from multiple VMs sharing the disk group, as vSAN distributes objects.

Answer

Cause: vSAN cache is unable to handle the write burst. Solution: Add more cache capacity by using larger SSDs.

Answer

Cause: The VM's memory ballooning is causing excessive swapping to vSAN, which is slow. Solution: Increase the VM's memory reservation.

Answer

Cause: vSAN is encountering disk contention due to multiple VMs sharing the same disk. Solution: Deploy a dedicated vSAN datastore for the customer.

Question 4

A company runs a critical application on a VM with 16 vCPUs and 128 GB RAM on an ESXi host that has 2 sockets (12 cores per socket, hyperthreading enabled) and 512 GB RAM. The application is known to scale well with multiple threads and memory bandwidth. Recently, a DRS migration moved the VM to a different host with the same CPU and memory configuration. After the migration, the application's performance dropped by 30%. The administrator checks vCenter and finds no other VMs on the destination host. esxtop shows the VM's CPU ready time is less than 1%, but the 'CPU cost' metric is high, and the 'Memory' section shows high values for 'Remote' memory accesses. What is the most likely cause of the performance drop?

Accepted Answer

The VM is spanning multiple NUMA nodes, causing remote memory access.. The high 'Remote' memory access indicates that the VM's vCPUs are spread across both NUMA nodes, causing remote memory access latency. Since the host has 2 NUMA nodes and the VM has 16 vCPUs, it likely uses both nodes. The 'CPU cost' metric reflects memory latency. Option C directly addresses this. Option A is unrelated. Option B would help but is not as direct as enabling NUMA affinity. Option D is not a supported option for huge pages.

Answer

The VM's virtual hardware version is not compatible with NUMA.

Answer

The VM's memory shares have been reduced after the migration.

Answer

Transparent Huge Pages are not enabled on the destination host.

Question 5

A vSphere cluster with 3 ESXi hosts (each with 2 sockets, 8 cores per socket, hyperthreading enabled, and 256 GB RAM) runs a set of web server VMs. The cluster is configured with DRS enabled and a migration threshold of 3 (conservative). The administrator notices that one host has consistently high CPU ready time (average 15%) while the other two hosts have ready time below 2%. The host with high ready time has 10 VMs, while the others have 6 each. CPU utilization on the busy host is 80%, while on the other hosts it is 40%. What should the administrator do to improve the situation with minimal disruption?

Accepted Answer

Increase the DRS migration threshold to a more aggressive value (e.g., 4 or 5).. The cluster is unbalanced because DRS is not migrating VMs aggressively enough. Increasing the DRS migration threshold to a more aggressive level will allow DRS to move VMs from the overloaded host to the underutilized hosts. Option D is the best immediate step. Option A would increase overhead and is not best practice. Option B would be effective but requires manual intervention and may not be the simplest. Option C would add capacity but is a longer-term solution.

Answer

Disable Hyper-Threading on all hosts to reduce vCPU contention.

Answer

Manually migrate some VMs from the overloaded host to the other hosts using vMotion.

Answer

Add a fourth host to the cluster.

Question 6

A vSphere administrator is implementing Lockdown Mode on an ESXi host that hosts critical VMs for a healthcare application. After enabling Normal Lockdown Mode, the administrator tests that vCenter can still manage the host, but the local DCUI root account is disabled. Later, a network outage occurs, causing vCenter to become unreachable. The administrator needs to access the host directly via DCUI to perform emergency troubleshooting. The host's DCUI is still running, but the local root account is disabled due to Lockdown Mode. What should the administrator have configured to ensure DCUI access during such an outage?

Accepted Answer

Configure the DCUI access list with specific users or groups before enabling Lockdown Mode.. Option A is correct. Normal Lockdown Mode allows you to configure a DCUI access list of users (from the host's local authentication or AD) who can log in via DCUI even when Lockdown Mode is active. Option B is wrong because Strict Lockdown Mode disables all local accounts and DCUI entirely. Option C is wrong because disabling Lockdown Mode would require prior vCenter access. Option D is wrong because the vSphere Web Client is not available during an outage.

Answer

Use the vSphere Web Client to add the host as an exception before the outage.

Answer

Enable Strict Lockdown Mode to allow vCenter access exclusively.

Answer

Disable Lockdown Mode only during the maintenance window.

Question 7

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

Accepted Answer

The VM is fully accessible because it still has one replica and the witness.. With FTT=1, the object has 2 replicas + 1 witness. The surviving replica and witness are sufficient to maintain read/write access. The VM remains fully accessible despite losing one replica. Option B is incorrect because vSAN can rebuild on another host if available. Option D is incorrect because the witness is metadata, not data.

Answer

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

Answer

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

Answer

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

Question 8

A company uses vSphere 8 with a vSAN cluster consisting of 4 ESXi hosts. Each host has a single disk group with one 400 GB NVMe cache SSD and two 2 TB capacity SSDs. The vSAN cluster is used to host a mix of production VMs and test VMs. During peak business hours, the vSAN performance service shows high write latency (over 30 ms) for several production VMs, while test VMs are not affected. The administrator examines the vSAN performance charts and notices that the disk groups are not balanced: one disk group shows over 80% used capacity and high congestion, while the others are below 40%. The administrator wants to improve performance without adding new hardware or changing the storage policy. The vSAN health service reports no errors. Which action should the administrator take first?

Accepted Answer

Enable vSAN proactive rebalance.. Enabling vSAN proactive rebalance (A) automatically rebalances data across disk groups based on capacity and performance, which can alleviate congestion on the overutilized disk group. Option B is not a supported practice as manual evacuation is not recommended. Option C may not be feasible without additional components. Option D does not address the imbalance and could increase overhead.

Answer

Manually evacuate data from the most utilized disk group.

Answer

Increase the number of disk groups on the busiest hosts.

Answer

Change the storage policy to use RAID-5 erasure coding to reduce capacity overhead.

Question 9

A company has a vSphere cluster with 8 ESXi 7.0 U3 hosts managed by vCenter Server 7.0 U3. The administrator wants to upgrade the cluster to ESXi 8.0 U1 using vLCM. The administrator has already upgraded the vCenter Server to 8.0 U1 and enabled vLCM on the cluster. The desired image is set to ESXi 8.0 U1 with no additional VIBs. However, when attempting to remediate, the first host fails with error: 'Failed to remediate host: The host does not support the selected image'. The other hosts are still pending. The administrator checks the host hardware and confirms it is on the HCL for ESXi 8.0. What is the most likely cause?

Accepted Answer

The host firmware is not compatible with the desired image and HSM is not configured.. Option A is correct because the error 'The host does not support the selected image' typically indicates a hardware compatibility issue that vLCM cannot resolve without Hardware Support Manager (HSM) configured. Even if the host is on the HCL, the firmware version may not meet the requirements for ESXi 8.0 U1, and vLCM uses HSM to validate and remediate firmware as part of the image compliance process. Without HSM, vLCM cannot ensure the firmware is compatible, leading to the remediation failure.

Answer

The host was not put into maintenance mode before remediation.

Answer

The host was already upgraded to ESXi 8.0 U1, causing a conflict.

Answer

The vCenter Server version is not compatible with the host.

Question 10

A multinational corporation runs a vSphere environment with 100 ESXi hosts managed by a single vCenter Server. The security team mandates that all virtual machine disks (VMDKs) must be encrypted at rest. The administrator enables vSphere Virtual Machine Encryption and creates a Key Management Server (KMS) cluster. After encrypting a test VM, the VM powers on successfully, but the administrator notices that the VM's configuration files (VMX, NVRAM) are not encrypted. The security policy requires that all VM files, including configuration files, be encrypted. The administrator checks the VM storage policy and sees that the policy is set to 'VM Encryption Policy' with 'Disk Encryption' enabled. What should the administrator do to ensure the entire VM is encrypted?

Accepted Answer

Modify the VM storage policy to include encryption of VM home files. The VM storage policy 'VM Encryption Policy' with only 'Disk Encryption' enabled encrypts VMDK files but not the VM configuration files (VMX, NVRAM, logs, etc.). To encrypt all VM files, the storage policy must include the 'Encrypt VM home files' option, which applies encryption to the entire VM home directory on the datastore. This ensures compliance with the security mandate for full VM encryption at rest.

Answer

Enable encryption on the datastore where the VM resides

Answer

Add a second KMS cluster for redundancy

Answer

Enable vSphere Host Encryption on each ESXi host

Question 11

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?

Accepted Answer

Perform a storage rescan on the affected host.. 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.

Answer

Reboot the affected ESXi host.

Answer

Change the multipathing policy on the affected host to Round Robin.

Answer

Unmount the datastore from the affected host and then remount it.

Question 12

A company runs a four-node vSphere 7 cluster with all-flash storage and 25GbE networking. The cluster hosts 50 VMs, including a critical database VM with 16 vCPUs and 64 GB memory. The database VM's performance has degraded over the past week. vCenter reports high CPU ready time (average 15%) for the database VM, while other VMs show less than 2%. CPU utilization on the host is 70%. The database VM is configured with CPU affinity pinned to cores 0-15 on a dual-socket host with 16 cores per socket (32 total). The administrator also notices that the database VM's CPU co-stop counter is high. What should the administrator do to improve performance?

Accepted Answer

Remove the CPU affinity setting for the database VM.. The high CPU ready time (15%) and elevated co-stop counter indicate that the database VM is suffering from contention due to CPU affinity pinning to cores 0-15. On a dual-socket host with 16 cores per socket, pinning to cores 0-15 restricts the VM to a single NUMA node, preventing the scheduler from load-balancing across both sockets. Removing the affinity allows the ESXi scheduler to distribute vCPUs across all 32 cores, reducing co-scheduling overhead and ready time.

Answer

Migrate the database VM to a host with fewer VMs.

Answer

Enable CPU hot-add for the database VM.

Answer

Increase the number of vCPUs for the database VM to 32.

Question 13

A global company manages multiple vSphere clusters across different data centers. They have a standard operating procedure to upgrade ESXi hosts every two years. The vSphere administrator is planning the upgrade of a critical production cluster that runs a mix of VMs, including some latency-sensitive applications. The cluster consists of 20 ESXi 7.0 Update 3 hosts managed by vLCM with a single image. The target is ESXi 8.0 Update 1. The administrator wants to minimize downtime and ensure rollback capability. The company has a hardware support manager (HSM) integrated with vLCM. After staging the new image, the administrator remediates the cluster. During the remediation of the first host, the host fails to reboot after applying the image and becomes unresponsive. What is the most likely cause of this failure?

Accepted Answer

The hardware support manager (HSM) did not deploy the correct firmware version for the host.. The most likely cause is that the hardware support manager (HSM) deployed an incorrect firmware version for the host during the vLCM remediation. vLCM integrates with HSM to automatically update firmware as part of the image-based lifecycle, and if the firmware is incompatible with ESXi 8.0 Update 1, the host can fail to reboot and become unresponsive. This is a known risk when upgrading across major ESXi versions, as hardware firmware requirements often change.

Answer

The vCenter Server version is not compatible with ESXi 8.0 Update 1.

Answer

The host was not placed in maintenance mode before remediation.

Answer

The vLCM single image is corrupted and was applied incorrectly.

Question 14

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?

Accepted Answer

Change the path selection policy to Round Robin on the ESXi host.. 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.

Answer

Add a vSphere Flash Read Cache to the VM.

Answer

Upgrade the Fibre Channel infrastructure to 16 Gbps.

Answer

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

Question 15

A large financial institution runs a vSphere 7.0 environment with 100 ESXi hosts and 2,000 VMs. The security team has identified that several VMs are vulnerable to a critical side-channel attack that requires disabling hyperthreading on the ESXi hosts. The administrator needs to implement a solution that minimizes performance impact while ensuring compliance. The environment uses DRS clusters with varying workloads: some VMs are CPU-intensive (financial modeling) and others are memory-bound (database servers). The administrator cannot afford to take hosts offline for maintenance during business hours. The change must be implemented within 48 hours. Which course of action should the administrator take?

Accepted Answer

Place each host in maintenance mode individually, disable hyperthreading in the host BIOS, reboot the host, and then move to the next host. Rebalance VMs after all hosts are updated.. Option B is correct because disabling hyperthreading to mitigate side-channel attacks (e.g., L1TF or MDS) requires a host BIOS change, which necessitates a reboot. The only supported method in vSphere 7.0 is to place each host into maintenance mode, change the BIOS setting, reboot, and then repeat for all hosts. This approach minimizes performance impact by allowing VMs to be migrated via vMotion and avoids simultaneous downtime, meeting the 48-hour requirement without taking all hosts offline during business hours.

Answer

Use a vSphere DRS rule to disable hyperthreading for all VMs in the cluster, avoiding the need to modify host BIOS.

Answer

Delay the change and schedule a maintenance window for the next month when business impact is lower.

Answer

Disable hyperthreading on all hosts simultaneously using a vSphere Cluster feature, then reboot all hosts at once during off-peak hours.