VCP-DCV Practice Test 11 — 15 Questions

Question 1

An administrator has configured Storage DRS on a cluster of datastores. The cluster includes both NFS and VMFS datastores. The administrator notices that Storage DRS recommendations are not being generated for some datastores. What is the most likely cause?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

NFS datastores are not supported by Storage DRS. Storage DRS does not support NFS datastores unless they are on a NAS array that supports VAAI for storage offload operations. In this scenario, the cluster includes both NFS and VMFS datastores, but Storage DRS recommendations are not generated for some datastores. The most likely cause is that those datastores are NFS and do not meet the requirements for Storage DRS. Option B (space utilization below threshold) is incorrect because Storage DRS would still generate recommendations when space utilization is below the threshold, just perhaps less frequently. Option C (datastores part of a vSAN cluster) is incorrect because vSAN uses its own distributed resource scheduler, not Storage DRS, and would not be included in the cluster. Option D (I/O metrics not enabled) is incorrect because if I/O metrics were not enabled, recommendations based on I/O latency would not be generated, but recommendations based on space utilization would still be generated; however, the question states recommendations are not being generated for some datastores, which points to the NFS incompatibility.

Answer

The datastore space utilization is below the threshold

Answer

The datastores are part of a vSAN cluster

Answer

I/O metrics are not enabled for the Storage DRS cluster

Question 2

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 memory is being accessed from a NUMA node different from the one where the vCPUs are running. This occurs when a large VM spans multiple NUMA nodes. In this case, the VM has 16 vCPUs and the host has 2 NUMA nodes (each with 12 cores and hyperthreading). After DRS migration, the VM may be placed across both NUMA nodes, causing remote memory accesses and increasing the 'CPU cost' metric. This explains the 30% performance drop. Option B correctly identifies this cause. Option A (virtual hardware version) is not directly related. Option C (memory shares) affects prioritization, not remote access. Option D (Transparent Huge Pages) could affect performance but is not indicated by the metrics.

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 3

An organization wants to migrate a VM from one vCenter Server to another without shutting down the VM. Both vCenter Servers are in Enhanced Linked Mode. Which migration method should the administrator use?

Accepted Answer

Cross-vCenter vMotion. Cross-vCenter vMotion (option B) is the correct method because it allows a live, zero-downtime migration of a running VM between vCenter Server instances, even when both are in Enhanced Linked Mode. This feature uses the vMotion protocol to transfer memory and execution state across vCenter boundaries without requiring shared storage, as long as the source and destination hosts are in the same vCenter Single Sign-On domain and meet compatibility requirements.

Answer

Cold migration

Answer

Storage vMotion

Answer

Export the VM as OVF and import it to the other vCenter

Question 4

Sequence the steps to configure a VM to use a static IP address via vSphere's customization specification.

Accepted Answer

Initiate customization, then select or create a customization specification, then configure the IP settings within the specification, then apply the customization, then power on the VM.. The correct sequence ensures that the VM receives the static IP configuration during the first boot after customization. Initiating the customization opens the wizard, selecting or creating a spec defines the settings, configuring IP within the spec sets the static address, applying saves the configuration, and powering on triggers the OS customization process.

Answer

Initiate customization, then configure IP settings, then select or create a customization specification, then apply, then power on.

Answer

Power on the VM, then initiate customization, then select or create a specification, then configure IP, then apply.

Answer

Initiate customization, then select or create a specification, then apply, then configure IP, then power on.

Question 5

A financial services company runs a critical trading application on a vSphere 7 cluster with four ESXi hosts. Each host has 512 GB RAM and dual 16-core CPUs. The application is extremely latency-sensitive and runs in a single VM named TRADER-01. The VM currently has 16 vCPUs and 128 GB RAM assigned. The cluster uses vSphere HA and DRS in fully automated mode with aggressive migration threshold. Recently, the application experienced occasional latency spikes. Monitoring shows that these spikes correlate with DRS migrations of other VMs on the same host as TRADER-01. The administrator needs to eliminate these latency spikes without sacrificing application performance. The company has budget constraints and cannot add new hardware. Which action should the administrator take?

Accepted Answer

Set the DRS migration threshold to conservative (level 1) to minimize vmotion events. Setting the DRS migration threshold to conservative (level 1) reduces the frequency of vMotion migrations by requiring a higher imbalance score before DRS recommends or executes a migration. This directly addresses the latency spikes caused by DRS migrations of other VMs on the same host as TRADER-01, as fewer vMotion events will occur, while still allowing DRS to balance the cluster when necessary. The aggressive threshold was triggering migrations too readily, causing resource contention and latency for the latency-sensitive VM.

