Question 650
At Convention Center, a shared accommodation WLAN gateway leaks inter-client traffic on a common broadcast domain. Which diagnostic comparison would distinguish this fault from nearby mechanisms?
Explanation
Correct Answer
For Convention Center, the decisive mechanism is Private client isolation. Client isolation can block same-segment lateral traffic without relying on routing ACLs. Inspect the actual local-bridge or gateway data path and peer-to-peer traffic is the most direct way to isolate this particular failure before making a change.
Incorrect Answers
This is relevant to Tagged trunk allowlist, where a VLAN trunk forwards only permitted tagged VLANs and its native VLAN according to configuration In the Convention Center case, Those observations could be normal while the stated fault persists. The specific mechanism is client isolation can block same-segment lateral traffic without relying on routing ACLs
This is relevant to Native VLAN mismatch, where a native VLAN defines forwarding for untagged frames on a VLAN-aware trunk In the Convention Center case, Those observations could be normal while the stated fault persists. The specific mechanism is client isolation can block same-segment lateral traffic without relying on routing ACLs
This is relevant to Access VLAN classification, where an access port carries untagged frames in one configured access VLAN In the Convention Center case, Those observations could be normal while the stated fault persists. The specific mechanism is client isolation can block same-segment lateral traffic without relying on routing ACLs