Free Practice Questions for Cisco 300-110 Exam

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 Cisco Aironet 2800 Series APs feature a dual-radio architecture with a dedicated 5 GHz radio (slot 1) and a Flexible Radio Assignment (XOR) radio (slot 0) that can operate in either 2.4 GHz or 5 GHz, or be assigned to monitor mode for scanning functions. Since all existing SSIDs and services are 5 GHz only, the slot 1 (dedicated 5 GHz) radio is responsible for all current client connectivity — it must remain in Client Serving mode to maintain uninterrupted 5 GHz WLAN service. The XOR radio (slot 0), currently either idle or operating as a secondary 5 GHz radio, can be repurposed without impacting client service. Setting the XOR radio to Monitor mode enables it to continuously scan all channels across both the 2.4 GHz and 5 GHz spectrum for rogue AP detection, using the embedded CleanAir and WIDS capabilities. In Monitor mode, the XOR radio operates full-time as a dedicated scanner, providing rogue detection coverage on 2.4 GHz (previously uncovered since all services were 5 GHz) and supplementary scanning on 5 GHz. This eliminates the need for additional dedicated monitor mode APs. Options A, C, and D either place the slot 1 radio in a non-client-serving role (disrupting existing connectivity) or use the inappropriate Sniffer mode instead of Monitor mode for rogue detection. Reference: WLSD Study Guide — Cisco 2800 XOR Radio Architecture, Monitor Mode for Rogue Detection, Flexible Radio Assignment, WIDS Design.

Link Aggregation Group (LAG) is the correct design approach for a single Cisco 9800-40 WLC that requires high availability between the WLC and the core switch in the event of a cable failure. LAG combines multiple physical ports on the WLC into a single logical channel, providing both redundancy (traffic automatically redistributes across remaining links when one fails) and load balancing (traffic is distributed across all active links). Importantly, LAG operates transparently to AP management — APs see a single logical uplink regardless of which physical port their traffic traverses. With a single WLC, Multi-LAG (Option B) is not applicable — Multi-LAG is a feature of the Catalyst 9800 that allows multiple separate LAG bundles for different network connections, typically used with SSO pairs. LACP (Option C) is the protocol used to negotiate LAG member links — it is the mechanism within LAG, not an independent design approach. PAgP (Option D) is a Cisco proprietary alternative to LACP for port aggregation but the question asks for the design approach, which is LAG. Reference: WLSD Study Guide — Catalyst 9800 LAG Design, Port Redundancy and Load Balancing, Single-Controller High Availability.

Cisco Application Visibility and Control (AVC) is a deep packet inspection and traffic classification framework integrated into the Cisco WLC and AP platform. AVC performs real-time analysis of wireless client traffic, classifying applications based on Layer 4-7 signatures using the NBAR2 (Network Based Application Recognition) engine. This provides the network administrator with granular visibility into exactly which applications are consuming bandwidth — enabling data-driven decisions about network congestion remediation, link utilization management, and infrastructure investment planning. For example, AVC can reveal that a video streaming application is consuming 60% of available wireless bandwidth during peak hours, informing the decision to implement QoS rate limiting for that application class or upgrade the backhaul infrastructure. AVC also supports control functions through per-application QoS policies, rate limiting, and traffic shaping — directly addressing congestion reduction. Band selection (Option A) steers dual-band clients to 5 GHz but provides no application-level analysis. QoS (Option B) implements traffic prioritization but requires prior application identification — it does not perform the analysis itself. 802.11r (Option D) is a fast roaming protocol with no relevance to traffic analysis or congestion management. Reference: WLSD Study Guide — Application Visibility and Control, NBAR2 Integration, Wireless Traffic Analysis and 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.

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 support high availability with client SSO (Stateful Switchover) and no interruption to live services during failover, the design must incorporate two requirements. First, redundant WLCs (Option A) are essential — without a physical standby controller, there is no entity to take over when the primary WLC fails. In an SSO configuration, one WLC is active and one is standby, and the standby must be ready to assume the active role instantaneously. Second, the high availability pair requires one of the WLCs to have a valid AP count license (Option B). In a Cisco WLC SSO pair, the standby controller ' s AP count license applies when it becomes active — without a valid license on at least one WLC in the pair, APs cannot join after failover. A 10-second RTT maximum (Option C) is a latency requirement for the redundancy link but is not a primary design requirement that addresses the overall high availability architecture. A back-to-back direct connection (Option D) is one way to connect the redundancy ports but is not mandatory if a low-latency switch connection is used. Code version 7.5 or newer (Option E) is a requirement for specific legacy SSO platforms but not a general design principle. Reference: WLSD Study Guide — WLC SSO High Availability Design, AP License Requirements, Redundant Controller Architecture.

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.

On the Cisco Catalyst 9800 IOS XE WLC platform, the tag-based configuration model uses site tags to associate APs with specific profiles including a flex profile and an AP join profile. The site tag is a fundamental binding element — when any component of a site tag is modified, including renaming the flex profile associated with that tag, the WLC treats this as a material configuration change requiring the AP to re-evaluate its operational parameters. Specifically, the AP must disconnect its existing DTLS (Datagram Transport Layer Security) control plane tunnel to the WLC and re-establish it. This DTLS session disconnect and rejoin cycle is equivalent to a full AP rejoin: CAPWAP discovery, DTLS handshake, join request, configuration download, and image verification. Client service is interrupted on the affected AP during this process. Firmware updates (Option A) occur via a separate image download process. Temporary SSID disable (Option B) is not a defined behavior for profile name changes. Switching to a backup controller (Option C) requires AP failover conditions, not configuration changes. Understanding the disruptive nature of site tag modifications is essential for change management in production 9800 deployments. Reference: WLSD Study Guide — Catalyst 9800 Tag-Based Configuration Model, Site Tag Architecture, Flex Profile and AP Join Profile Management.

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.