A customer requires multiple VLANs on an HPE campus network. Which configuration is essential on the switch interfaces connected to other switches to ensure VLAN traffic passes through?

Question

Options

• AConfigure the interfaces as access ports
• BEnable LACP on the interfaces
• CSet the interfaces as trunk ports
• DEnable DHCP relay on the interfaces

• A
  5% (2)
• B
  3% (1)
• C
  89% (33)
• D
  3% (1)

Explanation

Trunk ports carry traffic for multiple VLANs simultaneously between switches by tagging frames with 802.1Q VLAN IDs, making them essential on inter-switch links in a multi-VLAN environment. Without trunking, a switch-to-switch link would only pass traffic for a single VLAN, siloing the rest.

Why the distractors are wrong:

• A (Access ports): Access ports carry traffic for only one VLAN and strip the 802.1Q tag - they're for end devices (PCs, printers), not inter-switch links carrying multiple VLANs.
• B (LACP): LACP is a link aggregation protocol for bundling physical links into one logical channel for bandwidth/redundancy - it has nothing to do with VLAN propagation.
• D (DHCP relay): DHCP relay forwards DHCP requests across Layer 3 boundaries; it's a routing function, not a mechanism for passing VLAN traffic between switches.

Memory tip: Think "Trunk = Transit for Tags" - a trunk port is the highway between switches where every VLAN's tagged traffic can travel freely, while an access port is the off-ramp for a single VLAN at the end destination.

No community discussion yet for this question.