Free Cisco Designing Cisco Wireless Networks 300-110 Exam Questions

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 eping command is used on Cisco Wireless LAN Controllers to verify that the redundancy peer in a Stateful Switchover (SSO) pair of controllers is up and connected. This command sends ECHO packets (EoIP echo packets) to the peer controller to ensure the data path connectivity is functioning. In an SSO configuration, eping verifies the EoIP tunnel between the active and standby controllers, which is critical for state synchronization and seamless failover. If eping succeeds, it confirms that both the network path and the EoIP data encapsulation between the controllers are functional. The standard ping command (Option B) tests basic IP connectivity but does not validate the EoIP data path used by the SSO redundancy mechanism. The mping command (Option D) tests mobility control path connectivity between mobility group peers, not the SSO redundancy path. The rping command (Option A) is not a standard Cisco WLC command for testing SSO peer connectivity. Reference: WLSD Study Guide --- WLC SSO Troubleshooting, eping Command, Redundancy Peer Connectivity Validation.

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

This multi-constraint design scenario requires precise alignment of EWC architecture, N+1 redundancy hierarchy, AAA integration, and WLAN security policies. Option B correctly addresses all requirements. With only three APs per branch and a requirement to keep traffic local, converting a single C9130 to EWC mode is the correct and resource-efficient approach --- converting two APs to EWC (Options A and C) wastes AP capacity in a small three-AP branch. The preferred controller set to the EWC AP ensures local APs join locally. The HQ WLC as primary N+1 backup satisfies the data center WLC always being primary requirement. Other branches' EWC APs configured as secondary and tertiary controllers creates the cross-branch redundancy hierarchy. Since guests and employees share the same SSID but require different VLANs, MAC Authentication Bypass (MAB) with AAA override allows the HQ ISE/AAA server to return VLAN attributes based on device or user identity --- dynamically assigning the correct VLAN at the policy level. The 2 Mbps guest rate limiting is applied through per-client QoS policies on the EWC. Option D's use of local web auth for guests does not enable dynamic VLAN assignment from AAA. Reference: WLSD Study Guide --- EWC Architecture, N+1 Redundancy Hierarchy, AAA Override and Dynamic VLAN Assignment.

In an anchored WLAN deployment, client traffic is encapsulated within CAPWAP mobility tunnels between the foreign WLC (where the AP joins) and the anchor WLC (in the DMZ or designated network segment). This tunneling adds encapsulation overhead --- CAPWAP/mobility tunnel headers consume a portion of the available MTU on the transport path. When video streaming clients generate large TCP segments, these segments may exceed the effective MTU of the mobility tunnel path, causing IP fragmentation at the WLC or along the path to the anchor. Fragmentation significantly degrades throughput and increases CPU overhead for high-volume video traffic. The correct solution is TCP MSS Clamping --- reducing the Maximum Segment Size value advertised in TCP SYN packets so that TCP endpoints negotiate a segment size remaining below the fragmentation threshold. The Cisco 9800 WLC supports TCP MSS adjustment, which intercepts TCP handshake packets and rewrites the MSS option to a value accounting for CAPWAP tunnel overhead. Setting matching MTUs (Option A) does not prevent fragmentation if the effective tunnel MTU is lower than the client segment size. Increasing the MTU (Option B) is often constrained by physical infrastructure. Setting the DF bit (Option D) would cause packets to be dropped rather than fragmented. Reference: WLSD Study Guide --- Anchored WLAN Design, CAPWAP Mobility Tunnel MTU, TCP MSS Clamping.

