Cisco Updated 350-101 Exam Questions and Answers by ilyas

Optimized roaming is a Cisco WLC feature designed to reduce sticky-client behavior. A sticky client remains associated to an AP even after moving far enough away that another AP would provide better RF service. Cisco describes optimized roaming as actively monitoring client data RSSI and disconnecting clients when received signal strength falls below the configured threshold. The official Catalyst 9800 documentation states that optimized roaming “disassociates client when the RSSI is lower than the set threshold,” which directly matches option A.

This function does not calculate device location through peer-to-peer beaconing, does not depend on external experience services, and is not static load balancing. It is an RF/client-roaming enforcement mechanism controlled by the wireless infrastructure. In practical operation, the AP/WLC evaluates client signal quality and, when the configured optimized roaming criteria are met, forces the client to disconnect so it can reassess the RF environment and roam to a better AP. Cisco also notes that optimized roaming helps maintain client connectivity by managing disassociationn based on RSSI and data-rate thresholds. Reference topics:Client Connectivity Configuration — client roaming behavior, sticky-client mitigation, RSSI thresholds, and WLC roaming optimization

The correct command issecurity dot1x authentication-list RADIUS_AUTH_LIST. On a Catalyst 9800 WLC, the WLAN configuration must bind the WLAN’s 802.1X authentication process to an AAA authentication method list. Cisco’s Catalyst 9800 802.1X configuration workflow shows the WLAN entered with wlan < profile-name > < wlan-id > < ssid-name > , followed by the command security dot1x authentication-list < dot1x-list-name > . Cisco configuration guide examples also show the same syntax under WLAN configuration mode as Device(config-wlan)# security dot1x authentication-list auth-list-name.

In the exhibit, security wpa akm dot1x enables 802.1X as the key-management method, while security wpa wpa2 and security wpa wpa2 ciphers aes establish WPA2/AES security. These statements define the WLAN security framework, but they do not identify which AAA method list will be used to reach the RADIUS backend. The missing command must therefore attach the named authentication list RADIUS_AUTH_LIST to dot1x authentication. Options A, B, and C are parser-invalid or incorrectly ordered IOS XE syntax. Reference topic:Client Connectivity Configuration — WPA2-Enterprise WLAN configuration, 802.1X authentication, AAA method lists, RADIUS-backed client access, and Catalyst 9800 WLAN security commands.

Cisco lightweight and Catalyst access points use CAPWAP for AP-to-controller discovery and join operations. For AP-side preconfiguration, Cisco documents the syntax as capwap ap {primary-base | secondary-base | tertiary-base} controller-name controller-ip-address, specifically for configuring primary, secondary, and tertiary controllers on the AP. This matches option B exactly because it includes the CAPWAP AP command, the controller priority keyword, the controller name, and the controller management IP address. (Cisco)

The Catalyst 9800 AP join process also recognizes these configured controller entries in priority order: primary controller using capwap ap primary-base, secondary controller using capwap ap secondary-base, and tertiary controller using capwap ap tertiary-base. (Cisco) This allows the AP to attempt a backup controller when the preferred controller is unavailable, which is appropriate for remote sites with intermittent WAN reachability. Option A uses obsolete or invalid setcontroller syntax. Option C invents an ap join command format. Option D incorrectly inserts wlc into the AP CAPWAP command. Reference topics:Wireless Network Implementation —CAPWAP discovery, AP join process, Catalyst 9800 controller redundancy, and AP CLI provisioning.

Optimized roaming is a Cisco WLC feature designed to reduce sticky-client behavior. A sticky client remains associated to an AP even after moving far enough away that another AP would provide better RF service. Cisco describes optimized roaming as actively monitoring client data RSSI and disconnecting clients when received signal strength falls below the configured threshold. The official Catalyst 9800 documentation states that optimized roaming “disassociates client when the RSSI is lower than the set threshold,” which directly matches option A.

This function does not calculate device location through peer-to-peer beaconing, does not depend on external experience services, and is not static load balancing. It is an RF/client-roaming enforcement mechanism controlled by the wireless infrastructure. In practical operation, the AP/WLC evaluates client signal quality and, when the configured optimized roaming criteria are met, forces the client to disconnect so it can reassess the RF environment and roam to a better AP. Cisco also notes that optimized roaming helps maintain client connectivity by managing disassociationn based on RSSI and data-rate thresholds. Reference topics:Client Connectivity Configuration — client roaming behavior, sticky-client mitigation, RSSI thresholds, and WLC roaming optimization