In local AP mode, a lightweight access point builds CAPWAP connectivity to the wireless LAN controller and normally sends both control and client data traffic through the controller. Cisco commonly describes this as separate CAPWAP control and data tunnels. FlexConnect mode is different because it is designed for remote or branch deployments where the AP may locally switch client data traffic instead of backhauling it all through the WLC. That is why option C is wrong: with local switching, FlexConnect bridges traffic locally, not from the AP to the WLC. FlexConnect can also continue serving clients during a WAN or controller outage, depending on configuration and authentication method, so option B is wrong. Local mode does not turn the AP into an autonomous AP; it remains controller-based. Cisco CCNA 200-301 v1.1 Network Access expects the distinction between centralized WLC forwarding and branch-friendly FlexConnect operation. The clearly correct difference in the options is A.