300-110 Cisco Designing Cisco Wireless Networks (300-110 WLSD) v1.2 Free Practice Exam Questions (2026 Updated)

A brownfield deployment scenario involves an existing operational wireless network where a physical remodel will change the RF environment. The engineer ' s task is to assess the impact of new furniture and wall materials on the existing AP placement — a scenario requiring a predictive re-analysis of how changed materials will alter propagation from the existing AP locations. Using a survey tool such as Ekahau with the known AP positions superimposed on updated floor plans, the engineer can reconfigure material attenuation properties to reflect new construction materials and re-run the predictive propagation model. This produces a before/after comparison identifying coverage gaps or interference hotspots introduced by the remodel without requiring physical downtime or temporary infrastructure changes. Option A (sweep analysis) measures existing signal strength but does not model future material changes. Option B (neighbor AP statistics) evaluates the current RF environment using WLC data, not future conditions. Option C (throughput measurements) tests current performance, not future RF impact. Reference: WLSD Study Guide — Brownfield Survey Methodology, Material Attenuation Modeling, Post-Remodel RF Impact Analysis.

The design requirements — optimized performance, interference avoidance, high-density support, and roaming capability — collectively point to a dual-band strategy using narrow channel widths. For 5 GHz operation (Option A), 20 MHz channels are the correct choice for high-density and campus-scale deployments. The 5 GHz band has significantly more non-overlapping channels compared to 2.4 GHz (up to 24 non-overlapping 20 MHz channels in UNII-1, UNII-2, and UNII-3), enabling a robust channel reuse plan with minimal co-channel interference and excellent roaming cell separation. Wider 5 GHz channels (Options C and E — 80 MHz and 40 MHz) would consume multiple channel blocks, dramatically reducing the number of available non-overlapping channels and increasing co-channel interference in dense deployments. For 2.4 GHz operation (Option B), 20 MHz channels are mandatory — there are only three non-overlapping 20 MHz channels (1, 6, 11) in the 2.4 GHz band. Using 40 MHz channels in 2.4 GHz (Option D) eliminates all non-overlapping channel separation, causing massive co-channel interference and is universally contraindicated in enterprise designs. Reference: WLSD Study Guide — Channel Planning, High-Density Design, Frequency Band Selection.

Non-802.11 device detection on the 5 GHz band without a dedicated spectrum analyzer is possible through Cisco ' s CleanAir technology, which is embedded as an RF ASIC in many Cisco AP models including the 9120 series. CleanAir operates at the hardware layer — below the 802.11 MAC — enabling the APs to detect, classify, and report non-802.11 interference sources such as cordless phones, microwave ovens, video cameras, radar, and other unlicensed RF emitters in the 5 GHz spectrum. The WLC aggregates CleanAir reports from all APs and provides a consolidated interference device list accessible through the WLC ' s monitoring interface. Since the question specifies the 5 GHz band, the relevant 802.11 protocol for 5 GHz is 802.11a (and its successors 802.11n and 802.11ac). Exporting the list of 802.11a interferers from the WLC using the CleanAir RF ASIC correctly targets the 5 GHz band and identifies non-802.11 devices detected there. Option A incorrectly references 802.11b, which operates only on 2.4 GHz. Options B and C attempt to use the WLAN adapter for non-802.11 detection, but a standard WLAN adapter in monitor mode can only capture 802.11 frames — it cannot detect non-802.11 RF energy without a spectrum analyzer chipset. Reference: WLSD Study Guide — Cisco CleanAir Technology, Non-802.11 Interference Detection, Post-Deployment Survey Methodology.

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.

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.

The design requirements — optimized performance, interference avoidance, high-density support, and roaming capability — collectively point to a dual-band strategy using narrow channel widths. For 5 GHz operation (Option A), 20 MHz channels are the correct choice for high-density and campus-scale deployments. The 5 GHz band has a significantly greater number of non-overlapping channels compared to 2.4 GHz (up to 24 non-overlapping 20 MHz channels in UNII-1, UNII-2, and UNII-3), enabling a robust channel reuse plan with minimal co-channel interference. Wider 5 GHz channels (Options C and E — 80 MHz and 40 MHz) would consume multiple channel blocks, dramatically reducing the number of available non-overlapping channels and increasing co-channel interference in dense deployments. For 2.4 GHz operation (Option B), 20 MHz channels are mandatory — there are only three non-overlapping 20 MHz channels (1, 6, 11) in the 2.4 GHz band. Using 40 MHz channels in 2.4 GHz (Option D) eliminates all non-overlapping channel separation, causing massive co-channel interference and is universally contraindicated in enterprise designs. Reference: WLSD Study Guide — Channel Planning, High-Density Design, Frequency Band Selection.

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.

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.

