Wireless Lan

Wireless LAN — Network Access (20%) Wireless LAN architecture is a consistent multiple-choice topic in the Network Access domain — expect questions on the difference between autonomous and controller-based deployments, how CAPWAP works, and where specific wireless functions live in each architecture. --- ## Why Wireless LAN Matters on the Exam The CCNA blueprint places wireless architecture squarely in the Network Access domain (20% of the exam). While VLANs and STP dominate the simulations, wireless questions are reliable multiple-choice points you can bank. Understanding the architectural split between autonomous APs and controller-based APs — and the role of CAPWAP — is essential. --- ## Core Concepts ### Autonomous vs. Controller-Based Architecture In traditional wireless deployments, every Access Point (AP) was a standalone, self-contained device. These are called autonomous APs (sometimes called "fat APs"). Each one had to be individually configured — its own SSIDs, security settings, channel selection, and radio power. This worked fine for a small office with one or two APs, but it becomes an administrative nightmare at scale. Controller-based architecture solves this by centralizing intelligence. A Wireless LAN Controller (WLC) manages many lightweight APs (also called "thin APs") from a single point. The APs themselves do very little decision-making — they just handle the radio transmissions and hand everything else off to the controller. | Feature | Autonomous AP | Controller-Based (Lightweight AP) | |---|---|---| | Configuration location | Per-AP | Centralized on WLC | | Management overhead | High (per device) | Low (single pane of glass) | | Intelligence | Resides in AP | Resides in WLC | | Scalability | Poor | Excellent | | Typical use case | Small office, home |…