CWTS study materials
CWTS study resources

CWTS: Applications, Support, and Troubleshooting

CWTS · Work through your exam, one topic at a time.

All guide sections

Applications, Support, and Troubleshooting

This domain tests how wireless supports real applications and how to isolate faults. Questions cover application requirements, QoS, roaming, DHCP and VLAN integration, troubleshooting method, and common WLAN symptoms.

Applications and support

  • Data applications tolerate variable latency. Voice needs low latency, low jitter, and low loss; video needs sustained throughput. IoT and location services may need long battery life and dense AP coverage.
  • WMM provides four access categories: voice, video, best effort, and background. QoS on the WLAN must be matched by QoS on the wired network to be effective.
  • Roaming is a client decision. 802.11k provides neighbor reports, 802.11v supports BSS transition management, and 802.11r speeds reauthentication. A sticky client stays on a distant AP and suffers low rates.
  • Troubleshoot in layers: physical link and PoE, association and authentication, IP addressing and DHCP, name resolution, then application performance. Use client utilities, ping, ARP, and protocol analyzers; use a spectrum analyzer for RF noise.
  • Common symptoms map to causes: no association points to a security mismatch; association without an IP points to DHCP or VLAN; slow throughput points to low SNR, co-channel interference, or high retries; intermittent drops point to roaming or interference. Capacity problems appear as high utilization and retries at busy times.

Worked example

Users associate to the SSID but receive 169.254.x.x addresses. Reasoning: association and authentication succeeded, but DHCP did not. Check the VLAN assigned to the SSID, the DHCP scope, the relay, and any ACL between the WLAN and DHCP server. The fix is not a new AP.

Traps

Do not blame Wi-Fi for an IP address failure before checking DHCP. Do not confuse low RSSI with interference; check SNR and retries. Do not expect 802.11k, 802.11v, or 802.11r to work without client support. Do not ignore uplink congestion and wired bottlenecks. A strong signal at the AP does not prove the client's uplink is strong.