CWNA-109: Wireless Fundamentals During the 2026 Transition

An organization installs new access points across three office floors and assumes the wireless network will improve because the hardware supports higher theoretical throughput. Instead, voice calls drop near the elevators, conference rooms become slow when full, and clients cling to distant access points after moving between rooms. None of these problems can be solved reliably by choosing the most expensive radio. Certified Wireless Network Administrator (CWNA) skills begin with the physics, protocol behavior, and measurement practices that explain why a WLAN works—or fails—in a particular building. The CWNA-109 exam belongs to that wireless engineering foundation.

CWNP released CWNA-110 on September 29, 2026 and states that CWNA-109 remains available through December 31, 2026. The overlap matters: the older test is not yet unbookable, but its blueprint must not be confused with the newly released version. CWNA-109 assesses transferable knowledge in radio-frequency behavior, antennas, 802.11 architecture, client association, security, deployment, and fault analysis. Candidates choosing a test date should use the objectives for that exact version and confirm availability with CWNP.

Start with RF behavior, not vendor signal bars

Wireless signals change as they pass through walls, reflect from surfaces, encounter interference, and share a channel with other transmitters. Received signal strength matters, but throughput depends on signal quality, available airtime, modulation, client capabilities, and competing traffic. A client reporting a strong signal can still deliver poor performance if neighboring access points occupy the same channel or the environment has substantial non-Wi-Fi interference. Distinguish signal level, noise floor, signal-to-noise ratio, and actual packet behavior. A superficial “full bars” measurement does not tell an administrator whether the radio path is useful for a time-sensitive application.

Link-budget reasoning explains why access-point power is not a universal cure. Antenna gain shapes energy distribution; antenna orientation and polarization affect coverage; attenuation and path loss change with frequency and material. Higher transmit power can create an asymmetric link where the access point reaches the client but the client cannot transmit a reliable response. Ceiling placement, metal shelving, glass, and dense meeting spaces complicate textbook assumptions. Wireless channel management must account for the environment: the same configuration can behave differently in an open office, warehouse, and hospital corridor.

Choose bands and channel widths for airtime, not a headline rate

The 2.4 GHz band offers different coverage and interference characteristics from 5 GHz and 6 GHz deployments. A wider channel can increase peak throughput under favorable conditions while reducing the number of nonoverlapping channels available for neighboring cells. In a crowded environment, narrower channels may allow more predictable reuse and better aggregate service even when one speed test looks slower. Channel planning must account for local regulatory rules, supported client devices, DFS behavior where relevant, and the kinds of applications sharing the air. Do not assume every device supports every band or every Wi-Fi generation advertised by the controller.

Airtime fairness is another practical consideration. A slow client at the edge of coverage may consume disproportionate airtime to move a modest amount of data, affecting faster clients sharing the medium. Retransmissions caused by interference can make utilization appear high without increasing useful throughput. Administrators should distinguish data rate from application goodput, and judge channel plans by client experience and spectrum observations. Selecting Wi-Fi bands and channels requires testing how different channel widths perform under actual client load, not relying only on memorized channel tables.

Understand the 802.11 connection lifecycle

A client does not join a WLAN simply because it sees an SSID. Scanning and discovery, authentication, association, security negotiation, IP configuration, and application connectivity are separate stages. A wireless device may associate successfully but fail because the VLAN mapping is wrong, DHCP offers cannot reach it, or identity policy rejects authorization. BSS and ESS concepts describe how clients observe and move through access-point service areas. Controller-based and autonomous deployments distribute management functions differently, yet the client still needs compatible protocol behavior at the radio and network layers.

Management, control, and data frames perform different work. Beacons advertise network capabilities, while association exchanges establish how a client participates; a successful exchange at one stage does not prove later encryption, routing, or DNS is functioning. When investigating failure, capture the stage where progress stopped rather than changing every WLAN setting in sequence. A client failing to obtain an address after successful association has a different investigation path from one unable to authenticate. The basic service set model helps place these events in context, especially in environments with multiple access points advertising the same network identity.