Answer

Disable DRS on the cluster and rely solely on vSphere HA

Answer

Create a DRS rule to keep TRADER-01 on a single host and set the host as a preferred host for the VM

Answer

Reduce the vCPU count of TRADER-01 to 8 to reduce CPU schedul time

Question 6

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?

Accepted Answer

The virtual disk is thin-provisioned, so only the actual written blocks consume space on the datastore.. 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.

Answer

The virtual disk needs to be defragmented to reclaim space.

Answer

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

Answer

The virtual disk is thick-provisioned lazy zeroed, which delays allocation.

Question 7

An administrator is creating a new vSphere Standard Switch on an ESXi host. The host has two physical NICs: vmnic0 and vmnic1. The administrator wants to use vmnic0 for VM traffic and vmnic1 for management traffic. How should the administrator configure the switch?

Accepted Answer

Create two standard switches: one with vmnic0 and a VM port group, and another with vmnic1 and a VMkernel port group.. The requirement is to use separate physical NICs for different traffic types (VM traffic on vmnic0 and management traffic on vmnic1). In vSphere, a standard switch is a per-host virtual switch that connects virtual machines and VMkernel interfaces to physical NICs. To isolate traffic at the physical NIC level, you must create two distinct standard switches: one with vmnic0 and a VM port group for VM traffic, and another with vmnic1 and a VMkernel port group for management traffic. This ensures that management traffic never traverses vmnic0 and VM traffic never traverses vmnic1, providing physical separation and avoiding contention.

Answer

Create one standard switch with vmnic0 only and use VLANs for separation.

Answer

Create one standard switch with both vmnics and separate port groups for VM and VMkernel.

Answer

Create a vSphere Distributed Switch with both vmnics.

Question 8

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

Accepted Answer

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

Answer

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.

Answer

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.

Answer

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.

Question 9

An administrator notices that after applying a baseline to hosts, some hosts fail to reboot properly. What is the most likely cause?

Accepted Answer

Incompatible hardware. The most likely cause is incompatible hardware (Option D). Applying a baseline that includes drivers or firmware updates can cause boot failures if the hardware is not supported by the new components. Network misconfiguration (A) might cause connectivity issues but not typically reboot failures. Incorrect BIOS settings (B) could lead to boot issues, but they are less likely to be caused by applying a baseline. Insufficient memory (C) would typically result in performance issues or crashes, not specifically reboot failures.

Answer

Network misconfiguration

Answer

Incorrect BIOS settings

Answer

Insufficient memory

Question 10

A company has a vSphere 7 cluster with 6 hosts, each with 2 sockets (16 cores per socket, hyperthreading enabled) and 1 TB RAM. The cluster uses DRS with a migration threshold of 4 (moderate). A single VM runs a latency-sensitive trading platform with 12 vCPUs and 256 GB RAM. During market hours, the administrator notices that the VM's CPU ready time spikes to 15%, and the application reports high response times. The administrator runs esxtop on the host and sees the following: %RDY for the VM is 15%, %CSTP is low, and the host's overall CPU utilization is 60%. The VM is on a host that also has 5 other VMs with smaller resource footprints. The administrator wants to minimize disruption while improving performance. Which action should the administrator take first?

Accepted Answer

Configure the VM's NUMA node preference to use a single NUMA node.. Trading VMs with high vCPU counts often benefit from NUMA-awareness. The host has 2 NUMA nodes (one per socket). With 12 vCPUs, the VM likely spans both nodes, causing remote memory access. By setting the VM to prefer one NUMA node (or limiting vCPUs to 8), performance improves. Option D is the most effective immediate step. Option A may cause excessive vMotion. Option B might not address the root cause. Option C would reduce parallelism and might not help if the application is multithreaded.

Answer

Manually migrate the VM to a host with fewer running VMs.

Answer

Increase the VM's CPU reservations to guarantee CPU cycles.

Answer

Reduce the VM's vCPU count from 12 to 8.

Question 11

A company with a small vSphere environment has a single vCenter Server managing three ESXi hosts. The hosts are running ESXi 6.7 and the company wants to upgrade to ESXi 7.0. The vCenter Server is version 6.7 and runs on Windows. The administrator plans to use vSphere Update Manager (VUM) for the upgrade. The administrator attaches a baseline of ESXi 7.0 to the cluster and starts remediation. The remediation fails on all hosts with an error stating that the upgrade cannot be performed from a host that is part of a cluster. What is the likely issue?

