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.

During a client roaming event in a Cisco SD-Access fabric deployment, the Wireless LAN Controller (WLC) is responsible for communicating the new Layer 2 Endpoint ID (EID) mapping of a wireless supplicant to the fabric domain. In the SD-Access architecture, the WLC acts as a mobility orchestrator and serves as the interface between the wireless domain and the wired fabric. When a client roams from one AP to another, the WLC detects the roaming event and updates the fabric control plane with the new EID-to-RLOC (Routing Locator) mapping by notifying the fabric control plane node (CP). This ensures that the fabric knows the client ' s new location and can route traffic correctly without interruption. The Border Node (BN) handles traffic between the fabric and external networks. CP1 and CP2 are control plane nodes that maintain the mapping database but receive EID update notifications from the WLC — they do not initiate the EID mapping communication themselves. Reference: WLSD Study Guide — SD-Access Wireless Architecture, Client Roaming in Fabric Deployments, EID Mapping and Control Plane Notifications.

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.

The command ' debug mobility handoff enable ' is used to validate the mobility control packets between Wireless LAN Controllers (WLCs). This command enables debugging of the handoff process, which is critical for ensuring seamless client roaming between controllers. When WLCs are separated by firewalls, it is essential to confirm that mobility control packets can traverse these firewalls without being dropped or rejected. The ' debug mobility handoff enable ' command allows network administrators to monitor the handoff process in real time and identify whether mobility PDUs are being exchanged successfully. If mobility control packets are being blocked by the firewall, this debug output will show failures in the handoff sequence. This command directly validates bidirectional mobility traffic flow, making it the correct troubleshooting tool for the scenario described. Options A and D are not valid Cisco WLC commands. Option C enables configuration-level mobility debugging but does not specifically validate handoff packet flow. Reference: WLSD Study Guide — Mobility Troubleshooting, Debug Commands, Inter-Controller Roaming Validation.

Cisco ' s WLAN location and asset tracking architecture (based on Cisco Spaces or legacy Cisco MSE/CMX) relies on the ability to receive and measure the RF signal from tagged assets at multiple APs simultaneously. For accurate location determination using triangulation or trilateration algorithms, a minimum of three APs must receive the tag ' s signal with sufficient RSSI. Monitor mode APs are dedicated to passive RF listening — they do not transmit client-serving SSIDs and focus their full radio attention on scanning all channels for signal measurement. Placing monitor mode APs specifically on the perimeter of an asset tracking area provides the spatial diversity and boundary detection capability needed to accurately triangulate assets throughout the interior, without requiring any modifications to the existing data/voice serving APs. Adding monitor mode APs at the perimeter as an overlay ensures the existing 2.4 GHz and 5 GHz voice/data design is entirely undisturbed. Adding local mode APs (Option B) would serve clients and compete for channel capacity. Grouping APs closer (Option C) reduces capacity and increases co-channel interference. Increasing transmit power (Option D) worsens hidden node conditions without improving location accuracy. Reference: WLSD Study Guide — Cisco Location Services, Monitor Mode APs, Asset Tracking and WLAN Overlay Design.

Metal doors cause the most signal attenuation among common building materials due to the fundamental electromagnetic properties of metal. Metal is highly reflective and absorptive of radio frequency signals — it creates what is effectively a Faraday cage effect around any room or space it encloses. In wireless design attenuation modeling tools such as Ekahau, metal is assigned the highest attenuation value among standard building materials, typically 30+ dB per surface. Cinder block walls (Option A) are dense and provide significant attenuation (10-15 dB) but are not as RF-impenetrable as solid metal. Glass walls (Option C) and office windows (Option D) have relatively low attenuation values (2-4 dB) due to the minimal RF-absorbing properties of glass. When engineers model attenuation materials in predictive survey tools, metal doors and metal-containing structures consistently produce the highest per-surface attenuation values, making them the primary barrier obstacles to plan around. Reference: WLSD Study Guide — RF Signal Attenuation, Building Material Attenuation Values, Predictive Survey Material Modeling.

Mobility groups are created by configuring each Wireless LAN Controller (WLC) to use the same mobility domain name (mobility group name) and defining each WLC as a peer in the static mobility members list of every other WLC in the group. This bidirectional configuration establishes the trusted peer relationship and enables WLCs to exchange client information, security credentials, and state data for seamless roaming. The same mobility group name on all WLCs creates a shared identity; the static peer list defines which controllers are trusted mobility partners and provides their management IP addresses and MAC addresses for tunnel establishment. Option A is incorrect because members should run compatible (ideally the same) software versions, not different ones. Option B is incorrect — all WLCs in a mobility group must use the same virtual IP address for proper roaming. Option D is incorrect — in an HA SSO pair, the pair presents as a single logical mobility entity, not as two separate peers. Reference: WLSD Study Guide — Mobility Group Configuration, Peer Configuration Requirements, Mobility Domain Architecture.

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.

The design challenge is enabling IEEE 802.11r Fast BSS Transition for the new iPads (the standards-based fast roaming method) while maintaining backward compatibility for legacy RF scanners that may not support 802.11r. The SSID uses WPA2 Personal (PSK), not 802.1X enterprise authentication — therefore the correct Fast Transition variant is FT PSK (pre-shared key), not FT 802.1X (Options A and B). The critical configuration parameter is setting Fast Transition to Adaptive mode rather than mandatory. Adaptive mode is a Cisco feature that allows the AP and SSID to support both 802.11r-capable clients (which will use FT PSK for fast roaming) and non-802.11r legacy clients (which will use the standard pre-FT roaming process). In Adaptive mode, legacy scanners that cannot negotiate 802.11r during association will fall back transparently to standard roaming, while the new iPads leverage FT PSK for minimal-interruption handoffs. If Fast Transition is set to mandatory, legacy clients that do not support 802.11r will fail to associate entirely. Option C uses optimized roaming globally, which is a different mechanism and does not address the iPads ' specific need for a standards-based fast roaming solution. Reference: WLSD Study Guide — 802.11r Fast BSS Transition, FT PSK Configuration, Adaptive Fast Transition for Mixed Client Environments.

This multi-constraint design scenario requires precise alignment of EWC architecture, N+1 redundancy hierarchy, AAA integration, and WLAN security policies. Option B correctly addresses all requirements. With only three APs per branch and a requirement to keep traffic local, converting a single C9130 to EWC mode is the correct and resource-efficient approach — converting two APs to EWC (Options A and C) wastes AP capacity in a small three-AP branch. The preferred controller set to the EWC AP ensures local APs join locally. The HQ WLC as primary N+1 backup satisfies the data center WLC always being primary requirement. Other branches ' EWC APs configured as secondary and tertiary controllers creates the cross-branch redundancy hierarchy. Since guests and employees share the same SSID but require different VLANs, MAC Authentication Bypass (MAB) with AAA override allows the HQ ISE/AAA server to return VLAN attributes based on device or user identity — dynamically assigning the correct VLAN at the policy level. The 2 Mbps guest rate limiting is applied through per-client QoS policies on the EWC. Option D ' s use of local web auth for guests does not enable dynamic VLAN assignment from AAA. Reference: WLSD Study Guide — EWC Architecture, N+1 Redundancy Hierarchy, AAA Override and Dynamic VLAN Assignment.