CCNP Architecture Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Mesh networking

  Why it's wrong here

  Mesh networking is designed for outdoor or hard-to-wire environments where Ethernet backhaul is unavailable, but in a high-density indoor office it introduces a wireless backhaul that competes for the same RF spectrum as client traffic. This shared medium increases airtime utilization and latency, and mesh APs often suffer from a throughput penalty known as the 'half-backhaul' effect. Since seamless roaming requires stable, low-latency links between APs and a wired connection, the unpredictable mesh topology and reduced capacity make it a poor fit for this deployment.

• ✗

  Autonomous APs

  Why it's wrong here

  Autonomous APs operate as standalone devices with independent configuration, lacking any centralized controller to coordinate RF parameters, security policies, or client roaming. While they can forward traffic locally, they rely entirely on the client to initiate 802.11 reassociation, which often results in sticky clients and disconnects during movement between APs. Without support for fast roaming mechanisms like 802.11r/k/v (which require controller-based key caching and neighbor lists), autonomous APs cannot provide the smooth, low-latency handoff necessary for high-density indoor roaming and real-time applications.

• ✗

  Centralized switching with a WLC

  Why it's wrong here

  Centralized switching with a WLC tunnels all client data traffic over CAPWAP to the controller, which then bridges it onto the wired network. This hairpin design adds a round-trip latency to every packet and makes the controller a single point of congestion, especially problematic for voice and video in dense environments. Even though the WLC can orchestrate fast roaming and coordinate channels, the data plane latency inherent in centralized switching negates many benefits, and traffic that could be locally exited must unnecessarily traverse the core for every flow, making this architecture less efficient for high-capacity indoor offices.

• ✓

  FlexConnect

  Why this is correct

  FlexConnect is correct because it separates the control plane (which remains with the WLC) from the data plane (which is switched locally at the AP). This allows client traffic to be forwarded directly to the wired network at each access point, avoiding unnecessary latency and controller bottlenecks, which is ideal for high-bandwidth, high-density indoor environments. Furthermore, FlexConnect supports IEEE 802.11r fast roaming and can perform client-based or AP-based neighbor discovery when connected to a WLC, ensuring seamless and fast handoffs as users move across the office. Its design balances centralized management with localized forwarding, offering both the operational consistency of a controller and the performance of distributed switching.