300-110 Exam Dumps - Cisco CCNP Wireless Questions and Answers

The Cisco Catalyst 9800 IOS XE WLC uses a tag-based configuration architecture. Three primary tag types are used: site tags, policy tags, and RF tags. The site tag associates an AP with its operational context and contains two specific profile references: the AP join profile (defining AP-level parameters such as NTP, syslog, SSH, LED behavior, and CAPWAP timers) and the flex profile (defining FlexConnect-specific parameters including locally switched VLANs, split tunneling, local authentication settings, and VLAN-ACL mappings). The flex profile within the site tag enables the AP to operate in FlexConnect mode with locally configured switching behavior when WLC connectivity is lost. QoS (Option A) policies are applied at the policy tag level within WLAN policies. NAT (Option B) is not a native profile type in the 9800 tag architecture. VLAN (Option D) configurations are defined within the flex profile or policy profile and are not standalone profile types at the tag level. Understanding the three-tag model is essential for designing and troubleshooting 9800-based deployments. Reference: WLSD Study Guide — Catalyst 9800 Configuration Model, Site Tag Architecture, Flex Profile and AP Join Profile.

In a Cisco Catalyst 9800 SSO deployment using Link Aggregation Group (LAG) for network interface redundancy, the SSO pair — WLC1 (active) and WLC2 (standby) — must both have their physical interfaces connected to the network infrastructure as part of the LAG bundle. LAG on the 9800 in an SSO configuration is implemented as a multi-chassis LAG across both the active and standby controllers. This means both WLC1 and WLC2 contribute physical member links to the port channel, and the connected switches must have LACP or PAgP bundle members from both controllers in the same port channel group. When an SSO failover occurs — WLC1 fails and WLC2 takes over as active — the LAG remains operational because WLC2 ' s physical links are already established members of the bundle and continue forwarding traffic without any link renegotiation. If only WLC1 had LAG connectivity and WLC2 had independent links, an SSO failover would cause a LAG topology change requiring re-convergence, introducing downtime. WLC3 is a separate N+1 backup controller joined via a mobility tunnel — not part of the SSO pair and its LAG configuration is independent. Reference: WLSD Study Guide — Catalyst 9800 SSO with LAG, Multi-Chassis Link Aggregation, High Availability Network Redundancy Design.

This design scenario requires careful interpretation of the SSO pair function and AP priority semantics. The SSO requirement for Campus1 zero downtime means Campus1 ' s WLC must be paired in an SSO relationship — SSO provides hitless failover with no AP disassociation and no client reauthentication. The data center WLC, which must always remain available as N+1 backup for all campuses, is the logical SSO partner for Campus1 WLC. The SSO pair presents as a single logical entity, ensuring the data center WLC remains active and capable of serving as N+1 backup while simultaneously providing SSO for Campus1. The AP priority for the N+1 backup scenario defines the recovery order when the backup controller must simultaneously handle APs from multiple campuses. In Cisco WLC AP failover priority, priority 1 is Critical (highest). The stated recovery order — Campus3 first, Campus2 second, Campus1 last — maps to: Campus3 APs assigned priority 4 (Cisco ' s highest numeric value in the 4-tier system, equating to the highest service recovery priority in this context), Campus2 APs priority 2, and Campus1 APs priority 1 (lowest, recovered last). Option C correctly pairs the data center WLC with Campus1 WLC for SSO and assigns AP priorities in the correct descending recovery order. Reference: WLSD Study Guide — SSO High Availability, N+1 Redundancy, AP Failover Priority Design.

