Q: 11
Where are wireless client roaming decisions made?
Options
Discussion
Always confused me at first too. It's A for this one.
C/D? I always thought the APs talk to each other and sort out roaming, especially with newer Aruba gear. Central seems like it could be involved with decision making too. Not totally convinced it's just the client deciding here, so maybe C or D.
A Device makes the call here.
A Official Aruba study guides and vendor labs both clarify that client devices handle roaming decisions, not the network side. If anyone found a conflicting answer on another practice exam, would be good to double check with official docs.
C or D? Seen people pick C because APs coordinate for seamless roaming, but the question says "decision," not "facilitation." In standard setups, client decides, so picking A makes sense. Easy to overthink if you mix up 802.11k/v hints vs actual handoff trigger.
A . While Aruba Central and controllers can provide steering hints, the actual decision to roam sits with the client device itself. It checks its own RSSI and thresholds before jumping to another AP. Not 100% sure if there’s some exception on certain managed networks, but pretty sure it’s A for standard wireless configs. Anyone see different behavior with proprietary clients?
It's actually A. The decision to roam is made by the client device based on things like signal strength and quality, not by the APs or controller. Network gear can suggest or steer, but only the client triggers the move. Seen this a few times in Aruba docs too. Correct me if I'm off.
B, not A. The client device itself makes the final decision to roam, not the virtual controller. Controllers can assist with features like 802.11k/v but can't force the client to jump APs. Seen this explained a few times in Aruba docs.
Maybe B? I thought the controller had a say in roaming. Not totally sure, can someone confirm if this is right or if it's actually handled by the APs or something else?
Be respectful. No spam.
