How should I use these Configure and Manage vSphere Networking practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

VCP-DCV · topic practice

Configure and Manage vSphere Networking practice questions

Q: Can I practise just Configure and Manage vSphere Networking questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Configure and Manage vSphere Networking domain.

Practise VMware Certified Professional Data Center Virtualization VCP-DCV Configure and Manage vSphere Networking practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: Configure and Manage vSphere Networking

Practice 10 questions Browse domain →

What the exam tests

What to know about Configure and Manage vSphere Networking

Configure and Manage vSphere Networking questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common Configure and Manage vSphere Networking exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Configure and Manage vSphere Networking questions

20 questions · select your answer, then reveal the explanation

Question 1mediummatching

Read the full Configure and Manage vSphere Networking explanation →

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

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Basic virtualization with vMotion and HA

Full features including DRS, DPM, and Host Profiles

Includes performance monitoring and capacity management

Adds AppDefense for security

Licensing for small ROBO deployments

Trap 1: vSphere Standard: Provides vMotion, High Availability, and Fault…

Incorrect. vSphere Standard includes vMotion and High Availability, but Fault Tolerance is an Enterprise Plus feature.

Trap 2: vSphere Standard: Includes Distributed Switch and DRS

Incorrect. Distributed Switch and DRS are Enterprise Plus features, not available in Standard.

Trap 3: vSphere Enterprise Plus: Supports vSAN and vSphere Replication

Incorrect. While vSAN is an Enterprise Plus feature, vSphere Replication is available in all editions, so this is not uniquely tied to Enterprise Plus. The key feature match for Enterprise Plus is the cluster-level capabilities.

Study all Configure and Manage vSphere Networking common traps →

A
vSphere Standard: Provides vMotion, High Availability, and Fault Tolerance
Why wrong: Incorrect. vSphere Standard includes vMotion and High Availability, but Fault Tolerance is an Enterprise Plus feature.
B
vSphere Standard: Includes Distributed Switch and DRS
Why wrong: Incorrect. Distributed Switch and DRS are Enterprise Plus features, not available in Standard.
C
vSphere Enterprise Plus: Includes Distributed Switch, DRS, and Storage vMotion
Correct. Enterprise Plus includes Distributed Switch, DRS, and Storage vMotion.
D
vSphere Enterprise Plus: Supports vSAN and vSphere Replication
Why wrong: Incorrect. While vSAN is an Enterprise Plus feature, vSphere Replication is available in all editions, so this is not uniquely tied to Enterprise Plus. The key feature match for Enterprise Plus is the cluster-level capabilities.
E
vSphere Essentials: Includes vCenter Server for up to 3 hosts
Correct. Essentials includes vCenter Server for managing up to 3 hosts.
F
vSphere Essentials: Supports unlimited hosts and advanced features
Why wrong: Incorrect. Essentials is limited to 3 hosts and does not include advanced features; it is for small environments.

Full breakdown with real-world context →

Question 2mediummultiple choice

Read the full Configure and Manage vSphere Networking explanation →

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?

Trap 1: The peak bandwidth limit is being exceeded.

Peak is 200 Mbps; if traffic exceeds that, drops would occur, but burst size is more likely.

Trap 2: The traffic shaping policy is disabled.

If disabled, no shaping occurs, so no packet loss from shaping.

Trap 3: The physical uplink speed is less than 200 Mbps.

Uplinks are typically 1 Gbps or faster.

Study all Configure and Manage vSphere Networking common traps →

A
The peak bandwidth limit is being exceeded.
Why wrong: Peak is 200 Mbps; if traffic exceeds that, drops would occur, but burst size is more likely.
B
The burst size is too small, causing packets to be dropped when burst traffic exceeds the average.
With 50 KB burst, sustained bursts above average cause drops.
C
The traffic shaping policy is disabled.
Why wrong: If disabled, no shaping occurs, so no packet loss from shaping.
D
The physical uplink speed is less than 200 Mbps.
Why wrong: Uplinks are typically 1 Gbps or faster.

Full breakdown with real-world context →

Question 3hardmultiple choice

Read the full Configure and Manage vSphere Networking explanation →

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?

Trap 1: Increase the shares for Virtual Machine traffic to 200.

Increasing shares only affects priority, not guarantees. It does not guarantee a minimum bandwidth.

Trap 2: Increase the number of uplinks to four per host.

Adding uplinks is expensive and may not directly address the guarantee requirement.

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

