An engineer must deploy FlexConnect APs to a site that typically has 300 ms latency to the WLC. Which typical operating mode must the engineer plan on for normal operations?

With 300ms WAN latency the FlexConnect AP will regularly operate in standalone mode where it cannot maintain a reliable real-time connection to the WLC. Local authentication - using cached credentials or a local RADIUS server - and local switching allow clients to authenticate and pass traffic entirely at the branch without WLC involvement, which is the required design for high-latency or unreliable WAN links.

Central authentication and central switching both require continuous low-latency communication with the WLC for each client session, and 300ms latency would cause authentication timeouts and unacceptable user experience.

Central authentication still depends on real-time WLC reachability for each 802.1X or web authentication event, making it unsuitable when WAN latency reaches 300ms.

Connected mode describes the FlexConnect operational state when the AP has a stable low-latency link to the WLC; at 300ms latency, standalone mode - not connected mode - is the expected normal operating state.