You have proposed an Aruba wireless solution to a hospital with very high availability requirements for the wireless network. Which feature of Aruba solutions should you explain provides seamless…

Question

Options

• Alive mobility tracking with Aruba Meridian
• Bconnectivity Health in AirWave or Central
• Cclustering with ArubaOS 8.x and above
• DAirMatch and ClientMatch with Mobility Master (MM)

• A
  3% (1)
• B
  11% (4)
• C
  83% (30)
• D
  3% (1)

Explanation

Clustering with ArubaOS 8.x and above (C) is correct because ArubaOS 8.x introduced controller clustering, which allows multiple Mobility Controllers to operate as a single logical unit - providing active-active redundancy, seamless client failover without session drops, and hitless software upgrades where one controller upgrades while others maintain traffic. This directly addresses the hospital's high availability requirement.

Why the distractors are wrong:

• A (Aruba Meridian) is a location services/wayfinding platform - it tracks people and assets indoors, not controller redundancy.
• B (Connectivity Health in AirWave/Central) is a monitoring and diagnostics tool; it can detect problems but does not prevent downtime or provide failover.
• D (AirMatch/ClientMatch with MM) are RF optimization and client steering features - AirMatch handles channel/power planning, ClientMatch steers clients to better APs, but neither provides controller-level failover or live upgrades.

Memory tip: Think "cluster = continuity" - just like a hospital needs multiple doctors on call so no single absence disrupts care, ArubaOS clustering keeps multiple controllers active so no single controller failure (or upgrade) disrupts the network.

No community discussion yet for this question.