Limiting replication could help but does not guarantee VM bandwidth and may still allow replication to burst if the limit is not set appropriately.

Study all Configure and Manage vSphere Networking common traps →

A
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.
B
Increase the shares for Virtual Machine traffic to 200.
Why wrong: Increasing shares only affects priority, not guarantees. It does not guarantee a minimum bandwidth.
C
Increase the number of uplinks to four per host.
Why wrong: Adding uplinks is expensive and may not directly address the guarantee requirement.
D
Set a hard limit of 4 Gbps on vSphere Replication traffic.
Why wrong: Limiting replication could help but does not guarantee VM bandwidth and may still allow replication to burst if the limit is not set appropriately.

Full breakdown with real-world context →

Question 4mediummultiple choice

Open the full VLAN trunking answer →

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?

Trap 1: Enable promiscuous mode on the VM port group.

Promiscuous mode is for MAC address issues, not VLAN.

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

The physical switch is already trunking VLAN 100.

Trap 3: Set the VM port group VLAN to 4095.

VLAN 4095 is used for VLAN tagging by the guest OS.

Study all Configure and Manage vSphere Networking common traps →

A
Enable promiscuous mode on the VM port group.
Why wrong: Promiscuous mode is for MAC address issues, not VLAN.
B
Change the physical switch port to access mode on VLAN 100.
Why wrong: The physical switch is already trunking VLAN 100.
C
Ensure the VM port group is set to VLAN 100.
The VM port group must match the VM's VLAN.
D
Set the VM port group VLAN to 4095.
Why wrong: VLAN 4095 is used for VLAN tagging by the guest OS.

Full breakdown with real-world context →

Question 5easymultiple choice

Read the full Configure and Manage vSphere Networking explanation →

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?

Trap 1: Route based on IP hash

This is a load-balancing policy that also provides fault tolerance.

Trap 2: Route based on originating virtual port

This is a load-balancing policy.

Trap 3: Route based on source MAC hash

This is a load-balancing policy.

Study all Configure and Manage vSphere Networking common traps →

A
Route based on IP hash
Why wrong: This is a load-balancing policy that also provides fault tolerance.
B
Route based on originating virtual port
Why wrong: This is a load-balancing policy.
C
Use explicit failover order (Active/Standby)
This provides fault tolerance without load balancing.
D
Route based on source MAC hash
Why wrong: This is a load-balancing policy.

Full breakdown with real-world context →

Question 6hardmultiple choice

Read the full Configure and Manage vSphere Networking explanation →

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?

Trap 1: Configure a single vDS with all four uplinks and enable NetFlow for…

NetFlow is for monitoring, not performance guarantees.

Trap 2: Create two separate vDS, each with two uplinks, and separate VM…

This provides isolation but no bandwidth guarantees.

Trap 3: Configure a single vDS with all four uplinks and use Route based on…

This provides redundancy and load balancing but no bandwidth guarantees.

Study all Configure and Manage vSphere Networking common traps →

A
Configure a single vDS with all four uplinks, enable NIOC, and set shares and reservations for each traffic type.
NIOC provides minimum bandwidth guarantees and fair sharing.
B
Configure a single vDS with all four uplinks and enable NetFlow for monitoring.
Why wrong: NetFlow is for monitoring, not performance guarantees.
C
Create two separate vDS, each with two uplinks, and separate VM traffic from VMkernel traffic.
Why wrong: This provides isolation but no bandwidth guarantees.
D
Configure a single vDS with all four uplinks and use Route based on IP hash teaming.
Why wrong: This provides redundancy and load balancing but no bandwidth guarantees.

Full breakdown with real-world context →

Question 7mediummultiple choice

Open the full VLAN trunking answer →

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?

Trap 1: VLAN mismatch between VM port group and physical switch

VLANs match.

Trap 2: The VM's NIC is in promiscuous mode

Promiscuous mode would not prevent incoming traffic.

Trap 3: The physical switch port is configured as an access port instead of…

Access port is correct for a single VLAN.

Study all Configure and Manage vSphere Networking common traps →

A
VLAN mismatch between VM port group and physical switch
Why wrong: VLANs match.
B
The VM's NIC is in promiscuous mode
Why wrong: Promiscuous mode would not prevent incoming traffic.
C
The VM is using a different default gateway than the VMkernel interface
Asymmetric routing can cause one-way traffic.
D
The physical switch port is configured as an access port instead of a trunk
Why wrong: Access port is correct for a single VLAN.

