Pass the Cisco CCNP Wireless 300-110 Questions and answers with Dumpstech

In a high-availability configuration with multiple WLCs in a mobility group, when APs that only have a primary controller configured become orphaned (their primary WLC fails), they will by default join the controller with the lowest percentage of associated APs per license capacity. This load-based selection mechanism ensures a balanced distribution of APs across the remaining controllers in the mobility group. The WLC with the lowest percentage of AP capacity utilized is chosen because it has the most headroom to accept additional APs without becoming overloaded. This prevents a single backup controller from becoming overwhelmed while others remain underutilized. The selection is not based on absolute number of APs (Option D), available free licenses in absolute terms (Option A), or CPU utilization (Option C) — it specifically uses the percentage of license capacity occupied, which normalizes across controllers with different total AP capacities. Reference: WLSD Study Guide — N+1 Redundancy Default Behavior, AP Orphan Failover Logic, WLC Load-Based AP Assignment.

The Cisco Catalyst 9300-48HX is a high-density PoE switch specifically designed for Cisco Catalyst 9100 Series AP deployments. The 48HX variant features 48 Multi-Gigabit PoE ports with IEEE 802.3bt (PoE++) support, providing up to 90W per port. The Cisco 9166 Access Point is a Wi-Fi 6E AP that requires IEEE 802.3bt (PoE++) power to achieve full radio functionality — enabling all three radios including the 6 GHz radio. In a two-switch stack of 48HX units, the total PoE budget is designed and rated to support full-port utilization with Cisco 9100 series APs simultaneously. The design intent is to connect APs to all ports on all switches — maximizing the deployment density and ensuring every AP runs with full functionality. Connecting to only half the ports on one switch (Option B), half of each switch (Option C), or all ports on only one switch (Option D) would underutilize the infrastructure and fail to achieve the full deployment density that the switch stack was architected to deliver. The AP naming scheme requiring sequential area numbering requires all APs to be connected and fully operational across the entire stack. Reference: WLSD Study Guide — Catalyst 9300 PoE Infrastructure, 9166 AP Power Requirements, High-Density Wired Infrastructure Design.

When using Metageek Chanalyzer in conjunction with a Cisco CleanAir-capable AP for Layer 1 spectrum analysis, the AP must be configured in SE-Connect mode (Spectrum Expert Connect). SE-Connect mode enables the AP ' s CleanAir radio to operate as a dedicated spectrum analyzer, feeding raw spectrum data to the connected Chanalyzer software for visualization and analysis. In this mode, the AP does not serve any Wi-Fi clients and instead focuses all radio resources on spectrum scanning. Metageek Chanalyzer uses the SE-Connect mode specifically to receive the CleanAir ASIC ' s spectrum analysis data. Local mode (Option A) serves clients normally, only providing periodic CleanAir reports. Sniffer mode (Option B) captures 802.11 frames for protocol analysis and does not provide raw spectrum data to Chanalyzer. Monitor mode (Option C) performs WIDS scanning and RRM measurements but does not support the direct Chanalyzer integration. SE-Connect is the specific mode that enables external spectrum analysis software to use the CleanAir ASIC ' s spectrum data in real time. Reference: WLSD Study Guide — Cisco CleanAir Technology, AP Operating Modes, SE-Connect Mode for Spectrum Analysis.

For APs to be able to fail over between a primary SSO pair in one data center and a standalone WLC in a remote data center connected via WAN with firewalls, two design requirements must be met. First, a mobility tunnel must be created between the wireless controllers (Option A). The mobility tunnel enables the controllers to exchange mobility control messages, peer information, and eventually AP context when failover occurs. Without the mobility tunnel, the remote WLC is not recognized as a valid failover target by the APs through the mobility domain. Second, UDP ports 16666 and 16667 must be open through the firewalls between the controllers (Option D). UDP port 16666 is used for mobility control traffic and UDP port 16667 is used for mobility data traffic — both must be permitted through the firewalls at both data centers for the mobility tunnel to establish and function. HTTPS port 443 (Option B) is used for web management and API communication, not for mobility tunneling. A static RF group leader (Option C) is a RRM configuration unrelated to AP failover capability. Creating a mobility group with the same names (Option E) is a component of the configuration but alone is insufficient without the mobility tunnel and open firewall ports. Reference: WLSD Study Guide — Inter-Site WLC Failover Design, Mobility Tunnel Requirements, Firewall Port Planning for WAN-Separated Controllers.

