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

Question 1

An administrator manages a vSphere 7 environment with standard switches. A VM's port group is configured with VLAN ID 0, and the physical switch port that the ESXi host uplink connects to is configured as an access port in VLAN 30. The VM cannot communicate with other devices in VLAN 30. Which action should the administrator take to allow the VM to communicate on VLAN 30?

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

Accepted Answer

Change the VM's port group VLAN ID to 30.. With a standard switch, the port group VLAN ID determines how the virtual switch tags egress frames. Setting it to 30 ensures frames are tagged with VLAN 30, matching the physical switch access port. Using VLAN ID 0 sends untagged frames, which the physical switch would place in VLAN 30, but if that is not working, explicitly tagging is the correct fix. Changing the physical switch to trunk or enabling promiscuous mode does not address the tagging mismatch.

Answer

Set the VM's virtual NIC to use VLAN 30 in the guest OS.

Answer

Enable promiscuous mode on the port group.

Answer

Change the physical switch port to a trunk port and allow VLAN 30.

Question 2

An administrator manages a vSphere 7 cluster where each ESXi host has two physical NICs (vmnic0 and vmnic1) connected to a vSphere Standard Switch. The team wants to ensure that if one physical NIC fails, virtual machine traffic continues to flow with minimal disruption. They also want to avoid any single point of failure. Which standard switch configuration should the administrator implement?

Accepted Answer

Configure both physical NICs as active uplinks in the same team, with the default route based on originating virtual port.. The correct configuration is to team both physical NICs as active uplinks with the default load balancing policy. This provides both redundancy and increased bandwidth by using both links simultaneously. If one NIC fails, the other continues to carry traffic, ensuring minimal disruption. The default route based on originating virtual port is suitable for standard switch environments without special physical switch configuration.

Answer

Configure a single physical NIC as the only active uplink and add a second standard switch with the other NIC.

Answer

Configure both physical NICs as active uplinks but use IP hash load balancing.

Answer

Configure one physical NIC as an active uplink and the other as a standby uplink, with the default route based on originating virtual port.

Question 3

A vSphere administrator manages a vSphere Distributed Switch (vDS) with three ESXi hosts. The administrator needs to apply a new VLAN ID to the vMotion VMkernel adapter on all hosts without affecting the vMotion traffic of other hosts. Which action should the administrator take?

Accepted Answer

Create a new distributed port group with the required VLAN ID and migrate only the vMotion VMkernel adapters to that port group.. The vMotion VMkernel adapter's VLAN is determined by the distributed port group it is connected to. To change only vMotion traffic without affecting other hosts, the administrator should create a new distributed port group with the desired VLAN and migrate the vMotion VMkernel adapters to it. This isolates the change and maintains other traffic on the original port group.

Answer

Edit the VLAN setting on the existing distributed port group that carries all VMkernel traffic.

Answer

Modify the vMotion TCP/IP stack to use a different VLAN tag.

Answer

Change the VLAN ID on the vSphere Standard Switch that backs the vMotion VMkernel adapter.

Question 4

A vSphere administrator is configuring a vSphere Distributed Switch (vDS) with multiple uplinks. The administrator wants to ensure that a specific virtual machine's traffic always uses a particular physical uplink, regardless of other VMs' traffic. Which vDS feature should the administrator use?

Accepted Answer

Use a dedicated uplink port and override the teaming policy on the port group.. To pin a VM's traffic to a specific uplink, you must override the teaming and failover policy on the port group and configure it to use only that uplink as active. This bypasses the default load balancing and ensures all traffic from that port group uses the designated uplink. Other options like LAGs or load-based policies distribute traffic dynamically and cannot guarantee a specific uplink. Static port binding does not affect uplink selection.

Answer

Set the teaming and failover policy to 'Route based on physical NIC load'.

Answer

Configure a static port binding on the distributed port group.

Answer

Create a LAG and assign the VM's port group to it.

Question 5

