A cloud administrator is managing a VMware Cloud on AWS environment connected to an on- premises data center using IPSec VPN connection. The administrator is Informed of performance issues with…

Question

Options

• ADeploy VMware HCX.
• BDeploy AWS Direct Connect.
• CDeploy a layer 2 VPN connection.
• DContact VMware support to request more bandwidth for IPSec VPN connection.

• A
  14% (9)
• B
  77% (49)
• C
  6% (4)
• D
  3% (2)

Explanation

AWS Direct Connect provides a dedicated, private network link between on-premises infrastructure and AWS with consistent throughput up to 100 Gbps - purpose-built for high-bandwidth workloads like 3.8 Gbps replication that far exceeds what an IPSec VPN can reliably sustain (VMware Cloud on AWS IPSec VPN tunnels are typically capped around 1.25 Gbps with internet-inherent jitter and latency overhead).

Option A (HCX) is wrong because HCX is a workload migration and network extension tool - it adds abstraction overhead and doesn't resolve underlying bandwidth constraints. Option C (Layer 2 VPN) is wrong because L2 VPN extends broadcast domains for network continuity, not throughput - it doesn't add bandwidth capacity. Option D is wrong because VMware support cannot provision more bandwidth for an internet-based IPSec VPN; the bottleneck is architectural, not a configuration limit VMware controls.

Memory tip: If traffic exceeds ~1 Gbps between on-premises and VMware Cloud on AWS, the answer is almost always Direct Connect - think "Direct = Dedicated = High Bandwidth." IPSec VPN is for connectivity; Direct Connect is for performance.

No community discussion yet for this question.