VCP-DCV Configure and Manage vSphere Networking Practice Test 5 — 15 Questions

Question 1

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?

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

Accepted Answer

Review the NIC teaming failover order and ensure active uplinks are up.. Intermittent connectivity drops on a VM connected to a vDS, despite no errors on the vDS health check or physical switch logs, often point to a NIC teaming misconfiguration. If the active uplinks are not properly set or one uplink is down, the VM traffic may fail over to a standby or unused uplink, causing packet loss. Verifying the teaming failover order and ensuring all active uplinks are operational directly addresses this common cause of intermittent drops.

Answer

Verify the VMkernel port configuration

Answer

Check the VM's firewall settings

Answer

Check DNS resolution for the gateway

Question 2

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?

Accepted Answer

Change the load balancing policy to Route based on IP hash.. Route based on IP hash uses a hash of source and destination IP addresses to determine which uplink to use for each traffic flow, ensuring that all packets in a given flow use the same uplink while distributing different flows across multiple uplinks. This improves load distribution for VM traffic compared to the default Route based on the originating virtual port, which only considers the vNIC port ID and can lead to uneven distribution when multiple VMs share the same port group.

Answer

Change the VLAN ID to 100.

Answer

Enable failover on the port group.

Answer

Set one NIC as active and the other as standby.

Question 3

Which THREE are valid methods to isolate and secure management traffic on a vSphere Distributed Switch? (Choose three.)

Accepted Answer

Assign a specific VLAN ID to the management port group.. Assigning a specific VLAN ID to the management port group isolates management traffic at Layer 2 by tagging frames with a unique VLAN identifier. This prevents unauthorized access from other VLANs and ensures that management traffic is logically separated from other network traffic on the same vSphere Distributed Switch.

Answer

Enable Route based on IP hash on the management port group.

Answer

Use Private VLANs on the management port group.

Question 4

A company runs a three-tier application on vSphere 7.0. The web tier uses VLAN 100, app tier VLAN 200, and database tier VLAN 300. Each tier is on a separate port group on a vSphere distributed switch. The environment uses Network I/O Control (NIOC) with shares set to: Web (50), App (30), Database (20). The physical uplinks are two 10 GbE NICs in a team. Recently, the database team reports slow performance during peak hours. The network team checks the physical switches and finds no congestion. The ESXi host shows the two uplinks are heavily utilized with many dropped packets on the database port group. The administrator suspects that the database traffic is being starved by other traffic. Which action should the administrator take to resolve the issue?

A. Increase the number of physical uplinks to four 10 GbE NICs.
B. Change the NIOC shares to Web (10), App (30), Database (60).
C. Create a separate vSphere standard switch for the database tier.
D. Enable SR-IOV on the physical NICs and assign virtual functions to database VMs.

Accepted Answer

Change the NIOC shares to Web (10), App (30), Database (60).. The database traffic is being starved due to low NIOC shares relative to the web and app tiers. By increasing the database shares to 60 and reducing web to 10, the database port group will receive a higher proportion of the available bandwidth during congestion, alleviating the dropped packets and slow performance. NIOC shares are relative and only take effect when there is contention, so adjusting them directly addresses the starvation without requiring additional hardware.

Answer

Create a separate vSphere standard switch for the database tier.

Answer

Enable SR-IOV on the physical NICs and assign virtual functions to database VMs.

Answer

Increase the number of physical uplinks to four 10 GbE NICs.

Question 5

Order the steps to perform a vMotion migration of a powered-on virtual machine.

Accepted Answer

Verify prerequisites, Initiate migration, Select migration type, Choose destination, Confirm settings. Prerequisites check, initiate migration, select type, choose destination, and confirm.

Answer

Select migration type, Verify prerequisites, Initiate migration, Choose destination, Confirm settings

Answer

Initiate migration, Choose destination, Select migration type, Verify prerequisites, Confirm settings

Answer

Confirm settings, Initiate migration, Verify prerequisites, Choose destination, Select migration type