For optimized roaming across multiple Wireless LAN Controllers (WLCs) with Cisco 8821 IP phones, two critical settings must be configured. First, configuring mobility groups between WLCs (Option A) allows for seamless inter-controller roaming by establishing mobility tunnels between controllers, enabling them to share client security context, preventing re-authentication when a phone roams from an AP on one WLC to an AP on another. Second, using Cisco Centralized Key Management (CCKM) for authentication (Option B) reduces the time required for re-authentication during roaming from a full 802.1X exchange to a single-message re-key process. CCKM stores the wireless security keys at the WLC level, enabling rapid key re-derivation during roaming without contacting the RADIUS server. AP groups (Option C) control SSID and VLAN assignments per AP cluster but have no impact on inter-controller roaming. AVC profiles (Options D and E) control application visibility and QoS marking --- marking voice as best effort (Option E) would actually degrade rather than improve voice quality. Reference: WLSD Study Guide --- VoWLAN Mobility Optimization, CCKM Configuration, Mobility Group Design for Multi-Controller Deployments.

This question requires a straightforward PoE power budget calculation. The IEEE 802.3at standard (PoE+) delivers a maximum of 30W at the Power Sourcing Equipment (PSE/switch port). Cisco 9100 Series access points such as the C9120, C9130, and C9136 are designed to operate with full functionality using PoE+ at 30W per AP. The total PoE power requirement for 12 APs is calculated as: 12 APs 30W per AP = 360W. This figure represents the total power draw that the Cisco 3800 Series PoE+ switch must be capable of supplying across the connected AP ports simultaneously. The Cisco Catalyst 3800 Series switches offer a total PoE power budget that must be validated against this 360W requirement during the design phase. Note that some Cisco 9100 APs support higher power modes through IEEE 802.3bt (PoE++), which can provide up to 90W --- but the question specifies PoE+ (802.3at) for the switch infrastructure, making 30W 12 = 360W the correct answer. Option D (720W) would correspond to 24 APs at 30W each. Option B (1080W) would represent 36 APs. Option C (184.8W) corresponds to a non-standard per-AP power value. Reference: WLSD Study Guide --- PoE Power Budget Planning, Cisco 9100 Series AP Power Requirements, Wired Infrastructure Design for Wireless Deployments.

Warehouse wireless deployments present unique RF engineering challenges: extremely high ceilings (often 25-45 feet), dense metallic shelving systems that create specular reflections and RF shadows, narrow aisles between rack systems, and the need to cover linear travel paths for RF scanner devices. The recommended Cisco antenna strategy for warehouses is wall-mounted patch (directional) antennas. Patch antennas provide a forward-facing radiation pattern that can be aimed precisely down warehouse aisles, delivering concentrated RF energy where RF scanners actually operate --- in the aisles between shelving --- rather than dispersing energy into metallic shelving structures. Wall mounting at intermediate height (typically 10-15 feet on aisle-end walls) places the antenna at a height that aligns the main lobe with the working zone of handheld scanners. Ceiling-mounted omnidirectional antennas (Options A and C) at warehouse ceiling height suffer from excessive path loss to floor-level devices and metal shelving obstructions. Low-gain wall-mounted omnidirectional antennas (Option B) lack the directivity needed to focus energy down specific aisles. Reference: WLSD Study Guide --- Warehouse Wireless Design, Antenna Selection and Placement, Industrial RF Environment Considerations.

The Cisco WLAN site survey methodology follows a structured, sequential process. The initial walkthrough --- sometimes called the discovery or orientation phase --- is the first step, during which the engineer physically tours the facility to understand its physical characteristics: building materials, structural layout, potential AP mounting locations, wiring closet positions, and environmental factors. After completing the initial walkthrough, the next logical phase is the predeployment survey (also referred to as a pre-deployment or predictive survey). The predeployment survey uses the information gathered during the walkthrough to create a detailed design plan --- either through a manual AP placement plan or a predictive survey tool such as Ekahau, where floor plans are annotated with materials and attenuation values and APs are virtually placed to model coverage. The predeployment survey output is the design document that drives the actual physical installation. A post-deployment survey (Option A) validates coverage after installation --- it cannot precede deployment. Active and passive surveys (Options B and D) are physical measurement techniques conducted either pre-deployment (with temporary APs) or post-deployment (with installed APs) --- they do not logically follow immediately after a walkthrough before any design work is done. Reference: WLSD Study Guide --- WLAN Site Survey Process, Predeployment Survey Phase, Airport Wireless Design Considerations.