A customer has an Aruba ESP (Edge Services Platform) solution. A site uses an AP-only deployment model. Later the customer wants to use gateways.

Question

Options

• AAdd the gateways, use thorn to control the existing APs. and use the gateways' Ul to manage the
• BAdd the gateways, there is no need to change the existing APs' mode, and the gateway can be
• CReplace the existing APs will) now Campus APs, and then add the gateways.
• DChange the Apps' mode to Campus mode. upgrade to campus software and thon add the

• A
  3% (1)
• B
  76% (25)
• C
  6% (2)
• D
  15% (5)

Explanation

Option B is correct because Aruba ESP is designed for flexible, non-disruptive expansion - when gateways are added to an existing AP-only site, the APs can continue operating in their current Instant mode without any mode change or reconfiguration. The gateway simply joins the existing infrastructure and Aruba Central continues as the unified management plane for both APs and gateways.

Option A is wrong because it implies using the gateway's local UI to manage APs - in an ESP solution, Aruba Central is the management plane, not a local gateway interface; local management would undermine the cloud-first architecture.

Option C is wrong because physically replacing existing Instant APs with "Campus APs" is unnecessary and costly - ESP's architecture allows gateways and Instant APs to coexist without hardware swaps.

Option D is wrong because changing AP mode to Campus mode and upgrading software would be a disruptive, unnecessary migration - ESP's value proposition is exactly that you don't need to do this to scale up.

Memory tip: Think of Aruba ESP as a "plug-in and grow" platform - like adding a router to a Wi-Fi network, you just add the gateway without touching what already works. If an answer involves changing or replacing existing APs when adding a gateway, it's wrong.

No community discussion yet for this question.