Cisco 300-110 Practice Test Questions Answers

In a mixed deployment where a Cisco Catalyst 9800 IOS XE WLC operating in SSO is required to establish a mobility peer relationship with a legacy AireOS WLC, the critical configuration requirement is that the 9800 SSO pair presents a single, consistent mobility MAC address to all peer WLCs. When the 9800 is in SSO mode, the active and standby controllers function as a single logical entity, but AireOS WLCs identify mobility peers by MAC address. If the MAC address changes during an SSO switchover, the AireOS peer will detect the change and tear down the mobility tunnel, disrupting inter-controller client roaming. The command ' wireless mobility mac-address < MAC > ' configures a static, persistent mobility MAC address on the 9800 SSO pair that remains constant regardless of which physical unit is active. This ensures the AireOS WLC always identifies the 9800 pair by the same MAC address, maintaining the mobility tunnel and enabling seamless client roaming. Option A configures the HA interface for SSO synchronization but not for AireOS mobility interoperability. Option B sets a default gateway. Option D enables management gateway failover, unrelated to mobility peer identification. Reference: WLSD Study Guide — IOS XE WLC SSO Configuration, AireOS to 9800 Migration, Mobility Peer MAC Address Management.

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

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

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

This question requires a straightforward PoE power budget calculation. The IEEE 802.3at standard (PoE+) delivers a maximum of 30W at the Power Sourcing Equipment (PSE/switch port). Cisco 9100 Series access points such as the C9120, C9130, and C9136 are designed to operate with full functionality using PoE+ at 30W per AP. The total PoE power requirement for 12 APs is calculated as: 12 APs × 30W per AP = 360W. This figure represents the total power draw that the Cisco 3800 Series PoE+ switch must be capable of supplying across the connected AP ports simultaneously. The Cisco Catalyst 3800 Series switches offer a total PoE power budget that must be validated against this 360W requirement during the design phase. Note that some Cisco 9100 APs support higher power modes through IEEE 802.3bt (PoE++), which can provide up to 90W — but the question specifies PoE+ (802.3at) for the switch infrastructure, making 30W × 12 = 360W the correct answer. Option D (720W) would correspond to 24 APs at 30W each. Option B (1080W) would represent 36 APs. Option C (184.8W) corresponds to a non-standard per-AP power value. Reference: WLSD Study Guide — PoE Power Budget Planning, Cisco 9100 Series AP Power Requirements, Wired Infrastructure Design for Wireless Deployments.