How is traffic handled in a Cisco Mobility Express environment?

Why the Answer Is Correct

Mobility Express is fundamentally built on the FlexConnect model, where one AP acts as the master controller while all APs switch client data traffic locally at the access layer. Control-plane functions such as management, RF management, and client authentication are centralized on the master controller AP. This design reduces latency and backhaul load by keeping data traffic on the local network segment. Community comment [1] correctly notes that Mobility Express is "based on Flexconnect (central auth with local switching)," and comment [2] concisely summarizes it as "Centrally controlled, locally switched."

Why the Other Options Are Wrong

Option A incorrectly states that data traffic is switched centrally by the controller, which describes a traditional local-mode or centralized data-plane deployment rather than Mobility Express. Option C suggests that control traffic and authentication are handled locally by each AP, which contradicts the centralized management model that Mobility Express provides through its master controller. Option D reverses the architecture entirely, claiming local control with centralized data switching, which does not match any standard Cisco wireless deployment mode. These distractors test whether candidates can clearly separate control-plane and data-plane responsibilities.

Community Comment Notes

All five comments unanimously agree on answer B, with comment [1] providing the key insight linking Mobility Express to FlexConnect. Comment [4] helpfully breaks down the split: "Control traffic/client authentication → centrally by the controller. Data traffic → locally by the access points," making the concept easy to memorize. Comment [3] shares a Cisco FAQ PDF that reinforces the official documentation supporting this architecture.