A core principle of Aruba Central is cloud-native, zero-touch provisioning and management. While option A describes a benefit, option B most accurately captures the fundamental operational shift: APs receive their entire configuration, software, and policies from Central, eliminating the need to manage individual configuration files on the devices themselves.

Good RSSI means the signal is strong, but poor SNR means the noise floor is also high, drowning out the good signal. This is a classic signature of RF interference, most commonly from other Wi-Fi networks on the same or overlapping channels. Investigating airtime utilization and channel congestion is the correct, data-driven first step.

An Open SSID with a Captive Portal is the standard method for guest access. Aruba Central’s built-in Social Login feature (like Facebook, Google) allows for easy, password-less authentication while also providing a mechanism to present terms of service and collect consent, meeting both the seamlessness and marketing requirements.

Aruba Central’s Local Survivability feature is specifically designed for this scenario. When enabled for an SSID, critical configuration is cached on the lead IAP. If the connection to Central is lost, the IAP cluster continues to operate and serve that SSID using the last-known-good configuration, ensuring business continuity.

Labels provide a non-hierarchical, cross-cutting tagging mechanism. For example, you could label all APs as “Critical-Infrastructure” or all devices in a building as “Building-A,” regardless of their Group. This allows for powerful filtering in alerts, reports, and the UI, and can be used to apply certain monitoring or alerting policies across organizational boundaries.

The Client Insights report provides detailed, searchable information about connected clients. Filtering by ‘Protocol’ (e.g., 802.11b, 802.11g, 802.11n) or ‘PHY Type’ is the most direct way to identify legacy clients. This data-driven approach allows the admin to find specific devices and address the issue, such as updating NIC drivers or device firmware.

For WPA2-Enterprise to work seamlessly, client devices must trust the certificate presented by the RADIUS server during the EAP-TLS or PEAP handshake. By uploading the internal CA’s public certificate to the SSID’s Trusted Server Certificates list, the AP instructs the client to trust server certificates signed by that CA, preventing untrusted certificate warnings and connection failures.

The Audit Trail is a critical troubleshooting tool in Central. It provides a timestamped log of administrative actions and system events for each device. Checking it for the disconnected APs can reveal if a recent configuration push failed, a firmware update was attempted, or if there were other alerts before the disconnect, providing crucial context before taking more drastic action.

Configuration Templates offer a DevOps-like approach. They allow you to define configuration as code (using CLI-like syntax), maintain different versions, and easily roll back to a previous version if needed. This is especially powerful for applying standardized, complex configurations (e.g., specific firewall rules or advanced radio settings) across many different AP Groups with consistency and control.

A core principle of Aruba Central is cloud-native, zero-touch provisioning and management. While option A describes a benefit, option B most accurately captures the fundamental operational shift: APs receive their entire configuration, software, and policies from Central, eliminating the need to manage individual configuration files on the devices themselves.0