Accepted Answer

The vCenter Server must be upgraded to version 7.0 before upgrading the ESXi hosts.. VSphere Update Manager (VUM) requires the vCenter Server version to be equal to or higher than the ESXi version being applied. Since the vCenter Server is still running version 6.7, it cannot orchestrate an upgrade to ESXi 7.0. The vCenter Server must first be upgraded to version 7.0 before any ESXi 7.0 baseline can be attached and remediated against the hosts.

Answer

The ESXi hosts are part of a cluster; VUM cannot remediate clustered hosts.

Answer

vSphere DRS is not enabled on the cluster.

Answer

The hosts are not in maintenance mode; put them in maintenance mode and retry.

Question 12

A financial institution operates a vSphere 7 environment with 1,000 VMs, many of which process sensitive data. The security team mandates VM encryption at rest using a Key Management Server (KMS) cluster. The administrator has configured the KMS cluster as a key provider in vCenter and enabled encryption on a test VM, which works correctly. However, after adding a new ESXi host to the cluster and attempting to power on a previously encrypted VM, the VM fails to start with the error: 'Key provider unavailable for host <hostname>.' The new host is correctly licensed for encryption and has network connectivity to the KMS. The administrator verifies that the KMS cluster is operational and that other hosts can power on encrypted VMs. What is the most likely cause of this issue?

Accepted Answer

The ESXi host has not been added to the Key Provider's trust list or KMS configuration.. When a new ESXi host is added to the cluster, it must be added to the Key Provider's trust list or the KMS must be configured to trust the host's certificate. Without this, the host cannot retrieve keys from the KMS, even though it has network connectivity and is properly licensed. Option B is incorrect: a firewall issue would typically cause a connection timeout or refusal error, not a 'key provider unavailable' error. Option C is incorrect because the host is verified to have the correct encryption license. Option D is incorrect because the error indicates the KMS is not available to that host, not a policy mismatch.

Answer

The ESXi host's firewall is blocking outbound connections to the KMS cluster.

Answer

The ESXi host does not have the required encryption feature license.

Answer

The VM's encryption policy is set to 'vSphere Native Key Provider' instead of 'KMS'.

Question 13

Which TWO actions are effective in reducing CPU ready time on a vSphere host that is heavily overcommitted on CPU? (Choose two.)

Accepted Answer

Add more hosts to the cluster.. Reducing the number of vCPUs on over-provisioned VMs directly decreases scheduling contention. Adding more hosts to the cluster increases the pool of physical CPUs, reducing overcommitment. Increasing vCPUs worsens the issue. Enabling hyperthreading does not reduce ready time if the host is already CPU-bound. Configuring CPU affinity restricts scheduling and can increase ready time.

Answer

Enable hyperthreading on the host CPUs.

Answer

Increase the number of vCPUs on VMs with high ready times.

Answer

Configure CPU affinity to pin vCPUs to specific pCPUs.

Question 14

Which vSphere component is responsible for managing the lifecycle of ESXi hosts, including patching and upgrading?

Accepted Answer

vSphere Lifecycle Manager. vSphere Lifecycle Manager (vLCM) is the correct component because it is specifically designed to manage the lifecycle of ESXi hosts, including patching, upgrading, and firmware/driver updates. It uses desired-state management to ensure hosts conform to a specified image or baseline, automating the entire update process across clusters.

Answer

Host Profiles

Answer

Auto Deploy

Answer

vSphere Distributed Resource Scheduler

Question 15

An administrator needs to upgrade the ESXi hosts in a cluster to version 7.0 U3. The administrator uses vSphere Lifecycle Manager (vLCM) with a cluster image. After staging the image on one host, the administrator attempts to remediate that host but gets an error that the host is not compliant. Which is the most likely reason?

Accepted Answer

The host is not in maintenance mode. When using vLCM with a cluster image, the host must be in maintenance mode before remediation can proceed. vLCM orchestrates the full software stack update, which requires the host to be evacuated of all running VMs to avoid disruption. The error 'host is not compliant' in this context indicates that the host is not in the required state to begin the remediation process, not that the image itself is invalid.

Answer

The ESXi version difference between the image and the host is too large

Answer

The host does not have the required firmware version

Answer

The vCenter Server service needs to be restarted