Cisco WLC Optimized Roaming and BSS Transition Configuration
Short answer
D Enable BSS transition on the SSID and optimized roaming at the radio level.
Question
Key Takeaways
It tests the specific location of feature activation: BSS transition belongs at the SSID level, while optimized roaming thresholds are configured at the radio level.
This question addresses the correct configuration hierarchy for Cisco WLC optimized client roaming and BSS transition (802.11v) to prevent disconnections.
Common mistake: Candidates often confuse the scope of these features, selecting options that place BSS transition on the radio or optimized roaming on the SSID without the radio threshold.
Expert Analysis
Why the Answer Is Correct
The correct configuration requires enabling BSS transition (802.11v) at the SSID level to allow the AP to suggest candidate APs to the client. Simultaneously, optimized roaming must be enabled at the radio level with an RSSI threshold to trigger the steering process when signal strength drops below the defined limit (e.g., -72dBm). This combination ensures the controller proactively guides clients to better connected APs rather than letting them disconnect.
Why the Other Options Are Wrong
Option A incorrectly places optimized roaming on the SSID; it is a radio-level setting. Option B suggests disabling coverage hole detection, which would worsen roaming issues by removing proactive reconnection logic. Option C disables optimized roaming entirely, relying solely on 802.11v, which may not enforce the specific RSSI-based steering required in this scenario as effectively as the combined approach.
Community Comment Notes
Community consensus strongly supports Option D. As noted by user raresalexa_22, "The BSS is enable on SSID and not on radio," highlighting the critical distinction in configuration hierarchy. Another user, Lutech, confirmed the path via the Advanced tab under Wireless settings, reinforcing the radio-level nature of optimized roaming. While some users initially debated A or C, the majority correctly identified that D aligns with Cisco's official architecture for steering clients.
Exam Strategy
Always distinguish between global/SSID-level policies and radio-level operational parameters. When configuring roaming, remember that steering mechanisms (BSS Transition) are policy-driven (SSID), while trigger thresholds (RSSI) are hardware/channel-specific (Radio).
Frequently Asked Questions
Why is BSS transition configured at the SSID level?
Can optimized roaming be set globally?
Community Votes
78% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 6 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 6
-
raresalexa_22 👍 5 Answered DThe BSS transition will help customer to move to the next AP in there roaming process. The BSS is enable on SSID and not on radio.
-
n3sh 👍 2 Answered ABSS Transition (802.11v): This feature helps in steering the client to a better AP by providing information about the best candidate APs for roaming. Enabling BSS transition ensures that clients are informed about other APs they can move to, improving the roaming decisions made by the client devices. Optimized Roaming: This feature on the SSID level ensures that the clients are prompted to roam to a better AP when their signal strength falls below the configured RSSI threshold.
-
Lutech 👍 1 Answered DChoose Configuration > Wireless > Advanced. Step 2 On the Advanced page, click the relevant band's tab: either 5 GHz Band or 2.4 GHz Band. Game over
-
Farhad123 👍 1A is the right choice, 802.11V or BSS Transition should apply on the radio level, and Optimized roaming should apply on SSID level
-
Farhad123 👍 1 Answered DMy previous answer is wrong, D is the correct answer.
Show 1 more comment
-
abam_ 👍 2option C sounds better
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.