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

In outdoor wireless deployments, foliage — particularly dense trees — represents the most significant and variable RF obstruction that engineers must account for during site survey and design. Trees are problematic for multiple compounding reasons: the high water content of living tissue causes signal absorption consistent with the principle that water is an effective absorber of 2.4 GHz and 5 GHz RF energy; the irregular branching structure causes multi-path scattering; and foliage density changes seasonally, meaning signal propagation characteristics measured during winter may differ substantially from summer readings when leaves are fully developed. A fully leafed deciduous tree can attenuate a 5 GHz signal by 6–15 dB depending on density and depth. Wind (Option A) causes only momentary mechanical movement of foliage and is not an obstruction itself. Rain (Option B) causes some absorption at higher frequencies but its effect at 2.4 GHz and 5 GHz in typical conditions is marginal compared to foliage. Poles (Option D) are thin structures with minimal RF impact. Outdoor surveys for university campuses must specifically account for tree locations, canopy density, and seasonal variation. Reference: WLSD Study Guide — Outdoor Wireless Design, Environmental RF Attenuation Factors, Outdoor Site Survey Considerations.

Cisco Catalyst Center uses a tiered licensing model — Essentials and Advantage — applied to both switching and wireless infrastructure. To enable a fully fabric-enabled (SD-Access) deployment with centralized management, the Cisco Catalyst Advantage license is required across all device types. The Advantage tier unlocks Software-Defined Access fabric capabilities including macro and micro-segmentation, integration with Cisco ISE for policy enforcement, AI/ML-driven analytics via DNA Spaces and Assurance, and automated provisioning. The Essentials license provides only basic device management, inventory, and software image management — it does not unlock SD-Access fabric functionality. Since the branch design specifically extends an existing fabric-enabled network, the Essentials tier for either the switch or APs would create a licensing gap preventing full fabric participation. Options B, C, and D all create asymmetric licensing that would partially disable fabric capabilities. The correct design mandates Catalyst Advantage for the Catalyst 9300 switch and all 25 APs. Reference: WLSD Study Guide — Cisco Catalyst Center Licensing, SD-Access Design, Fabric-Enabled Wireless Architecture.

Configuring a high availability SSO pair on Cisco Catalyst 9800 IOS XE WLCs has specific technical prerequisites that must be satisfied for the SSO relationship to form and function correctly. The two critical requirements are: each WLC must have a unique Redundancy Management Interface (RMI) IP address (Option B), and both WLCs must run identical IOS XE software versions (Option D). The Redundancy Management Interface is the dedicated in-band control channel over which the active and standby WLCs exchange state synchronization information, keepalive messages, and configuration updates. Each controller requires its own unique RMI IP address within the same subnet — the active uses one address and the standby uses another. If they shared the same RMI IP (Option C), there would be an IP address conflict preventing the interface from functioning. Identical software versions (Option D) are mandatory because the SSO state synchronization protocol and data structures must be version-compatible between the active and standby controllers. Any mismatch in IOS XE version will prevent SSO formation. License count (Option A) does not need to be identical for SSO. Service port IP addresses (Option E) must be unique per controller, not identical. Reference: WLSD Study Guide — Catalyst 9800 SSO Prerequisites, Redundancy Management Interface Configuration, High Availability Pair Formation Requirements.

Cisco Stateful Switchover (SSO) on the Catalyst 9800 platform is the definitive high availability solution when requirements specify zero client reauthentication during failover, active-passive redundancy, and ease of management. With SSO enabled, the active and standby 9800 WLCs maintain a synchronized state database via a dedicated redundancy link — this includes all client association state, authentication credentials, AP join information, and WLAN configurations. When the active controller fails, the standby assumes control instantaneously with no CAPWAP session teardown and no 802.1X reauthentication required. The Redundancy Management Interface (RMI) provides a dedicated in-band keepalive and state synchronization path. N+1 redundancy (Option D) requires APs to rejoin a new controller and clients to reauthenticate, failing the seamless requirement. Manual configuration synchronization (Options A and C) is operationally complex and does not guarantee stateful failover. VRRP provides gateway redundancy at Layer 3 but does not address CAPWAP session continuity. Reference: WLSD Study Guide — Catalyst 9800 High Availability, SSO Architecture, Redundancy Management Interface Configuration.

In a Cisco wireless mobility group, all Wireless LAN Controllers (WLCs) must be configured with the same virtual IP address to ensure proper roaming. The virtual IP address is a Layer 3 construct used by wireless clients during the DHCP renewal process when roaming between subnets managed by different WLCs. All WLCs in the same mobility group use the same virtual IP (typically from the unused 1.1.1.0/24 or similar non-routable space) so that clients receive consistent DHCP server responses regardless of which controller they are associated with. If different virtual IP addresses were used (Option B), clients roaming between controllers would experience DHCP failures during inter-controller roaming because the DHCP server address seen by the client would change. Options A and C relate to DNS hostname configuration, which is useful for AP discovery but does not affect the roaming behavior of client devices. The virtual IP address consistency across all mobility group members is a fundamental requirement for seamless inter-controller roaming. Reference: WLSD Study Guide — Mobility Group Configuration, Virtual IP Address, Inter-Controller Roaming Requirements.

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.

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.

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.

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.

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.