Warehouse wireless deployments present unique RF engineering challenges: extremely high ceilings (often 25-45 feet), dense metallic shelving systems that create specular reflections and RF shadows, narrow aisles between rack systems, and the need to cover linear travel paths for RF scanner devices. The recommended Cisco antenna strategy for warehouses is wall-mounted patch (directional) antennas. Patch antennas provide a forward-facing radiation pattern that can be aimed precisely down warehouse aisles, delivering concentrated RF energy where RF scanners actually operate — in the aisles between shelving — rather than dispersing energy into metallic shelving structures. Wall mounting at intermediate height (typically 10-15 feet on aisle-end walls) places the antenna at a height that aligns the main lobe with the working zone of handheld scanners. Ceiling-mounted omnidirectional antennas (Options A and C) at warehouse ceiling height suffer from excessive path loss to floor-level devices and metal shelving obstructions. Low-gain wall-mounted omnidirectional antennas (Option B) lack the directivity needed to focus energy down specific aisles. Reference: WLSD Study Guide — Warehouse Wireless Design, Antenna Selection and Placement, Industrial RF Environment Considerations.

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.

The Cisco Aironet 4800 Series Access Point is a tri-radio, high-performance access point designed for high-density environments. It draws significantly more power than older dual-radio APs and requires IEEE 802.3bt (also known as PoE++), which provides up to 90W per port at the Power Sourcing Equipment. IEEE 802.3af (Type 1 PoE) delivers only 15.4W and 802.3at (Type 2 PoE+) provides up to 30W — both are insufficient for full functionality of the 4800 series, which has a dedicated third scanning radio that requires the additional power budget provided by 802.3bt. IEEE 802.3ac is a standard related to VLAN tagging and is entirely unrelated to Power over Ethernet. Engineers designing wired infrastructure for Cisco 4800 deployments must ensure switches support 802.3bt Type 3 or Type 4 to guarantee full AP functionality across all three radios simultaneously. Reference: WLSD Study Guide — Wired Infrastructure Design, PoE Standards and Power Budget Planning, Cisco 4800 Series AP Specifications.

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.

Voice over WLAN (VoWLAN) deployments require a minimum SNR threshold to maintain acceptable Mean Opinion Score (MOS) values for call quality. Cisco ' s 300-110 WLSD curriculum specifies that VoWLAN requires a minimum SNR of 25 dB throughout the coverage area. In an Ekahau post-deployment survey SNR heatmap, when the heatmap displays a consistent color indicating SNR at or above this threshold across the entire surveyed area — including all rooms, corridors, and common areas such as the lobby — the conclusion is that voice service is supported in all locations. The color coding in Ekahau ' s SNR heatmap uses green tones to indicate adequate SNR (typically ≥25 dB) and shifts toward yellow and red for degraded conditions. When the exhibit heatmap shows uniform adequate coverage across all surveyed areas without yellow or red zones, it confirms the SNR requirement for VoWLAN is universally met. Options A, B, and C suggest partial or no coverage, which would be indicated by mixed or poor SNR values — conditions not present in this scenario. The post-deployment survey with Ekahau is the validation step confirming that the predictive design was accurately realized in the physical environment. Reference: WLSD Study Guide — VoWLAN Design Requirements, SNR Thresholds, Post-Deployment Survey Validation with Ekahau.

In a mixed deployment where a Cisco Catalyst 9800 IOS XE WLC operating in SSO is required to establish a mobility peer relationship with a legacy AireOS WLC, the critical configuration requirement is that the 9800 SSO pair presents a single, consistent mobility MAC address to all peer WLCs. When the 9800 is in SSO mode, the active and standby controllers function as a single logical entity, but AireOS WLCs identify mobility peers by MAC address. If the MAC address changes during an SSO switchover, the AireOS peer will detect the change and tear down the mobility tunnel, disrupting inter-controller client roaming. The command ' wireless mobility mac-address < MAC > ' configures a static, persistent mobility MAC address on the 9800 SSO pair that remains constant regardless of which physical unit is active. This ensures the AireOS WLC always identifies the 9800 pair by the same MAC address, maintaining the mobility tunnel and enabling seamless client roaming. Option A configures the HA interface for SSO synchronization but not for AireOS mobility interoperability. Option B sets a default gateway. Option D enables management gateway failover, unrelated to mobility peer identification. Reference: WLSD Study Guide — IOS XE WLC SSO Configuration, AireOS to 9800 Migration, Mobility Peer MAC Address Management.