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

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.

The design requirements specify a multi-LAG configuration where each LAG connects to a single switch, different VLANs are assigned to different LAGs, the controller must dynamically learn partner LAG capabilities per port, and standby ports provide redundancy upon active port failure. These requirements collectively point to IEEE 802.3ad LACP (Link Aggregation Control Protocol) as the correct protocol. LACP is the industry-standard IEEE protocol that enables dynamic negotiation of LAG membership between endpoints — the WLC and each Catalyst 9300 switch exchange LACP PDUs (LACPDUs) to discover port capabilities, negotiate bundle membership, and monitor link status. LACP supports active and passive port states where active ports initiate negotiation and passive ports respond, and it provides the standby port mechanism through its hot-standby capability for link redundancy within the bundle. The requirement to ' learn the identity of partners that can support LAG capabilities ' is the defining characteristic of LACP ' s standardized PDU exchange mechanism. PAgP (Option C) is a Cisco proprietary port aggregation protocol that, while functionally similar, is not the IEEE standard and is incompatible with non-Cisco equipment in mixed environments. OSPF (Option B) and BGP (Option D) are Layer 3 routing protocols entirely unrelated to port channel negotiation. Reference: WLSD Study Guide — Catalyst 9800 LAG Configuration, LACP IEEE 802.3ad, Multi-LAG High Availability Design.

The requirement for users to retain their session state and IP address when roaming between buildings managed by different WLCs is a Layer 3 roaming scenario. In Cisco ' s wireless architecture, IP address preservation across controller boundaries is achieved through inter-controller mobility — specifically the foreign-anchor mobility tunnel mechanism. When a client roams from Building A (WLC-A) to Building B (WLC-B), WLC-B becomes the foreign controller and WLC-A becomes the anchor controller. WLC-B tunnels the client ' s traffic back to WLC-A, allowing the client to retain its original IP address even while physically associated to an AP managed by WLC-B. This requires a mobility tunnel between WLC-A and WLC-B with both controllers configured in the same mobility group name — the group name is the trust identifier that permits the mobility tunnel and anchor-foreign relationship to form. Without the same group name, the controllers will not form a trusted mobility peer relationship. AP groups (Option C) control SSID and VLAN assignments per AP cluster but have no impact on inter-controller roaming. HA cluster configuration (Option B) creates SSO redundancy, not roaming capability between separate N+1 controllers. Redundancy port connection (Option D) is used for SSO keepalive and state sync, not mobility tunneling. Reference: WLSD Study Guide — Inter-Controller Mobility, Mobility Tunnels, Layer 3 Roaming and IP Address Preservation.

Cisco Spectrum Expert is a dedicated spectrum analysis tool designed to identify and analyze non-Wi-Fi interference sources at Layer 1. During a post-deployment site survey, it can detect interference from various devices such as cordless phones, Bluetooth devices, microwave ovens, video cameras, and other unlicensed RF emitters. The tool provides a visual representation of the RF environment across the frequency spectrum, allowing engineers to pinpoint the exact source of interference and characterize it by duty cycle, frequency, and interference pattern. A network analysis module (Option A) operates at Layer 2 and above, unable to detect non-802.11 RF emissions. Wireless intrusion prevention (Option B) detects rogue APs and 802.11 attacks but not Layer 1 RF noise. Wireshark (Option C) is a packet capture tool for Layer 2-7 analysis and cannot detect non-Wi-Fi RF energy. Reference: WLSD Study Guide — Layer 1 Spectrum Analysis, Post-Deployment Survey, Non-Wi-Fi Interference Identification.

Non-802.11 device detection on the 5 GHz band without a dedicated spectrum analyzer is possible through Cisco ' s CleanAir technology, which is embedded as an RF ASIC in many Cisco AP models including the 9120 series. CleanAir operates at the hardware layer — below the 802.11 MAC — enabling the APs to detect, classify, and report non-802.11 interference sources such as cordless phones, microwave ovens, video cameras, radar, and other unlicensed RF emitters in the 5 GHz spectrum. The WLC aggregates CleanAir reports from all APs and provides a consolidated interference device list accessible through the WLC ' s monitoring interface. Since the question specifies the 5 GHz band, the relevant 802.11 protocol for 5 GHz is 802.11a (and its successors 802.11n and 802.11ac). Exporting the list of 802.11a interferers from the WLC using the CleanAir RF ASIC correctly targets the 5 GHz band and identifies non-802.11 devices detected there. Option A incorrectly references 802.11b, which operates only on 2.4 GHz. Options B and C attempt to use the WLAN adapter for non-802.11 detection, but a standard WLAN adapter in monitor mode can only capture 802.11 frames — it cannot detect non-802.11 RF energy without a spectrum analyzer chipset. Reference: WLSD Study Guide — Cisco CleanAir Technology, Non-802.11 Interference Detection, Post-Deployment Survey Methodology.

