300-110 Exam Questions & Answers

Enabling AP fallback globally on the WLC allows access points to reconnect to their primary controller after they have connected to a secondary controller due to the primary being offline. This is the exact behavior described in the scenario --- APs successfully fail over to the secondary WLC but do not return to the primary WLC when it recovers. AP Fallback is a WLC-level setting that monitors the availability of each AP's configured primary controller and initiates a reconnection when the primary becomes reachable again. Without AP Fallback enabled, APs remain on whatever controller they most recently joined --- in this case, the secondary --- even after the primary recovers. The CAPWAP AP Controller IP Address command (Option A) permanently changes the primary controller configuration on the AP, which is not the intended solution --- the AP already has the correct primary configured. DHCP Option 43 (Option B) is used for initial AP discovery, not fallback. AP Failover Priority (Option D) controls which APs are processed first during a failover event, not whether APs return to their primary controller. Reference: WLSD Study Guide --- AP Fallback Configuration, N+1 Redundancy Recovery, Controller Primary/Secondary Hierarchy.

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, and automated provisioning. The Essentials license provides only basic device management 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.

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

In Cisco's guest anchor WLC deployment model, multiple anchor controllers can be configured in a DMZ to provide redundancy for guest WLAN traffic. The anchor priority value determines which anchor controller is preferred for establishing the guest mobility tunnel from the foreign WLC. Cisco's anchor priority system assigns the highest preference to the lowest numerical priority value. Priority 1 is the highest priority, meaning the foreign WLC will prefer Anchor1 when establishing the CAPWAP mobility tunnel for anchoring guest client traffic. Priority 2 would be assigned to Anchor2, and Priority 3 to Anchor3, creating a deterministic failover hierarchy. If Anchor1 becomes unreachable, the foreign controller automatically falls over to Anchor2, then to Anchor3. Priority 0 is not a valid anchor priority value in the Cisco WLC configuration. This design pattern is critical for enterprise guest deployments where DMZ anchor redundancy must be maintained without manual intervention. Reference: WLSD Study Guide --- Guest Wireless Architecture, Anchor WLC Configuration, Mobility and DMZ Design.