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

Question 1

An administrator has configured a vSphere Distributed Switch (VDS) with Network I/O Control. They need to guarantee bandwidth for a specific set of virtual machines. Which method should be used?

Accepted Answer

Create a port group with a custom network resource pool.. Create a port group with a custom network resource pool. Network I/O Control allows administrators to create network resource pools to guarantee bandwidth for specific virtual machines or port groups. By creating a custom network resource pool and assigning it to a port group, you can reserve a certain amount of bandwidth. Option B is incorrect because SR-IOV provides direct hardware passthrough but does not manage bandwidth guarantees; it can actually bypass Network I/O Control. Option C is incorrect because setting a VLAN tag does not guarantee bandwidth; it only separates traffic. Option D is incorrect because traffic shaping is used to limit bandwidth (throttle outgoing traffic) but does not guarantee a minimum bandwidth; it only caps it.

Answer

Enable SR-IOV on the physical NICs.

Answer

Set the virtual machine's network adapter to use a specific VLAN.

Answer

Configure Traffic Shaping on the distributed switch.

Question 2

An administrator configures a VDS with two uplinks and sets the load balancing policy to 'Route based on IP hash'. What additional configuration is required on the physical switches to ensure proper traffic distribution?

Accepted Answer

Configure a static EtherChannel.. 'Route based on IP hash' on a vSphere Distributed Switch requires the physical switch ports to be configured as a static EtherChannel (or equivalent LAG). IP hash uses a hash of source and destination IPs to select an uplink, and the physical switch must treat the uplinks as a single logical link so return traffic flows correctly.

Answer

Use individual ports with no aggregation.

Answer

Set port security to allow multiple MAC addresses.

Answer

Enable Link Aggregation Control Protocol (LACP).

Question 3

An administrator has created a standard vSwitch port group with VLAN ID 100. Virtual machines in this port group can communicate with each other but not with devices on the physical network. What is a possible cause?

Accepted Answer

The physical switch port is not configured to pass VLAN 100.. When a standard vSwitch port group is assigned VLAN ID 100, the ESXi host tags outbound frames with VLAN 100 (802.1Q). For those frames to reach the physical network, the physical switch port that the uplink connects to must be configured as a trunk that permits VLAN 100. If the physical switch port is an access port on a different VLAN or does not allow VLAN 100, traffic stays isolated within the virtual switch, which is exactly the symptom described.

Answer

The vSwitch has only one uplink.

Answer

The virtual machines have duplicate MAC addresses.

Answer

The virtual machines are using different subnets.

Question 4

An administrator needs to capture traffic from a specific virtual machine for troubleshooting. Which vSphere networking feature should be used?

Accepted Answer

Port mirroring on the VDS.. Port mirroring on a vSphere Distributed Switch (VDS) copies traffic from a source VM's vNIC (or uplink) to a destination port where a packet analyzer is attached. It is the purpose-built feature for capturing VM traffic for troubleshooting, supporting both ingress/egress directions and multiple session types.

Answer

LLDP on the VDS.

Answer

NetFlow on the VDS.

Answer

Traffic shaping on the VDS.

Question 5

An administrator needs to separate vMotion traffic from management traffic. Which should be created?

Accepted Answer

A new VMkernel adapter on a different subnet.. Separating vMotion traffic from management traffic requires a dedicated VMkernel adapter, because VMkernel adapters carry vMotion, management, and other system traffic. Placing it on a different subnet ensures traffic isolation at Layer 3 and prevents vMotion from competing with management on the same network.

Answer

A new physical NIC.

Answer

A new VLAN on the existing port group.

Answer

A new standard switch port group.

Question 6

A vSphere administrator is troubleshooting connectivity issues for a virtual machine that is unable to communicate with other VMs on the same VLAN. The VM is connected to a distributed port group on a vSphere Distributed Switch (vDS). The administrator verifies that the VM's IP configuration is correct and that the port group is configured with the correct VLAN ID. However, the VM can only communicate with other VMs on the same ESXi host. What is the most likely cause?

