VCP-DCV Practice Test 35 — 15 Questions

Question 1

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?

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

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 2

You manage a vSphere 7 environment with 20 hosts, each with 2 x 10-core CPUs and 512 GB RAM. The environment runs 300 VMs, including a critical ERP application that uses 8 vCPUs and 64 GB RAM. Recently, the ERP VM has been experiencing periodic performance degradation, especially during month-end processing. The host running the ERP VM shows CPU ready time averaging 8%, with spikes to 20% during the processing. The host has 10 other VMs, each with 2-4 vCPUs. The cluster has DRS enabled with default settings. You suspect CPU contention. Which two actions should you take to mitigate the issue? (Choose two.)

Accepted Answer

Migrate the ERP VM to a host with fewer VMs to reduce CPU over-provisioning.. Migrating the ERP VM to a host with fewer VMs reduces the CPU over-provisioning ratio, directly lowering CPU ready time. With 8% average and 20% spikes, the host's physical CPU cores are oversubscribed; moving the VM to a less contended host alleviates the scheduling pressure without changing VM configuration.

Answer

Enable DPM and set the cluster to aggressive power management.

Answer

Increase the number of vCPUs on the ERP VM to 12 to distribute load.

Answer

Increase the memory allocation of the ERP VM to reduce ballooning.

Question 3

Refer to the exhibit. An administrator runs the vmkfstools command on an ESXi host and views the output. Which conclusion can be drawn from the output?

Accepted Answer

The datastore has approximately 50% free space.. The vmkfstools command output shows the capacity and free space values for the datastore. In this case, the free space is approximately half of the total capacity, indicating roughly 50% free space. This is a direct calculation from the displayed numbers, not an inference about provisioning or encryption.

Answer

The VMDK file is thin provisioned.

Answer

The datastore has a block size of 1 MB, which is the maximum for VMFS-6.

Answer

The virtual machine's disk is encrypted.

Question 4

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 5

During a security audit, it is found that the vCenter Server is using the default self-signed certificate. The administrator is tasked to replace it with a certificate from an enterprise CA. What is the first step after obtaining the CA-signed certificate?

Accepted Answer

Convert the certificate and private key into PEM format and place them in the appropriate directory.. The certificate must be in a format that vCenter can use; typically, it needs to be combined with the private key. Option B is premature before preparing the certificate. Option C is incorrect because certificate import is done via certificate management tools, not vSphere Web Client. Option D is incorrect because the private key is included in the signed certificate generation process, not imported separately.

Answer

Use the vSphere Web Client to upload the certificate.

Answer

Import the private key into the Windows Certificate Store.

Answer

Restart the VMware Certificate Service.

Question 6

A rapidly growing company currently uses vSphere 7 Standard Edition across two data centers connected via a high-latency link. They plan to implement a vSAN stretched cluster to provide a unified storage solution and enable automatic failover between sites. The cluster must support VM-level encryption at rest and in transit, as well as intelligent capacity management with deduplication and compression. The budget is strictly allocated to a per-CPU licensing model. Which vSAN edition should the company select to meet all requirements while minimizing costs?

Accepted Answer

vSAN Enterprise. vSAN Enterprise is the only edition that includes all required features: stretched cluster support, VM-level encryption at rest and in transit, and deduplication and compression. It also supports per-CPU licensing, aligning with the budget constraint. vSAN Advanced and Standard lack encryption at rest and in transit, while vSAN Starter does not support stretched clusters or deduplication/compression.

Answer

vSAN Starter

Answer

vSAN Advanced

Answer

vSAN Standard

Question 7

A vSphere administrator is planning to upgrade a vSphere 7.0 U3 cluster to vSphere 8.0. The cluster currently uses vSphere Lifecycle Manager (vLCM) with a single image. After the upgrade, the administrator wants to ensure that all ESXi hosts apply firmware updates from a hardware support manager (HSM) integrated with vLCM. Which step must the administrator take before starting the cluster upgrade?

Accepted Answer

Ensure the desired ESXi version and firmware component are specified in the vLCM image.. VLCM with a single image can include both the ESXi version and firmware components from an integrated hardware support manager (HSM). By specifying the desired ESXi version and firmware component in the vLCM image, the administrator ensures that during the cluster upgrade, vLCM will apply the firmware updates provided by the HSM as part of the image-based remediation process. This is the required step before starting the upgrade to vSphere 8.0.

