Sample questions
VMware Certified Professional Data Center Virtualization VCP-DCV practice questions
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?
Trap 1: The hosts cannot communicate with the vCenter Server.
If hosts couldn't communicate, vLCM would not show compliance status.
Trap 2: The image validation failed due to missing dependencies.
Validation would occur before remediation.
Trap 3: The desired image was not saved after adding the patch.
The image must be saved; otherwise, remediation would not start.
- A
The software depot URL in the image is incorrect or unreachable.
vLCM uses depot URLs to fetch VIBs; if wrong, retrieval fails.
- B
The hosts cannot communicate with the vCenter Server.
Why wrong: If hosts couldn't communicate, vLCM would not show compliance status.
- C
The image validation failed due to missing dependencies.
Why wrong: Validation would occur before remediation.
- D
The desired image was not saved after adding the patch.
Why wrong: The image must be saved; otherwise, remediation would not start.
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?
Trap 1: Attach a patch baseline to the cluster and remediate.
Baselines are not used in vLCM; vLCM uses desired-state images.
Trap 2: Export the current image, add the patch, and import it to the…
vLCM does not support export/import of images; you edit the desired image directly.
Trap 3: Use Quick Boot to apply the patch to each host individually.
Individual patching is not supported in vLCM clusters.
- A
Create a new desired state image with the patch, validate, and remediate the cluster.
vLCM requires updating the desired image and then remediating.
- B
Attach a patch baseline to the cluster and remediate.
Why wrong: Baselines are not used in vLCM; vLCM uses desired-state images.
- C
Export the current image, add the patch, and import it to the cluster.
Why wrong: vLCM does not support export/import of images; you edit the desired image directly.
- D
Use Quick Boot to apply the patch to each host individually.
Why wrong: Individual patching is not supported in vLCM clusters.
An administrator sees the above JSON output from a vLCM compliance report. What should the administrator do to resolve the compliance issue?
Exhibit
Refer to the exhibit.
```
{
"image": {
"version": "8.0.1",
"vibs": [
{"name": "vmware-esx", "version": "8.0.1-123456"},
{"name": "custom-vib", "version": "1.0.0-1"}
],
"firmware": {
"vendor": "Dell",
"version": "2.10.0"
}
},
"compliance": {
"status": "NON_COMPLIANT",
"issues": [
{"host": "esxi-02.corp.com", "type": "VIB_MISSING", "vib": "custom-vib"}
]
}
}
```Trap 1: Add the custom-vib to the desired image.
The VIB is already in the image.
Trap 2: Update the firmware version for esxi-02.
Firmware is not mentioned in the issues.
Trap 3: Re-define the desired image for the cluster.
The image is correctly defined; the issue is on the host.
- A
Add the custom-vib to the desired image.
Why wrong: The VIB is already in the image.
- B
Verify that the custom-vib is available in the depot and that esxi-02 can install it.
The host is missing the VIB; check depot and acceptance level.
- C
Update the firmware version for esxi-02.
Why wrong: Firmware is not mentioned in the issues.
- D
Re-define the desired image for the cluster.
Why wrong: The image is correctly defined; the issue is on the host.
An administrator is planning to migrate from legacy baselines to vLCM for a cluster. Which TWO statements are true about vLCM?
Trap 1: vLCM allows individual host remediation for flexibility.
vLCM remediates the entire cluster; individual host remediation is not available.
Trap 2: vLCM supports different images for different hosts in the same…
vLCM enforces a single image per cluster.
Trap 3: vLCM uses baseline groups to apply updates.
vLCM does not use baselines.
- A
vLCM allows individual host remediation for flexibility.
Why wrong: vLCM remediates the entire cluster; individual host remediation is not available.
- B
vLCM uses a desired state image to manage host configurations.
vLCM enforces a desired state image across the cluster.
- C
vLCM supports different images for different hosts in the same cluster.
Why wrong: vLCM enforces a single image per cluster.
- D
vLCM can integrate with Hardware Support Manager for firmware updates.
HSM allows vLCM to manage firmware compliance.
- E
vLCM uses baseline groups to apply updates.
Why wrong: vLCM does not use baselines.
A vSphere administrator is using vLCM and needs to ensure that all hosts are compliant with the desired image. Which TWO actions are valid when remediating a vLCM cluster?
Trap 1: Remediate without putting hosts into maintenance mode.
Maintenance mode is required for updates that need reboot.
Trap 2: Remediate only hosts that are non-compliant.
vLCM remediates all hosts in the cluster.
Trap 3: Remediate the cluster even if there are compliance issues.
You must resolve compliance issues first.
- A
Perform a pre-remediation check to validate the image.
vLCM validates the image before applying it.
- B
Remediate without putting hosts into maintenance mode.
Why wrong: Maintenance mode is required for updates that need reboot.
- C
Remediate only hosts that are non-compliant.
Why wrong: vLCM remediates all hosts in the cluster.
- D
Use Quick Boot to minimize host reboot time.
Quick Boot can reduce reboot time during remediation.
- E
Remediate the cluster even if there are compliance issues.
Why wrong: You must resolve compliance issues first.
Which TWO actions are recommended to secure the vCenter Server Appliance (VCSA)?
Trap 1: Enable the auto-lock feature for the admin account
Auto-lock is not a VCSA feature.
Trap 2: Configure the password policy for local accounts
Already enforced by default.
Trap 3: Enable FIPS 140-2 compliance mode
Optional, not always recommended.
- A
Enable the auto-lock feature for the admin account
Why wrong: Auto-lock is not a VCSA feature.
- B
Change the default 'root' password
Default passwords should be changed.
- C
Disable SSH access
Disabling SSH reduces attack surface.
- D
Configure the password policy for local accounts
Why wrong: Already enforced by default.
- E
Enable FIPS 140-2 compliance mode
Why wrong: Optional, not always recommended.
Which THREE security features are available in vSphere Trust Authority (vTA)?
Trap 1: Integration with Active Directory for authentication
vTA does not handle AD integration.
Trap 2: Encryption of vMotion traffic
vMotion encryption is separate from vTA.
- A
Attestation of ESXi hosts
vTA attests host integrity.
- B
Integration with Active Directory for authentication
Why wrong: vTA does not handle AD integration.
- C
Trusted Platform Module (TPM) based attestation
vTA uses TPM for attestation.
- D
Encryption of vMotion traffic
Why wrong: vMotion encryption is separate from vTA.
- E
Key provider services for virtual machines
vTA acts as a key server.
An administrator is configuring a distributed switch and needs to ensure that all virtual machine traffic on a specific VLAN is isolated. The administrator creates a port group with VLAN ID 100. However, a security scanner reports that packets from this VLAN are appearing on other VLANs. Which security policy setting on the distributed switch should the administrator verify?
Trap 1: MAC address changes
This controls whether guest can change MAC.
Trap 2: Forged transmits
Forged transmits control MAC spoofing.
Trap 3: Promiscuous mode
Promiscuous mode allows all traffic to be seen.
- A
MAC address changes
Why wrong: This controls whether guest can change MAC.
- B
Forged transmits
Why wrong: Forged transmits control MAC spoofing.
- C
VLAN trunking
VLAN trunking ensures proper tagging.
- D
Promiscuous mode
Why wrong: Promiscuous mode allows all traffic to be seen.
A vSphere administrator is planning the storage configuration for a new cluster of 10 hosts running VDI workloads. Each VM requires approximately 100 IOPS for typical operation. Which storage design best balances performance and scalability?
Trap 1: Implement vSAN using HDDs with a flash cache tier.
HDDs still have higher latency than all-flash VDI requirements.
Trap 2: Deploy a centralized all-flash FC SAN with multiple paths.
Centralized SAN may become a bottleneck as VDI scales.
Trap 3: Use a single NFS datastore on a large spinning-disk array.
Single datastore creates a bottleneck and lacks IOPS.
- A
Implement vSAN using HDDs with a flash cache tier.
Why wrong: HDDs still have higher latency than all-flash VDI requirements.
- B
Deploy a centralized all-flash FC SAN with multiple paths.
Why wrong: Centralized SAN may become a bottleneck as VDI scales.
- C
Configure each host with local NVMe or SSD drives and use vSphere Local Storage.
Local flash storage provides high IOPS per host and scales with hosts.
- D
Use a single NFS datastore on a large spinning-disk array.
Why wrong: Single datastore creates a bottleneck and lacks IOPS.
During a performance review, an administrator notices that a VM with 4 vCPUs and 16 GB memory is experiencing over 10% CPU ready time. The host has two 8-core sockets (hyper-threading enabled) and 256 GB memory. The host runs 15 other VMs with varying CPU loads. What is the most likely cause?
Trap 1: NUMA node mismatch causing cross-node memory access.
NUMA issues cause memory latency, not CPU ready.
Trap 2: CPU hot-add is enabled on the VM.
CPU hot-add does not cause high ready time.
Trap 3: Memory over-provisioning causing ballooning.
Ballooning affects memory, not CPU ready time.
- A
NUMA node mismatch causing cross-node memory access.
Why wrong: NUMA issues cause memory latency, not CPU ready.
- B
CPU hot-add is enabled on the VM.
Why wrong: CPU hot-add does not cause high ready time.
- C
Memory over-provisioning causing ballooning.
Why wrong: Ballooning affects memory, not CPU ready time.
- D
Over-provisioning of vCPUs on the host leading to contention.
Too many vCPUs relative to cores causes CPU ready time.
Which THREE actions would help reduce network latency for VMs in a vSphere environment?
Trap 1: Separate vMotion traffic onto a different VLAN.
vMotion traffic separation does not affect VM network latency.
Trap 2: Increase the MTU on the vSphere Standard Switch to 9000.
This is the same as jumbo frames, but option A is the correct phrasing.
- A
Separate vMotion traffic onto a different VLAN.
Why wrong: vMotion traffic separation does not affect VM network latency.
- B
Enable jumbo frames on the virtual switch and physical network.
Larger MTU reduces per-packet overhead.
- C
Increase the MTU on the vSphere Standard Switch to 9000.
Why wrong: This is the same as jumbo frames, but option A is the correct phrasing.
- D
Use Network I/O Control to set a higher network share for latency-sensitive VMs.
QoS ensures priority for critical traffic.
- E
Assign dedicated physical NICs for VM traffic.
Dedicated NICs avoid contention with other traffic.
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?
Trap 1: Increase the memory allocation of VMs with high CPU ready times.
This does not address CPU contention.
Trap 2: Increase the CPU reservation for VMs with high ready times.
Reservations can increase contention.
Trap 3: Enable Storage DRS to balance storage I/O load.
Storage DRS does not affect CPU ready times.
- A
Increase the memory allocation of VMs with high CPU ready times.
Why wrong: This does not address CPU contention.
- B
Increase the CPU reservation for VMs with high ready times.
Why wrong: Reservations can increase contention.
- C
Reduce the number of virtual CPUs assigned to VMs and consider adding more hosts.
Reducing vCPUs and adding hosts reduces CPU contention.
- D
Enable Storage DRS to balance storage I/O load.
Why wrong: Storage DRS does not affect CPU ready times.
Which TWO are valid methods to monitor vSphere performance metrics?
Trap 1: PowerCLI scripts that retrieve performance data.
PowerCLI is a scripting tool, not a monitoring method.
Trap 2: VMware Workstation.
Workstation is not for monitoring vSphere.
Trap 3: vCenter Log Insight.
Log Insight is for log analysis, not performance metrics.
- A
PowerCLI scripts that retrieve performance data.
Why wrong: PowerCLI is a scripting tool, not a monitoring method.
- B
VMware Workstation.
Why wrong: Workstation is not for monitoring vSphere.
- C
vCenter Log Insight.
Why wrong: Log Insight is for log analysis, not performance metrics.
- D
vSphere Performance Charts.
Built-in tool for performance monitoring.
- E
esxtop (or resxtop).
Command-line performance monitoring tool.
An administrator wants to ensure that a critical database VM has consistent low-latency access to its virtual disks. The VM currently resides on a datastore backed by a hybrid array. Which configuration change best meets this requirement?
Trap 1: Configure the VM to use multiple paths with Round Robin policy.
Path policy affects throughput, not latency.
Trap 2: Assign a separate VMDK for each critical VM on a dedicated…
This is not a standard practice and does not guarantee low latency.
Trap 3: Enable Storage I/O Control (SIOC) on the datastore.
SIOC manages congestion but does not improve underlying latency.
- A
Create a VM storage policy that requires flash-based storage and apply it to the VM.
A storage policy with rule set for flash ensures placement on low-latency storage.
- B
Configure the VM to use multiple paths with Round Robin policy.
Why wrong: Path policy affects throughput, not latency.
- C
Assign a separate VMDK for each critical VM on a dedicated datastore.
Why wrong: This is not a standard practice and does not guarantee low latency.
- D
Enable Storage I/O Control (SIOC) on the datastore.
Why wrong: SIOC manages congestion but does not improve underlying latency.
Which TWO factors contribute to increased CPU ready time on a vSphere host?
Trap 1: Memory ballooning due to memory over-commitment.
Ballooning affects memory, not CPU.
Trap 2: Using CPU affinity to pin VMs to specific cores.
Affinity can reduce ready time by preventing migration.
Trap 3: High disk latency on the datastore.
Disk latency does not cause CPU ready time.
- A
Memory ballooning due to memory over-commitment.
Why wrong: Ballooning affects memory, not CPU.
- B
Over-provisioning of vCPUs relative to physical cores.
Too many vCPUs cause contention and ready time.
- C
Using CPU affinity to pin VMs to specific cores.
Why wrong: Affinity can reduce ready time by preventing migration.
- D
Enabling hyper-threading on hosts that already have high vCPU-to-core ratios.
HT can increase contention because logical processors share cores.
- E
High disk latency on the datastore.
Why wrong: Disk latency does not cause CPU ready time.
Refer to the exhibit. The performance data shows MEMCTL at 5% and SWPOUT at 2%. What does this indicate about the host?
Exhibit
Refer to the exhibit. ``` esxtop -b -d 30 -n 2 > /tmp/perf.csv # Sample output (abbreviated): # CPU(%): 10.5, 12.3, 8.9, ... # PMEM(%): 65, 70, 68, ... # MEMCTL(%): 5, 4, 3, ... # SWPOUT(%): 2, 1, 0, ... ```
Trap 1: The host is experiencing CPU contention.
CPU% is moderate, no sign of contention.
Trap 2: The host has network congestion.
No network metrics are shown.
Trap 3: The host has high storage latency.
No storage metrics are shown.
- A
The host is over-committed on memory, causing ballooning and swapping.
MEMCTL and SWPOUT indicate memory pressure.
- B
The host is experiencing CPU contention.
Why wrong: CPU% is moderate, no sign of contention.
- C
The host has network congestion.
Why wrong: No network metrics are shown.
- D
The host has high storage latency.
Why wrong: No storage metrics are shown.
Match each vSphere storage concept to its definition.
Drag a concept onto its matching description — or click a concept then click the description.
Cluster file system for VM storage
Network file system protocol for VM storage
Block storage protocol over IP networks
Raw device mapping for direct LUN access
Hyper-converged storage from local disks
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.
62 TB
256
6 TB
64
1024
An administrator is troubleshooting a vLCM cluster that has multiple ESXi hosts with non-compliant status. The cluster uses a single image with an HSM for firmware. Which TWO actions should the administrator take to identify the root cause of non-compliance? (Choose two.)
Trap 1: Validate the cluster image against the desired image specification.
This only checks the image itself, not per-host compliance.
Trap 2: Run the vSphere Update Manager baseline scan on each host.
vSphere Update Manager (VUM) is separate from vLCM; VUM baselines are not used.
Trap 3: Check the baseline compliance report for the cluster.
Baselines are not used with single-image vLCM.
- A
Validate the cluster image against the desired image specification.
Why wrong: This only checks the image itself, not per-host compliance.
- B
Run the vSphere Update Manager baseline scan on each host.
Why wrong: vSphere Update Manager (VUM) is separate from vLCM; VUM baselines are not used.
- C
Verify the HSM is properly connected and reporting firmware inventory.
If HSM is offline or misconfigured, firmware component cannot be applied.
- D
Review the vLCM compliance status for each host in the cluster to see specific missing components.
The compliance view shows per-host discrepancies.
- E
Check the baseline compliance report for the cluster.
Why wrong: Baselines are not used with single-image vLCM.
Order the steps to enable vSphere HA on a cluster.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Arrange the steps to create a new virtual machine in vSphere Client.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Order the steps to perform a vMotion migration of a powered-on virtual machine.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
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.
Place the steps to create a new standard virtual switch in vSphere in order.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.