Full breakdown with real-world context →

Question 8easymultiple choice

Read the full Configure and Manage vSphere Networking explanation →

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?

Trap 1: Create one standard switch with vmnic0 only and use VLANs for…

No NIC for management.

Trap 2: Create one standard switch with both vmnics and separate port…

This would not dedicate NICs.

Trap 3: Create a vSphere Distributed Switch with both vmnics.

Not necessary for two NICs.

Study all Configure and Manage vSphere Networking common traps →

A
Create one standard switch with vmnic0 only and use VLANs for separation.
Why wrong: No NIC for management.
B
Create one standard switch with both vmnics and separate port groups for VM and VMkernel.
Why wrong: This would not dedicate NICs.
C
Create two standard switches: one with vmnic0 and a VM port group, and another with vmnic1 and a VMkernel port group.
Separation of traffic types.
D
Create a vSphere Distributed Switch with both vmnics.
Why wrong: Not necessary for two NICs.

Full breakdown with real-world context →

Question 9hardmultiple choice

Read the full Configure and Manage vSphere Networking explanation →

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?

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

Teaming policy does not affect NIOC.

Trap 2: All hosts must have the vDS in Link Aggregation Control Protocol…

NIOC does not require LACP.

Trap 3: The vDS must have a Network Resource Pool configured.

NIOC can be used without a Resource Pool.

Study all Configure and Manage vSphere Networking common traps →

A
All hosts must be running ESXi 7.0 or later.
NIOCv3 requires ESXi 7.0 or later.
B
The vDS must be configured with Route based on IP hash teaming.
Why wrong: Teaming policy does not affect NIOC.
C
All hosts must have the vDS in Link Aggregation Control Protocol (LACP) mode.
Why wrong: NIOC does not require LACP.
D
The vDS must have a Network Resource Pool configured.
Why wrong: NIOC can be used without a Resource Pool.

Full breakdown with real-world context →

Question 10mediummultiple choice

Open the full VLAN trunking answer →

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?

Trap 1: Verify the VMkernel port configuration

VMkernel is for host management, not VM traffic.

Trap 2: Check the VM's firewall settings

Firewall would cause consistent drop, not intermittent.

Trap 3: Check DNS resolution for the gateway

Ping uses IP, not DNS.

Study all Configure and Manage vSphere Networking common traps →

A
Verify the VMkernel port configuration
Why wrong: VMkernel is for host management, not VM traffic.
B
Check the VM's firewall settings
Why wrong: Firewall would cause consistent drop, not intermittent.
C
Check DNS resolution for the gateway
Why wrong: Ping uses IP, not DNS.
D
Review the NIC teaming failover order and ensure active uplinks are up.
Intermittent drops can be caused by failover events.

Full breakdown with real-world context →

Question 11hardmultiple choice

Read the full Configure and Manage vSphere Networking explanation →

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?

Exhibit

Refer to the exhibit.

# esxcli network ip connection list | grep -E "10.10.10.1|10.10.10.2"
tcp        0      0  10.10.10.1:22            10.10.10.2:45678        ESTABLISHED  new-session
udp        0      0  10.10.10.1:123           0.0.0.0:*

# esxcli network ip route ipv4 list
Network          Netmask          Gateway          Interface
0.0.0.0          0.0.0.0          10.10.10.254     vmk0
10.10.10.0       255.255.255.0    0.0.0.0          vmk0
169.254.0.0      255.255.0.0      0.0.0.0          vmk1

Trap 1: The default gateway is not set correctly.

Route shows default gateway.

Trap 2: The SSH service is not running on the host.

SSH is established.

Trap 3: The management workstation is on a different VLAN.

SSH works, so layer 3 connectivity exists.

Study all Configure and Manage vSphere Networking common traps →

A
The default gateway is not set correctly.
Why wrong: Route shows default gateway.
B
ICMP traffic is blocked by the ESXi firewall.
ESXi firewall blocks ping by default.
C
The SSH service is not running on the host.
Why wrong: SSH is established.
D
The management workstation is on a different VLAN.
Why wrong: SSH works, so layer 3 connectivity exists.

Full breakdown with real-world context →

Question 12easymultiple choice

Read the full Configure and Manage vSphere Networking explanation →

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?

Exhibit

Refer to the exhibit.

<config>
  <vswitch name="vSwitch0">
    <portgroup name="VM Network">
      <vlan>0</vlan>
      <nicteaming>
        <policy>
          <failover>yes</failover>
          <loadbalance>srcmac</loadbalance>
          <active>vmnic0,vmnic1</active>
        </policy>
      </nicteaming>
    </portgroup>
  </vswitch>
