You have proposed an Aruba Central solution for a customer that requires high availability for management. What benefit of Central should you explain?

Question

Options

• ACentral can be deployed as a primary appliance and standby appliance with no additional licensing
• BCentral supports integration with third-party backup solutions such as Veeam.
• CCentral can switch to a local management consoled if the connection to the cloud is lost.
• DCentral is automatically deployed as a clustered solution in the customer also has a Mobility

• A
  6% (1)
• B
  11% (2)
• C
  83% (15)

Explanation

Option C is correct because Aruba Central, being a cloud-based management platform, addresses the single biggest HA concern customers have: "what happens if my cloud connection drops?" The answer is that Central supports a local management console fallback - devices can continue to be managed locally if connectivity to the cloud is lost, ensuring no management gap.

Why the distractors are wrong:

• A is false - Central is a cloud SaaS platform, not an on-premises appliance, so there is no "primary/standby appliance" deployment model.
• B is a fabricated distractor - Central is a cloud service backed by HPE's infrastructure; it doesn't integrate with third-party backup tools like Veeam, which are for on-prem VM/data backups.
• D is incomplete and misleading - the sentence appears cut off, and Central's HA is not dependent on whether the customer has a Mobility Controller; it's inherent to the cloud architecture.

Memory tip: Think of Central's HA promise as a "cloud-first, local-safe" model - it lives in the cloud for scalability, but never leaves you stranded if the cloud becomes unreachable. The key phrase to remember is "local management console fallback," which is the core HA differentiator Central salespeople emphasize.

No community discussion yet for this question.