Question 6

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 7

Match each vSphere feature to its correct description.

Accepted Answer

vMotion: Enables live migration of running virtual machines with zero downtime. Key vSphere features: vMotion (live migration), HA (automatic restart), DRS (load balancing), FT (continuous availability via lockstep). Common confusions involve swapping the feature and its description.

Answer

vMotion: Provides automatic restart of VMs after host failure

Answer

HA: Enables live migration of running VMs

Question 8

An administrator is configuring a distributed switch for a cluster of ESXi hosts. The requirements are: VLAN 100 for production, VLAN 200 for management, and a separate VLAN 300 for vMotion. The management network should be isolated from production traffic. What is the best practice for configuring these networks on the distributed switch?

Accepted Answer

Create three separate distributed port groups, each with the appropriate VLAN ID, and assign each VM kernel adapter or VM to the correct port group.. Best practice on a vSphere Distributed Switch is to create one distributed port group per VLAN/network function, each with its own VLAN ID, and attach the appropriate VMkernel adapters (management, vMotion) or VM vNICs to the correct port group. This provides clean traffic isolation, simplifies troubleshooting, and aligns with VMware's recommended design for separating management, vMotion, and production traffic.

Answer

Create one distributed port group with VLAN 100, and use VLAN tagging on the VMs for management and vMotion.

Answer

Use standard switches for management and vMotion to avoid complexity.

Answer

Create one distributed port group with VLAN trunk (4095) and use port-based VLAN filtering on the VMs.

Answer

Create two port groups: one for production (VLAN 100) and one for management+vMotion (VLAN 200) because vMotion can share VLAN with management.

Question 9

A VM cannot connect to the network after being migrated to a different host in the cluster. The VM's network adapter is connected to a standard switch port group that exists on the source host but not on the destination host. What is the most likely cause?

Accepted Answer

The standard switch is not configured on the destination host.. A standard vSwitch and its port groups are host-local objects — they are not shared across ESXi hosts in a cluster. If the VM's port group exists only on the source host, the destination host has no matching port group, so the VM's network adapter cannot connect after migration. This is the classic cause of post-migration network loss with standard switches.

Answer

The VM's MAC address is not allowed on the destination port group.

Answer

The VLAN ID on the port group does not match.

Answer

The ESXi host's firewall is blocking the VM's traffic.

Question 10

A network administrator needs to isolate traffic between VMs in the same VLAN on a distributed switch. Which feature should be used?

Accepted Answer

Private VLAN. Private VLANs (PVLANs) on a vSphere Distributed Switch allow Layer 2 isolation between VMs in the same VLAN by using primary and secondary VLANs with promiscuous, isolated, and community port types. This is the specific feature designed to prevent VM-to-VM traffic within a single VLAN while still allowing communication with a gateway or designated promiscuous ports. It directly addresses the requirement to isolate same-VLAN VM traffic.

Answer

Network I/O Control

Answer

VLAN trunking

Answer

Traffic shaping

Answer

Port binding

Question 11

A VM experiences high packet loss during peak hours. The VM is connected to a distributed switch port group with a traffic shaping policy: average bandwidth 100 Mbps, peak bandwidth 200 Mbps, burst size 50 KB. What is the most likely cause?

Accepted Answer

The burst size is too small, causing packets to be dropped when burst traffic exceeds the average.. Traffic shaping allows sustained traffic up to the average bandwidth (100 Mbps) and only permits bursts up to the peak bandwidth (200 Mbps) within the configured burst size. If the burst size is too small, burst traffic above the average during peak hours will be dropped, causing packet loss. The peak bandwidth limit is not necessarily being exceeded, a disabled policy would remove these shaping drops, and while a physical uplink slower than 200 Mbps could cause loss, the most likely cause given the configured policy and peak-hour burst behavior is the too-small burst size.

Answer

The peak bandwidth limit is being exceeded.

Answer

The traffic shaping policy is disabled.

Answer

