Cisco Updated 300-110 Exam Questions and Answers by cian

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.

Cisco Catalyst Center ' s AI-driven network management capabilities — including AI Analytics, AI-Enhanced RRM (Radio Resource Management), location analytics (DNA Spaces integration), and automated RF profile management — are exclusively available under the Catalyst Advantage license tier. The Advantage tier builds upon the Essentials tier and adds access to the full suite of AI/ML-powered assurance and optimization features. Specifically, AI-Enhanced RRM leverages machine learning models trained on historical RF telemetry to predict and prevent RF issues, dynamically adjust channel and power assignments, and automate RF profile selection — capabilities that cannot be activated without the Advantage license. Location analytics through Catalyst Center integrates with Cisco Spaces to provide real-time client location tracking, asset tracking, and spatial analytics. Catalyst Essentials (Option C) provides basic device management, software image management, and network plug-and-play provisioning — it does not include AI Analytics or advanced RRM automation. Right-To-Use (Option B) is a legacy licensing model not applicable to Catalyst Center. SNTC SmartNet (Option D) is a support and maintenance contract, not a software feature license. Reference: WLSD Study Guide — Cisco Catalyst Center Licensing, AI-Enhanced RRM, Catalyst Advantage Feature Set.

In a high-availability configuration with multiple WLCs in a mobility group, when APs that only have a primary controller configured become orphaned (their primary WLC fails), they will by default join the controller with the lowest percentage of associated APs per license capacity. This load-based selection mechanism ensures a balanced distribution of APs across the remaining controllers in the mobility group. The WLC with the lowest percentage of AP capacity utilized is chosen because it has the most headroom to accept additional APs without becoming overloaded. This prevents a single backup controller from becoming overwhelmed while others remain underutilized. The selection is not based on absolute number of APs (Option D), available free licenses in absolute terms (Option A), or CPU utilization (Option C) — it specifically uses the percentage of license capacity occupied, which normalizes across controllers with different total AP capacities. Reference: WLSD Study Guide — N+1 Redundancy Default Behavior, AP Orphan Failover Logic, WLC Load-Based AP Assignment.

For APs to be able to fail over between a primary SSO pair in one data center and a standalone WLC in a remote data center connected via WAN with firewalls, two design requirements must be met. First, a mobility tunnel must be created between the wireless controllers (Option A). The mobility tunnel enables the controllers to exchange mobility control messages, peer information, and eventually AP context when failover occurs. Without the mobility tunnel, the remote WLC is not recognized as a valid failover target by the APs through the mobility domain. Second, UDP ports 16666 and 16667 must be open through the firewalls between the controllers (Option D). UDP port 16666 is used for mobility control traffic and UDP port 16667 is used for mobility data traffic — both must be permitted through the firewalls at both data centers for the mobility tunnel to establish and function. HTTPS port 443 (Option B) is used for web management and API communication, not for mobility tunneling. A static RF group leader (Option C) is a RRM configuration unrelated to AP failover capability. Creating a mobility group with the same names (Option E) is a component of the configuration but alone is insufficient without the mobility tunnel and open firewall ports. Reference: WLSD Study Guide — Inter-Site WLC Failover Design, Mobility Tunnel Requirements, Firewall Port Planning for WAN-Separated Controllers.