A company is expanding its operations to multiple cloud environments and needs seamless connectivity between their on-premises data centers and the cloud environments. They want to ensure high…

Question

Options

• APrisma SD-WAN's integration with AWS Cloud WAN using Tunnel-less Connect
• BDedicated MPLS lines to each cloud provider for guaranteed bandwidth
• CTraditional VPN tunnels with manual configuration for each cloud environment
• DPrisma SD-WAN CloudEdge Connector for dynamic traffic routing

• A
  61% (39)
• B
  5% (3)
• C
  22% (14)
• D
  13% (8)

Explanation

Option A is correct because Prisma SD-WAN's integration with AWS Cloud WAN using Tunnel-less Connect provides native, high-performance connectivity between on-premises environments and cloud infrastructure by eliminating IPSec tunnel overhead - directly addressing the requirement for high performance without complex tunneling protocols. Option B (MPLS) is wrong because dedicated MPLS circuits are expensive, slow to provision, and don't natively integrate with cloud environments the way SD-WAN does. Option C (Traditional VPN) fails because the scenario explicitly rules out complex tunneling protocols, and manual VPN configuration doesn't scale across multiple cloud environments. Option D (CloudEdge Connector) is a plausible-sounding distractor, but it is not a real Prisma product feature tied to the specific "Tunnel-less Connect" capability that solves the multi-cloud, high-performance, no-tunnel requirement described.

Memory tip: Think "Tunnel-less = Trouble-less" - when a scenario demands multi-cloud connectivity with no complex tunneling, look for the answer that specifically mentions "tunnel-less" technology paired with a cloud-native WAN service (AWS Cloud WAN). If you see "manual configuration" or "MPLS" in a modern cloud connectivity question, those are almost always wrong.

No community discussion yet for this question.