</config>

Trap 1: Change the VLAN ID to 100.

VLAN does not affect load balancing.

Trap 2: Enable failover on the port group.

Failover is already enabled.

Trap 3: Set one NIC as active and the other as standby.

This would reduce throughput.

Study all Configure and Manage vSphere Networking common traps →

A
Change the VLAN ID to 100.
Why wrong: VLAN does not affect load balancing.
B
Enable failover on the port group.
Why wrong: Failover is already enabled.
C
Change the load balancing policy to Route based on IP hash.
IP hash provides better distribution.
D
Set one NIC as active and the other as standby.
Why wrong: This would reduce throughput.

Full breakdown with real-world context →

Question 13mediummulti select

Read the full Configure and Manage vSphere Networking explanation →

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

Trap 1: Each ESXi host must have a dedicated vDS.

One vDS can be shared across hosts.

Trap 2: The vDS must have at least one uplink.

NIOC does not require uplinks.

Trap 3: The physical switches must support LACP.

LACP is not required for NIOC.

Study all Configure and Manage vSphere Networking common traps →

A
All ESXi hosts in the cluster must be connected to the same vDS.
NIOC is configured on the vDS.
B
Each ESXi host must have a dedicated vDS.
Why wrong: One vDS can be shared across hosts.
C
The vDS must have at least one uplink.
Why wrong: NIOC does not require uplinks.
D
The vSphere license must be Enterprise Plus.
NIOC is an Enterprise Plus feature.
E
The physical switches must support LACP.
Why wrong: LACP is not required for NIOC.

Full breakdown with real-world context →

Question 14hardmulti select

Read the full Configure and Manage vSphere Networking explanation →

Which THREE are valid methods to isolate and secure management traffic on a vSphere Distributed Switch? (Choose three.)

Trap 1: Enable Route based on IP hash on the management port group.

Load balancing does not isolate.

Trap 2: Use Private VLANs on the management port group.

PVLANs are for VM isolation, not management.

Study all Configure and Manage vSphere Networking common traps →

A
Enable Route based on IP hash on the management port group.
Why wrong: Load balancing does not isolate.
B
Assign a specific VLAN ID to the management port group.
VLANs provide isolation.
C
Use Private VLANs on the management port group.
Why wrong: PVLANs are for VM isolation, not management.
D
Configure the ESXi firewall to restrict management access.
Firewall rules control access.
E
Create a dedicated VMkernel port group for management.
Dedicated port groups isolate traffic.

Full breakdown with real-world context →

Question 15hardmultiple choice

Review the full routing breakdown →

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?

Trap 1: Disable LACP on the physical switches and configure the vDS with…

Disabling LACP would remove the MLAG benefits.

Trap 2: Add a third physical NIC to each host and configure it as a standby…

Does not address the root cause.

Trap 3: Change the vDS teaming policy to 'Use explicit failover order' with…

Would not leverage the MLAG.

Study all Configure and Manage vSphere Networking common traps →

A
Disable LACP on the physical switches and configure the vDS with 'Route based on originating virtual port' only.
Why wrong: Disabling LACP would remove the MLAG benefits.
B
Add a third physical NIC to each host and configure it as a standby uplink.
Why wrong: Does not address the root cause.
C
Change the vDS teaming policy to 'Use explicit failover order' with vmnic0 active and vmnic1 standby.
Why wrong: Would not leverage the MLAG.
D
Configure the vDS with LACP support and set the teaming policy to 'Route based on IP hash'.
This aligns the vDS with the physical LAG.

Full breakdown with real-world context →

Question 16easymulti select

Read the full Configure and Manage vSphere Networking explanation →

An administrator is configuring a vSphere distributed switch. Which TWO are valid uplink teaming policies? (Choose two.)

Trap 1: Explicit failover order

Failover policy, not load balancing.

Trap 2: Route based on MAC hash

Valid but not listed in this scenario.

Trap 3: Route based on round robin

Not a valid VMware policy.

Study all Configure and Manage vSphere Networking common traps →

A
Explicit failover order
Why wrong: Failover policy, not load balancing.
B
Route based on MAC hash
Why wrong: Valid but not listed in this scenario.
C
Route based on round robin
Why wrong: Not a valid VMware policy.
D
Route based on physical NIC load
Valid load balancing policy.
E
Route based on IP hash
Valid load balancing policy.

