What happens when a FlexConnect AP changes to standalone mode?

Question

Options

• AAll controller-dependent activities stop working except the DFS.
• BAll client roaming continues to work
• COnly clients on central switching WLANs stay connected.
• DAll clients on an WLANs are disconnected

• A
  87% (33)
• B
  3% (1)
• C
  8% (3)
• D
  3% (1)

Explanation

FlexConnect Standalone Mode Behavior

When a FlexConnect AP loses its connection to the WLC and enters standalone mode, it can continue to locally switch traffic for locally switched WLANs, but any feature that requires active communication with the controller (such as RADIUS authentication, rogue detection reporting, and certain management functions) will stop working. DFS (Dynamic Frequency Selection) is a radio-level function built into the AP itself and continues to operate independently of the controller, making option A correct.

Why the distractors are wrong:

• B is incorrect because client roaming that depends on the controller (inter-AP roaming with controller involvement) will not fully function in standalone mode.
• C is incorrect because it's actually the opposite - clients on locally switched WLANs stay connected; clients on centrally switched WLANs lose connectivity since their traffic path requires the controller.
• D is incorrect because FlexConnect's entire purpose is to maintain some client connectivity during controller outages - clients on locally switched WLANs remain connected.

Memory Tip: Think of FlexConnect standalone mode as "local survives, central dies" - anything that can run locally on the AP keeps working, while controller-dependent features (except DFS) go dark.

No community discussion yet for this question.