Free Practice Questions for the Cisco CCNP Wireless 300-110 Exam (2026 Updated)

To support high availability with client SSO (Stateful Switchover) and no interruption to live services during failover, the design must incorporate two requirements. First, redundant WLCs (Option A) are essential — without a physical standby controller, there is no entity to take over when the primary WLC fails. In an SSO configuration, one WLC is active and one is standby, and the standby must be ready to assume the active role instantaneously. Second, the high availability pair requires one of the WLCs to have a valid AP count license (Option B). In a Cisco WLC SSO pair, the standby controller ' s AP count license applies when it becomes active — without a valid license on at least one WLC in the pair, APs cannot join after failover. A 10-second RTT maximum (Option C) is a latency requirement for the redundancy link but is not a primary design requirement that addresses the overall high availability architecture. A back-to-back direct connection (Option D) is one way to connect the redundancy ports but is not mandatory if a low-latency switch connection is used. Code version 7.5 or newer (Option E) is a requirement for specific legacy SSO platforms but not a general design principle. Reference: WLSD Study Guide — WLC SSO High Availability Design, AP License Requirements, Redundant Controller Architecture.

IEEE 802.11v BSS Transition Management is the standard that enables the network (via the AP) to actively provide roaming recommendations and suggestions to associated clients. When enabled on a SSID, the AP can send BSS Transition Management Request frames to clients, informing them of preferred target APs ranked by signal quality, load, and channel conditions. Critically, BSS Transition Management is a voluntary mechanism — clients that support 802.11v can act on the AP ' s recommendation, while clients that do not support 802.11v simply ignore the BSS Transition Request frames and continue operating normally. This selective applicability directly satisfies the requirement that non-VoWLAN clients must not be impacted. 802.11k (Option A) enables clients to build neighbor lists through measurement reports — this is a client-initiated process, not an AP-to-client recommendation. CCKM (Option B) is a Cisco proprietary fast roaming mechanism for legacy clients, unrelated to roaming guidance. 802.11r (Option D) accelerates the re-association handshake during roaming but does not provide proactive roaming recommendations. Reference: WLSD Study Guide — VoWLAN Design, 802.11v BSS Transition Management, Roaming Optimization Protocols.

When a data path mobility tunnel fails to come up between WLCs, one of the key troubleshooting steps is to verify whether the necessary ports are open through firewalls in the path. Cisco AireOS mobility tunnels use UDP port 16666 for mobility control traffic and IP Protocol 97 (EtherIP) for mobility data traffic in legacy mode. Establishing a Telnet connection from a local PC to the firewall on port 16666 tests whether the control path port is reachable and not being blocked by the firewall. If the Telnet connection fails, it confirms that the firewall is blocking port 16666, which would prevent the mobility control tunnel from establishing — a prerequisite for the data tunnel. While a Telnet test to port 16666 specifically tests the control path, in practice this is the first verification performed when the data path cannot establish (since the data path depends on the control path being operational). IP Protocol 97 cannot be tested via Telnet (which is TCP). The mping command (Option D, not ' mapping ' ) tests mobility tunnel connectivity from the WLC itself after the tunnel is established. Reference: WLSD Study Guide — Mobility Tunnel Troubleshooting, Firewall Port Requirements, UDP 16666 and IP Protocol 97.

Designing for 50-100 clients per cell with 5 Mbps minimum throughput and no 802.11b clients requires two critical optimizations. First, setting minimum mandatory data rates to 12-18 Mbps (Option A) removes legacy lower data rates from the AP ' s supported rate set. When 1, 2, 5.5, and 11 Mbps rates are disabled and 12 Mbps becomes the minimum mandatory rate, legacy 802.11b clients are excluded from the cell, airtime efficiency improves dramatically, and clients connecting at higher rates use less channel time per frame, increasing effective capacity. Second, Flexible Radio Assignment (FRA) for 2.4 GHz reduction (Option D) is critical in high-density environments. FRA allows the WLC to dynamically reassign some 2.4 GHz radios to 5 GHz operation or monitor mode, reducing 2.4 GHz cell size and interference while increasing 5 GHz capacity in the high-density area. Option C directly contradicts the no-802.11b requirement. Option B (6 SSIDs per AP) is a management consideration but does not directly address throughput. Option E (80-160 MHz channels) would consume available spectrum, reducing the number of usable non-overlapping channels and worsening co-channel interference at high density. Reference: WLSD Study Guide — High-Density WLAN Design, Minimum Data Rate Configuration, Flexible Radio Assignment (FRA).

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.

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.

