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 1mediummultiple 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 2easymultiple 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 3hardmultiple 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 4mediummultiple 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 5easymultiple 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 6hardmultiple 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 7mediummultiple 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 8hardmultiple 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 9easymultiple 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 10mediummulti 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 11hardmulti 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 12hardmultiple choice

Read the full NAT/PAT explanation →

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 13easymulti 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 14hardmultiple 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 15mediumdrag 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

Question 16mediumdrag 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

Question 17mediummatching

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

Question 18mediummatching

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

Question 19easymultiple choice

Read the full NAT/PAT explanation →

A network administrator notices that all traffic from two VMs connected to the same standard switch port group is going through the same physical uplink, causing congestion. The teaming policy is set to Route based on originating virtual port. What change should the administrator make to distribute traffic more evenly?

Trap 1: Increase the number of uplinks to 4.

More uplinks do not change the distribution based on port ID.

Trap 2: Enable LACP on the standard switch.

LACP is not supported on standard vSwitches.

Trap 3: Change the load balancing policy to Explicit failover order.

Explicit failover order does not distribute traffic dynamically.

Study all Configure and Manage vSphere Networking common traps →

A
Change teaming policy to Route based on IP hash.
Correctly distributes traffic based on IP pairs.
B
Increase the number of uplinks to 4.
Why wrong: More uplinks do not change the distribution based on port ID.
C
Enable LACP on the standard switch.
Why wrong: LACP is not supported on standard vSwitches.
D
Change the load balancing policy to Explicit failover order.
Why wrong: Explicit failover order does not distribute traffic dynamically.

Full breakdown with real-world context →

Question 20mediummultiple choice

Open the full VLAN trunking answer →

An administrator is configuring a distributed switch for a cluster of ESXi hosts. The requirements are: VLAN 100 for production, VLAN 200 for management, and a separate VLAN 300 for vMotion. The management network should be isolated from production traffic. What is the best practice for configuring these networks on the distributed switch?

Trap 1: Create one distributed port group with VLAN 100, and use VLAN…

VLAN tagging on VMs is not used for kernel adapters.

Trap 2: Use standard switches for management and vMotion to avoid…

Distributed switches offer centralized management and advanced features.

Trap 3: Create one distributed port group with VLAN trunk (4095) and use…

VLAN trunk is for guest-level tagging, not for kernel traffic.

Study all Configure and Manage vSphere Networking common traps →

A
Create three separate distributed port groups, each with the appropriate VLAN ID, and assign each VM kernel adapter or VM to the correct port group.
This provides isolation and follows best practices.
B
Create one distributed port group with VLAN 100, and use VLAN tagging on the VMs for management and vMotion.
Why wrong: VLAN tagging on VMs is not used for kernel adapters.
C
Use standard switches for management and vMotion to avoid complexity.
Why wrong: Distributed switches offer centralized management and advanced features.
D
Create one distributed port group with VLAN trunk (4095) and use port-based VLAN filtering on the VMs.
Why wrong: VLAN trunk is for guest-level tagging, not for kernel traffic.
E
Create two port groups: one for production (VLAN 100) and one for management+vMotion (VLAN 200) because vMotion can share VLAN with management.
Why wrong: vMotion should be on a separate VLAN for performance and security.

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

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.

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

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