Configure and Manage vSphere Networking →easyMultiple Choice

VCP-DCV Configure and Manage vSphere Networking Practice Question

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?

⚠ Common exam trap

Test-takers frequently assume a single standard switch with multiple uplinks and separate port groups is sufficient for traffic separation, but they overlook that physical NIC assignment is per-switch, not per-port-group, so both traffic types could still share the same NICs via teaming or failover unless explicit NIC binding is configured.

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

✓

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 analysis

Option-by-option breakdown

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

✗
Create one standard switch with vmnic0 only and use VLANs for separation.
Why it's wrong here
Using vmnic0 alone leaves vmnic1 unused and provides no physical separation of management traffic, so management would share vmnic0 with VM traffic. It would be correct where a single uplink is available and VLAN tagging must separate traffic on that shared link.
✗
Create one standard switch with both vmnics and separate port groups for VM and VMkernel.
Why it's wrong here
Both vmnics on one switch with separate port groups does not pin traffic to a specific NIC; teaming and failover determine which uplink carries each port group, so vmnic1 could still carry VM traffic. It would be correct where uplink redundancy is wanted and traffic separation is achieved by port group or VLAN instead.
✓
Create two standard switches: one with vmnic0 and a VM port group, and another with vmnic1 and a VMkernel port group.
Why this is correct
Separating vmnic0 and vmnic1 onto distinct standard switches gives each traffic type a dedicated uplink, satisfying the requirement that VM traffic and management traffic never share a physical NIC. The VM port group binds to vmnic0, while the VMkernel port group on the second switch carries management traffic over vmnic1.
✗
Create a vSphere Distributed Switch with both vmnics.
Why it's wrong here
A vSphere Distributed Switch requires vCenter Server and manages multiple hosts; the scenario covers one ESXi host creating a Standard Switch, and a distributed switch cannot be created from the host client. It would be correct when consistent networking across many hosts in a vCenter-managed cluster is required.

Go deeper

VCP-DCV Configure and Manage vSphere Networking Practice Question

Why each option matters

Option-by-option breakdown

Related to this question