Free Cisco 300-110 Practice Exam with Questions & Answers

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.

In Ekahau Site Survey ' s multi-floor predictive modeling workflow, alignment points are the critical mechanism that allows the software to understand the precise vertical spatial relationship between floors in a multi-story building. Once floor plans are imported with their scale correctly defined, alignment points must be placed on each floor at the same real-world physical location — such as a stairwell corner, elevator shaft, or structural column — so that Ekahau can accurately calculate vertical signal propagation and inter-floor RF bleed. Without alignment points, the software has no spatial reference to determine which area on Floor 2 is directly above a given point on Floor 1, making floor-to-floor signal bleed calculations geometrically impossible. Drawing coverage areas (Option A) is a post-AP-placement activity. Starting the auto planner (Option B) would attempt to place APs without the required spatial reference. Choosing AP models (Option D) is a subsequent step. Alignment points are a fundamental requirement for any predictive survey involving multi-floor buildings. Reference: WLSD Study Guide — Ekahau Predictive Survey Methodology, Multi-Floor Building Configuration, Signal Propagation Modeling.

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.

In outdoor wireless deployments, foliage — particularly dense trees — represents the most significant and variable RF obstruction that engineers must account for during site survey and design. Trees are problematic for multiple compounding reasons: the high water content of living tissue causes signal absorption consistent with the principle that water is an effective absorber of 2.4 GHz and 5 GHz RF energy; the irregular branching structure causes multi-path scattering; and foliage density changes seasonally, meaning signal propagation characteristics measured during winter may differ substantially from summer readings when leaves are fully developed. A fully leafed deciduous tree can attenuate a 5 GHz signal by 6–15 dB depending on density and depth. Wind (Option A) causes only momentary mechanical movement of foliage and is not an obstruction itself. Rain (Option B) causes some absorption at higher frequencies but its effect at 2.4 GHz and 5 GHz in typical conditions is marginal compared to foliage. Poles (Option D) are thin structures with minimal RF impact. Outdoor surveys for university campuses must specifically account for tree locations, canopy density, and seasonal variation. Reference: WLSD Study Guide — Outdoor Wireless Design, Environmental RF Attenuation Factors, Outdoor Site Survey Considerations.

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.

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.

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.

The Cisco Aironet 4800 Series Access Point is a tri-radio, high-performance access point designed for high-density environments. It draws significantly more power than older dual-radio APs and requires IEEE 802.3bt (also known as PoE++), which provides up to 90W per port at the Power Sourcing Equipment. IEEE 802.3af (Type 1 PoE) delivers only 15.4W and 802.3at (Type 2 PoE+) provides up to 30W — both are insufficient for full functionality of the 4800 series, which has a dedicated third scanning radio that requires the additional power budget provided by 802.3bt. IEEE 802.3ac is a standard related to VLAN tagging and is entirely unrelated to Power over Ethernet. Engineers designing wired infrastructure for Cisco 4800 deployments must ensure switches support 802.3bt Type 3 or Type 4 to guarantee full AP functionality across all three radios simultaneously. Reference: WLSD Study Guide — Wired Infrastructure Design, PoE Standards and Power Budget Planning, Cisco 4800 Series AP Specifications.

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.

The Cisco Catalyst 9300-48HX is a high-density PoE switch specifically designed for Cisco Catalyst 9100 Series AP deployments. The 48HX variant features 48 Multi-Gigabit PoE ports with IEEE 802.3bt (PoE++) support, providing up to 90W per port. The Cisco 9166 Access Point is a Wi-Fi 6E AP that requires IEEE 802.3bt (PoE++) power to achieve full radio functionality — enabling all three radios including the 6 GHz radio. In a two-switch stack of 48HX units, the total PoE budget is designed and rated to support full-port utilization with Cisco 9100 series APs simultaneously. The design intent is to connect APs to all ports on all switches — maximizing the deployment density and ensuring every AP runs with full functionality. Connecting to only half the ports on one switch (Option B), half of each switch (Option C), or all ports on only one switch (Option D) would underutilize the infrastructure and fail to achieve the full deployment density that the switch stack was architected to deliver. The AP naming scheme requiring sequential area numbering requires all APs to be connected and fully operational across the entire stack. Reference: WLSD Study Guide — Catalyst 9300 PoE Infrastructure, 9166 AP Power Requirements, High-Density Wired Infrastructure Design.