Explanation:
The correct answer is C.
The scenario has these key needs:
This calls for a hub-and-spoke model using a central network account for shared networking resources.
Option C combines AWS Transit Gateway (for inter-VPC/multi-account connectivity inside AWS) with AWS Direct Connect Gateway + transit virtual interfaces (for secure, private, high-bandwidth on-premises connectivity):
This architecture is highly available, scalable, uses private connectivity (no public VIFs), centralizes management, and meets the bandwidth and redundancy needs without operational complexity.
Option A: Uses only one DX partner (less redundancy) and transit VIFs attached directly to the Transit Gateway. While transit VIFs can attach to a Transit Gateway, the standard recommended pattern for multi-account + DX is to use a DX Gateway as an intermediary for better management and association flexibility. Single partner reduces HA compared to two partners. No explicit gateway association step.
Option B: Uses a DX Gateway with public virtual interfaces. Public VIFs are for accessing public AWS services (e.g., S3, DynamoDB) over DX, not for private connectivity to VPCs or Transit Gateways. This would not provide secure private IP routing to the legacy system or VPCs. Incorrect for this use case.
Option D: Uses private VIFs directly associated with individual virtual private gateways per VPC/account. This creates a point-to-point model (no central hub). It does not scale well for multi-account environments (management nightmare as accounts grow) and does not easily provide full any-to-any connectivity between all AWS workloads. Redundancy across two locations/partners is also weaker.
For hybrid connectivity with multi-account/multi-VPC + on-premises in a single Region:
This is the modern, scalable pattern (Transit Gateway + DX Gateway + transit VIF). Direct Connect supports up to 100 Gbps per connection, but 10 Gbps × multiples easily satisfies ≥5 Gbps with headroom.
Key exam concepts tested here:
This solution minimizes operational overhead while meeting all stated requirements for bandwidth, availability, and connectivity.
Ultimate access to all questions.
No comments yet.
A company is configuring connectivity to a multi-account AWS environment to support application workloads fiat serve users in a single geographic region. The workloads depend on a highly available, on premises legacy system deployed across two locations It is critical for the AWS workloads to manias connectivity to the legacy system, and a minimum of 5 Gbps of bandwidth is required All application workloads within AWS must have connectivity with one another. Which solution will meet these requirements?
A
Configure multiple AWS Direct Connect (DX) 10 Gbps dedicated connections from a DX partner for each onpremises location Create and attach a virtual private gateway for each AWS account VPC. Create a transit gateway in a central network account and associate It with the virtual private gateways Create a transit virtual interface on each DX connection and attach the interface to the transit gateway.
B
Configure multiple AWS Direct Connect (DX) 10 Gbps dedicated connections from two DX partners for each onpremises location Create and attach a virtual private gateway for each AWS account VPC. Create a DX gateway m a central network account and associate it with the virtual private gateways Create a public virtual interface on each DX connection and associate the interface with me DX gateway.
C
Create a transit gateway in a central network account and associate It with the virtual private gateways Create a transit virtual interface on each DX connection and attach the interface to the transit gateway. B. Configure multiple AWS Direct Connect (DX) 10 Gbps dedicated connections from two DX partners for each onpremises location Create and attach a virtual private gateway for each AWS account VPC. Create a DX gateway m a central network account and associate it with the virtual private gateways Create a public virtual interface on each DX connection and associate the interface with me DX gateway. C. Configure multiple AWS Direct Connect (DX) 10 Gbps dedicated connections from two DX partners for each onpremises location Create a transit gateway and a DX gateway in a central network account. Create a transit virtual interface for each DX interlace and associate them with the DX gateway. Create a gateway association between the DX gateway and the transit gateway
D
Configure multiple AWS Direct Connect (OX) 10 Gbps dedicated connections from a DX partner for each on premises location Create private virtual interfaces on each connection for each AWS account VPC Associate me private virtual interface with a virtual private gateway attached to each VPC