The physical uplink speed is less than 200 Mbps.

Question 12

Which three factors influence the behavior of Network I/O Control (NIOC) when allocating bandwidth to different traffic types? (Choose three.)

Accepted Answer

Reservation per traffic type. Network I/O Control (NIOC) allocates bandwidth on a vSphere Standard or Distributed Switch based on three per-traffic-type settings: Reservation (B), which guarantees a minimum bandwidth in Mbps or Gbps that the traffic type can always use; Shares (C), which determine the relative priority for distributing any remaining bandwidth when the link is contended (e.g., High=100, Normal=50, Low=25 per active uplink); and Limit (D), which caps the maximum bandwidth the traffic type may consume. These three parameters together define how NIOC divides and prioritizes bandwidth among traffic types such as vMotion, iSCSI, and VM traffic. The total physical bandwidth (A) is not a configurable NIOC factor — it is the underlying capacity that reservations, shares, and limits act upon, and NIOC itself does not let you set it. The number of physical uplinks (E) affects aggregate capacity and teaming behavior, but NIOC allocation is driven by the per-traffic-type reservation, shares, and limit values, not by the uplink count.

Answer

The total physical bandwidth

Answer

The number of physical uplinks

Question 13

An administrator is configuring a distributed switch with LACP. Which two statements are true regarding LACP support on vSphere distributed switches? (Choose two.)

Accepted Answer

LACP supports both active and passive modes.. Option A is correct because vSphere distributed switches support LACP in both active and passive modes, allowing the ESXi host to either initiate LACPDU negotiation (active) or respond to the physical switch's negotiation (passive). Option D is correct because LACP on a vSphere distributed switch requires creating a Link Aggregation Group (LAG), which is then bound to a distributed port group or uplink port group to aggregate multiple uplinks. Option B is incorrect because IP hash is a static NIC teaming load-balancing policy, not an LACP behavior; LACP uses a dynamic link aggregation hashing scheme. Option C is incorrect because LACP is only supported on vSphere distributed switches, not on standard vSwitches. Option E is incorrect because LACP LAGs can carry management, vMotion, and VM traffic, not just virtual machine traffic.

Answer

LACP automatically distributes traffic based on IP hash.

Answer

LACP can be configured on standard vSwitches.

Answer

LACP is only supported for virtual machine traffic, not for management or vMotion.

Question 14

An administrator sees this health check output. What should be done to verify VLAN 100 connectivity?

Accepted Answer

Create a VMkernel adapter on VLAN 100 and ping a gateway.. To verify VLAN 100 connectivity at the ESXi host level, the administrator must create a VMkernel adapter tagged with VLAN 100 on the distributed or standard switch and then ping a gateway or another host in that VLAN. This tests the host's own L2/L3 path for that VLAN without involving a guest VM. It directly validates that the physical switch trunk, VLAN tagging, and uplink configuration are correct.

Answer

Enable VLAN pruning on the physical switch.

Answer

Configure a port group for VLAN 100 and connect a VM.

Answer

Restart the management agents.

Question 15

The administrator configured this LAG on a distributed switch and corresponding LACP settings on the physical switch. But the LAG is not coming up. What is a likely issue?

Accepted Answer

The LAG mode is passive, but the physical switch is also configured as passive.. When both the vSphere distributed switch LAG and the physical switch are configured in passive mode, LACP negotiation fails because neither side initiates the negotiation. One side must be set to active for LACP to establish. Option A is incorrect because the load balancing policy (e.g., IP hash) is separate from LACP mode; it controls traffic distribution, not LACP negotiation. Option B is incorrect because the LAG name is not used by LACP; LACP uses system identifiers and port keys, so a name mismatch does not prevent the LAG from coming up. Option D is incorrect because active/active mode refers to the uplink teaming policy, not the LACP mode setting.

Answer

The load balancing policy should be IP hash.

Answer

The LAG name is not used by the physical switch.

Answer

The uplinks should be in active/active mode.