What is one way that an Aruba SD-WAN solution transforms a company's WAN?

Question

Options

• AIt requires all traffic to pass through security appliances in the data center before exiting to the
• BIt enables the company to use a mix of MPLS. Internet, and LIE uplinks to connect branches to the
• CIt replaces expensive appliances for providing WAN uplinks win WAN software that runs on Aruba
• DIt increases specialization for branch equipment, so that a single appliance is no longer expected

• A
  15% (8)
• B
  71% (37)
• C
  8% (4)
• D
  6% (3)

Explanation

Option B is correct because a core value proposition of SD-WAN is transport independence - it abstracts the underlying connectivity so branches can simultaneously use MPLS, broadband Internet, and LTE (the "LIE" in the question is likely a typo for LTE), bonding them intelligently for cost savings and redundancy without being locked into a single expensive link type.

Why the distractors are wrong:

• A describes traditional hub-and-spoke backhauling to a data center - exactly the legacy WAN model SD-WAN is designed to replace with direct, policy-driven cloud/internet breakout.
• C is a tempting distractor but inverts reality: SD-WAN still requires physical WAN uplinks (fiber, cable, LTE modems); the "software-defined" part is the control plane, not the physical connectivity layer itself.
• D is the opposite of SD-WAN's promise - SD-WAN reduces specialization by consolidating routing, security, and WAN optimization into a single branch appliance (the gateway), rather than increasing the number of dedicated devices.

Memory tip: Think of SD-WAN as a "blender for WAN links" - you pour in MPLS, Internet, and LTE, and it blends them into one smart, policy-driven connection. The whole point is mixing link types, so whenever you see "mix of uplinks," that's your SD-WAN signal.

No community discussion yet for this question.