Configure and Manage vSphere Networking →easyMultiple Select

VCP-DCV Configure and Manage vSphere Networking Practice Question

Which two actions must the administrator take to ensure network connectivity for VMs on a new distributed switch?

⚠ Common exam trap

VCP-DCV often tests the confusion between host-level and VM-level networking requirements, tricking candidates into selecting VMkernel interfaces or optional features like MTU or NIOC instead of the mandatory host addition and port group creation.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Add the ESXi hosts to the distributed switch

To provide network connectivity for VMs on a new vSphere Distributed Switch, the administrator must first add the ESXi hosts to the distributed switch (option B), because a vDS only manages networking on hosts that are members of it; without host membership, no physical uplinks or VM traffic can traverse the switch. The administrator must also create a port group and assign a VLAN (option D), since VM vNICs connect to distributed port groups, and the VLAN ID on that port group determines the Layer 2 broadcast domain for the VMs. Configuring a VMkernel interface (option A) is only required for host management, vMotion, iSCSI, or vSAN traffic, not for general VM connectivity. Setting MTU to 9000 (option C) is an optional jumbo-frame tuning, and enabling Network I/O Control (option E) is an optional traffic-shaping/QoS feature; neither is required for basic VM network connectivity.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Configure a VMkernel interface on the distributed switch
Why it's wrong here
A VMkernel interface carries host management, vMotion and storage traffic, not VM guest traffic; VMs need a distributed port group with uplinks. It tempts because VMkernel adapters are mandatory on a distributed switch, but they serve ESXi host services rather than virtual machine connectivity.
✓
Add the ESXi hosts to the distributed switch
Why this is correct
Adding ESXi hosts to the distributed switch is mandatory because a vSphere Distributed Switch spans multiple hosts, and each host must be a member before its physical uplinks (vmnic) can be attached to dvUplinks. Without host membership, VMs cannot reach the dvPortGroup, so connectivity fails.
✗
Set the MTU to 9000
Why it's wrong here
MTU 9000 is jumbo frames, an optional performance tuning for storage or vMotion traffic, not a connectivity requirement; mismatched MTU causes drops. It tempts because MTU settings appear in distributed switch configuration, yet default 1500 already permits VM traffic once port groups and uplinks exist.
✓
Create a port group and assign a VLAN
Why this is correct
Creating a port group on the distributed switch and assigning a VLAN provides the logical network segment VMs attach their vNICs to, satisfying the requirement for VM network connectivity. Without a port group, VMs cannot connect to the switch; the VLAN assignment ensures traffic is tagged correctly onto the required segment.
✗
Enable Network I/O Control
Why it's wrong here
Network I/O Control allocates bandwidth shares among traffic types; it neither creates nor enables VM connectivity. It tempts because it is configured on distributed switches and improves performance under contention, but VMs still require a distributed port group bound to an uplink before any traffic flows.

Visual reference

Go deeper

VCP-DCV Configure and Manage vSphere Networking Practice Question

Why each option matters

Option-by-option breakdown

Related to this question