Full breakdown with real-world context →

Question 17hardmultiple choice

Open the full VLAN trunking answer →

A company runs a three-tier application on vSphere 7.0. The web tier uses VLAN 100, app tier VLAN 200, and database tier VLAN 300. Each tier is on a separate port group on a vSphere distributed switch. The environment uses Network I/O Control (NIOC) with shares set to: Web (50), App (30), Database (20). The physical uplinks are two 10 GbE NICs in a team. Recently, the database team reports slow performance during peak hours. The network team checks the physical switches and finds no congestion. The ESXi host shows the two uplinks are heavily utilized with many dropped packets on the database port group. The administrator suspects that the database traffic is being starved by other traffic. Which action should the administrator take to resolve the issue?

A. Increase the number of physical uplinks to four 10 GbE NICs. B. Change the NIOC shares to Web (10), App (30), Database (60). C. Create a separate vSphere standard switch for the database tier. D. Enable SR-IOV on the physical NICs and assign virtual functions to database VMs.

Trap 1: Create a separate vSphere standard switch for the database tier.

Unnecessary; NIOC applies at the distributed switch level.

Trap 2: Enable SR-IOV on the physical NICs and assign virtual functions to…

Complex and not for bandwidth prioritization.

Trap 3: Increase the number of physical uplinks to four 10 GbE NICs.

Does not address prioritization; may still result in starvation.

Study all Configure and Manage vSphere Networking common traps →

A
Create a separate vSphere standard switch for the database tier.
Why wrong: Unnecessary; NIOC applies at the distributed switch level.
B
Enable SR-IOV on the physical NICs and assign virtual functions to database VMs.
Why wrong: Complex and not for bandwidth prioritization.
C
Increase the number of physical uplinks to four 10 GbE NICs.
Why wrong: Does not address prioritization; may still result in starvation.
D
Change the NIOC shares to Web (10), App (30), Database (60).
Increases database shares, giving it higher priority.

Full breakdown with real-world context →

Question 18mediumdrag order

Read the full Configure and Manage vSphere Networking explanation →

Order the steps to perform a vMotion migration of a powered-on virtual machine.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: Select migration type, Verify prerequisites, Initiate migration,…

Incorrect because prerequisites must be checked before selecting the migration type; the wizard prompts for prerequisites verification after initiation, not before.

Trap 2: Initiate migration, Choose destination, Select migration type,…

Incorrect because the migration type must be chosen before selecting the destination, and prerequisites are checked at the start, not after choosing the destination.

Trap 3: Confirm settings, Initiate migration, Verify prerequisites, Choose…

Incorrect because confirmation happens last; you cannot initiate migration before verifying prerequisites or selecting destination and type.

Study all Configure and Manage vSphere Networking common traps →

A
Verify prerequisites, Initiate migration, Select migration type, Choose destination, Confirm settings
This is the correct sequence: first ensure compatibility, then start the migration wizard, pick vMotion, specify the target host, and finalize.
B
Select migration type, Verify prerequisites, Initiate migration, Choose destination, Confirm settings
Why wrong: Incorrect because prerequisites must be checked before selecting the migration type; the wizard prompts for prerequisites verification after initiation, not before.
C
Initiate migration, Choose destination, Select migration type, Verify prerequisites, Confirm settings
Why wrong: Incorrect because the migration type must be chosen before selecting the destination, and prerequisites are checked at the start, not after choosing the destination.
D
Confirm settings, Initiate migration, Verify prerequisites, Choose destination, Select migration type
Why wrong: Incorrect because confirmation happens last; you cannot initiate migration before verifying prerequisites or selecting destination and type.

Full breakdown with real-world context →

Question 19mediumdrag order

Read the full Configure and Manage vSphere Networking explanation →

Order the steps to enable vSphere HA on a cluster.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Trap 1: Step 1: Select the cluster, Step 2: Enable vSphere HA, Step 3:…

This is incorrect because you cannot enable vSphere HA before accessing the HA settings; the enable option is only available within the settings page.

Trap 2: Step 1: Access HA settings, Step 2: Select the cluster, Step 3:…

This is incorrect because you must first select the cluster before you can access its HA settings; the cluster must be highlighted or selected in the inventory.

Trap 3: Step 1: Select the cluster, Step 2: Configure HA options, Step 3:…

This is incorrect because you cannot configure HA options before enabling vSphere HA; the options are greyed out until HA is enabled.

