Which customer is a good target for an Aruba SD-Branch solution?

Question

Options

• Aan enterprise that needs to add one large branch over MPLS
• Ba retailer that needs to support a large number of small branch sites
• Ca university that needs to provide VPN access for faculty at home
• Da small to medium business (SMB) that needs a simple solution to add a branch.

• A
  9% (3)
• B
  69% (22)
• C
  3% (1)
• D
  19% (6)

Explanation

Aruba SD-Branch is purpose-built for enterprises managing many distributed, small-to-medium branch locations - exactly the scenario a retailer faces with dozens or hundreds of small stores needing consistent, centrally managed connectivity. Option B is correct because SD-Branch bundles SD-WAN, routing, switching, and wireless into a single managed solution that scales efficiently across many sites.

Why the distractors fail:

• A - Adding one large branch over MPLS is a traditional WAN use case; SD-Branch's value is in simplifying many branches, not a single large one with an established MPLS circuit.
• C - Remote faculty VPN access is a remote-access/VPN gateway problem (e.g., Aruba VIA or a VPN concentrator), not a branch infrastructure problem.
• D - An SMB needing a branch (singular, simple) is better served by a lightweight single-device solution; SD-Branch's orchestration overhead is justified by scale, not simplicity at one site.

Memory tip: Think "SD-Branch = Scale + Simplicity for many branches." The "Branch" in SD-Branch implies a fleet of branch sites - whenever you see "large number of small sites," that's your SD-Branch signal.

No community discussion yet for this question.