In a Cisco Catalyst 9800 SSO deployment using Link Aggregation Group (LAG) for network interface redundancy, the SSO pair — WLC1 (active) and WLC2 (standby) — must both have their physical interfaces connected to the network infrastructure as part of the LAG bundle. LAG on the 9800 in an SSO configuration is implemented as a multi-chassis LAG across both the active and standby controllers. This means both WLC1 and WLC2 contribute physical member links to the port channel, and the connected switches must have LACP or PAgP bundle members from both controllers in the same port channel group. When an SSO failover occurs — WLC1 fails and WLC2 takes over as active — the LAG remains operational because WLC2 ' s physical links are already established members of the bundle and continue forwarding traffic without any link renegotiation. If only WLC1 had LAG connectivity and WLC2 had independent links, an SSO failover would cause a LAG topology change requiring re-convergence, introducing downtime. WLC3 is a separate N+1 backup controller joined via a mobility tunnel — not part of the SSO pair and its LAG configuration is independent. Reference: WLSD Study Guide — Catalyst 9800 SSO with LAG, Multi-Chassis Link Aggregation, High Availability Network Redundancy 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.

A pre-site survey questionnaire is used to gather information before the physical survey begins, helping to define design requirements. The two most important information points it should contain are the access point density required and the applications that will run over the wireless network. Access point density (Option C) must be understood early because it depends on the number and types of users in each area, directly influencing the survey approach and AP placement strategy. Applications (Option E) are critical because they define the QoS requirements — a company developing code may run video conferencing, large file transfers, and real-time collaboration tools, each with distinct bandwidth and latency requirements that shape the RF design criteria. The total number of existing APs (Option A) and the current controller model (Option D) are inventory questions, not design requirement inputs. Client device types (Option B) are important but are a subset of the application question — applications drive the specific device capability requirements. Reference: WLSD Study Guide — Pre-Site Survey Requirements Gathering, Customer Questionnaire, Design Requirements Definition.

Devices that can tolerate at most 100 ms of delay when roaming are voice devices. The 100 ms maximum roaming delay threshold is the Cisco-specified design criterion for VoWLAN implementations — it defines the maximum time a handset can tolerate being disconnected from the wireless network during a roam event before the voice call is degraded or dropped. This threshold drives specific design requirements: 15-20% cell overlap at -67 dBm, fast roaming mechanisms (802.11r, CCKM, or OKC), and AP placement along user movement paths. Location services (Option A) have flexible latency requirements. Data applications (Option B) can tolerate much higher latency — typically several hundred milliseconds. Video (Option C) streaming has buffering mechanisms that allow for higher latency tolerance than real-time voice. Only voice applications have the strict 100 ms roaming delay requirement that directly influences the predictive design criteria. Reference: WLSD Study Guide — VoWLAN Roaming Design, Roaming Delay Requirements, Predictive Survey Criteria.

