A customer has a management solution that provides RF-metrics for the wireless solution, but this information is not enough to identify the source of all connectivity issues. The customer needs one…

Question

Options

• AAppRF
• BUser and Entity Behavior Analytics
• CVisualRF
• DConnectivity Health

• A
  6% (2)
• B
  11% (4)
• C
  3% (1)
• D
  81% (29)

Explanation

Connectivity Health in Aruba Central goes beyond RF metrics by analyzing the full client connection journey - RF association, 802.1X authentication, DHCP, DNS, and gateway reachability - so helpdesk teams can pinpoint exactly where a failure occurs, not just that the signal was weak. This directly reduces tickets by giving support staff actionable, layered diagnostics in a single pane of glass.

Why the distractors are wrong:

• A. AppRF - Analyzes application-layer traffic and bandwidth usage; useful for visibility but irrelevant to diagnosing connectivity failures.
• B. User and Entity Behavior Analytics (UEBA) - A security feature that flags anomalous user/device behavior for threat detection, not connectivity troubleshooting.
• C. VisualRF - Provides RF floor-plan visualization and heat maps; it's still RF-focused, which is exactly what the customer already has and wants to move beyond.

Memory tip: Think of Connectivity Health as a "connection autopsy" - it walks through every step a client takes to get online (RF → Auth → DHCP → DNS → Gateway), so when something breaks, you know which step failed, not just that the RF looked fine.

No community discussion yet for this question.