A vSphere administrator is configuring a vSphere Distributed Switch (vDS) with multiple uplinks on each ESXi host. The administrator wants to use Link Aggregation Control Protocol (LACP) to aggregate uplinks into a LAG. Which two statements are true regarding LACP support on vSphere distributed switches? (Choose two.)

Accepted Answer

The physical switch must be configured with a matching LACP port channel.. LACP support on vSphere Distributed Switches requires vDS version 5.1 or later. The physical switch must be configured with a matching LACP port channel. A LAG is local to each host and cannot span multiple hosts. LACP on the vSphere side is always active, and the teaming policy for the port group must be set to use the LAG, typically with IP hash. Therefore, the true statements are that LACP is supported on vDS 5.1 and later, and the physical switch must have a matching LACP port channel.

Answer

A LAG can include uplinks from multiple ESXi hosts.

Answer

LACP supports both active and passive modes on the vSphere side.

Answer

LACP can be used with Route based on IP hash teaming policy.

Question 6

A vSphere administrator is configuring a vSphere Distributed Switch (vDS) with LACP. The physical switch ports are configured for LACP in active mode. The administrator creates a LAG on the vDS and assigns two uplinks to it. Which two statements are true regarding this configuration? (Choose two.)

Accepted Answer

The LAG can be used as an active uplink for a distributed port group by setting the teaming policy to use the LAG.. When configuring LACP on a vDS, the load balancing algorithm must match the physical switch's hashing method to ensure proper traffic distribution. Also, a LAG can be used by a distributed port group by selecting it in the teaming policy, which provides aggregated bandwidth and redundancy. These two statements are true and are key considerations for a successful LACP implementation.

Answer

LACP support on a vDS requires that all uplinks in the LAG be connected to the same physical switch.

Answer

Each uplink in the LAG can be used as an active uplink for standard port groups without additional configuration.

Answer

The LAG's load balancing algorithm can be changed without disrupting traffic.

Question 7

An administrator needs to configure a vSphere Standard Switch to allow virtual machines on different VLANs to communicate with each other without leaving the ESXi host. Which feature should the administrator enable?

Accepted Answer

A router appliance or external router.. VLANs segment traffic at Layer 2, so communication between different VLANs requires Layer 3 routing. A router appliance or external router with interfaces on each VLAN can route traffic between them. Enabling VLAN tagging only places VMs on VLANs; it does not route between them. Promiscuous mode and security policies do not provide routing. Thus, a router is the correct solution.

Answer

VLAN tagging on the port groups.

Answer

Promiscuous mode on the virtual switch.

Answer

MAC address changes and forged transmits.

Question 8

A vSphere administrator is configuring Network I/O Control (NIOC) on a vSphere Distributed Switch to prioritize different traffic types. The administrator wants to ensure that vMotion traffic does not saturate the uplinks during peak hours. Which two actions should the administrator take? (Choose two.)

Accepted Answer

Enable NIOC on the distributed switch and configure shares for vMotion traffic.. To prevent vMotion from saturating uplinks, you must both prioritize it appropriately and cap its maximum usage. Enabling NIOC and configuring shares ensures vMotion gets priority when bandwidth is contended. Setting a bandwidth limit ensures it cannot exceed a specified amount, preventing saturation. Together, these actions provide both prioritization and a ceiling. Reservations alone do not cap usage, and TCP/IP stacks or VLAN priorities do not directly control bandwidth allocation within the distributed switch.

Answer

Create a vMotion TCP/IP stack and assign it to a dedicated VMkernel adapter.

Answer

Assign vMotion traffic to a separate distributed port group with a higher VLAN priority.

Answer

Set a bandwidth reservation for vMotion traffic.

Question 9

A vSphere administrator is deploying a new vSphere Distributed Switch (vDS) with Network I/O Control (NIOC) version 3. The environment has multiple traffic types: vMotion, iSCSI, and virtual machine traffic. The administrator wants to guarantee that vMotion traffic gets at least 2 Gbps of bandwidth during times of contention, while allowing it to use more if available. Which NIOC configuration should be used?

Accepted Answer

