An organization is planning on concerting remote offices to FlexConnect to centralize their Cisco WLCs. When preparing the Cisco ACLs for the new deployment, which three restrictions must the…

FlexConnect deployments require FlexConnect-specific ACLs because standard WLC ACLs are not pushed to or enforced by the FlexConnect AP when traffic is locally switched at the branch.

FlexConnect ACLs support a maximum of 64 rules per ACL, which engineers must account for when designing access policy for branch office deployments.

The per-ACL rule limit for FlexConnect is 64, not 32, so this understates the actual capacity available to the engineer.

Standard WLC ACLs are not supported in FlexConnect mode for locally switched traffic; only FlexConnect-specific ACLs are applicable.

FlexConnect ACLs are applied inbound only on the AP, meaning traffic is inspected as it enters the AP interface but not as it exits, which limits bidirectional enforcement capability.

FlexConnect ACLs are enforced inbound only, not in both directions, making bidirectional enforcement unsupported in this deployment model.