Text preview & study summary

VMware VCP-DCV - vSphere Data Center Virtualization - Compute Networking Storage HA DRS

A free sample of 5 questions from this quiz, shown in full with answer choices and explanations. No interactivity — everything is visible on this page for study and review.

Want to test your knowledge? Launch the Interactive Exam Simulator

Question 1

An administrator wants to deploy multiple ESXi hosts with consistent configuration (networking, storage, security settings) and ensure that any configuration drift is detected and corrected automatically. Which vSphere feature should be used?

Answer choices

  • A. vSphere Update Manager (VUM) for patch compliance

  • B. vSphere Host Profiles to define desired state and check/remediate compliance (Correct)

  • C. vCenter Auto Deploy for stateless ESXi deployment

  • D. vSphere Lifecycle Manager (vLCM) with desired state images

Explanation

vSphere Host Profiles capture and enforce a reference host configuration (networking, storage, security, etc.) and can check all hosts against this profile, detecting configuration drift and providing remediation capabilities. Option D (vSphere Lifecycle Manager with desired state) is the modern evolution of this approach in vSphere 7.0+ and is also valid for image-based lifecycle management. Option A addresses patching, not configuration consistency. Option C (Auto Deploy) handles stateless deployment but doesn't continuously monitor/correct drift on running hosts. Host Profiles (B) is the most direct answer for ongoing drift detection and correction.

Question 2

An administrator is preparing for a vCenter Server upgrade from version 7.0 to 8.0. What is the correct upgrade sequence to minimize risk and maintain functionality?

Answer choices

  • A. Upgrade ESXi hosts first, then upgrade vCenter Server

  • B. Upgrade vCenter Server first, then upgrade ESXi hosts (Correct)

  • C. Upgrade both vCenter and ESXi hosts simultaneously to avoid compatibility issues

  • D. Upgrade ESXi hosts using vSphere Update Manager before upgrading vCenter

Explanation

VMware's recommended upgrade sequence is always: upgrade vCenter Server first, then upgrade ESXi hosts. This is because newer versions of vCenter are backward-compatible with older ESXi versions (within the supported compatibility matrix), allowing vCenter to manage older ESXi hosts during the transition period. Upgrading ESXi hosts before vCenter may result in a newer ESXi version that the older vCenter doesn't fully support, potentially causing management issues. Simultaneous upgrades increase risk and complicate troubleshooting.

Question 3

A storage administrator needs to present a new LUN from a SAN to ESXi hosts and wants to use a protocol that supports both block-level storage access and works natively over existing Ethernet infrastructure without requiring dedicated HBAs. Which protocol should they use?

Answer choices

  • A. Fibre Channel (FC)

  • B. iSCSI (Correct)

  • C. NFS

  • D. Fibre Channel over Ethernet (FCoE)

Explanation

iSCSI (Internet Small Computer Systems Interface) provides block-level storage access over standard Ethernet infrastructure and does not require dedicated Fibre Channel HBAs. It can use software iSCSI initiators built into ESXi or hardware iSCSI HBAs. FC requires dedicated Fibre Channel HBAs and a separate FC network infrastructure. NFS provides file-level (not block-level) access and is used for NAS storage. FCoE encapsulates Fibre Channel over Ethernet but still requires Converged Network Adapters (CNAs) and a specific FCoE infrastructure.

Question 4

An administrator is troubleshooting a VM that is experiencing slow disk performance. Using esxtop, they notice that the DAVG (device average latency) metric for the VM's datastore is consistently above 25ms during business hours. What does this indicate, and what are the recommended next steps?

Answer choices

  • A. DAVG above 25ms indicates host-level CPU saturation; add more vCPUs to the VM

  • B. DAVG above 25ms indicates storage device latency; investigate the storage array, check queue depths, and consider Storage I/O Control (SIOC) (Correct)

  • C. DAVG above 25ms indicates excessive snapshots; delete all VM snapshots

  • D. DAVG above 25ms indicates network saturation on the storage network; check iSCSI/NFS network throughput

Explanation

In esxtop, DAVG (Device Average Latency) measures latency at the storage device level — the time it takes from when a command is sent to the physical storage device until a response is received. Values consistently above 20-25ms indicate storage-side performance issues. Recommended actions include: investigating the storage array (check for overloaded controllers, cache misses), reviewing HBA queue depths (QFULL situations), enabling Storage I/O Control (SIOC) to prioritize critical VM I/O, and potentially migrating VMs to faster storage tiers. DAVG is not related to CPU, snapshots, or network bandwidth.

Question 5

A vCenter administrator needs to restrict a group of developers so they can only power on/off their assigned VMs and view performance data, but cannot modify VM configurations, create snapshots, or access other VMs. Which approach correctly implements this in vSphere?

Answer choices

  • A. Create a custom Role with only the required privileges, assign it to a vSphere Group at the VM folder level, with propagation enabled (Correct)

  • B. Add the developers to the built-in "Virtual Machine User" role at the vCenter root level

  • C. Create a custom Role and assign it directly at the individual VM level for each developer

  • D. Use vSphere Tags to restrict access to VMs with specific tags

Explanation

The correct approach is to create a custom Role with only the specific privileges needed (Power On/Off, View Performance), then assign this role to a group at the appropriate object level (VM folder) with "Propagate to children" enabled. This grants access to all VMs within that folder but not to other areas. Assigning the built-in VM User role at the vCenter root would give too broad access. Assigning per-individual-VM is administratively unscalable. vSphere Tags are used for organization and policy-based management, not directly for access control permissions.