Design roaming around continuity and client behavior

Roaming is largely a client decision informed by signal conditions, supported assistance mechanisms, and policy. A client may remain on a weaker access point because its roaming algorithm prioritizes stability, because neighboring candidates are poorly advertised, or because the current connection is just good enough to avoid a transition. Administrators can influence behavior through RF design, minimum data-rate policy, transmit power, client steering features, and supported 802.11 enhancements, but cannot assume a controller can force every client to behave identically. The right objective is to maintain acceptable application service during movement, not merely to record that a client changed association.

Real-time voice reveals roaming weakness quickly. Examine cell overlap, authentication delay, VLAN and policy consistency, handoff timing, and what happens to active sessions. A roaming problem can also be a network problem if the user moves into a different IP domain unexpectedly. Avoid interpreting every brief retransmission as a failed roam, and distinguish a client disconnect caused by authentication from one caused by RF coverage. A substantive understanding of wireless roaming behavior lets a candidate reason from user experience to protocol stage without relying on a particular vendor dashboard's terminology.

Use 802.11 security without treating encryption as complete access control

Wireless security involves authentication, key management, cipher protection, and the separate authorization that decides what an authenticated device may reach. Enterprise 802.1X deployments commonly rely on an authentication server and credential or certificate policy; personal network modes use different trust assumptions. The security mode must be compatible with clients and suitable for the environment, particularly where legacy IoT devices cannot support modern enterprise features. A shared network password may encrypt traffic but does not provide the same accountability as identifying users or devices individually. A captive portal alone is not a substitute for robust authentication and encryption at the link layer.

802.1X failures need methodical investigation. Did the client reach the authenticator? Did the RADIUS server receive and process the request? Was a certificate trusted? Did authorization place the client into the intended network? Each failure produces different evidence. Do not solve an authentication problem by temporarily opening an unrestricted WLAN without assessing the risk. 802.1X authentication and access policy work together: a wireless client may have perfect RF connectivity while its identity never receives the rights needed to use the network.

Plan site surveys around applications and failure boundaries

A predictive design uses floor plans, building materials, anticipated clients, application requirements, and estimated interference to propose access-point locations. A measured survey tests those assumptions in the actual environment. Pre-deployment surveys and post-deployment validation serve different purposes; the former guides design, while the latter proves coverage and performance under realistic operating conditions. Note where users work, move, congregate, and use latency-sensitive services. A conference center has different density needs from a corridor even when both occupy the same floor area. Survey methods and acceptance criteria should reflect the workload.

Document measurements with location and context. Signal strength, SNR, channel occupancy, supported data rates, client throughput, retry behavior, and actual application performance can all matter, but their relevance depends on the design target. A good report differentiates a coverage gap from an airtime-capacity problem. If moving an access point improves one room while causing a weak area elsewhere, the site-survey record should show that tradeoff. Building the wrong network beautifully is not a success; testing whether the original service requirements were met is the administrator's responsibility.

Troubleshoot the entire WLAN service path

Start with the user's complaint and a reproducible symptom. If one device fails, examine its radio capabilities, credentials, drivers, and local configuration. If all users on one access point fail, examine that access point's power, uplink, controller relationship, VLAN behavior, and policy. If an entire site slows at predictable times, inspect RF occupancy and upstream congestion before modifying client settings. Tools such as spectrum analysis, protocol captures, client logs, and controller telemetry answer different questions. Avoid using a general throughput test as the only acceptance measure for a voice or industrial-control network.

Study CWNA-109 by building a small deployment with two access points and several distinct clients, then experiment with channel width, placement, security method, and client movement. Record what changes and what remains stable. Compare the historical CWNA-109 objectives with the new CWNA-110 outline rather than assuming the versions are interchangeable. CWNP positions CWNA as a foundation for more specialized design, security, and analysis credentials. The enduring competence is the ability to connect RF observations, 802.11 behavior, wired infrastructure, and application outcomes in a defensible explanation of wireless performance.