VCP-DCV Configure and Manage vSphere Networking — Timed 15 Questions

Question 1

Match each vSphere edition/license tier to its key feature.

Accepted Answer

vSphere Enterprise Plus: Includes Distributed Switch, DRS, and Storage vMotion. vSphere licensing tiers: Standard (basic features like vMotion and HA), Enterprise Plus (advanced features like DRS, DVS, Storage vMotion, and Fault Tolerance), Essentials (small environments up to 3 hosts with vCenter Server). Common confusions involve assigning Fault Tolerance to Standard (it is Enterprise Plus) or including vSphere Replication incorrectly.

Answer

vSphere Standard: Provides vMotion, High Availability, and Fault Tolerance

Answer

vSphere Standard: Includes Distributed Switch and DRS

Answer

vSphere Enterprise Plus: Supports vSAN and vSphere Replication

Answer

vSphere Essentials: Supports unlimited hosts and advanced features

Question 2

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.. If the physical uplink speed is less than the peak bandwidth of 200 Mbps, packets will be dropped at the physical NIC level when the VM sends traffic at or near the peak rate, causing high packet loss during peak hours. Option B is incorrect; a burst size of 50 KB is not too small and would not cause drops when burst traffic exceeds the average, as the traffic shaping policy allows bursts up to the peak bandwidth for short periods. Option A is less likely because the peak bandwidth limit is 200 Mbps, which is not being exceeded. Option C would not cause packet loss if the policy is disabled.

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 3

A company runs a vSphere 7 cluster with 4 ESXi hosts, each connected to a single vSphere Distributed Switch (VDS) with two 10GbE uplinks. The environment hosts 100 production VMs and uses vSphere Replication for disaster recovery to a remote site. Network I/O Control (NIOC) is enabled on the VDS with the following shares: vSphere Replication (System Traffic) = 100, Virtual Machine Traffic = 50. During the scheduled replication window (every 2 hours), users report significant VM performance degradation. The administrator observes that during replication, the VMkernel interfaces handling replication consume 95% of the available uplink bandwidth. The goal is to guarantee at least 6 Gbps of bandwidth for VM traffic on each host while still allowing replication to occur. Which action should the administrator take?

Accepted Answer

Create a network resource pool for VM traffic on the VDS and assign a reservation of 6 Gbps.. Creating a network resource pool for VM traffic and assigning a reservation of 6 Gbps guarantees that VM traffic gets at least that amount of bandwidth, regardless of replication demands. This is the proper use of NIOC resource pools. Option B (increasing shares) only affects priority, not guarantees. Option C (limiting replication) could help but does not guarantee VM bandwidth and may still allow replication to burst if the limit is not set appropriately. Option D (adding uplinks) is expensive and may not directly address the guarantee requirement.

Answer

Increase the shares for Virtual Machine traffic to 200.

Answer

Increase the number of uplinks to four per host.

Answer

Set a hard limit of 4 Gbps on vSphere Replication traffic.

Question 4

A vSphere administrator is troubleshooting connectivity issues for a virtual machine on a standard switch. The VM is configured with VLAN 100, but cannot ping the default gateway. The VMkernel port on the host is on VLAN 200. The physical switch port connected to the host is configured as a trunk port allowing VLANs 100 and 200. Which action should the administrator take to resolve the issue?

Accepted Answer

Ensure the VM port group is set to VLAN 100.. The VM is configured with VLAN 100, and the physical switch trunk port already allows VLAN 100 and 200. The VMkernel port on VLAN 200 is working, so the issue is that the VM port group must be explicitly set to VLAN 100 to tag egress frames with VLAN 100 and to accept only VLAN 100-tagged frames on ingress. Option C ensures the standard switch port group applies the correct VLAN ID, matching the physical switch trunk configuration.

Answer

Enable promiscuous mode on the VM port group.

Answer

Change the physical switch port to access mode on VLAN 100.

Answer

Set the VM port group VLAN to 4095.

Question 5

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?

Accepted Answer

Use explicit failover order (Active/Standby). The 'Use explicit failover order (Active/Standby)' policy designates one or more NICs as active and the rest as standby, providing pure fault tolerance without any load balancing. When the active NIC fails, traffic automatically fails over to the standby NIC, ensuring redundancy without distributing traffic across multiple uplinks.

Answer

Route based on IP hash

Answer

Route based on originating virtual port

Answer

Route based on source MAC hash

Question 6

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?

Accepted Answer

Configure a single vDS with all four uplinks, enable NIOC, and set shares and reservations for each traffic type.. NIOC enables per-traffic-type resource management using shares, reservations, and limits, ensuring that mission-critical VMs receive consistent network throughput even under contention. Combining all four uplinks into a single vDS maximizes aggregate bandwidth and provides redundancy through teaming policies, while NIOC prioritizes traffic flows to prevent VMkernel or management traffic from starving VM traffic.

Answer

Configure a single vDS with all four uplinks and enable NetFlow for monitoring.

Answer

Create two separate vDS, each with two uplinks, and separate VM traffic from VMkernel traffic.

Answer

Configure a single vDS with all four uplinks and use Route based on IP hash teaming.

Question 7

A VM on a vSphere Distributed Switch is unable to receive traffic from external networks. The VM can send traffic out successfully. The VM port group has no security policies set (default). The physical switch port is configured as an access port on VLAN 100. The VM port group VLAN is set to 100. What is the most likely cause?

Accepted Answer

The VM is using a different default gateway than the VMkernel interface. The VM can send traffic out successfully but cannot receive traffic from external networks, which indicates a routing issue rather than a switching or VLAN problem. The most likely cause is that the VM's default gateway is set to the VMkernel interface's IP address instead of the physical network's gateway, causing return traffic to be misrouted. This is a common misconfiguration where the VM's default gateway does not match the subnet's gateway, preventing inbound traffic from reaching the VM.

