Question 230
The HPE AOS-CX switching case is: An overbroad trunk carries a guest VLAN onto a restricted server aggregation path. Which TWO choices together provide the targeted remedy and independent validation? (Select TWO.)
Explanation
Correct Answers
The targeted correction for An overbroad trunk carries a guest VLAN onto a restricted server aggregation path is: Configure and validate tagged VLAN membership across each uplink and consistent native VLAN treatment where required by the topology. It reduces the risk that a missing tagged VLAN on one hop silently isolates clients, while unintended VLAN allowance bridges security domains.
A separate operational validation for An overbroad trunk carries a guest VLAN onto a restricted server aggregation path is: A hop-by-hop tag trace proves required VLANs pass and disallowed VLANs are absent on all uplinks. It proves intended behavior instead of accepting configuration presence alone.
Incorrect Answers
This alternative concerns vlan access port membership and untagged traffic; its associated risk is: A correct IP address cannot repair wrong VLAN membership, and access ports in unintended VLANs can expose protected resources. The observed case An overbroad trunk carries a guest VLAN onto a restricted server aggregation path requires the more specific vlan trunk tagging and permitted vlan filters control. The targeted action is: Configure and validate tagged VLAN membership across each uplink and consistent native VLAN treatment where required by the topology.
This alternative concerns lacp member selection and load distribution; its associated risk is: A partially formed aggregation can strand traffic or produce surprising throughput because a single flow usually hashes to one member. The observed case An overbroad trunk carries a guest VLAN onto a restricted server aggregation path requires the more specific vlan trunk tagging and permitted vlan filters control. The targeted action is: Configure and validate tagged VLAN membership across each uplink and consistent native VLAN treatment where required by the topology.
This alternative concerns mstp configuration and loop control; its associated risk is: A mismatched MSTP region or unintended root can block critical trunks or increase convergence disruption. The observed case An overbroad trunk carries a guest VLAN onto a restricted server aggregation path requires the more specific vlan trunk tagging and permitted vlan filters control. The targeted action is: Configure and validate tagged VLAN membership across each uplink and consistent native VLAN treatment where required by the topology.