Accepted Answer

The physical switch ports connecting the ESXi hosts are not configured as trunk ports for the VLAN.. If the VM can communicate with other VMs on the same ESXi host but not with VMs on other hosts in the same VLAN, the issue is almost certainly that the physical switch ports connecting the ESXi hosts are not configured as trunk ports carrying that VLAN. The vDS and port group are correctly configured, so the failure is at the physical uplink layer where VLAN tags must be allowed to pass between hosts.

Answer

The vDS is not configured with a VLAN trunking policy.

Answer

The VM's network adapter is configured with the wrong MAC address.

Answer

The distributed port group has forging transmits set to reject.

Question 7

An administrator needs to configure a vSphere Standard Switch (vSS) for a small environment. Which component must be created first before adding a virtual machine to the network?

Accepted Answer

Create a standard switch.. Before a VM can be attached to a network on a vSphere Standard Switch, a standard switch must exist. The switch is the foundational layer; port groups and VMkernel interfaces are created on top of it. Therefore, creating the standard switch is the first required step.

Answer

Configure a VMkernel interface.

Answer

Create a virtual machine port group.

Answer

Add a physical uplink to the host.

Question 8

Which TWO of the following are functions of a vSphere Distributed Switch that are not available in a vSphere Standard Switch? (Select exactly two.)

Accepted Answer

Port mirroring (Distributed Port Mirroring).. Option A (Port mirroring / Distributed Port Mirroring) is correct because the vSphere Distributed Switch provides a centralized, dvSwitch-wide port mirroring feature configured at the distributed switch or distributed port group level, whereas a vSphere Standard Switch has no native port mirroring capability and requires third-party tools or workarounds. Option C (Network I/O Control / NIOC) is correct because NIOC, which uses shares, reservations, and limits to prioritize and manage bandwidth across traffic types (e.g., vMotion, iSCSI, NFS, VM traffic) on a per-dvSwitch basis, is a Distributed Switch-only feature and is not available on a Standard Switch. Option B (NIC teaming with explicit failover order) is not correct because Standard Switches also support NIC teaming with configurable failover order, so it is not exclusive to the Distributed Switch. Option D (Traffic shaping policies) is not correct because both Standard and Distributed Switches support traffic shaping, though the Distributed Switch offers more granular per-port-group control. Option E (VLAN tagging and trunking) is not correct because VLAN tagging (VST, EST, VGT) and trunking are supported on both Standard and Distributed Switches.

Answer

NIC teaming with explicit failover order.

Answer

Traffic shaping policies.

Answer

VLAN tagging and trunking.

Question 9

A vSphere administrator notices that VMs on a specific ESXi host lose connectivity intermittently. The VMs are on a distributed switch port group. The administrator finds that the Uplink 1 on that host is down. What should the administrator do first?

Accepted Answer

Check the physical switch port configuration for the failed uplink. When an uplink is down on a host attached to a distributed switch, the first step is to verify the physical layer — the physical switch port, cable, and SFP — because the most common cause is a physical link failure or misconfiguration on the upstream switch. Only after confirming the physical layer should you adjust vSphere teaming or failover settings.

Answer

Increase the number of uplinks in the teaming policy

Answer

Set the load balancing policy to Route based on source MAC

Answer

Configure a different failover order

Question 10

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

Accepted Answer

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

Configure a VMkernel interface on the distributed switch

Answer

Set the MTU to 9000

Answer

Enable Network I/O Control

Question 11

Which four types of traffic can be assigned to a separate VMkernel adapter on an ESXi host?

Accepted Answer

