Company a has recently acquired Company B, which has two remote office. Company A is using VMware hosted Cloud Gateways, and Company B is using a VMware SD-WAN with a Hub- Spoke topology. Which…

Question

Options

• ASite-to-Site VPN
• BBranch to CASH
• CBranch to Branch VPN
• DBranch to Non VMware SU-WAN Site

• A
  6% (2)
• B
  77% (24)
• C
  13% (4)
• D
  3% (1)

Explanation

Option B (Branch to CASH) is correct because Company B's SD-WAN branches need to establish connectivity to Company A's VMware-hosted Cloud Gateways (CASH = Cloud Access Security Hub), which serve as the centralized termination point for inter-company traffic. This VMware Cloud VPN profile is specifically designed to connect SD-WAN branch edges to VMware-hosted Cloud Gateway infrastructure.

Why the others are wrong:

• A (Site-to-Site VPN) is a generic term for traditional VPN tunnels and is not a VMware SD-WAN–specific Cloud VPN profile; it doesn't leverage the SD-WAN overlay.
• C (Branch to Branch VPN) creates direct tunnels between two SD-WAN branch edges - appropriate for intra-company branch traffic, but not for reaching Cloud Gateways on the other company's side.
• D (Branch to Non-VMware SD-WAN Site) is used when the remote site has no VMware SD-WAN infrastructure at all; Company A does have VMware infrastructure (Cloud Gateways), so this profile doesn't apply.

Memory tip: Match the destination to the profile name - if one company's "endpoint" is a Cloud Gateway (CASH), the VPN profile must say "Branch to CASH." Think: "Who am I connecting TO?" - Cloud Gateway → CASH profile.

No community discussion yet for this question.