VMware · Free Practice Questions · Last reviewed May 2026
36real exam-style questions organised by domain, each with the correct answer highlighted and a plain-English explanation of why it's right — and why the others are wrong.
17% of exam · 6 sample questions below
A vSphere administrator is planning to upgrade a vSphere 7.0 U2 cluster to vSphere 8.0 U1. The cluster is managed by a vCenter Server 7.0 U2. The administrator wants to use vSphere Lifecycle Manager (vLCM) to manage the upgrade. What must the administrator do first?
Enable vLCM on the cluster and set the desired image to ESXi 8.0 U1.
Upgrade vCenter Server to version 8.0 U1.
vLCM image management requires the managing vCenter Server to run the same or newer version than the target ESXi release. Upgrading vCenter Server to 8.0 U1 first satisfies that dependency, enabling the cluster upgrade to 8.0 U1.
Upgrade one ESXi host to 8.0 U1 manually to test compatibility.
Create a baseline for ESXi 8.0 U1 in vLCM.
An administrator needs to apply a security patch to a vLCM-managed cluster. The patch is available as an ESXi image in the vSphere Lifecycle Manager depot. What is the correct procedure?
Create a new desired state image with the patch, validate, and remediate the cluster.
vLCM manages hosts through a desired-state image rather than baselines. Adding the patch means editing the image to include the updated ESXi base image, validating it against the cluster, then remediating so each host converges to that declared state, satisfying the depot-sourced patch requirement.
Attach a patch baseline to the cluster and remediate.
Export the current image, add the patch, and import it to the cluster.
Use Quick Boot to apply the patch to each host individually.
A company has a vLCM-managed cluster with a desired image that includes ESXi 8.0 U1 and multiple VIBs. After remediating, one host fails with an error: 'Failed to retrieve VIBs from depot'. What is the most likely cause?
The cluster has a baseline attached that conflicts with the desired image.
The image validation failed due to incompatible VIBs.
The host firmware is not compatible with the selected VIBs.
The vCenter Server does not have internet access to the VMware depot.
The error indicates vLCM cannot pull VIB payloads from the depot. If the vCenter Server lacks internet access to the VMware depot and no local depot or proxy is configured, retrieval fails during remediation, matching the stem's post-remediation host error.
An administrator wants to use vLCM to manage a cluster with 10 ESXi hosts. After enabling vLCM, what is the first step to ensure all hosts are running the same desired image?
Define a desired state image for the cluster.
Defining a desired-state image establishes the cluster's target software specification, which vLCM then remediates each host against. This directly satisfies the stem's requirement to bring all ten ESXi hosts to a consistent image, since vLCM compares each host's current state to the image and flags drift for remediation.
Remediate the cluster immediately to apply the default image.
Place all hosts into maintenance mode.
Create a host upgrade baseline and attach it to the cluster.
A vSphere administrator is managing a cluster with vLCM and receives a notification that a new ESXi patch is available. The administrator updates the desired image to include the patch and attempts to remediate, but the remediation fails with 'Cannot retrieve software depots'. What could be the issue?
The software depot URL in the image is incorrect or unreachable.
An unreachable or malformed depot URL prevents vLCM from downloading the patch payloads referenced by the desired image, so remediation aborts before any host enters maintenance mode. The error text names the depot retrieval stage specifically, making connectivity or URL accuracy the constraint that must be satisfied first.
The hosts cannot communicate with the vCenter Server.
The image validation failed due to missing dependencies.
The desired image was not saved after adding the patch.
An administrator is planning to migrate from legacy baselines to vLCM for a cluster. Which TWO statements are true about vLCM?
vLCM allows individual host remediation for flexibility.
vLCM uses a desired state image to manage host configurations.
vLCM replaces per-host baselines with a single desired-state image declared for the whole cluster. Hosts are remediated to match that image, so this statement accurately describes vLCM's core model and satisfies the stem's migration-planning question.
vLCM supports different images for different hosts in the same cluster.
vLCM can integrate with Hardware Support Manager for firmware updates.
vLCM pairs with a Hardware Support Manager plugin, letting the desired-state image include firmware components alongside ESXi and VIBs. Remediation then updates host firmware through the vendor's HSM, satisfying the stem's question about vLCM capabilities during migration planning.
vLCM uses baseline groups to apply updates.
Want more vSphere Lifecycle Management practice?
Practice this domain17% of exam · 6 sample questions below
An administrator needs to provide redundancy for VM traffic across multiple physical NICs on a vSphere Standard Switch. Which NIC teaming policy should be used to ensure fault tolerance without load balancing?
Route based on IP hash
Route based on originating virtual port
Use explicit failover order (Active/Standby)
Explicit failover order with Active/Standby keeps one NIC passing traffic and holds the others as standby, providing fault tolerance without distributing load. Other policies such as route based on originating port ID actively load balance, which the requirement excludes.
Route based on source MAC hash
A vSphere administrator is designing a network for a cluster of ESXi hosts. Each host has four 10GbE uplinks. The cluster will host mission-critical VMs that require maximum throughput and redundancy. The administrator plans to use Network I/O Control (NIOC) and a vSphere Distributed Switch (vDS). Which configuration best ensures consistent network performance for all VMs?
Configure a single vDS with all four uplinks, enable NIOC, and set shares and reservations for each traffic type.
A single vDS pooling all four uplinks with NIOC shares and reservations guarantees bandwidth allocation per traffic type, satisfying the consistent-performance and redundancy requirement. Reservations protect mission-critical VM throughput during contention across the 10GbE uplinks.
Configure a single vDS with all four uplinks and enable NetFlow for monitoring.
Create two separate vDS, each with two uplinks, and separate VM traffic from VMkernel traffic.
Configure a single vDS with all four uplinks and use Route based on IP hash teaming.
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?
Create one standard switch with vmnic0 only and use VLANs for separation.
Create one standard switch with both vmnics and separate port groups for VM and VMkernel.
Create two standard switches: one with vmnic0 and a VM port group, and another with vmnic1 and a VMkernel port group.
Separating vmnic0 and vmnic1 onto distinct standard switches gives each traffic type a dedicated uplink, satisfying the requirement that VM traffic and management traffic never share a physical NIC. The VM port group binds to vmnic0, while the VMkernel port group on the second switch carries management traffic over vmnic1.
Create a vSphere Distributed Switch with both vmnics.
A VM on a vSphere Distributed Switch is experiencing intermittent connectivity drops. The administrator checks the vDS health check and sees no errors. The physical switch logs show no issues. The VM is on a port group with VLAN 200. The administrator runs a ping from the VM to the gateway and notices packet loss. What should the administrator investigate next?
Verify the VMkernel port configuration
Check the VM's firewall settings
Check DNS resolution for the gateway
Review the NIC teaming failover order and ensure active uplinks are up.
Intermittent loss with clean health checks and switch logs points to uplink pathing. If the active uplink in the teaming failover order is down, traffic drops until failover, matching the observed packet loss on VLAN 200.
An administrator is reviewing the network configuration of a standard switch. The exhibit shows the current settings for a port group. Which change would improve load distribution for VM traffic?
Change the VLAN ID to 100.
Enable failover on the port group.
Change the load balancing policy to Route based on IP hash.
Route based on IP hash distributes traffic across physical uplinks by hashing source and destination IP addresses, spreading VM flows over multiple NICs. The default port-based policy pins each VM to one uplink, so this change directly improves load distribution for the port group's traffic.
Set one NIC as active and the other as standby.
Which THREE are valid methods to isolate and secure management traffic on a vSphere Distributed Switch? (Choose three.)
Enable Route based on IP hash on the management port group.
Assign a specific VLAN ID to the management port group.
VLANs provide isolation.
Use Private VLANs on the management port group.
Configure the ESXi firewall to restrict management access.
Firewall rules control access.
Create a dedicated VMkernel port group for management.
Dedicated port groups isolate traffic.
Want more Configure and Manage vSphere Networking practice?
Practice this domain17% of exam · 6 sample questions below
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?
FC with Fixed path policy.
FC with Most Recently Used (MRU) path policy.
iSCSI with Round Robin path policy.
FC with Round Robin path policy.
Fibre Channel provides dedicated, lossless transport with lower latency and higher sustained IOPS than iSCSI over Ethernet. Round Robin spreads I/O across all active paths, maximising throughput and balancing load, which satisfies the database's low-latency, high-IOPS requirement.
Which storage feature in vSphere allows a VM to be migrated from one datastore to another without any downtime?
vMotion
Distributed Resource Scheduler (DRS)
Storage DRS
Storage vMotion
Storage vMotion relocates a virtual machine's files between datastores while the VM remains powered on and running, satisfying the no-downtime constraint. Compute vMotion moves the VM between hosts instead, and neither cold nor suspended migration avoids an outage.
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?
The virtual disk needs to be defragmented to reclaim space.
The VM has a snapshot that is consolidating, reducing storage usage.
The virtual disk is thick-provisioned lazy zeroed, which delays allocation.
The virtual disk is thin-provisioned, so only the actual written blocks consume space on the datastore.
Thin provisioning allocates datastore blocks only when the guest actually writes data, so consumed capacity reflects written blocks rather than the guest-reported 1.5 TB. The 800 GB datastore figure is therefore expected, not an error, and matches the thin disk's on-demand allocation behaviour.
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?
The CHAP secret is not set on the failing hosts.
The storage array requires mutual CHAP, but the failing hosts are configured for one-way CHAP.
Mutual CHAP requires authentication in both directions: the host authenticates to the target and the target authenticates to the host. The working hosts supply both sets of credentials, whereas one-way CHAP sends only the initiator's credentials, so the array's reverse challenge fails.
The iSCSI target name is incorrect on the failing hosts.
The storage array is configured to use only one-way CHAP.
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?
Change the path selection policy to Round Robin on the ESXi host.
Round Robin spreads I/O across all active Fibre Channel paths, using the array's available bandwidth instead of one path. With Fixed policy, a single path bottlenecks at 15–50 ms latency, so this change is free and immediate.
Add a vSphere Flash Read Cache to the VM.
Upgrade the Fibre Channel infrastructure to 16 Gbps.
Convert the virtual disk to thin provisioning to reduce I/O.
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?
Perform a storage rescan on the affected host.
A rescan refreshes the affected host's storage adapter and VMFS volume inventory, re-establishing the datastore path without touching the host that still has working access. Because the SAN LUN is online and visible, rescanning is the non-disruptive remedy.
Reboot the affected ESXi host.
Change the multipathing policy on the affected host to Round Robin.
Unmount the datastore from the affected host and then remount it.
Want more Configure and Manage vSphere Storage practice?
Practice this domain17% of exam · 6 sample questions below
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?
Cold migration
Cross-vCenter vMotion
Cross-vCenter vMotion moves a running VM's compute and storage between vCenter Servers while it stays powered on, with no downtime. Enhanced Linked Mode provides the shared SSO and inventory visibility this migration requires across both vCenters.
Storage vMotion
Export the VM as OVF and import it to the other vCenter
An administrator is troubleshooting a performance issue where a VM is not receiving the expected CPU resources. The VM is a member of a resource pool with a CPU Shares value of 2000. The host has two other resource pools: one with 1000 shares and another with 500 shares. All resource pools are competing for CPU. The VM's reservation is set to 2 GHz, and the host has 8 GHz available. What is the minimum CPU allocation the VM is guaranteed?
4 GHz (based on share ratio)
2 GHz
A reservation is a guaranteed minimum, not a share-based entitlement. The VM's 2 GHz reservation is fully covered by the host's 8 GHz capacity, so regardless of the competing resource pools' shares, the VM is guaranteed at least 2 GHz.
8 GHz (all host CPU)
0 GHz (no guarantee without reservation)
Which vSphere component is responsible for managing the lifecycle of ESXi hosts, including patching and upgrading?
vSphere Lifecycle Manager
vSphere Lifecycle Manager manages ESXi host remediation through desired-state images, applying patches and upgrades across clusters. It satisfies the stem's lifecycle requirement by basing host compliance on a single image, unlike baselines or standalone update tools, and integrates directly with vCenter Server for orchestrated remediation.
Host Profiles
Auto Deploy
vSphere Distributed Resource Scheduler
An administrator is configuring a new iSCSI storage array for a vSphere cluster. The array supports multiple iSCSI targets. What is the recommended best practice for multipathing to ensure high availability and load balancing?
Use the management VMkernel port for iSCSI traffic to simplify configuration.
Create multiple VMkernel ports for iSCSI, each bound to a separate physical NIC, and configure multiple iSCSI targets.
Multipathing requires multiple VMkernel ports, each bound to a distinct physical NIC, so vSphere can present separate paths to the array. Configuring multiple iSCSI targets across those paths enables both failover and load balancing, satisfying the high-availability constraint.
Configure a single physical NIC with multiple VLANs for iSCSI traffic.
Use a single VMkernel port for iSCSI and assign multiple IP addresses to it.
Which THREE components are required to implement vSphere with Tanzu (Workload Management)? (Choose three.)
A separate vCenter Server for Tanzu management
A vSphere Distributed Switch (vDS)
A vSphere Distributed Switch provides the port groups and uplinks that Supervisor control plane and Tanzu Kubernetes Grid clusters attach to, satisfying the networking prerequisite for Workload Management. Without a vDS, the Supervisor cannot present its Kubernetes API endpoint or route pod traffic, so deployment fails.
NSX-T Data Center for networking
A vSphere cluster with vSphere DRS enabled
Workload Management requires a vSphere cluster with vSphere DRS enabled, because the Supervisor Control Plane VMs and Tanzu Kubernetes Grid clusters rely on DRS for initial placement and ongoing load balancing across the cluster's ESXi hosts.
Shared storage accessible by all ESXi hosts in the cluster
Shared storage accessible by every ESXi host in the cluster is mandatory, since Supervisor Control Plane VMs and Tanzu Kubernetes Grid nodes must remain reachable and be able to migrate between hosts via vSphere DRS and vMotion.
Which TWO of the following are characteristics of vSphere High Availability (HA) heartbeat networks? (Choose two.)
Datastore heartbeats can be used as a secondary heartbeat mechanism.
Datastore heartbeats provide a secondary mechanism when the management network fails, letting the master host distinguish a partitioned host from a genuinely failed one. This satisfies the stem's requirement for a valid HA heartbeat characteristic, since HA uses both management network and datastore heartbeats to confirm host state.
A separate physical network is required for HA heartbeats.
The management network is the primary heartbeat network.
The management network carries the primary HA heartbeat by default, so this satisfies the stem's requirement for a genuine HA heartbeat characteristic. Each host sends heartbeats over this network to the master, and datastore heartbeating only supplements it when the management network partitions.
The default isolation address is the vCenter Server IP address.
Heartbeats are sent over the VM network to avoid interference with management traffic.
Want more vSphere Architecture, Products and Solutions practice?
Practice this domainA vSphere environment uses Active Directory for authentication. The administrator notices that users from a specific AD group cannot log in to the vCenter Server, although other AD users can. The group is added to vCenter Server with the correct permissions. What is the most likely cause?
The users are not members of the vCenter Single Sign-On domain
The user accounts have expired passwords
The group is nested within another group
The domain of the group is not configured as an identity source in vCenter Single Sign-On
vCenter Single Sign-On only authenticates principals from identity sources it has been configured with. If that AD domain was never added as an identity source, its groups resolve to nothing, so members fail to log in despite correct vCenter permissions.
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?
Modify the VM storage policy to include encryption of VM home files
The VM storage policy's VM Encryption Policy encrypts only VMDKs by default; VM home files (VMX, NVRAM) require the separate 'Encrypt VM home files' setting. Enabling that component in the policy satisfies the mandate that configuration files be encrypted at rest.
Enable encryption on the datastore where the VM resides
Add a second KMS cluster for redundancy
Enable vSphere Host Encryption on each ESXi host
A vSphere administrator needs to ensure that all virtual machine disks are encrypted at rest. The environment uses a KMS cluster with multiple KMIP-compliant servers. The administrator has already configured a storage policy with encryption enabled. However, newly created VMs on a particular datastore still show unencrypted disks. What is the most likely cause?
The datastore is a vSAN datastore, which does not support VM-level encryption.
The KMS cluster must have at least two KMS servers to function correctly.
The datastore is formatted with VMFS6, which does not support encryption.
The storage policy with encryption is not assigned to the VMs or their home namespace.
Encryption is enforced through the VM storage policy, not the datastore itself. If that policy is not assigned to the VMs or their home namespace, their disks remain unencrypted despite the KMS cluster and policy existing.
An administrator is troubleshooting a failed attempt to add an ESXi host to a vCenter Server domain. The error message states: 'The host's certificate has been tampered with or is invalid.' What is the most likely cause?
The vCenter Server's account lockout policy has been triggered.
The ESXi host's SSH keys have been rotated.
The ESXi host's certificate has expired.
The ESXi host's certificate thumbprint does not match the thumbprint stored in vCenter Server.
vCenter stores the ESXi thumbprint captured at first connection; any mismatch, such as after a host certificate regeneration or reinstall, triggers the tampered-or-invalid error. The stored thumbprint no longer matches the host's presented certificate, blocking the add.
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?
Use a vSphere DRS rule to disable hyperthreading for all VMs in the cluster, avoiding the need to modify host BIOS.
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.
Hyperthreading is a BIOS setting, so disabling it requires a host reboot. Sequentially placing each host in maintenance mode lets DRS evacuate VMs to remaining hosts, avoiding downtime, then rebalancing after all 100 hosts are updated within the 48-hour window.
Delay the change and schedule a maintenance window for the next month when business impact is lower.
Disable hyperthreading on all hosts simultaneously using a vSphere Cluster feature, then reboot all hosts at once during off-peak hours.
A company is implementing vSphere 7.0 and wants to encrypt all vMotion traffic between ESXi hosts in a cluster. The cluster is not using any other encryption features. What is the minimum requirement to enable vMotion encryption?
A VM Encryption Key Management Server must be configured.
The ESXi hosts must be joined to an Active Directory domain.
The ESXi hosts must have a host profile applied with encryption enabled.
A host profile applied with encryption enabled is the minimum requirement because it ensures consistent encryption policy across the cluster, leveraging default certificate trust.
The cluster must be configured with Enhanced vMotion Compatibility (EVC).
Want more vSphere Security practice?
Practice this domain16% of exam · 6 sample questions below
A company's vSphere environment has multiple clusters with varying workloads. The operations team notices that one cluster consistently shows high CPU ready times on several hosts. Which action should be taken to address this performance issue?
Increase the memory allocation of VMs with high CPU ready times.
Increase the CPU reservation for VMs with high ready times.
Reduce the number of virtual CPUs assigned to VMs and consider adding more hosts.
High CPU ready indicates VMs are waiting for physical CPU cycles, so reducing vCPUs cuts scheduling contention and adding hosts increases available cores. This directly relieves the oversubscription driving the elevated ready times across that cluster's hosts.
Enable Storage DRS to balance storage I/O load.
A vSphere administrator is troubleshooting a VM that is experiencing excessive disk latency. The VM is on a datastore accessed via NFS over a 1GbE network. The host shows high network utilization. Which action should be taken to improve performance?
Enable Storage I/O Control on the datastore.
Convert the datastore from NFS to VMFS.
Increase the memory reservation for the VM.
Upgrade the network link to 10GbE or enable multiple NICs with teaming.
NFS traffic traverses the 1GbE link, so high network utilisation saturates the path and inflates disk latency. Upgrading to 10GbE, or teaming multiple NICs, raises aggregate throughput and relieves that bottleneck, directly addressing the constrained network link.
Refer to the exhibit. The performance data shows MEMCTL at 5% and SWPOUT at 2%. What does this indicate about the host?
The host is over-committed on memory, causing ballooning and swapping.
MEMCTL at 5% reflects the balloon driver reclaiming guest memory, while SWPOUT at 2% confirms the hypervisor is swapping to disk. Together these counters indicate the host has over-committed physical memory beyond what its workload demands, so ESXi is actively reclaiming pages to satisfy the configured memory constraint.
The host is experiencing CPU contention.
The host has network congestion.
The host has high storage latency.
Refer to the exhibit. A distributed virtual switch port shows dropped Rx packets and CRC errors. What is the most likely cause?
Faulty physical network cable or NIC.
CRC errors and dropped receive packets indicate corrupted frames arriving at the physical layer, typically from a damaged cable, faulty NIC, or bad transceiver. This points to the physical medium rather than switch policy or VLAN misconfiguration.
Outdated NIC driver on the ESXi host.
MTU mismatch between the switch and the VM.
Incorrect VLAN configuration on the port group.
An administrator notices that a critical VM running a database has a high CPU ready time average (over 20%) on a host with 2 physical CPUs (16 cores each). The host is running 6 VMs, each with 8 vCPUs. What is the most likely cause of the high ready time?
Hyper-Threading should be disabled to reduce scheduling overhead.
The host has too many vCPUs relative to physical cores; reduce vCPU count on some VMs.
Over-commitment of vCPUs causes high CPU ready time: 6 VMs × 8 vCPUs = 48 vCPUs on 32 physical cores, so the scheduler forces VMs to wait for physical cores. Reducing vCPU counts on the non-database VMs lowers contention, directly addressing the ready-time constraint.
The VMs are not configured with NUMA awareness.
Memory overcommitment is causing excessive swapping.
An administrator is troubleshooting a VM that is running slowly. The VM has 4 vCPUs and 16 GB of memory. The host has 2 physical CPUs with 10 cores each, hyper-threading enabled. The administrator runs esxtop and sees that %RDY for the VM is consistently above 15%. Which action would most likely reduce the ready time?
Increase the CPU shares for the VM.
Increase the number of vCPUs to 8 to improve parallelism.
Increase the memory allocation to 32 GB.
Reduce the number of vCPUs to 2 if the workload does not require 4.
High %RDY means vCPUs wait for physical cores. With hyper-threading, four vCPUs contend for limited logical processors, so reducing to two lowers scheduling pressure and co-stop, directly cutting ready time while still meeting the workload's needs.
Want more vSphere Performance and Scaling practice?
Practice this domainThe VCP-DCV exam has 70 questions and must be completed in 135 minutes. The passing score is 300/1000.
Scenario-based questions covering exam objectives with detailed answer explanations.
The exam covers 6 domains: vSphere Lifecycle Management, Configure and Manage vSphere Networking, Configure and Manage vSphere Storage, vSphere Architecture, Products and Solutions, vSphere Security, vSphere Performance and Scaling. Questions are weighted by domain — higher-weight domains appear more on your actual exam.
No. These are original exam-style practice questions written against the official VMware VCP-DCV exam objectives. They are not copied from the real exam. Courseiva focuses on genuine understanding, not memorisation of braindumps.
Courseiva tracks your accuracy per domain and routes you toward weak areas automatically. Free, no account required.