A mid-sized customer is having trouble deciding between in a controllerless Aruba solution and a controller-based one. What can you explain to the customer about how Aruba protects the company's…

Question

Options

• AThe same Aruba APs can be deployed in controllerless Instant mode and then later changed to
• BAruba offers a buy-back program for controllerless Instant APs, making it cost effective to later
• CThere is no difference in features and capabilities between a controllerless and controller-based
• DAruba uses a cloud subscription-based licensing model for controllerless APs, and these licenses

• A
  4% (1)
• B
  77% (20)
• C
  4% (1)
• D
  15% (4)

Explanation

Option B is correct because Aruba's buy-back program directly addresses the investment protection concern: if a customer starts with a controllerless Instant deployment and later determines they need a controller-based architecture, Aruba offers a program to recoup value from those Instant APs, reducing the financial risk of the initial decision.

Why the distractors are wrong:

• Option A is misleading because while Aruba Instant APs share hardware with controller-managed APs, simply "changing mode" is not the primary investment protection story Aruba markets - the answer is cut off but implies a clean migration that oversimplifies the process.
• Option C is false - there are meaningful differences between Instant and controller-based deployments (scale, centralized policy management, advanced features like PEF), so claiming no difference is inaccurate and would be a poor selling point.
• Option D is a distractor that conflates cloud/Aruba Central licensing with investment protection - subscription licenses for Instant APs don't directly protect the customer's hardware investment if they need to switch architectures.

Memory tip: Think "B = Buy-Back = Bridge." The buy-back program acts as a financial bridge, letting customers move from Instant to controller-based without abandoning sunk costs. If a question mentions a mid-sized customer worried about commitment, Aruba's answer is a structured exit ramp, not a technical workaround.

No community discussion yet for this question.