RF Profiles are a Cisco WLC configuration construct that allows administrators to define a customized set of Radio Resource Management (RRM) parameters and apply them to a subset of APs operating in a specific environment or coverage zone. Within a university high-density deployment — where a lecture hall, outdoor quad, cafeteria, and library may each require fundamentally different RF settings — RF Profiles enable differentiation without globally modifying all RRM parameters. An RF Profile can define custom values for: minimum mandatory data rates, maximum transmit power, minimum transmit power, channel width (20/40/80 MHz), RxSOP thresholds, client load balancing parameters, and coverage hole detection sensitivity. This allows the engineer to apply aggressive interference mitigation settings to high-density assembly areas while maintaining full-coverage settings for perimeter zones. AP Groups (Option A) assign WLANs and interface mappings to subsets of APs but do not directly control RF parameters. RF Groups (Option B) are automatically formed by RRM and represent a cluster of APs coordinating channel and power assignment. AP Profiles (Option C) define AP behavior parameters such as NTP and SSH settings, not RF optimization parameters. Reference: WLSD Study Guide — RF Profile Configuration, High-Density WLAN Design, RRM Parameter Customization.

The design requirements specify a multi-LAG configuration where each LAG connects to a single switch, different VLANs are assigned to different LAGs, the controller must dynamically learn partner LAG capabilities per port, and standby ports provide redundancy upon active port failure. These requirements collectively point to IEEE 802.3ad LACP (Link Aggregation Control Protocol) as the correct protocol. LACP is the industry-standard IEEE protocol that enables dynamic negotiation of LAG membership between endpoints — the WLC and each Catalyst 9300 switch exchange LACP PDUs (LACPDUs) to discover port capabilities, negotiate bundle membership, and monitor link status. LACP supports active and passive port states where active ports initiate negotiation and passive ports respond, and it provides the standby port mechanism through its hot-standby capability for link redundancy within the bundle. The requirement to ' learn the identity of partners that can support LAG capabilities ' is the defining characteristic of LACP ' s standardized PDU exchange mechanism. PAgP (Option C) is a Cisco proprietary port aggregation protocol that, while functionally similar, is not the IEEE standard and is incompatible with non-Cisco equipment in mixed environments. OSPF (Option B) and BGP (Option D) are Layer 3 routing protocols entirely unrelated to port channel negotiation. Reference: WLSD Study Guide — Catalyst 9800 LAG Configuration, LACP IEEE 802.3ad, Multi-LAG High Availability Design.

The requirement for users to retain their session state and IP address when roaming between buildings managed by different WLCs is a Layer 3 roaming scenario. In Cisco ' s wireless architecture, IP address preservation across controller boundaries is achieved through inter-controller mobility — specifically the foreign-anchor mobility tunnel mechanism. When a client roams from Building A (WLC-A) to Building B (WLC-B), WLC-B becomes the foreign controller and WLC-A becomes the anchor controller. WLC-B tunnels the client ' s traffic back to WLC-A, allowing the client to retain its original IP address even while physically associated to an AP managed by WLC-B. This requires a mobility tunnel between WLC-A and WLC-B with both controllers configured in the same mobility group name — the group name is the trust identifier that permits the mobility tunnel and anchor-foreign relationship to form. Without the same group name, the controllers will not form a trusted mobility peer relationship. AP groups (Option C) control SSID and VLAN assignments per AP cluster but have no impact on inter-controller roaming. HA cluster configuration (Option B) creates SSO redundancy, not roaming capability between separate N+1 controllers. Redundancy port connection (Option D) is used for SSO keepalive and state sync, not mobility tunneling. Reference: WLSD Study Guide — Inter-Controller Mobility, Mobility Tunnels, Layer 3 Roaming and IP Address Preservation.

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.

Metal doors cause the most signal attenuation among common building materials due to the fundamental electromagnetic properties of metal. Metal is highly reflective and absorptive of radio frequency signals — it creates what is effectively a Faraday cage effect around any room or space it encloses. In wireless design attenuation modeling tools such as Ekahau, metal is assigned the highest attenuation value among standard building materials, typically 30+ dB per surface. Cinder block walls (Option A) are dense and provide significant attenuation (10-15 dB) but are not as RF-impenetrable as solid metal. Glass walls (Option C) and office windows (Option D) have relatively low attenuation values (2-4 dB) due to the minimal RF-absorbing properties of glass. When engineers model attenuation materials in predictive survey tools, metal doors and metal-containing structures consistently produce the highest per-surface attenuation values, making them the primary barrier obstacles to plan around. Reference: WLSD Study Guide — RF Signal Attenuation, Building Material Attenuation Values, Predictive Survey Material Modeling.

