Practice Free 300-110 Designing Cisco Wireless Networks (300-110 WLSD) v1.2 Exam Questions Answers With Explanation

Cisco ' s Embedded Wireless Controller (EWC) architecture is the ideal solution for small deployments with strict budget constraints where only the access points can be replaced. EWC is a controller function that runs directly within the Cisco Catalyst 9100 Series access point itself — eliminating the need for a dedicated physical or virtual WLC appliance. The APs serve dual roles as both the wireless radio infrastructure and the controller platform. The unified model (Option B) requires a dedicated hardware WLC such as the 9800 series, exceeding the customer ' s budget. Fabric (Option C) requires Cisco DNA Center and SD-Access infrastructure, making it cost-prohibitive for a small deployment. Cloud (Option D) requires ongoing subscription fees that may not fit a fixed one-time budget. EWC provides enterprise-grade features including centralized SSID management, RRM, and client mobility within the AP cluster — all without additional controller hardware investment. This makes it the canonical solution for SMB migrations from autonomous deployments. Reference: WLSD Study Guide — Controller Deployment Models, Embedded Wireless Controller Architecture, SMB and Branch Wireless Design.

In Cisco mesh networking architecture, access points are classified into two primary roles: Root Access Points (RAP) and Mesh Access Points (MAP). A RAP is an access point that maintains a wired Ethernet backhaul connection back to the network infrastructure, while a MAP operates wirelessly, relying on mesh backlinks to upstream RAPs. When an engineer needs to change an AP mode — such as switching to bridge mode to extend the mesh — the AP role must first be defined correctly. The AP must be designated as a RAP before any mode-level configuration changes are applied. This sequencing is critical because the AP role defines the fundamental backhaul path; changing the mode without first establishing the role results in misconfiguration and potential connectivity loss. The RAP communicates directly with the wired infrastructure via its Ethernet port, making it the gateway for all downstream MAPs in the mesh topology. Options A (monitor), C (bridge), and D (local) refer to AP modes, not roles, and cannot be configured until the role is properly defined. Reference: WLSD Study Guide — Mesh Networking Fundamentals, Outdoor Wireless Design, AP Role and Mode Configuration.

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.

Raising the minimum data rate to 24 Mbps reduces the effective coverage range of each AP because clients at the cell edge operating at low data rates are effectively excluded from the cell. This shrinks cell size, reducing channel overlap between neighboring APs on the same channel. Using directional antennas limits the coverage area of some APs by focusing RF energy in specific directions rather than radiating omnidirectionally, which directly reduces the lateral overlap between adjacent APs. Increasing AP transmit power (Option B) would worsen overlap, not reduce it. Allowing UNII-2e channels (Option C) provides more channel options but does not reduce the physical cell overlap — it only provides more channels to avoid co-channel interference. Power saving mode (Option E) is a client-side power management feature unrelated to AP cell sizing during a survey. Reference: WLSD Study Guide — Channel Overlap Mitigation, Data Rate Configuration, Directional Antenna Use Cases.

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.

In the Cisco Catalyst 9800 IOS XE WLC configuration framework, the site tag serves as the primary organizational and functional grouping element for FlexConnect APs at a given physical location. The site tag defines the FlexConnect site — a logical boundary within which APs can perform local switching and local inter-AP roaming without requiring CAPWAP tunnel traversal to the WLC for every client handoff. Within a FlexConnect site defined by the site tag, APs can exchange client roaming context information directly with each other (peer-to-peer), enabling fast Layer 2 roaming for clients moving between APs that share the same site tag — effectively defining the roaming domain for FlexConnect APs at that site. The site tag also references the flex profile (which defines VLAN mappings, local auth settings, and split tunneling parameters) and the AP join profile. Switch port configuration (Option A) is performed on the infrastructure switches, not through the WLC site tag. IP address assignment (Option B) is a DHCP function. Firewall policies (Option C) are applied through ACLs and policy tags, not site tags. Reference: WLSD Study Guide — Catalyst 9800 Tag Architecture, FlexConnect Site Tag Role, Local Roaming in FlexConnect Deployments.

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.

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.

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.

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.

