Cisco Certified Network Associate (CCNA) 200-301 · Free study guide

Objective 2.6 — Describe wireless architectures and AP modes

Wireless architecture determines where AP configuration, control, forwarding, and monitoring occur. AP mode determines the job a specific radio or device is performing inside that architecture.

Autonomous access points

An autonomous AP holds local configuration and makes many local control decisions. It can fit small or isolated designs but requires consistent management as the fleet grows. Changes and assurance are spread across devices unless another tool coordinates them.

Controller-based wireless

Lightweight APs join a wireless LAN controller that centralizes compatible WLAN policy, RF decisions, software, and telemetry. AP-to-controller control traffic and client data forwarding depend on the selected mode and design. Some traffic may tunnel to the controller; some modes can switch client traffic locally.

A controller is a critical management and control dependency, so designs address reachability, redundancy, identity, and recovery. Centralized does not mean every function happens on one physical box.

Cloud-managed wireless

Cloud-managed APs communicate with a provider-hosted management plane. Local client forwarding can continue according to product behavior while configuration and telemetry use the cloud service. Internet dependency, administrator identity, licensing, logging, data location, and failure behavior are part of the design.

Common AP modes

Local mode commonly serves clients under controller policy. FlexConnect supports remote-site designs and can switch selected traffic locally. Monitor mode focuses on RF observation rather than ordinary client service. Sniffer mode captures 802.11 traffic for analysis. Other specialized modes support bridging, rogue detection, or sensor functions depending on platform.

Match the mode to the operational requirement. An AP dedicated to monitoring is not an extra client-serving cell, and a sniffer needs a capture destination and analysis workflow.

Worked scenario

A branch has limited WAN capacity and needs local user traffic to remain local while policy is centrally managed. A controller-based design with an appropriate remote-site mode can fit better than tunneling every client packet to headquarters. The design still needs a defined behavior for controller or WAN loss.

Verification questions

Identify where configuration is stored, how an AP discovers and authenticates its manager, where client frames are forwarded, which services survive a control- plane outage, and which mode each radio uses. Use controller or cloud inventory, AP join state, tunnel state, and client-path evidence.

Common traps

• Treating controller-based as synonymous with centralized data forwarding.
• Expecting a monitor-mode AP to serve clients normally.
• Ignoring cloud management identity and outage behavior.
• Naming an AP mode without explaining its traffic path.
• Assuming autonomous means unmanaged.

Readiness checklist

• I can compare autonomous, controller, and cloud management.
• I can match common AP modes to their jobs.
• I trace control and client data separately.
• I include failure behavior in an architecture choice.