This design scenario requires careful interpretation of the SSO pair function and AP priority semantics. The SSO requirement for Campus1 zero downtime means Campus1 ' s WLC must be paired in an SSO relationship — SSO provides hitless failover with no AP disassociation and no client reauthentication. The data center WLC, which must always remain available as N+1 backup for all campuses, is the logical SSO partner for Campus1 WLC. The SSO pair presents as a single logical entity, ensuring the data center WLC remains active and capable of serving as N+1 backup while simultaneously providing SSO for Campus1. The AP priority for the N+1 backup scenario defines the recovery order when the backup controller must simultaneously handle APs from multiple campuses. In Cisco WLC AP failover priority, priority 1 is Critical (highest). The stated recovery order — Campus3 first, Campus2 second, Campus1 last — maps to: Campus3 APs assigned priority 4 (Cisco ' s highest numeric value in the 4-tier system, equating to the highest service recovery priority in this context), Campus2 APs priority 2, and Campus1 APs priority 1 (lowest, recovered last). Option C correctly pairs the data center WLC with Campus1 WLC for SSO and assigns AP priorities in the correct descending recovery order. Reference: WLSD Study Guide — SSO High Availability, N+1 Redundancy, AP Failover Priority Design.

To focus the coverage heat map on the desired coverage threshold, the engineer should use the RSSI slider to set the heat map to the desired cutoff filter. This action adjusts the display to show only the signal levels that meet or exceed the specified RSSI value, effectively filtering out weaker signals and highlighting areas with sufficient coverage. In Ekahau and similar survey tools, the RSSI slider provides a dynamic way to set minimum signal thresholds, allowing the engineer to quickly validate whether coverage meets design targets such as -67 dBm for voice or -70 dBm for data. Changing the color scheme (Option A) only modifies the visual representation without filtering data. The RSSI calibration tool (Option B) adjusts how the tool perceives signal levels, not the display filter. Filtering by AP (Option D) would remove APs from the view, potentially hiding coverage gaps. Reference: WLSD Study Guide — Post-Deployment Survey, Ekahau Heat Map Tools, RSSI Coverage Filtering.

The design challenge is enabling IEEE 802.11r Fast BSS Transition for the new iPads (the standards-based fast roaming method) while maintaining backward compatibility for legacy RF scanners that may not support 802.11r. The SSID uses WPA2 Personal (PSK), not 802.1X enterprise authentication — therefore the correct Fast Transition variant is FT PSK (pre-shared key), not FT 802.1X (Options A and B). The critical configuration parameter is setting Fast Transition to Adaptive mode rather than mandatory. Adaptive mode is a Cisco feature that allows the AP and SSID to support both 802.11r-capable clients (which will use FT PSK for fast roaming) and non-802.11r legacy clients (which will use the standard pre-FT roaming process). In Adaptive mode, legacy scanners that cannot negotiate 802.11r during association will fall back transparently to standard roaming, while the new iPads leverage FT PSK for minimal-interruption handoffs. If Fast Transition is set to mandatory, legacy clients that do not support 802.11r will fail to associate entirely. Option C uses optimized roaming globally, which is a different mechanism and does not address the iPads ' specific need for a standards-based fast roaming solution. Reference: WLSD Study Guide — 802.11r Fast BSS Transition, FT PSK Configuration, Adaptive Fast Transition for Mixed Client Environments.

Mobility groups are created by configuring each Wireless LAN Controller (WLC) to use the same mobility domain name (mobility group name) and defining each WLC as a peer in the static mobility members list of every other WLC in the group. This bidirectional configuration establishes the trusted peer relationship and enables WLCs to exchange client information, security credentials, and state data for seamless roaming. The same mobility group name on all WLCs creates a shared identity; the static peer list defines which controllers are trusted mobility partners and provides their management IP addresses and MAC addresses for tunnel establishment. Option A is incorrect because members should run compatible (ideally the same) software versions, not different ones. Option B is incorrect — all WLCs in a mobility group must use the same virtual IP address for proper roaming. Option D is incorrect — in an HA SSO pair, the pair presents as a single logical mobility entity, not as two separate peers. Reference: WLSD Study Guide — Mobility Group Configuration, Peer Configuration Requirements, Mobility Domain Architecture.

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.