Cisco Designing Cisco Wireless Networks 300-110 WLSD Exam Questions

Answer : D

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.

Answer : C

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.

Answer : A

The requirement for users to retain their VLAN assignment 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 creating a mobility group between WLC-A and WLC-B with both controllers configured with the same mobility group name --- the group name is the trust identifier that permits the mobility tunnel and anchor-foreign relationship to form. An SSO cluster (Option B) creates redundancy between two WLCs operating as one logical entity, not inter-building roaming between independent controllers. 802.11r (Option C) accelerates re-association but does not preserve IP addresses across different Layer 3 subnets. AP groups (Option D) control SSID and VLAN assignments but do not enable inter-controller IP preservation. Reference: WLSD Study Guide --- Inter-Controller Mobility, Layer 3 Roaming, IP Address Preservation.

Answer : D

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.

Answer : C

For a high-density classroom deployment using 5 GHz with channel bonding in groups of two (40 MHz channels), the correct configuration is to set the channel width for 802.11a (5 GHz) to 40 MHz and set the 24 Mbps data rate to Mandatory. Channel bonding refers to combining two adjacent 20 MHz channels into a single 40 MHz channel, doubling the channel width. Since the requirement specifies 5 GHz operation (where high-density design is appropriate), this must be applied to the 802.11a radio profile, not 802.11b (which operates only on 2.4 GHz). Setting 24 Mbps as Mandatory ensures that APs transmit management frames (beacons, probe responses, and other control frames) only at 24 Mbps --- this is how the 'only allow APs to send 802.11 management frames at 24 Mbps' requirement is implemented. Setting it as Supported (Options B and D) would allow the AP to use lower rates for management frames. Options A and D incorrectly target 802.11b, which does not support 40 MHz channels. Reference: WLSD Study Guide --- High-Density WLAN Design, 802.11a Channel Configuration, Data Rate and Channel Width Settings.

Answer : C

Mobility groups are created by configuring each Wireless LAN Controller (WLC) to use the same mobility domain name (mobility group name) and defining each WLC as a peer in the static mobility members list of every other WLC in the group. This bidirectional configuration establishes the trusted peer relationship and enables WLCs to exchange client information, security credentials, and state data for seamless roaming. The same mobility group name on all WLCs creates a shared identity; the static peer list defines which controllers are trusted mobility partners and provides their management IP addresses and MAC addresses for tunnel establishment. Option A is incorrect because members should run compatible (ideally the same) software versions, not different ones. Option B is incorrect --- all WLCs in a mobility group must use the same virtual IP address for proper roaming. Option D is incorrect --- in an HA SSO pair, the pair presents as a single logical mobility entity, not as two separate peers. Reference: WLSD Study Guide --- Mobility Group Configuration, Peer Configuration Requirements, Mobility Domain Architecture.

Answer : B

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.