Answer

Disable vLCM and use baseline-based remediation for the upgrade.

Answer

Create separate baselines for ESXi and firmware and attach them to the cluster.

Answer

Remove the HSM integration because vLCM cannot apply firmware updates.

Question 8

Refer to the exhibit. An administrator creates a storage policy with the rule: "Rule: provisioningType equals thick". When the policy is applied to a VM on this array, what will be the compliance status?

Accepted Answer

Not compliant - the array does not advertise thick provisioning capability.. The array only advertises thin provisioning and replication capabilities. The policy requires thick provisioning, which is not advertised. Therefore the VM will be marked as uncompliant because the array does not support the required capability. Option B is incorrect because it does not match; the array supports thin only. Option C is incorrect because VVols do not automatically default to thick. Option D is incorrect because the array does not provide thick.

Answer

Not compliant - the replication RPO is too high.

Answer

Compliant - the storage policy is applied regardless of capabilities.

Answer

Compliant - the array supports thin provisioning by default.

Question 9

A vSphere administrator is troubleshooting a VM that hosts a critical database. The VM is configured with 8 vCPUs and 64 GB memory on an ESXi host with two 10-core CPUs (hyperthreading enabled). Performance charts show CPU ready time averaging 12% during peak hours, and the database application is experiencing high transaction latency. The administrator has verified that no other VMs are contending for CPU. Which action will most likely reduce CPU ready time without negatively impacting database performance?

Accepted Answer

Reduce the number of vCPUs assigned to the VM to 4.. Reducing the number of vCPUs to 4 reduces CPU scheduler overhead and can lower CPU ready time when the VM has more vCPUs than needed. With 8 vCPUs on a host with 20 physical cores (40 logical with HT), and 12% ready time, the VM is likely oversubscribed for its workload. Many database applications do not scale linearly beyond 4 vCPUs, so reducing to 4 often improves performance by decreasing contention and improving cache locality. Option A is wrong: disabling hyperthreading reduces logical CPUs, potentially increasing contention. Option B is wrong: CPU affinity can lead to unbalanced load and is not recommended in DRS clusters. Option C is wrong: increasing memory reservation does not affect CPU ready time.

Answer

Disable hyperthreading on the host.

Answer

Assign a CPU affinity mask to pin the VM to specific physical cores.

Answer

Increase the VM's memory reservation.

Question 10

An organization has a vLCM-managed cluster with 5 ESXi 8.0 hosts. The desired image includes ESXi 8.0 U1 and a specific third-party storage driver VIB. The administrator recently updated the desired image to a new version of the storage driver. After remediation, three hosts show 'Compliant' but two hosts show 'Non-Compliant' with the error: 'VIB missing: storage-driver-vib'. The administrator confirms that the VIB is present in the image and that the hosts were recently added to the cluster. What is the most likely cause of the non-compliance on the two hosts?

Accepted Answer

The two hosts have a host acceptance level set to 'CommunitySupported' while the VIB requires 'PartnerSupported'.. When a host is added to a vLCM-managed cluster, the desired image is applied to it. If the host's acceptance level (e.g., 'CommunitySupported') is lower than the VIB's required acceptance level (e.g., 'PartnerSupported'), vLCM will refuse to install the VIB, causing a 'Non-Compliant' status with a 'VIB missing' error. This is a common issue when hosts are imported from environments with relaxed acceptance policies.

Answer

The two hosts have incompatible firmware for the storage driver.

Answer

The VIB was not included in the image for those hosts.

Answer

The vCenter Server cannot reach the software depot for those hosts.

Question 11

Order the steps to enable vSphere HA on a cluster.

Accepted Answer

Step 1: Select the cluster, Step 2: Access HA settings, Step 3: Enable vSphere HA, Step 4: Configure HA options, Step 5: Confirm changes. The correct sequence for enabling vSphere HA ensures that all prerequisites are met, starting with cluster selection, then accessing the HA configuration page, toggling the enable option, customizing settings, and applying changes. Common mistakes include attempting to configure options before enabling HA or accessing settings before selecting the cluster.