Study all Configure and Manage vSphere Networking common traps →

A
Step 1: Select the cluster, Step 2: Access HA settings, Step 3: Enable vSphere HA, Step 4: Configure HA options, Step 5: Confirm changes
This order follows the standard VMware vSphere HA setup procedure: first select the cluster to apply HA, then access its settings, enable HA, configure specific options like admission control and monitoring, and finally confirm to apply the changes.
B
Step 1: Select the cluster, Step 2: Enable vSphere HA, Step 3: Access HA settings, Step 4: Configure HA options, Step 5: Confirm changes
Why wrong: This is incorrect because you cannot enable vSphere HA before accessing the HA settings; the enable option is only available within the settings page.
C
Step 1: Access HA settings, Step 2: Select the cluster, Step 3: Enable vSphere HA, Step 4: Configure HA options, Step 5: Confirm changes
Why wrong: This is incorrect because you must first select the cluster before you can access its HA settings; the cluster must be highlighted or selected in the inventory.
D
Step 1: Select the cluster, Step 2: Configure HA options, Step 3: Access HA settings, Step 4: Enable vSphere HA, Step 5: Confirm changes
Why wrong: This is incorrect because you cannot configure HA options before enabling vSphere HA; the options are greyed out until HA is enabled.

Full breakdown with real-world context →

Question 20mediummatching

Read the full Configure and Manage vSphere Networking explanation →

Match each vSphere feature to its correct description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Distributes VM workloads across hosts based on resource usage

Provides continuous availability by maintaining a secondary VM

Migrates VM storage without downtime

Powers hosts on/off to save energy based on demand

Standardizes host configuration across a cluster

Trap 1: vMotion: Provides automatic restart of VMs after host failure

This describes HA, not vMotion. vMotion is live migration.

Trap 2: HA: Enables live migration of running VMs

This describes vMotion, not HA. HA handles failover, not migration.

Study all Configure and Manage vSphere Networking common traps →

A
vMotion: Enables live migration of running virtual machines with zero downtime
vMotion migrates running VMs between hosts without interruption.
B
HA: Provides automatic restart of virtual machines in case of host failure
HA restarts VMs on healthy hosts after a host failure.
C
DRS: Distributes and balances workloads across hosts based on resource usage
DRS uses vMotion to balance compute resources in a cluster.
D
FT: Provides continuous availability by maintaining a secondary VM in lockstep
FT creates a shadow VM that instantly takes over if the primary fails.
E
vMotion: Provides automatic restart of VMs after host failure
Why wrong: This describes HA, not vMotion. vMotion is live migration.
F
HA: Enables live migration of running VMs
Why wrong: This describes vMotion, not HA. HA handles failover, not migration.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Configure and Manage vSphere Networking sessions

Start a Configure and Manage vSphere Networking only practice session

Every question in these sessions is drawn from the Configure and Manage vSphere Networking domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Configure and Manage vSphere Networking questions →Mixed VCP-DCV session

Frequently asked questions

What does the VCP-DCV exam test about Configure and Manage vSphere Networking?: Configure and Manage vSphere Networking questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Configure and Manage vSphere Networking questions in a focused session?: Yes — the session launcher on this page draws every question from the Configure and Manage vSphere Networking domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other VCP-DCV topics?: Use the topic links above to move to related areas, or go back to the VCP-DCV question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the VCP-DCV exam covers. They are not copied from any real exam or dump site.

Configure and Manage vSphere Networking only

10 questions 20 questions 30 questions 50 questions

Mixed VCP-DCV session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All VCP-DCV questions Configure and Manage vSphere Networking domain overview VCP-DCV exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Configure and Manage vSphere Networking practice questions

What to know about Configure and Manage vSphere Networking

Common Configure and Manage vSphere Networking exam traps

Configure and Manage vSphere Networking questions

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

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?

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?

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?

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?

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?

Exhibit

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?

Exhibit

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

Which THREE are valid methods to isolate and secure management traffic on a vSphere Distributed Switch? (Choose three.)

An administrator is configuring a vSphere distributed switch. Which TWO are valid uplink teaming policies? (Choose two.)

Order the steps to perform a vMotion migration of a powered-on virtual machine.

Order the steps to enable vSphere HA on a cluster.

Match each vSphere feature to its correct description.

Track your progress over time

Start a Configure and Manage vSphere Networking only practice session

Related VCP-DCV topic practice pages

vSphere Architecture, Products and Solutions practice questions