Management traffic. Management traffic (A) is a valid VMkernel service that can be enabled on a dedicated VMkernel adapter to isolate host management from other traffic. vMotion (B) is also a VMkernel service that can be assigned to its own VMkernel adapter to separate live migration traffic. vSAN (C) is a VMkernel service that can be enabled on a dedicated VMkernel adapter for vSAN storage communication. Fault Tolerance logging (E) is a VMkernel service that can be assigned to a separate VMkernel adapter for FT metadata traffic. Virtual machine network traffic (D) is not a VMkernel service; it is handled by standard or distributed virtual switches and port groups, not by a VMkernel adapter.

Answer

Virtual machine network traffic

Question 12

A company has a single ESXi host with a standard switch. The administrator creates a new port group for a DMZ network and assigns a VM to it. The VM cannot ping the default gateway. The physical switch port is configured as a trunk with VLAN 100 allowed. The port group VLAN ID is set to 100. The physical NIC is connected to the switch port and shows link up. What should the administrator do to resolve the issue?

Accepted Answer

Verify the VM's IP configuration. The physical switch port is already configured as a trunk allowing VLAN 100, and the port group VLAN ID is correctly set to 100, so the virtual networking layer is properly tagged. The most likely remaining cause is that the VM itself has an incorrect IP address, subnet mask, or default gateway setting for the DMZ subnet. Verifying the guest OS IP configuration is the correct next troubleshooting step.

Answer

Enable VLAN tagging on the physical switch port

Answer

Change the VLAN ID to 0

Answer

Add a second physical NIC to the standard switch

Question 13

After upgrading the physical switches, the LAG (Link Aggregation Group) on a VDS does not come up. The VDS LAG configuration shows LACP active mode. The physical switch ports are configured with LACP active mode as well. What is the most likely cause?

Accepted Answer

The physical switch ports are not in a port-channel. For a VDS LAG in LACP active mode to come up, the physical switch ports must be configured as a port-channel (LAG) with LACP enabled. If the switch ports are left as individual access ports without a port-channel, the ESXi host's LACP PDUs are not matched to a LAG on the switch side, and the LAG never forms. This is the most common cause after a switch upgrade where the port-channel configuration was not reapplied.

Answer

The physical switch uses a different LACP system priority

Answer

The ESXi hosts have different LAG IDs

Answer

The VDS LAG hashing algorithm is set to IP hash

Question 14

Refer to the exhibit. An administrator notices that the ESXi host is listening on both IPv4 and IPv6 for HTTPS. However, IPv6 traffic is not being forwarded to the host. Which configuration change is most likely needed?

Accepted Answer

Configure a default gateway for the IPv6 stack on the host.. If the ESXi host is listening on IPv6 for HTTPS but IPv6 traffic isn't being forwarded to it, the host likely lacks a default gateway for its IPv6 stack. Without an IPv6 default gateway, the host can communicate on-link but cannot route replies to off-subnet IPv6 clients, so forwarded traffic never returns. Configuring an IPv6 default gateway on the host resolves the routing gap.

Answer

Disable IPv6 and use only IPv4.

Answer

Remove the IPv4 HTTPS listener to force IPv6.

Answer

Enable IPv6 on the vSphere Distributed Switch.

Question 15

Refer to the exhibit. A virtual machine on the VM Network is experiencing intermittent connectivity. The administrator notices that vmnic0 is saturated. Which action would improve performance without causing a single point of failure?

Accepted Answer

Configure load-based teaming on vSwitch0 for the VM Network portgroup.. Load-based teaming (LBT) on vSwitch0 dynamically balances VM traffic across all active uplinks based on real-time utilization, so vmnic0's load is shared with vmnic1, relieving saturation. It also maintains redundancy because both uplinks remain active; if one fails, the other takes over. This directly addresses the intermittent connectivity caused by vmnic0 saturation without introducing a single point of failure.

Answer

Change the active uplinks for VM Network to vmnic1 only.

Answer

Increase the MTU on vSwitch0 to 9000.

Answer

Move the VM Network to vSwitch1.