When Cisco WLCs are configured to use multicast for mobility group communications, all WLCs participating in the same mobility group must be configured with an identical multicast group IP address. The mobility multicast mode allows a WLC to send a single multicast frame received simultaneously by all other WLCs in the group, rather than sending individual unicast copies to each peer. For this to function correctly, every WLC in the group must join the same IP multicast group address, and the underlying network infrastructure must be configured to support IP multicast routing or IGMP snooping for that specific group address. If any WLC is configured with a different multicast IP address, it will join a different multicast group and will not receive mobility messages from the other WLCs, effectively isolating it from the group ' s communication plane. Service port IP addresses (Option A) are unique per controller. Interface IDs (Option B) are locally significant identifiers. Management IP addresses (Option C) are unique per WLC and identify each peer in unicast configurations. Reference: WLSD Study Guide — Mobility Group Configuration, Multicast Mobility Messaging, WLC Peer Communication.

Cisco 3800 Series APs support IEEE 802.11ac Wave 2, which can deliver throughput exceeding 1 Gbps. Fast Ethernet switches are limited to 100 Mbps per port, creating a severe bottleneck. The two actions that provide maximum support are replacing with mGig switches (Option A) and replacing with gigabit switches with 10G uplinks (Option B). mGig (Multi-Gigabit Ethernet) switches support 2.5G and 5G speeds over existing CAT 6A cabling, allowing the full throughput of 802.11ac Wave 2 APs to be utilized without replacing the existing cable plant. Gigabit switches with 10G uplinks ensure that the access layer can support 1 Gbps per AP port while providing sufficient uplink capacity. Since the existing cabling is already CAT 6A, which supports 10 Gbps over short distances and 5 Gbps over 100 meters, there is no need to replace the wiring (Option D eliminates). The 100-meter distance limitation (Option C) already applies to standard Ethernet and is met by CAT 6A — this is not an action but a constraint check. Option E (55 meters) is only relevant for specific 5GBASE-T configurations and doesn ' t maximize support compared to A and B. Reference: WLSD Study Guide — mGig Infrastructure, 802.11ac Wave 2 Infrastructure Design, Switch Upgrade Planning.

The primary concern when upgrading to 802.11ac Wave 2 capable APs with existing switches that only provide IEEE 802.3at (PoE+, 30W maximum) is the output power limitation. 802.11ac Wave 2 APs, particularly Cisco ' s 3800 and 4800 series, can require significantly more power than 30W to operate all radios and capabilities at full capacity. The Wave 2 standard introduced features such as Multi-User MIMO (MU-MIMO), beamforming, and additional spatial streams, all of which increase power consumption. When an AP doesn ' t receive sufficient power, it may reduce transmit power, disable radios, or reduce the number of spatial streams — directly degrading wireless performance. Interface throughput (Option A) may also be a concern with multi-gigabit capable APs, but the question specifically asks about the limitation introduced by 802.3at, which is directly a power delivery constraint. Collision domains (Option C) and high availability (Option B) are unrelated to the PoE standard. Reference: WLSD Study Guide — PoE Upgrade Planning, 802.11ac Wave 2 Infrastructure Requirements, Switch Power Budget Considerations.

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.

The issue described indicates that there are more critical priority access points than the backup Cisco WLC can accommodate with its available AP licenses. The backup WLC has only 10 licenses available, but 7 APs are set to critical failover priority and 5 to high failover priority — a total of 12 APs attempting to join. Even though critical priority APs are processed before high priority APs, the backup WLC can only accept 10 APs total (its license limit). Since there are 7 critical priority APs and only 10 total licenses, all 7 critical APs will fail over successfully — but if the scenario involves additional critical APs beyond the license limit, the excess will not be able to join. The oversubscription of the critical priority AP count relative to available backup WLC capacity is the root cause. AP failover priority being disabled (Option D) would mean all APs have equal priority, not that critical APs fail to join. ' network ap-priority set to enable ' (Option B) enables the priority processing globally, which would be required for the feature to work at all. Reference: WLSD Study Guide — AP Failover Priority, N+1 Redundancy License Planning, WLC License Capacity Management.