The answer is that the physical switches must be configured with link aggregation, either through LACP or a static EtherChannel. This is required because the VDS IP hash load balancing policy distributes traffic based on a hash of source and destination IP addresses, which can cause out-of-order packets if the switch ports are not grouped into a single logical link; the EtherChannel or LACP bundle ensures the switch treats the multiple uplinks as one aggregated connection, preserving frame ordering. On the VMware Certified Professional Data Center Virtualization VCP-DCV exam, this question tests your understanding that IP hash is a source-based load-balancing method that demands switch-side coordination—a common trap is assuming ESXi must also run LACP, but the VDS itself only needs the IP hash policy selected. Remember the tip: “IP hash needs a switch hash”—if you see IP hash, think EtherChannel or LACP on the physical side, not on the host.
VCP-DCV vSphere Architecture, Products and Solutions Practice Question
This VCP-DCV practice question tests your understanding of vsphere architecture, products and solutions. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company's vSphere environment consists of four ESXi hosts, each with two 10 GbE physical NICs. The administrator configures a VDS with two dvUplinks and uses load-balancing policy 'Route based on IP hash'. To use IP hash, what additional configuration is required on the physical switches?
Why wrong: VLAN trunking is needed for VLANs but not specific to IP hash.
B
Configure LACP on the VDS uplink port groups
Why wrong: LACP can be used on VDS, but the physical switch must also be configured; the question asks for additional configuration on physical switches.
C
Configure link aggregation (LACP or static EtherChannel) on the switch ports
IP hash load balancing requires an aggregated link on the physical switch side.
D
Enable IGMP snooping on the switch
Why wrong: IGMP snooping is for multicast traffic, not load balancing.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure link aggregation (LACP or static EtherChannel) on the switch ports
Option C is correct because IP hash requires Link Aggregation Control Protocol (LACP) or static EtherChannel to be configured on the physical switch ports. Option A is not required because VLAN trunking is already configured. Option B is incorrect because IGMP snooping is for multicast, not required. Option D is incorrect because ESXi itself does not need LACP configuration on the VDS (though it can use LACP), but the physical switch must have EtherChannel.
Key principle: A trunk being up does not mean the VLAN is allowed across it. Always verify the allowed VLAN list and whether the VLAN exists on both switches.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Enable VLAN trunking on the switch ports
Why it's wrong here
VLAN trunking is needed for VLANs but not specific to IP hash.
✗
Configure LACP on the VDS uplink port groups
Why it's wrong here
LACP can be used on VDS, but the physical switch must also be configured; the question asks for additional configuration on physical switches.
✓
Configure link aggregation (LACP or static EtherChannel) on the switch ports
Why this is correct
IP hash load balancing requires an aggregated link on the physical switch side.
Related concept
Access ports place end devices into a single VLAN.
✗
Enable IGMP snooping on the switch
Why it's wrong here
IGMP snooping is for multicast traffic, not load balancing.
Common exam traps
Common exam trap: an active trunk can still block the VLAN you need
A trunk being up does not prove every VLAN is crossing it. Check allowed VLAN lists, native VLAN mismatch, VLAN existence and access-port assignment.
Detailed technical explanation
How to think about this question
VLAN questions usually combine access-port and trunking clues. The key is to identify whether the issue is local to one switchport, caused by the trunk, or caused by the VLAN not existing where it needs to exist.
KKey Concepts to Remember
Access ports place end devices into a single VLAN.
Trunk ports carry multiple VLANs between switches.
Allowed VLAN lists decide which VLANs can cross a trunk.
Native VLAN mismatch can create confusing symptoms.
TExam Day Tips
→Use show vlan brief to verify access VLANs.
→Use show interfaces trunk to verify trunk state and allowed VLANs.
→Do not treat every same-VLAN issue as a routing problem.
Key takeaway
A trunk being up does not mean the VLAN is allowed across it. Always verify the allowed VLAN list and whether the VLAN exists on both switches.
Real-world example
How this comes up in practice
A help-desk technician troubleshoots why a newly connected PC cannot reach shared printers on the same floor. The cable is good, the switch port is active, but the PC is in VLAN 20 and the printers are in VLAN 10. The uplink trunk only allows VLAN 10. A trunk being up does not mean every VLAN crosses it.
What to study next
Got this wrong? Here's your next step.
Review VLAN allowed lists, native VLAN mismatch detection, and how to verify VLAN membership with show vlan brief and show interfaces trunk. Then practise related VCP-DCV questions on switching, trunking, and access-port configuration.
vSphere Architecture, Products and Solutions — This question tests vSphere Architecture, Products and Solutions — Access ports place end devices into a single VLAN..
What is the correct answer to this question?
The correct answer is: Configure link aggregation (LACP or static EtherChannel) on the switch ports — Option C is correct because IP hash requires Link Aggregation Control Protocol (LACP) or static EtherChannel to be configured on the physical switch ports. Option A is not required because VLAN trunking is already configured. Option B is incorrect because IGMP snooping is for multicast, not required. Option D is incorrect because ESXi itself does not need LACP configuration on the VDS (though it can use LACP), but the physical switch must have EtherChannel.
What should I do if I get this VCP-DCV question wrong?
Review VLAN allowed lists, native VLAN mismatch detection, and how to verify VLAN membership with show vlan brief and show interfaces trunk. Then practise related VCP-DCV questions on switching, trunking, and access-port configuration.
What is the key concept behind this question?
Access ports place end devices into a single VLAN.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This VCP-DCV practice question is part of Courseiva's free VMware certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the VCP-DCV exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.