352-001 · Question #251
You are designing an 802.11 wireless network to include a controller as a central configuration point and access points across several remote sites. Which two aspects will manage the flow of the…
The correct answer is B. Layer 3 roaming is not supported for locally switched WLANs. E. WLAN access lists can be applied only to centrally switched WLANs. In a Cisco WLC-based design with remote APs using local switching, key traffic-flow constraints include the lack of Layer 3 roaming support and the restriction of WLAN access lists to centrally switched WLANs only.
Question
You are designing an 802.11 wireless network to include a controller as a central configuration point and access points across several remote sites. Which two aspects will manage the flow of the traffic to meet these design considerations? (Choose two.)
Options
- AWLAN local switching with VLAN mapping requires that VLAN ID that is mapped on the AP to match
- BLayer 3 roaming is not supported for locally switched WLANs.
- CThe 802.1x authentication for a client associated to an AP on a locally switched WLAN is always
- DThe access point can receive multicast traffic in the form of multicast packets from the WLC.
- EWLAN access lists can be applied only to centrally switched WLANs.
How the community answered
(37 responses)- A8% (3)
- B84% (31)
- C3% (1)
- D5% (2)
Why each option
In a Cisco WLC-based design with remote APs using local switching, key traffic-flow constraints include the lack of Layer 3 roaming support and the restriction of WLAN access lists to centrally switched WLANs only.
While VLAN ID consistency is required for local switching, this statement describes a configuration prerequisite rather than a traffic-flow design consideration that distinguishes local from central switching behavior.
In a locally switched WLAN, client traffic is switched at the AP and never tunneled back to the WLC, so the WLC cannot maintain the client mobility state required for Layer 3 roaming handoffs between subnets.
The statement is syntactically incomplete as presented and does not fully describe a valid or distinguishing design constraint for locally switched WLANs.
In FlexConnect local-switching mode, multicast traffic handling differs from centralized switching - APs do not simply receive standard multicast packets from the WLC for locally switched clients, making this statement technically inaccurate.
WLAN access lists rely on the WLC inspecting and filtering traffic through a centrally switched data path; locally switched traffic bypasses the WLC data plane entirely, making per-WLAN ACL enforcement impossible for those WLANs.
Concept tested: Cisco FlexConnect locally switched WLAN traffic flow limitations
Source: https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-8/b_FlexConnect_Deployment_Guide.html
Topics
Community Discussion
No community discussion yet for this question.