A cloud administrator is asked to validate a proposed internetworking design that will provide connectivity to a VMware Cloud on AWS environment from multiple company locations. The following…

Question

Options

• AConnectivity the VMware Cloud on AWS environment must NOT have a single point of failure.
• BAny network traffic between on-premises company locations must be sent over a private IP
• CConnectivity the VMware Cloud on AWS environment must support high-throughput data

• A
  83% (29)
• B
  6% (2)
• C
  11% (4)

Explanation

Eliminating a single point of failure (option A) is the correct answer because it is a fundamental architectural design constraint - it mandates redundant connectivity paths (e.g., dual AWS Direct Connect circuits, or Direct Connect + VPN failover) that must be baked into the topology itself, not patched in later. This directly validates whether the proposed internetworking design is sound before any implementation begins.

Option B (private IP between on-premises locations) is a routing policy concern, not a VMware Cloud on AWS connectivity design requirement - traffic between on-premises sites typically traverses the existing corporate WAN and doesn't depend on how VMC on AWS is connected. Option C (high-throughput support) is a capacity/performance consideration that is satisfied by choosing the right Direct Connect bandwidth tier, not by the topology design itself - you can add throughput without changing the fundamental architecture.

Memory tip: In architecture design questions, always prioritize availability (HA/redundancy) over performance and routing policy - "no SPOF" is a design-time decision; the other concerns are configuration-time decisions. Think: Design removes failure, config tunes performance.

No community discussion yet for this question.