Answer

Step 1: Select the cluster, Step 2: Enable vSphere HA, Step 3: Access HA settings, Step 4: Configure HA options, Step 5: Confirm changes

Answer

Step 1: Access HA settings, Step 2: Select the cluster, Step 3: Enable vSphere HA, Step 4: Configure HA options, Step 5: Confirm changes

Answer

Step 1: Select the cluster, Step 2: Configure HA options, Step 3: Access HA settings, Step 4: Enable vSphere HA, Step 5: Confirm changes

Question 12

Place the steps to create a resource pool in a cluster.

Accepted Answer

Right-click cluster, select New Resource Pool, name the resource pool, set CPU and memory resources (shares, reservation, limit), configure expandable reservation (optional), click OK.. Creating a resource pool in a vSphere cluster involves first initiating the creation by right-clicking the cluster and selecting New Resource Pool, then providing a name, followed by configuring CPU and memory resources including shares, reservation, and limit, optionally enabling expandable reservation, and finally confirming by clicking OK. This sequence ensures all required parameters are set before finalizing the resource pool.

Answer

Right-click cluster, select New Resource Pool, set CPU and memory resources (shares, reservation, limit), name the resource pool, configure expandable reservation (optional), click OK.

Answer

Right-click cluster, select New Resource Pool, name the resource pool, set CPU and memory resources (shares, reservation, limit), click OK, configure expandable reservation (optional).

Answer

Right-click cluster, select New Resource Pool, name the resource pool, configure expandable reservation (optional), set CPU and memory resources (shares, reservation, limit), click OK.

Question 13

Arrange the steps to convert a virtual machine to a template.

Accepted Answer

Power off the virtual machine, right-click and select Convert to Template, confirm the conversion, wait for the task to complete, verify the template appears in the inventory.. To convert a VM to a template in vSphere, you must first power off the VM, then right-click it and select Convert to Template, confirm the operation, wait for the task to finish, and finally verify the template in the inventory. This ensures the VM is not in use and the conversion process is properly executed.

Answer

Right-click and select Convert to Template, confirm the conversion, power off the virtual machine, wait for the task to complete, verify the template appears in the inventory.

Answer

Power off the virtual machine, confirm the conversion, right-click and select Convert to Template, wait for the task to complete, verify the template appears in the inventory.

Answer

Power off the virtual machine, wait for the task to complete, right-click and select Convert to Template, confirm the conversion, verify the template appears in the inventory.

Question 14

Order the steps to take a snapshot of a virtual machine.

Accepted Answer

Initiate snapshot, name it, choose memory and quiesce options, then confirm.. The correct order for taking a snapshot in VMware vSphere is to first initiate the snapshot by right-clicking the VM and selecting 'Snapshot > Take Snapshot', then in the dialog provide a name and optional description, select whether to snapshot the virtual machine's memory and whether to quiesce the file system, and finally confirm by clicking OK. This sequence ensures that all necessary parameters are set before the snapshot is created.

Answer

Initiate snapshot, choose memory and quiesce options, name it, then confirm.

Answer

Name the snapshot, initiate snapshot, choose memory and quiesce options, then confirm.

Answer

Initiate snapshot, confirm, then name it and choose memory and quiesce options.

Question 15

Arrange the steps to add an existing virtual machine to a vCenter Server inventory.

Accepted Answer

Right-click a datacenter or folder, click 'Add Existing Virtual Machine', browse to and select the VM's .vmx file, then click Finish.. The correct sequence to add an existing VM to vCenter inventory is: right-click a datacenter or folder, select 'Add Existing Virtual Machine', browse to the VM's .vmx file, and click Finish. This order ensures the wizard is properly initiated and the VM is registered in the desired inventory location.

Answer

Browse to and select the VM's .vmx file, right-click a datacenter or folder, click 'Add Existing Virtual Machine', then click Finish.

Answer

Click 'Add Existing Virtual Machine', right-click a datacenter or folder, browse to the VM's .vmx file, then click Finish.

Answer

Right-click a datacenter or folder, click Finish, browse to and select the VM's .vmx file, then click 'Add Existing Virtual Machine'.