CWDP-305 practice question 20 of 35

When selecting a centralized WLAN architecture, what new problem may arise when you change the data forwarding model from centralized to distributed? Response:

Full set: 341 questions

Domain WLAN Design Troubleshooting

Answer options
A: Centralized control functions, such as key management and distribution, RRM, and load balancing will no longer be supported.
B: The router between the APs and the controller must be made aware of the APs as forwarding client STAs.
C: APs that were designed for a centralized forwarding model may not support all features in distributed forwarding mode. Correct answer
D: All RRM controls will also need to be distributed to a master AP that acts as a channel and transmit power arbiter for other APs in the ESS.
Correct Answer:
C. APs that were designed for a centralized forwarding model may not support all features in distributed forwarding mode.
Explanation

When changing from a centralized to a distributed data forwarding model within a centralized WLAN architecture, the data plane processing shifts from the controller to the individual access points. APs typically have less processing power and memory compared to a dedicated WLAN controller. Consequently, some advanced features that rely on the controller's resources for tasks like deep packet inspection, complex quality of service (QoS) policies, or stateful firewalling may not be supported when the AP forwards data locally. The feature set available in distributed mode is often a subset of what is available in a fully centralized forwarding model.

Why Incorrect

A. Control plane functions like RRM, key management, and load balancing remain centralized at the controller; this is a fundamental characteristic of this architecture, regardless of the data forwarding model.
B. Routers operate at the network layer (Layer 3) and forward packets based on IP addresses. They do not require special awareness of an AP's data forwarding role.
D. This describes a controller-less (distributed control) architecture, not a centralized control architecture with distributed data forwarding. The central controller still manages RRM. ---

References

1. CWNP. (2021). CWDP-304 Certified Wireless Design Professional Official Study Guide. Chapter 3: WLAN Architecture, Section: "Distributed Data Forwarding", pp. 98-100.

The guide explains that in a distributed data forwarding model, "the AP is responsible for more of the 802.11-to-802.3 integration... This often means that some features available in the centralized data forwarding model are not available in the distributed data forwarding model."

2. Cisco. (2023). FlexConnect Deployment Guide. Cisco Catalyst 9800 Series Wireless Controllers, IOS XE Cupertino 17.9.x. Section: "Unsupported Cisco WLC Features on FlexConnect APs".

This official vendor documentation provides a specific list of features that are not supported on FlexConnect APs (Cisco's term for distributed data forwarding). Examples include certain security features like "OEAP" and limitations on features like "Multicast-Direct." This directly confirms that not all features are supported in this mode.

3. Westcott, D. (2018). CWNA Certified Wireless Network Administrator Study Guide. 5th Edition. Sybex. Chapter 11: 802.11 Architecture, Section: "Distributed WLAN Architecture", p. 418.

While a CWNA reference, the principle is foundational and covered here. It notes that with distributed data forwarding (also called local bridging), "the data traffic is bridged by the AP from the wireless medium to the local wired network... Some features may not be available when using local bridging." This establishes the concept of feature disparity as a known architectural trade-off.

Scroll to Top