Authentic Cisco Certification Exam 300-110 Questions Answers

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.

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.

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.