Exactprep 300-110 Questions

Cisco ' s mobility group architecture enables seamless client roaming between WLCs by establishing a trusted peer relationship and shared mobility domain. When two Cisco Catalyst 9800-80 WLCs are placed in the same mobility group, they establish CAPWAP mobility tunnels enabling both Layer 2 and Layer 3 roaming with session continuity including IP address preservation. Within the same mobility group, WLCs exchange client state information, allowing 802.11r Fast BSS Transition, 802.11k neighbor reports, and 802.11v BSS Transition Management to function across controller boundaries. No specific primary or secondary roles are assigned within a mobility group — all members are peers with equal standing for roaming purposes, which is precisely what Option D describes. Option A incorrectly implies a hierarchical structure that does not exist in mobility group peer relationships. Option B separating the WLCs into different groups would break inter-building roaming since clients would experience a full re-authentication cycle. Option C imposing an anchor relationship is appropriate only for guest WLANs. Reference: WLSD Study Guide — Mobility Group Architecture, Inter-Controller Roaming, 802.11r/k/v Fast Roaming Design.

To focus the coverage heat map on the desired coverage threshold, the engineer should use the RSSI slider to set the heat map to the desired cutoff filter. This action adjusts the display to show only the signal levels that meet or exceed the specified RSSI value, effectively filtering out weaker signals and highlighting areas with sufficient coverage. In Ekahau and similar survey tools, the RSSI slider provides a dynamic way to set minimum signal thresholds, allowing the engineer to quickly validate whether coverage meets design targets such as -67 dBm for voice or -70 dBm for data. Changing the color scheme (Option A) only modifies the visual representation without filtering data. The RSSI calibration tool (Option B) adjusts how the tool perceives signal levels, not the display filter. Filtering by AP (Option D) would remove APs from the view, potentially hiding coverage gaps. Reference: WLSD Study Guide — Post-Deployment Survey, Ekahau Heat Map Tools, RSSI Coverage Filtering.

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.

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.