Create a user-defined network resource pool for vMotion with a reservation of 2 Gbps and assign it to the vMotion port group.. To guarantee a minimum bandwidth for vMotion while allowing it to exceed that when available, a user-defined network resource pool with a reservation is required. NIOC version 3 supports reservations on user-defined pools, which can be assigned to port groups. System traffic types like vMotion do not support reservations directly, so the resource pool approach is necessary.

Answer

Create a vMotion traffic type in NIOC and assign it a reservation of 2 Gbps.

Answer

Configure a reservation of 2 Gbps on the vMotion VMkernel adapter.

Answer

Set the vMotion traffic type's shares to High and limit to 2 Gbps.

Question 10

An administrator is troubleshooting a vSphere Distributed Switch where a VM's traffic is not reaching the physical network. The VM is connected to a distributed port group with VLAN ID 100. The physical switch port connected to the ESXi host uplink is configured as a trunk port allowing VLAN 100. The administrator notices that the VM can communicate with other VMs on the same host and VLAN, but not with external devices. What is the most likely cause?

Accepted Answer

The VLAN ID on the distributed port group is set to 0 (untagged) instead of 100.. The VM can communicate with other VMs on the same host, indicating the virtual switch is functioning. However, external communication fails, suggesting a VLAN tagging mismatch on the uplink. If the port group VLAN ID is 0, frames are untagged, and the physical switch trunk port (expecting tagged VLAN 100) will not forward them correctly. This is the most likely cause. Other options are either contradicted by the scenario or based on misunderstandings of VLAN tagging in vSphere.

Answer

The ESXi host's physical uplink is not configured to tag VLAN 100.

Answer

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

Answer

The VM's virtual NIC is configured with a different VLAN ID in the guest OS.

Question 11

A vSphere administrator is configuring a vSphere Distributed Switch (vDS) to support Link Aggregation Control Protocol (LACP) with a physical switch. The administrator has created a LAG on the vDS and assigned two uplinks to it. Which two statements are true regarding LACP support on vSphere distributed switches? (Choose two.)

Accepted Answer

LACP is supported on vSphere Distributed Switches version 5.1 and later.. LACP on vSphere distributed switches requires the load balancing algorithm to be set to IP hash, which ensures that traffic is distributed based on IP addresses and maintains frame order. Additionally, LACP is supported starting with vDS version 5.1, so environments must meet that minimum version. Other options are either incorrect or not specific to LACP; for example, physical switch ports can be active or passive, and VLAN trunking is handled at the port group level, not by the LAG itself.

Answer

LACP support requires that the physical switch ports are configured in active mode.

Answer

The number of uplinks in a LAG must not exceed the number of physical switch ports in the port channel.

Answer

The LAG can be configured with multiple VLANs by using VLAN trunking on the port group.

Question 12

A vSphere administrator is troubleshooting a virtual machine that cannot communicate with other devices on the same VLAN. The virtual machine is connected to a standard switch port group with VLAN 100. The physical switch port that the ESXi host uplink connects to is configured as a trunk port allowing VLANs 100, 200, and 300. The administrator notices that the virtual machine can communicate with other VMs on the same ESXi host but not with VMs on other hosts. What is the most likely cause?

Accepted Answer

The ESXi host uplink is not tagging frames with VLAN 100.. The virtual machine can communicate with VMs on the same host but not with VMs on other hosts. This indicates that the virtual switch is correctly placing traffic into VLAN 100 internally, but the traffic is not being tagged with VLAN 100 when it leaves the ESXi host. As a result, the physical switch receives untagged frames and places them in the native VLAN, which is likely not VLAN 100. To resolve this, the administrator should ensure that the port group is configured with VLAN 100 and that the ESXi host is tagging frames appropriately. This is typically done by setting the port group VLAN ID to 100, which enables Virtual Switch Tagging.

Answer

The physical switch port is not configured to allow VLAN 100.

Answer

The virtual machine's guest operating system is not configured with the correct VLAN ID.

Answer

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

Question 13

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 14

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 15

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.