What facts relate to controllers and APs in a Split MAC architecture?

In a Split MAC architecture, the correct understanding is that controllers and access points (APs) use a centralized IP framework. This architecture separates the management and control functions from the data functions. The controller is responsible for managing and controlling the network, while the access points handle the actual data transmission. When APs are deployed in this structure, they usually connect back to a centralized controller, which helps manage configurations, security settings, and network policies across multiple APs efficiently.

This centralized approach allows for easier network management, better resource allocation, and improved consistency in security protocols across the deployment. Because of this centralized framework, the controller can effectively communicate with various APs, allowing them to function cohesively as part of a larger network architecture.

The other options don't accurately reflect the characteristics of Split MAC architecture. For example, while APs can function independently in some scenarios, they typically depend on a controller for configuration and management in a Split MAC setup, so the assertion that they can operate without any connection to the internet lacks context in terms of how they are used in this architecture. Additionally, the claim about controllers and APs needing to operate in different frequency bands is not a requirement of a Split MAC setup; they can operate on the same frequency bands