NetworkingNetwork+

Wireless Network Implementation for CompTIA Network+ N10-009

Wireless network implementation covers the design and deployment of Wi-Fi infrastructure, including access point placement, controller architecture, and roaming. CompTIA Network+ N10-009 tests wireless implementation in Domain 2, requiring knowledge of infrastructure vs ad-hoc modes, autonomous vs controller-based (thin AP) architectures, wireless mesh, and the factors that affect wireless coverage and capacity. These concepts connect directly to the troubleshooting domain.

8 min

3 sections · 7 exam key points

1 practice questions

Wireless Infrastructure Modes

Infrastructure mode: the standard Wi-Fi deployment. Clients connect to a central access point (AP) that connects to the wired network. The AP is the central device — all client-to-client traffic passes through the AP. This creates a star topology at Layer 2. Infrastructure mode is used in homes, offices, and enterprise environments.

Ad-hoc mode (IBSS — Independent Basic Service Set): devices communicate directly with each other without an AP. Peer-to-peer wireless. Limited range, no centralized management, security challenges. Used for temporary connectivity between two devices. Wi-Fi Direct is a modern ad-hoc technology used by printers and display sharing.

BSS (Basic Service Set): one AP and its associated clients, identified by the BSSID (the AP's MAC address). SSID (Service Set Identifier): the network name — the human-readable name clients see. ESS (Extended Service Set): multiple APs with the same SSID creating a seamless wireless network — enables roaming between APs.

Autonomous vs Controller-Based APs

Autonomous (fat) APs: each AP has all intelligence — configuration, security, radio management, and client association handled locally. Suitable for small deployments (home, small office). Each AP must be individually configured — management overhead grows with scale.

Controller-based (thin/lightweight) APs: the AP hardware handles only radio transmission (the 'thin' part). A wireless LAN controller (WLC) centralizes configuration, security policy, roaming, and radio resource management for all APs. All configuration is pushed from the controller. Suitable for enterprise deployments with dozens to thousands of APs. CAPWAP (Control and Provisioning of Wireless Access Points) is the protocol between thin APs and the controller.

Cloud-managed APs: a hybrid approach where APs are managed through a cloud controller (e.g., Cisco Meraki, Ubiquiti UniFi). Configuration is centralized in the cloud — no on-premises controller needed. Provides enterprise management capabilities with reduced infrastructure.

Wireless Mesh and Roaming

Wireless mesh: APs connect to each other wirelessly rather than all requiring a wired ethernet uplink. One or more APs have wired backhaul (root AP); others relay wirelessly (mesh AP). Enables coverage extension without cable runs to every AP location. Used in large venues, outdoor areas, and hard-to-cable buildings.

Roaming: when a client moves between APs in an ESS, it transitions from one AP to another. Good roaming requires all APs to have the same SSID, compatible security settings, and proper overlap (15–20% cell overlap recommended). Fast BSS Transition (802.11r) enables fast roaming by pre-negotiating keys with neighboring APs before the client moves.

Key exam facts — Network+

Infrastructure mode = clients connect to AP; ad-hoc = direct device-to-device
BSS = single AP + clients; ESS = multiple APs with same SSID (enables roaming)
SSID = network name; BSSID = AP's MAC address
Autonomous AP = self-contained; thin AP = managed by WLC via CAPWAP
WLC centralizes AP configuration, security, and radio management
Wireless mesh: APs relay traffic wirelessly — extends coverage without cable to every AP
15–20% cell overlap recommended for seamless roaming

Common exam traps

All APs in an ESS must be physically connected to the same switch

APs in an ESS share the same SSID for roaming, but they can be on different switches or even different VLANs — what matters is matching SSID and security configuration, with controller synchronization in enterprise deployments

A thin AP can operate without a controller

Thin (LWAP) APs depend on the WLC for all configuration and security policy. If the controller is unreachable, thin APs may revert to local mode (limited function) or go offline depending on the deployment

Practice questions — Wireless Implementation

These questions are representative of what you will see on Network+ exams. The correct answer and explanation are shown immediately below each question.

Q1.A company deploys 50 access points across a multi-floor campus and wants centralized management, uniform security policies, and seamless client roaming. Which architecture should be used?

A.50 autonomous fat APs configured individually

B.Wireless LAN Controller with lightweight (thin) APs

C.50 mesh APs with wireless backhaul only

D.Ad-hoc mode between all APs

Explanation: A Wireless LAN Controller (WLC) with lightweight/thin APs provides centralized configuration, uniform security policy, and seamless roaming management across all 50 APs. Autonomous APs require individual configuration — unmanageable at scale. Mesh is a backhaul technology, not a management architecture. Ad-hoc mode is for direct device-to-device connections.

Frequently asked questions — Wireless Implementation

What is CAPWAP?

CAPWAP (Control and Provisioning of Wireless Access Points, RFC 5415) is the standardized protocol used for communication between wireless LAN controllers (WLCs) and lightweight APs. It uses UDP ports 5246 (control) and 5247 (data). CAPWAP encapsulates client data and control messages between the AP and controller, allowing centralized management of distributed APs.

Practice this topic

Network+practice questions

Test yourself on Wireless Implementation

JT Exams routes you to questions in your exact weak areas — automatically, after every session.

Free practice test Start 7-Day Free Trial

No credit card · Cancel anytime