Free Cisco 300-110 Practice Exam with Questions & Answers | Set: 3

The requirement for users to retain their session state 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 a mobility tunnel between WLC-A and WLC-B with both controllers configured in the same mobility group name — the group name is the trust identifier that permits the mobility tunnel and anchor-foreign relationship to form. Without the same group name, the controllers will not form a trusted mobility peer relationship. AP groups (Option C) control SSID and VLAN assignments per AP cluster but have no impact on inter-controller roaming. HA cluster configuration (Option B) creates SSO redundancy, not roaming capability between separate N+1 controllers. Redundancy port connection (Option D) is used for SSO keepalive and state sync, not mobility tunneling. Reference: WLSD Study Guide — Inter-Controller Mobility, Mobility Tunnels, Layer 3 Roaming and IP Address Preservation.

The design requirements specify a multi-LAG configuration where each LAG connects to a single switch, different VLANs are assigned to different LAGs, the controller must dynamically learn partner LAG capabilities per port, and standby ports provide redundancy upon active port failure. These requirements collectively point to IEEE 802.3ad LACP (Link Aggregation Control Protocol) as the correct protocol. LACP is the industry-standard IEEE protocol that enables dynamic negotiation of LAG membership between endpoints — the WLC and each Catalyst 9300 switch exchange LACP PDUs (LACPDUs) to discover port capabilities, negotiate bundle membership, and monitor link status. LACP supports active and passive port states where active ports initiate negotiation and passive ports respond, and it provides the standby port mechanism through its hot-standby capability for link redundancy within the bundle. The requirement to ' learn the identity of partners that can support LAG capabilities ' is the defining characteristic of LACP ' s standardized PDU exchange mechanism. PAgP (Option C) is a Cisco proprietary port aggregation protocol that, while functionally similar, is not the IEEE standard and is incompatible with non-Cisco equipment in mixed environments. OSPF (Option B) and BGP (Option D) are Layer 3 routing protocols entirely unrelated to port channel negotiation. Reference: WLSD Study Guide — Catalyst 9800 LAG Configuration, LACP IEEE 802.3ad, Multi-LAG High Availability Design.

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.

An active ping survey is used to validate network performance by sending and receiving data packets to measure end-to-end network performance, including latency, packet loss, and throughput. Ekahau site survey tools can perform active ping surveys to test the connectivity and performance of the wireless network while the surveyor walks the floor plan, producing a geographically correlated map of network performance metrics. This differs fundamentally from passive surveys, which only measure signal strength from beacons. A GPS-assisted survey (Option A) is used for large outdoor areas to automate location tracking. Spectrum analysis (Option B) identifies Layer 1 RF conditions but does not measure network performance. A passive survey (Option C) measures RSSI and SNR but does not test actual data connectivity or throughput. Active ping is the correct tool for validating that the network delivers the expected end-to-end service levels. Reference: WLSD Study Guide — Ekahau Survey Types, Active Survey Methodology, Post-Deployment Validation.

The issue described indicates that there are more critical priority access points than the backup Cisco WLC can accommodate with its available AP licenses. The backup WLC has only 10 licenses available, but 7 APs are set to critical failover priority and 5 to high failover priority — a total of 12 APs attempting to join. Even though critical priority APs are processed before high priority APs, the backup WLC can only accept 10 APs total (its license limit). Since there are 7 critical priority APs and only 10 total licenses, all 7 critical APs will fail over successfully — but if the scenario involves additional critical APs beyond the license limit, the excess will not be able to join. The oversubscription of the critical priority AP count relative to available backup WLC capacity is the root cause. AP failover priority being disabled (Option D) would mean all APs have equal priority, not that critical APs fail to join. ' network ap-priority set to enable ' (Option B) enables the priority processing globally, which would be required for the feature to work at all. Reference: WLSD Study Guide — AP Failover Priority, N+1 Redundancy License Planning, WLC License Capacity Management.

An oil terminal presents specific wireless design constraints: the requirement is pervasive coverage (maximum geographic coverage) for low-bandwidth applications (casual web and email). These requirements prioritize coverage reach over throughput optimization. The correct approach is to keep all data rates enabled, including lower rates such as 6, 9, 12, and 18 Mbps — because in an industrial environment with challenging RF propagation paths, reflective surfaces, and potential obstructions, lower data rates extend the functional coverage range of each AP. Web and email traffic does not require high data rates; even 1-6 Mbps is sufficient for these applications. Disabling rates below 54 Mbps (Option A) would dramatically shrink each AP ' s effective coverage area, requiring many more APs for pervasive coverage and failing the primary design objective. Assigning static maximum power without RRM auto-adjustment creates excessive co-channel interference. Disabling rates below 24 Mbps (Option C) still reduces coverage reach unnecessarily. Disabling 802.11n and 802.11ac MCS rates (Option D) prevents the AP from using high-efficiency modulation for nearby clients without coverage benefit. Auto power assignment combined with all rates enabled provides the optimal balance for pervasive industrial deployment. Reference: WLSD Study Guide — Industrial WLAN Design, Coverage vs. Capacity Trade-offs, Data Rate Configuration for Pervasive Coverage.

When using Metageek Chanalyzer in conjunction with a Cisco CleanAir-capable AP for Layer 1 spectrum analysis, the AP must be configured in SE-Connect mode (Spectrum Expert Connect). SE-Connect mode enables the AP ' s CleanAir radio to operate as a dedicated spectrum analyzer, feeding raw spectrum data to the connected Chanalyzer software for visualization and analysis. In this mode, the AP does not serve any Wi-Fi clients and instead focuses all radio resources on spectrum scanning. Metageek Chanalyzer uses the SE-Connect mode specifically to receive the CleanAir ASIC ' s spectrum analysis data. Local mode (Option A) serves clients normally, only providing periodic CleanAir reports. Sniffer mode (Option B) captures 802.11 frames for protocol analysis and does not provide raw spectrum data to Chanalyzer. Monitor mode (Option C) performs WIDS scanning and RRM measurements but does not support the direct Chanalyzer integration. SE-Connect is the specific mode that enables external spectrum analysis software to use the CleanAir ASIC ' s spectrum data in real time. Reference: WLSD Study Guide — Cisco CleanAir Technology, AP Operating Modes, SE-Connect Mode for Spectrum Analysis.

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.