When designing a wireless network for any environment, including a historic building with ornate wall coverings and aesthetic constraints, RF coverage must always be considered first when placing access points. RF coverage is the fundamental requirement — without adequate signal strength throughout the space, no other design objective can be met. The engineer must first determine AP locations that provide the required signal strength and coverage to all areas before addressing aesthetics, overlap calculations, or interference mitigation. In a historic building specifically, the ornate wall coverings and dense construction materials may cause unexpected signal attenuation, making it even more important to model RF coverage before committing to AP positions. Once RF coverage requirements are established, aesthetic concerns (Option A) can guide the choice of AP form factor, enclosures, or cabling routes. Cell overlap (Option C) is derived from coverage calculations. RF interference (Option D) analysis follows after RF coverage baseline is established. Reference: WLSD Study Guide — Site Survey Methodology, AP Placement Priority, Special Environment Wireless Design.

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.

For a network supporting both data and voice over wireless, two key Cisco design recommendations apply. First, the 5 GHz radio band is recommended for voice over wireless due to its wider channel bandwidths, allowing for higher data rates and better quality of service for latency-sensitive applications. 40 MHz channels in the 5 GHz band provide significantly higher throughput than 20 MHz channels in 2.4 GHz, making Option B correct for the bandwidth reason stated. Second, setting the cell boundary to -67 dBm ensures sufficient signal strength for reliable voice communication at the cell edge, which is the Cisco standard threshold for VoWLAN coverage. Options C and E are partially correct (24 non-overlapping channels is accurate, 15-20% overlap is standard) but B and D are the primary Cisco recommendations that define the design targets for a predictive survey supporting voice. Reference: WLSD Study Guide — VoWLAN Design Requirements, Predictive Survey Design Criteria, 5 GHz Band Selection.

In Ekahau Site Survey, when planning a warehouse deployment using patch (directional) antennas, the antenna downtilt setting is the critical adjustment made when placing simulated APs on the floor plan map. Patch antennas have a defined radiation pattern with a main lobe that must be aimed precisely at the intended coverage zone. In a warehouse environment, APs with patch antennas are typically wall-mounted and aimed down aisles. The downtilt angle determines the vertical component of the antenna ' s aim — adjusting the downtilt in Ekahau tilts the simulated antenna ' s main radiation lobe downward toward the warehouse floor and the working zone of RF scanner devices, rather than projecting RF energy horizontally at an ineffective angle. Ekahau allows engineers to specify the horizontal and vertical orientation of the antenna in three dimensions, and the downtilt value directly controls how the software models the antenna ' s coverage pattern in the vertical plane. AP channel (Option A) is set during channel planning, not during AP placement. Wi-Fi technology (Option B) determines the modulation and protocol standard but is set as an AP property. AP transmission power (Option D) controls cell radius but is set separately from antenna orientation. Reference: WLSD Study Guide — Ekahau Predictive Survey, Directional Antenna Configuration, Warehouse RF Design and Antenna Orientation.

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.

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.

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.

This WGB (Workgroup Bridge) design scenario requires satisfying multiple simultaneous constraints. EAP-FAST (Flexible Authentication via Secure Tunneling) is the correct authentication protocol because it provides enterprise-grade 802.1X security using protected access credentials (PAC) without requiring a certificate to be installed on each AP or WGB device — directly satisfying the enterprise-grade security without certificates requirement. EAP-TLS (Options B and D) requires client certificates on every authenticating device, which is explicitly excluded. Mobile station mode is required rather than static mode (Options C and D) because mobile station mode enables the WGB to aggressively scan and roam to optimal mesh neighbors dynamically, evaluating neighbor signal quality and switching to better RAPs/MAPs as the truck moves along its path. Static mode fixes the WGB to a specific channel or AP, preventing the aggressive scanning and roaming required for the latency-sensitive application. The dot1q-capable switch connection supports multiple clients in different VLANs via 802.1Q VLAN tagging between the WGB and the truck ' s local network switch. Reference: WLSD Study Guide — Workgroup Bridge Design, EAP-FAST Authentication, Mobile vs. Static WGB Mode, Industrial Wireless Design.

The requirement for users to retain their VLAN assignment 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 creating a mobility group between WLC-A and WLC-B with both controllers configured with the same mobility group name — the group name is the trust identifier that permits the mobility tunnel and anchor-foreign relationship to form. An SSO cluster (Option B) creates redundancy between two WLCs operating as one logical entity, not inter-building roaming between independent controllers. 802.11r (Option C) accelerates re-association but does not preserve IP addresses across different Layer 3 subnets. AP groups (Option D) control SSID and VLAN assignments but do not enable inter-controller IP preservation. Reference: WLSD Study Guide — Inter-Controller Mobility, Layer 3 Roaming, IP Address Preservation.

