You are deploying a new AOS-10 mobility gateway cluster. Due to customer requirements, the gateways must be configured with static IP addresses and are restricted from communicating using port 443…

Question

Options

• AChoose Static Activate and Configure:
• BChoose Full Setup and Configure:
• CChoose Static Activate and Configure-
• DChoose Full Setup and Configure:

• A
  5% (3)
• B
  81% (47)
• C
  2% (1)
• D
  12% (7)

Explanation

Full Setup and Configure (Option B) is correct because the firewall restriction limits port 443 traffic exclusively to *.central.arubanetworks.com. The standard Aruba Activate onboarding process requires communication to activate.arubanetworks.com, which falls outside this allowed domain - making any Activate-based method impossible in this environment. Full Setup lets you manually configure the gateway's Central connection details directly, allowing it to reach Central without ever needing to contact the Activate service.

Options A and C ("Static Activate and Configure") fail for the same core reason: even when using static IPs, "Static Activate" still routes through the Aruba Activate service (activate.arubanetworks.com), which is blocked by the customer's firewall policy. Option D, while also labeled "Full Setup and Configure," is incorrect based on configuration details not shown (likely a wrong sub-option in the full exam), making B the only complete and accurate answer.

Memory tip: Think of it this way - "Activate" always needs activate.arubanetworks.com. If that URL is blocked, Activate is dead. "Full Setup" skips Activate entirely and talks directly to Central - so when the only open door is *.central.arubanetworks.com, Full Setup is the only key that fits.

No community discussion yet for this question.