Option B. Was it specifically asked for the AP not to revert automatically, or would auto-fallback be preferred if the original controller becomes available? That would change if A or B is correct here, since fallback setting is key.
I don’t think it’s A in this scenario. Since the customer wants to avoid automatic switchover, B is the way to go. Setting AP fallback to disabled keeps the AP on the new WLC until someone moves it manually. Pretty sure that’s how Cisco handles this, but always worth double-checking controller settings.
If they were asking about deployment planning instead of network requirements, wouldn't D (power sockets) actually matter more? The way it's worded feels like B and C fit better for design though.
Had something like this in a mock, pretty sure it's B since actual debugging for mobility tunneling issues is done using commands on the WLC. Connectivity checks like C are good for port testing, but not real debug steps. Agree?
A customer has a single anchor WLC named Anchor A. Anchor A is in a DMZ and provides guest access. The customer wants to deploy an additional anchor controller named Anchor B to provide redundancy if Anchor A fails. Which design approach should be taken for the guest WLAN priority on the foreign WLC for each anchor WLC?
Not totally sure because both options have valid use cases, but since it's for redundancy only (not load balancing), maybe D fits better here. Anyone else think otherwise?
Seen this in some practice labs, enabling AP fallback globally on the WLC (so C) is necessary for APs to automatically return to their primary controller after a failover. Just setting priorities or using DHCP options won’t trigger the fallback. If you’re prepping, official Cisco guides and lab practice really help clarify these controller behaviors. Pretty sure about C but let me know if someone has had different results.
I don't think D really solves the fallback issue here. Setting AP failover priority changes how APs pick a controller during a failover, but it doesn't make them return to their primary when it comes back up. That feature is controlled by enabling AP fallback globally (C). Seen similar question in practice materials, so I'm pretty sure that's what Cisco wants. Anyone get different results on real gear?
I think it's A since FlexConnect group is needed for local switching and CCKM handles the fast roaming piece. Saw similar question in practice and this combo was flagged as right. Open to other takes if I missed something though.
Had something like this in a mock and I picked C. Pretty sure some guides still list 4000 APs per RF group, maybe for certain hardware or earlier docs. Not 100% though since Cisco updated limits, so open to being wrong here.