CWNP CWNA-109: Transitioning to the Current CWNA-110 Exam
CWNA-109 is in a transition period rather than simply disappearing overnight. CWNP released CWNA-110 on September 29, 2026 and now identifies it as the current Certified Wireless Network Administrator version, while CWNA-109 remains available only through December 31, 2026. Candidates therefore need to distinguish “still testable” from “current blueprint.”
CWNP CWNA-109 remains relevant for candidates already committed to the previous exam before its final delivery date. Anyone beginning a new study plan should use CWNA-110 objectives and current learning materials because CWNP now lists 110 as the active version.
The role is still enterprise WLAN administration: RF fundamentals, antennas, hardware and software, standards, architecture, security, installation, management, site survey, and troubleshooting.
The CWNP certifications uses CWNA as the base credential for the professional analysis, design, and security certifications. That makes the administrator-level concepts worth learning even when an exam transition is underway.
CWNP now labels CWNA-110 as the current version, released on September 29, 2026, while CWNA-109 remains available only through December 31, 2026. That makes 109 transitional: still deliverable for candidates already committed to it, but no longer the blueprint a new candidate should choose by default.
The certification itself remains the foundational enterprise-Wi-Fi credential in the CWNP program. CWNA is valid for three years, and passing a current professional exam such as CWSP, CWDP, or CWAP before expiration can renew the underlying CWNA. The transition changes the exam version, not CWNA’s role in the certification hierarchy.
Frequency, wavelength, amplitude, signal loss, reflection, refraction, diffraction, absorption, interference, SNR, and channel use explain why WLANs behave differently across physical environments.
The wireless networking fundamentals is useful for refreshing those core relationships.
Version changes may adjust standards emphasis, but an administrator still needs to understand why signal and airtime conditions affect clients.
RF concepts should be applied quantitatively where possible. Understand dB relationships, transmit power, received signal, noise floor, SNR, free-space loss, attenuation, antenna gain, and how changes in distance or materials affect a link. These concepts explain why two clients in the same room can perform differently and why adding transmit power does not automatically repair a poor WLAN.
Antenna behavior also matters. Omnidirectional and directional patterns, polarization, gain, placement, and orientation change where energy goes. The administrator should be able to distinguish a radio problem from an antenna or placement problem before changing channel or power settings.
Know how stations discover networks, associate with access points, authenticate, obtain network configuration, and reach wired services.
WLANs depend on more than the RF link. DHCP, DNS, routing, VLANs, authentication services, controllers, and firewall policy can all create user-visible symptoms.
Administrators should understand the basic 802.11 service architecture and management exchanges well enough to follow a client from discovery through association and data service. SSID, BSSID, station address, AP, distribution system, and controller or management architecture provide the context for interpreting what the client is connected to.
The wired side should be treated as part of the WLAN service. AP uplinks, VLANs, PoE, DHCP, DNS, gateways, authentication servers, and policy enforcement all influence the user experience. A strong wireless administrator can determine where the transition from RF to ordinary IP networking occurs and troubleshoot across that boundary.
Troubleshooting is stronger when the administrator follows the client state rather than assuming every connectivity problem is “Wi-Fi.”
Channel width, band, transmit power, AP density, and client capability interact. Wider channels can improve peak rate while consuming more spectrum.
In dense environments, channel reuse and airtime efficiency can matter more than the maximum theoretical rate of one connection.
The 20, 40, and 80 MHz channel width provides additional context for choosing 20, 40, or 80 MHz according to the environment.
Channel planning should consider available spectrum, regulatory constraints, neighboring networks, AP density, client support, and the trade-off between peak rate and reuse. In high-density environments, narrower channels can create more independent cells and more aggregate airtime than a small number of very wide channels.
Transmit power and channel width should not be tuned independently. Large high-power cells can increase co-channel contention, and mismatched AP/client power can create asymmetric links. The administrator should look for a balanced design where clients can transmit back reliably and neighboring APs can reuse spectrum efficiently.
Administrators should understand personal and enterprise WLAN security, authentication, encryption, credential lifecycle, guest access, and the role of identity services.
Enterprise authentication can introduce RADIUS, EAP methods, certificates, directories, and policy dependencies.
A client that associates successfully but cannot authenticate is a different troubleshooting case from one that cannot discover or join the WLAN at all.
Enterprise security commonly introduces 802.1X, RADIUS, EAP methods, certificates, directories, and policy assignment. Personal security uses a different trust model with shared or individually managed credentials depending on the mechanism. Administrators should understand where authentication fails: client supplicant, AP or controller, RADIUS reachability, certificate trust, identity validation, or authorization policy.
Security also extends beyond encryption. Guest access, segmentation, management-plane protection, rogue-device awareness, credential lifecycle, and firmware hygiene help determine what an authenticated wireless client can actually reach and how the WLAN itself is administered safely.
Site survey work examines floor plans, attenuation, interference, neighboring networks, coverage, capacity, mounting constraints, and wired infrastructure.
Predictive designs are useful, but real measurements can expose material differences in wall loss, interference, or device behavior.
Post-deployment validation should compare the installed WLAN against the requirements rather than only confirming that every AP is online.
Different survey types answer different questions. Predictive work models expected RF before installation; on-site measurements validate attenuation, interference, neighboring WLANs, mounting, and cable constraints; post-deployment validation confirms that the installed system meets coverage, capacity, roaming, and application requirements.
Use representative clients during validation because radio capability and roaming behavior differ by device. A network can look healthy from the AP perspective while a low-power scanner or voice handset experiences poor uplink or delayed roaming.
Identify whether a problem affects one device, one AP, one SSID, one channel, one site, or everyone. Then follow discovery, association, authentication, addressing, routing, DNS, and application access.
This method prevents random configuration changes. A client with poor SNR requires a different response from a client with a valid RF connection but failed DHCP.
Use a healthy client as a comparison whenever possible. When the problem requires frame-level evidence rather than administrative checks alone, CWNP CWAP-405 is the adjacent analysis track focused on protocol, spectrum, and troubleshooting depth.
A disciplined troubleshooting sequence is discovery, association, authentication, address assignment, DNS and gateway reachability, then application behavior. RF evidence such as signal, noise, retries, and channel utilization should be compared with wired evidence such as DHCP, routing, and upstream packet loss. Packet capture analysis becomes useful when the symptom crosses the wireless/wired boundary and the administrator needs to verify what traffic actually left the client or reached the upstream network.
Scope is the fastest reducer of possibilities. One client points toward device or local RF conditions; one AP points toward radio, uplink, or configuration; one SSID points toward policy or authentication; a whole site suggests shared infrastructure. Comparing a healthy client in the same location can reveal whether the difference is capability, credentials, policy, or RF behavior.
If an exam is already scheduled before December 31, 2026 and preparation is heavily aligned to CWNA-109, continuing with 109 can still be reasonable because CWNP explicitly allows it through that date.
That choice should be made once, then reflected consistently in practice questions, notes, and lab work. A candidate who keeps switching between 109 and 110 may spend time reconciling differences instead of mastering the WLAN fundamentals that both versions expect. The transition window is useful only when the study plan stays explicit about the target exam.
For a new preparation plan, CWNA-110 is the better target because it is already the current version and will remain the basis for the certification path going forward.
CWNP still permits CWNA-109 through December 31, 2026, so a candidate already scheduled and substantially prepared for 109 does not need to switch automatically. But the study materials should remain isolated to the chosen version. Mixing 109 and 110 objectives without tracking which exam is being taken can create gaps and wasted study time.
CWNA-109 is a 60-question, 90-minute multiple-choice or multiple-answer exam with a 70% passing requirement for candidates. Those logistics remain relevant only to the 109 attempt window; current-version learning should now follow CWNA-110 objectives.
CWNP CWNA-109 material still provides a strong wireless foundation, but candidates should be explicit about which blueprint they are following. The safest study plan avoids mixing objectives from both versions without knowing which exam is actually being taken.
A practical transition method is to mark every 109 topic as either unchanged foundation, updated emphasis, or version-specific detail, then compare that map directly with the 110 objectives. RF, antennas, architecture, security, site survey, and troubleshooting remain durable; the current blueprint should decide the standards, terminology, and technology emphasis used for the actual exam.
For candidates taking 109 before its deadline, use the remaining window deliberately: keep practice aligned to the 109 objectives and avoid switching terminology midstream. For anyone starting now without an existing 109 commitment, 110 should be the organizing blueprint because it is already the version CWNP calls current.
