300-110 Questions and Answers

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.

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.

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.

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

In a wireless network design where anchor redundancy is required for guest access, setting different priorities for the anchor controllers ensures deterministic primary and backup behavior. Cisco anchor priority uses a lower numerical value to indicate higher preference — Priority 1 is the highest priority (most preferred) anchor, and Priority 3 is lower priority. Setting Anchor A to priority 1 (Option D) makes it the primary anchor controller — all new guest client sessions will preferentially anchor to Anchor A. Setting Anchor B to priority 3 makes it the standby anchor — guest clients will only be anchored to Anchor B when Anchor A is unavailable. This creates a clear primary/backup relationship with deterministic failover. Setting both anchors to the same priority (Options A and C) would result in load balancing between the two anchors rather than active/standby behavior. Option B incorrectly reverses the priorities, making Anchor B the primary and Anchor A the backup. Reference: WLSD Study Guide — Guest Anchor Redundancy Design, Anchor Priority Configuration, DMZ Anchor WLC Architecture.

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.

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.

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 eping (EoIP ping) fails between two Cisco Wireless LAN Controllers, it indicates that the data path of the mobility tunnel is blocked. In Cisco AireOS wireless networks, the mobility data path uses IP Protocol 97 (EtherIP — Ethernet-over-IP encapsulation) for tunneling client traffic between the anchor and foreign controllers. This is distinct from the control path, which uses UDP port 16666. When the mobility data path (IP Protocol 97) is blocked by a firewall or ACL between the two controllers ' networks, eping will fail because eping specifically tests the EoIP data encapsulation path. After a power cut, when clients disconnect and attempt to roam between APs on different controllers, the mobility tunnel must be operational for session continuity. If IP Protocol 97 is blocked, the mobility data plane cannot function, causing client disconnections during inter-controller roaming events. The other IP protocols listed (67, 77, 87) are not used for Cisco WLC mobility tunneling. Reference: WLSD Study Guide — Mobility Tunnel Data Path, IP Protocol 97 (EtherIP), eping Command and Troubleshooting.

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.

Floor loss calculation is a fundamental skill in multi-floor wireless site survey methodology. The floor attenuation value represents the signal power reduction caused by penetrating through a single floor structure including the floor decking, subfloor, ceiling material, plenum space, and any structural elements. In this measurement scenario, the engineer has two data points: -45 dBm measured at the ground level of the floor containing the access point (the signal level just below the AP ' s floor) and -50 dBm measured at the ceiling level of the floor below (the signal level just after passing through the floor structure). The floor loss is simply the difference between these two measurements: (-45 dBm) - (-50 dBm) = -45 + 50 = 5 dB. The result is expressed as a positive value (5 dB) representing attenuation — signal power decreases by 5 dB when passing through the floor. Expressing it as -5 dB (Option B) would incorrectly imply a signal gain. The 95 dB values (Options A and D) result from incorrectly adding rather than subtracting the dBm values — a common error when working with negative dBm figures. This floor attenuation value (5 dB) would then be entered into Ekahau ' s floor material properties to improve predictive model accuracy. Reference: WLSD Study Guide — Multi-Floor Signal Propagation, Floor Attenuation Factor (FAF), Ekahau Floor Loss Measurement Methodology.

The scenario presents a critical distinction in where Cisco WLC features are configured. Optimized roaming on Cisco WLC is a radio-level feature that monitors connected client RSSI and, when a client ' s signal falls below the configured threshold (-72 dBm), triggers a disassociation to force the client to reconnect to a stronger AP. However, without a mechanism to guide the client proactively before reaching the threshold, clients that disassociate simply reconnect to whatever AP their device selects, potentially causing the reported frequent disconnections. BSS Transition Management (802.11v) is configured at the SSID level and provides the complementary mechanism: before the client reaches the RSSI threshold, the AP sends a BSS Transition Management Request pointing the client toward a specific target AP with stronger signal. The correct architecture requires: optimized roaming configured at the radio level (triggering disconnection when RSSI falls too low) combined with BSS transition enabled at the SSID level (guiding the client to a better AP before forced disconnection). Options C and D incorrectly reverse the configuration levels for these features. Disabling coverage hole detection (Option B) addresses a different problem and would not resolve the disconnection issue. Reference: WLSD Study Guide — Optimized Roaming Configuration, BSS Transition Management (802.11v), Client Roaming Architecture on Cisco WLC.

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.

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.

This question hinges on a fundamental network engineering constraint: the maximum transmission distance of copper Ethernet cabling. IEEE 802.3 standards specify a maximum segment length of 100 meters (328 feet) for all standard PoE and Ethernet over Category 5e, 6, or 6A UTP copper cabling. The parking lot light poles are approximately 200 meters from the closest wiring closet — more than double the maximum copper distance. This immediately eliminates Options A and D, which specify Category 6 UTP cabling: at 200 meters, UTP copper cannot reliably carry Ethernet at any supported speed, and PoE cannot be delivered over this distance regardless of standard. The correct solution is fiber optic connectivity between the wiring closet and the parking lot, combined with a local AC/DC power module at each pole location. Fiber optic cabling supports single-mode runs of kilometers and multi-mode runs of hundreds of meters at Gigabit speeds — easily spanning 200 meters. At the AP mounting location on the light pole, an AC/DC power module (powered from the pole ' s existing electrical supply) converts AC power to the DC power the AP requires. Option B (fiber with 802.3af) is incorrect because PoE cannot be delivered over fiber — 802.3af requires copper cabling for simultaneous power and data delivery. Reference: WLSD Study Guide — Outdoor AP Deployment, Fiber vs. Copper Distance Limitations, Outdoor Power Solutions.

When configuring high availability on a Cisco access point, the AP can be configured with a maximum of three controllers: a primary controller, a secondary controller, and a tertiary controller. This three-tier hierarchy defines the failover order — the AP first attempts to join its primary controller, then the secondary if the primary is unavailable, and finally the tertiary if both the primary and secondary are unreachable. After exhausting all three configured options, the AP enters a discovery process to find any available controller. This three-controller configuration (primary, secondary, tertiary) allows network engineers to implement N+1 redundancy where critical APs can be directed to specific backup controllers in a deliberate sequence. Limiting the configuration to only 2 controllers (as stated in Option B which would be incorrect) would reduce redundancy options for environments with geographically distributed controllers requiring specific failover paths. Reference: WLSD Study Guide — AP High Availability Configuration, Primary/Secondary/Tertiary Controller Assignment, AP Failover Design.

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.

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.

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.

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.

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.