For which use case should you recommend an Aruba virtual gateway?

Question

Options

• AEliminating the need for branch gateway appliances by replacing thorn with virtual gateways that
• BManaging branch gateways across multiple sites and providing the SD-WAN orchestration
• CIntegrating Aruba CX switches into a virtualized data center, such as one that uses VMware
• DConnecting Aruba branch gateways to cloud applications through a virtual private cloud such as

• A
  7% (3)
• B
  76% (35)
• C
  4% (2)
• D
  13% (6)

Explanation

Option B is correct because Aruba virtual gateways are designed to run as hub/orchestrator nodes in an SD-WAN deployment - typically hosted in a data center or cloud environment - where they centrally manage spoke branch gateways across multiple sites and handle SD-WAN policy and orchestration without requiring dedicated physical hub appliances.

Option A is wrong because virtual gateways do not replace branch gateways; physical branch gateways still exist at each site. The virtual gateway is the hub, not a substitute for the spokes.

Option C is wrong because integrating Aruba CX switches into a VMware-based data center is a data center switching/fabric concern - unrelated to the SD-WAN gateway role that virtual gateways serve.

Option D is wrong because connecting branch gateways to cloud applications via a VPC describes a cloud on-ramp or IPsec tunnel scenario, which is a feature of the broader SD-WAN architecture rather than the defining purpose of a virtual gateway deployment.

Memory tip: Think of the virtual gateway as the brain in the cloud - it has no branch to serve locally, so its job must be managing and orchestrating the physical branches below it. "Virtual = hub orchestrator, physical = branch spoke."

No community discussion yet for this question.