Answer

VLAN mismatch between VM port group and physical switch

Answer

The VM's NIC is in promiscuous mode

Answer

The physical switch port is configured as an access port instead of a trunk

Question 8

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?

Accepted Answer

Create two standard switches: one with vmnic0 and a VM port group, and another with vmnic1 and a VMkernel port group.. The requirement is to use separate physical NICs for different traffic types (VM traffic on vmnic0 and management traffic on vmnic1). In vSphere, a standard switch is a per-host virtual switch that connects virtual machines and VMkernel interfaces to physical NICs. To isolate traffic at the physical NIC level, you must create two distinct standard switches: one with vmnic0 and a VM port group for VM traffic, and another with vmnic1 and a VMkernel port group for management traffic. This ensures that management traffic never traverses vmnic0 and VM traffic never traverses vmnic1, providing physical separation and avoiding contention.

Answer

Create one standard switch with vmnic0 only and use VLANs for separation.

Answer

Create one standard switch with both vmnics and separate port groups for VM and VMkernel.

Answer

Create a vSphere Distributed Switch with both vmnics.

Question 9

A vSphere administrator is deploying a vSphere Distributed Switch (vDS) version 7.0. The environment has ESXi hosts with hardware version 7.0. The administrator needs to ensure that the vDS supports Network I/O Control version 3 (NIOCv3). What must be true for NIOCv3 to function correctly?

Accepted Answer

All hosts must be running ESXi 7.0 or later.. NIOCv3 is a feature introduced with vSphere 7.0 that provides granular bandwidth allocation and reservation for network traffic. For NIOCv3 to function correctly, all ESXi hosts attached to the vDS must be running ESXi 7.0 or later because the feature relies on kernel-level enhancements and the vSphere Network Resource Management (vNRM) agent that are only present in that version. Hosts on earlier versions lack the necessary drivers and scheduling capabilities, causing NIOCv3 to be unavailable or non-functional.

Answer

The vDS must be configured with Route based on IP hash teaming.

Answer

All hosts must have the vDS in Link Aggregation Control Protocol (LACP) mode.

Answer

The vDS must have a Network Resource Pool configured.

Question 10

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?

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 11

An administrator is troubleshooting SSH connectivity to an ESXi host from a management workstation at 10.10.10.2. The SSH session is established, but the administrator cannot ping the host's IP 10.10.10.1. Based on the exhibit, what is the most likely cause?

Accepted Answer

ICMP traffic is blocked by the ESXi firewall.. The administrator can establish an SSH session, which proves that the ESXi host's SSH service is running and that TCP port 22 is reachable from the management workstation. However, the inability to ping the host's IP address (10.10.10.1) indicates that ICMP echo requests are being blocked. By default, the ESXi firewall blocks ICMP traffic, so the most likely cause is that ICMP is filtered by the host firewall.

Answer

The default gateway is not set correctly.

Answer

The SSH service is not running on the host.

Answer

The management workstation is on a different VLAN.

Question 12

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 13

Which TWO conditions must be met to successfully enable vSphere Network I/O Control (NIOC) on a vSphere Distributed Switch? (Choose two.)

Accepted Answer

All ESXi hosts in the cluster must be connected to the same vDS.. NIOC operates at the vDS level and requires all hosts participating in the NIOC configuration to be attached to the same distributed switch. This ensures consistent network resource allocation and traffic shaping policies across the cluster. Option D is correct because NIOC is a premium feature that requires an Enterprise Plus license, as it leverages advanced resource management capabilities not available in lower license tiers.

Answer

Each ESXi host must have a dedicated vDS.

Answer

The vDS must have at least one uplink.

Answer

The physical switches must support LACP.

Question 14

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 15

A company operates a three-node vSphere cluster for a critical application. Each ESXi host has two 10GbE physical NICs (vmnic0 and vmnic1) connected to two separate physical switches (Switch A and Switch B) for redundancy. The cluster uses a vSphere Distributed Switch (vDS) with two uplinks per host: uplink1 (vmnic0) connected to Switch A, and uplink2 (vmnic1) connected to Switch B. The teaming policy is set to 'Route based on originating virtual port' with both uplinks active. The physical switches are configured in a multi-chassis link aggregation group (MLAG) that bundles the ports from both switches into a single LAG interface. The LAG is configured with mode 'active' (802.3ad). Recently, the cluster experienced a network outage when one of the physical switch uplinks failed. The VMs on the affected host lost connectivity for several seconds before recovering. The administrator wants to prevent such outages in the future. Which action should the administrator take?

Accepted Answer

Configure the vDS with LACP support and set the teaming policy to 'Route based on IP hash'.. The current configuration uses a static LAG (MLAG) on the physical switches with 802.3ad active mode, but the vDS is not configured for LACP. This mismatch causes the vDS to send frames based on originating virtual port, which does not coordinate with the physical LAG's hashing algorithm. When a physical uplink fails, the MLAG may not properly redistribute traffic because the vDS is unaware of the LAG state, leading to connectivity loss. Configuring the vDS with LACP support and setting the teaming policy to 'Route based on IP hash' aligns the virtual and physical LAG configurations, ensuring proper load balancing and failover behavior.

Answer

Disable LACP on the physical switches and configure the vDS with 'Route based on originating virtual port' only.

Answer

Add a third physical NIC to each host and configure it as a standby uplink.

Answer

Change the vDS teaming policy to 'Use explicit failover order' with vmnic0 active and vmnic1 standby.