This question requires straightforward wireless capacity engineering calculation. The total throughput requirement is 100 users × 1 Mbps per user = 100 Mbps aggregate. Each channel in the design can support 20 Mbps of usable throughput — this is the per-cell, per-channel allocation defined in the design parameters, representing usable throughput prior to RF overhead as stated in the question. The number of channels required is therefore: total required throughput divided by throughput per channel = 100 Mbps ÷ 20 Mbps per channel = 5 channels. In practice, each channel corresponds to a non-overlapping frequency assignment in the 5 GHz band. With 5 channels and 20 Mbps per channel, the design provides exactly 100 Mbps of aggregate capacity for 100 concurrent users at 1 Mbps each. This calculation methodology is foundational to Cisco ' s high-density WLAN design approach, where the number of spatial streams, channel allocations, and AP placement are all derived from the per-user throughput requirement multiplied by the concurrent user population. Reference: WLSD Study Guide — High-Density WLAN Capacity Planning, Per-User Throughput Calculation, Channel Planning and Spatial Reuse.

VoWLAN handoff quality is fundamentally determined by the AP placement strategy relative to the direction of user movement. When a user is in motion carrying an active voice call, the roaming event must occur before signal quality degrades below the minimum acceptable VoWLAN threshold (typically -67 dBm for voice, with a minimum SNR of 25 dB). This requires the user to encounter increasing signal strength from a neighboring AP before the current AP ' s signal drops below the threshold. The optimal AP placement follows the principle of overlapping coverage along the predicted path of travel — APs must be positioned so that as a user moves, they progressively enter the coverage zone of the next AP while still within adequate range of the current one. Floor plan B represents the correct design where APs are positioned along the travel path with sufficient cell overlap (typically 15-20%) to ensure seamless 802.11r fast BSS transitions. Incorrect floor plans place APs perpendicular to travel direction, at path endpoints only, or with insufficient overlap zones — all of which create roaming dead zones where the handoff occurs too late, causing voice call disruption. Reference: WLSD Study Guide — VoWLAN AP Placement, Roaming Design for Moving Users, Cell Overlap and Fast Transition Planning.

To test whether mobility control packets can reach between WLC peers in a mobility group (used to validate the anchor controller DMZ setup), two steps are required. First, the mping (mobility ping) command (Option A) is the Cisco WLC CLI tool specifically designed to test mobility control path connectivity between WLC peers. Running mping on both WLCs verifies that mobility control messages (UDP port 16666) can be exchanged bidirectionally. Second, UDP port 16666 must be open between the WLCs (Option C) — mping uses this port, and if it is blocked by a firewall (which is common when the anchor is in a DMZ), the mobility control path cannot be established. These two steps together — sending mping packets and confirming the firewall permits UDP 16666 — validate mobility control plane connectivity. The eping (EoIP ping) command (Option B) tests the data path tunnel, not the control path. IP Protocol 97 (Option D) is for the data plane in legacy mobility mode. Tracert (Option E) traces routing paths but does not validate mobility protocol connectivity. Reference: WLSD Study Guide — Mobility Group Troubleshooting, mping Command, UDP 16666 Firewall Requirements.

The primary concern when upgrading to 802.11ac Wave 2 capable APs with existing switches that only provide IEEE 802.3at (PoE+, 30W maximum) is the output power limitation. 802.11ac Wave 2 APs, particularly Cisco ' s 3800 and 4800 series, can require significantly more power than 30W to operate all radios and capabilities at full capacity. The Wave 2 standard introduced features such as Multi-User MIMO (MU-MIMO), beamforming, and additional spatial streams, all of which increase power consumption. When an AP doesn ' t receive sufficient power, it may reduce transmit power, disable radios, or reduce the number of spatial streams — directly degrading wireless performance. Interface throughput (Option A) may also be a concern with multi-gigabit capable APs, but the question specifically asks about the limitation introduced by 802.3at, which is directly a power delivery constraint. Collision domains (Option C) and high availability (Option B) are unrelated to the PoE standard. Reference: WLSD Study Guide — PoE Upgrade Planning, 802.11ac Wave 2 Infrastructure Requirements, Switch Power Budget Considerations.