Floor loss calculation is a fundamental skill in multi-floor wireless site survey methodology. The floor attenuation value represents the signal power reduction caused by penetrating through a single floor structure including the floor decking, subfloor, ceiling material, plenum space, and any structural elements. In this measurement scenario, the engineer has two data points: -45 dBm measured at the ground level of the floor containing the access point (the signal level just below the AP ' s floor) and -50 dBm measured at the ceiling level of the floor below (the signal level just after passing through the floor structure). The floor loss is simply the difference between these two measurements: (-45 dBm) - (-50 dBm) = -45 + 50 = 5 dB. The result is expressed as a positive value (5 dB) representing attenuation — signal power decreases by 5 dB when passing through the floor. Expressing it as -5 dB (Option B) would incorrectly imply a signal gain. The 95 dB values (Options A and D) result from incorrectly adding rather than subtracting the dBm values — a common error when working with negative dBm figures. This floor attenuation value (5 dB) would then be entered into Ekahau ' s floor material properties to improve predictive model accuracy. Reference: WLSD Study Guide — Multi-Floor Signal Propagation, Floor Attenuation Factor (FAF), Ekahau Floor Loss Measurement Methodology.

The scenario presents a critical distinction in where Cisco WLC features are configured. Optimized roaming on Cisco WLC is a radio-level feature that monitors connected client RSSI and, when a client ' s signal falls below the configured threshold (-72 dBm), triggers a disassociation to force the client to reconnect to a stronger AP. However, without a mechanism to guide the client proactively before reaching the threshold, clients that disassociate simply reconnect to whatever AP their device selects, potentially causing the reported frequent disconnections. BSS Transition Management (802.11v) is configured at the SSID level and provides the complementary mechanism: before the client reaches the RSSI threshold, the AP sends a BSS Transition Management Request pointing the client toward a specific target AP with stronger signal. The correct architecture requires: optimized roaming configured at the radio level (triggering disconnection when RSSI falls too low) combined with BSS transition enabled at the SSID level (guiding the client to a better AP before forced disconnection). Options C and D incorrectly reverse the configuration levels for these features. Disabling coverage hole detection (Option B) addresses a different problem and would not resolve the disconnection issue. Reference: WLSD Study Guide — Optimized Roaming Configuration, BSS Transition Management (802.11v), Client Roaming Architecture on Cisco WLC.

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 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.

When conducting a Layer 2 site survey, it is recommended to match the survey to the worst client available. This ensures that the wireless network is designed to provide adequate coverage and performance even for clients with the poorest RF capabilities, thereby providing a consistent user experience for all devices. The worst client typically has fewer antennas, lower receiver sensitivity, and less sophisticated chipsets. By designing to its limitations, the engineer guarantees that every device in the environment meets the minimum performance threshold. Using the best client (Option A) or an average client (Option C) would result in coverage gaps for less capable devices. A phone client (Option B) may have unique characteristics but is not a universally applicable standard for general survey purposes. Reference: WLSD Study Guide — Site Survey Methodology, Client Selection for Survey, Layer 2 Pre-Deployment Survey.

A pre-site survey questionnaire is used to gather information before the physical survey begins, helping to define design requirements. The two most important information points it should contain are the access point density required and the applications that will run over the wireless network. Access point density (Option C) must be understood early because it depends on the number and types of users in each area, directly influencing the survey approach and AP placement strategy. Applications (Option E) are critical because they define the QoS requirements — a company developing code may run video conferencing, large file transfers, and real-time collaboration tools, each with distinct bandwidth and latency requirements that shape the RF design criteria. The total number of existing APs (Option A) and the current controller model (Option D) are inventory questions, not design requirement inputs. Client device types (Option B) are important but are a subset of the application question — applications drive the specific device capability requirements. Reference: WLSD Study Guide — Pre-Site Survey Requirements Gathering, Customer Questionnaire, Design Requirements Definition.

To optimize roaming in a wireless network with multiple controllers, it is essential to use the same WLAN name (SSID) across all controllers. When SSIDs differ between controllers, clients perceive them as different networks and must perform a full re-association and re-authentication when roaming between APs managed by different controllers. This causes a roaming disruption equivalent to connecting to an entirely new network. By using identical SSID names on both controllers, clients can seamlessly roam between APs on different controllers within the same mobility group — the controllers exchange client state information via the mobility tunnel, enabling seamless handoff. In the scenario described, ' Copr-NET390595865WLC-1 ' and ' Copr-NET6837l638WLC-2 ' are different SSIDs, meaning clients cannot roam transparently between them. Making both controllers broadcast the same SSID name (and using a mobility group to connect the controllers) resolves this. Reference: WLSD Study Guide — SSID Consistency Across Controllers, Inter-Controller Roaming, Mobility Group Configuration.