When conducting a Layer 2 site survey, it is recommended to match the survey to the worst client available. This ensures that the wireless network is designed to provide adequate coverage and performance even for clients with the poorest RF capabilities, thereby providing a consistent user experience for all devices. The worst client typically has fewer antennas, lower receiver sensitivity, and less sophisticated chipsets. By designing to its limitations, the engineer guarantees that every device in the environment meets the minimum performance threshold. Using the best client (Option A) or an average client (Option C) would result in coverage gaps for less capable devices. A phone client (Option B) may have unique characteristics but is not a universally applicable standard for general survey purposes. Reference: WLSD Study Guide — Site Survey Methodology, Client Selection for Survey, Layer 2 Pre-Deployment Survey.

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 Cisco Catalyst 9800 IOS XE WLC uses a tag-based configuration architecture. Three primary tag types are used: site tags, policy tags, and RF tags. The site tag associates an AP with its operational context and contains two specific profile references: the AP join profile (defining AP-level parameters such as NTP, syslog, SSH, LED behavior, and CAPWAP timers) and the flex profile (defining FlexConnect-specific parameters including locally switched VLANs, split tunneling, local authentication settings, and VLAN-ACL mappings). The flex profile within the site tag enables the AP to operate in FlexConnect mode with locally configured switching behavior when WLC connectivity is lost. QoS (Option A) policies are applied at the policy tag level within WLAN policies. NAT (Option B) is not a native profile type in the 9800 tag architecture. VLAN (Option D) configurations are defined within the flex profile or policy profile and are not standalone profile types at the tag level. Understanding the three-tag model is essential for designing and troubleshooting 9800-based deployments. Reference: WLSD Study Guide — Catalyst 9800 Configuration Model, Site Tag Architecture, Flex Profile and AP Join Profile.

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.

Cisco WLC AP Failover Priority governs the order in which APs are processed when a WLC recovers and APs begin re-associating. The priority levels are: Critical, High, Medium, and Low. During recovery situations, the WLC will accept and process AP join requests in order of priority — Critical priority APs are processed first, before all other priority levels. In a deployment where the WLC is located in a remote data center connected via WAN, the join process for all APs is slower due to WAN latency and potential bandwidth constraints. Under these conditions, assigning Critical priority to executive office APs ensures they are at the front of the processing queue and restore service before lower-priority APs. The executive office designation implies business-critical operations requiring the fastest possible wireless restoration — a requirement that directly maps to the Critical priority level. High priority (Option A) would position the executive APs second in the queue behind any Critical priority APs. Medium (Option B) and Low (Option C) would place them further down the processing order. Reference: WLSD Study Guide — AP Failover Priority Configuration, N+1 and SSO Redundancy Design, WAN-Linked Controller Deployments.

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.

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.

In Ekahau Site Survey, passive mode involves listening to beacon frames and probe responses from deployed APs without the survey laptop actively associating to any SSID. This is significantly faster than active mode because no association, DHCP, or throughput test overhead is introduced — the surveyor simply walks the floor while Ekahau passively captures signal strength data from all visible APs simultaneously. Using two wireless adapters in passive mode provides a critical speed advantage: one adapter scans 2.4 GHz channels while the second adapter simultaneously scans 5 GHz channels. Without dual adapters, a single adapter must time-multiplex between bands, reducing the sample rate per band and either slowing the survey walk or producing sparser data. Active mode (Options B and C) is used when throughput measurements are required for specific application validation such as voice or video, but it is inherently slower due to association overhead and sequential testing. The combination of passive scanning and dual adapter configuration delivers the highest possible data collection rate per unit of walk time. Reference: WLSD Study Guide — Ekahau Site Survey Modes, Passive vs. Active Survey Methodology, Multi-Adapter Survey Configuration.

In a Layer 1 passive wireless site survey using a channel analyzer tool (such as Metageek Chanalyzer or Cisco Spectrum Expert) in the 2.4 GHz spectrum, the chart that indicates the ratio of interference present during the capture duration is the Duty Cycle chart. The duty cycle chart displays the percentage of time that detected energy — including both Wi-Fi and non-Wi-Fi signals — is present on each channel. A high duty cycle on a channel indicates that the channel is occupied by transmissions for a significant portion of time, reducing available airtime for Wi-Fi clients. This chart directly communicates the ratio of interference because it shows what fraction of the observation period had detectable RF energy above the noise floor. Signal strength charts show amplitude (how strong), while duty cycle charts show temporal occupancy (how often) — the latter is the correct metric for quantifying interference ratio. Reference: WLSD Study Guide — Layer 1 Spectrum Analysis, Duty Cycle Chart Interpretation, Spectrum Analyzer Methodology.

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.

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.

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.

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.

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.