300-110 Certification Exam Guide + Practice Questions Updated 2026

Explanation:
The design requirements ― optimized performance, interference avoidance, high-density support, and roaming capability ― collectively point to a dual-band strategy using narrow channel widths. For 5 GHz operation (Option A), 20 MHz channels are the correct choice for high-density and campus-scale deployments. The 5 GHz band has a significantly greater number of non-overlapping channels compared to 2.4 GHz (up to 24 non-overlapping 20 MHz channels in UNII-1, UNII-2, and UNII-3), enabling a robust channel reuse plan with minimal co-channel interference. Wider 5 GHz channels (Options C and E ― 80 MHz and 40 MHz) would consume multiple channel blocks, dramatically reducing the number of available non-overlapping channels and increasing co-channel interference in dense deployments. For 2.4 GHz operation (Option B), 20 MHz channels are mandatory ― there are only three non-overlapping 20 MHz channels (1, 6, 11) in the 2.4 GHz band. Using 40 MHz channels in 2.4 GHz (Option D) eliminates all non-overlapping channel separation, causing massive co-channel interference and is universally contraindicated in enterprise designs.
Reference: WLSD Study Guide ― Channel Planning, High-Density Design, Frequency Band Selection.

Explanation:
Cisco's mobility group architecture enables seamless client roaming between WLCs by establishing a trusted peer relationship and shared mobility domain. When two Cisco Catalyst 9800-80 WLCs are placed in the same mobility group, they establish CAPWAP mobility tunnels enabling both Layer 2 and Layer 3 roaming with session continuity including IP address preservation. Within the same mobility group, WLCs exchange client state information, allowing 802.11r Fast BSS Transition, 802.11k neighbor reports, and 802.11v BSS Transition Management to function across controller boundaries. No specific primary or secondary roles are assigned within a mobility group ― all members are peers with equal standing for roaming purposes, which is precisely what Option D describes.
Option A incorrectly implies a hierarchical structure that does not exist in mobility group peer relationships.
Option B separating the WLCs into different groups would break inter-building roaming since clients would experience a full re-authentication cycle.
Option C imposing an anchor relationship is appropriate only for guest WLANs.
Reference: WLSD Study Guide ― Mobility Group Architecture, Inter-Controller Roaming, 802.11r/k/v Fast Roaming Design.

Explanation:
In Cisco's guest anchor WLC deployment model, multiple anchor controllers can be configured in a DMZ to provide redundancy for guest WLAN traffic. The anchor priority value determines which anchor controller is preferred for establishing the guest mobility tunnel from the foreign WLC. Cisco's anchor priority system assigns the highest preference to the lowest numerical priority value. Priority 1 is the highest priority, meaning the foreign WLC will prefer Anchor1 when establishing the CAPWAP mobility tunnel for anchoring guest client traffic. Priority 2 would be assigned to Anchor2, and Priority 3 to Anchor3, creating a deterministic failover hierarchy. If Anchor1 becomes unreachable, the foreign controller automatically falls over to Anchor2, then to Anchor3. Priority 0 is not a valid anchor priority value in the Cisco WLC configuration. This design pattern is critical for enterprise guest deployments where DMZ anchor redundancy must be maintained without manual intervention.
Reference: WLSD Study Guide ― Guest Wireless Architecture, Anchor WLC Configuration, Mobility and DMZ Design.

Explanation:
An active ping survey is used to validate network performance by sending and receiving data packets to measure end-to-end network performance, including latency, packet loss, and throughput. Ekahau site survey tools can perform active ping surveys to test the connectivity and performance of the wireless network while the surveyor walks the floor plan, producing a geographically correlated map of network performance metrics. This differs fundamentally from passive surveys, which only measure signal strength from beacons. A GPS-assisted survey (Option A) is used for large outdoor areas to automate location tracking. Spectrum analysis (Option B) identifies Layer 1 RF conditions but does not measure network performance. A passive survey (Option C) measures RSSI and SNR but does not test actual data connectivity or throughput. Active ping is the correct tool for validating that the network delivers the expected end-to-end service levels.
Reference: WLSD Study Guide ― Ekahau Survey Types, Active Survey Methodology, Post-Deployment Validation.

Explanation:
To focus the coverage heat map on the desired coverage threshold, the engineer should use the RSSI slider to set the heat map to the desired cutoff filter. This action adjusts the display to show only the signal levels that meet or exceed the specified RSSI value, effectively filtering out weaker signals and highlighting areas with sufficient coverage. In Ekahau and similar survey tools, the RSSI slider provides a dynamic way to set minimum signal thresholds, allowing the engineer to quickly validate whether coverage meets design targets such as -67 dBm for voice or -70 dBm for data. Changing the color scheme (Option A) only modifies the visual representation without filtering data. The RSSI calibration tool (Option B) adjusts how the tool perceives signal levels, not the display filter. Filtering by AP (Option D) would remove APs from the view, potentially hiding coverage gaps.
Reference: WLSD Study Guide ― Post-Deployment Survey, Ekahau Heat Map Tools, RSSI Coverage Filtering.