Q93 — AWS SAA-C03 Ch.11

Question 93 of 100 | ← Chapter 11

Q793. A company has an AWS Direct Connect connection from its on-premises location to an AWS account. The AWS account has 30 different VPCs in the same AWS Region. The VPCs use private virtual interfaces (VIFs). Each VPC has a CIDR block that does not overlap with other networks under the company's control.The company wants to centrally manage the networking architecture while still allowing each VPC to communicate with all other VPCs and on-premises networks.Which solution will meet these requirements with the LEAST amount of operational overhead?

• A. Create a transit gateway, and associate the Direct Connect connection with a new transit VIF. Turn on the transit gateway's route propagation feature. ✓
• B. Create a Direct Connect gateway. Recreate the private VIFs to use the new gateway. Associate each VPC by creating new virtual private gateways.
• C. Create a transit VPConnect the Direct Connect connection to the transit VPCreate a peering connection between all other VPCs in the Region. Update the route tables.
• D. Create AWS Site-to-Site VPN connections from on premises to each VPC. Ensure that both VPN tunnels are UP for each connection. Turn on the route propagation feature.

Correct Answer: A. Create a transit gateway, and associate the Direct Connect connection with a new transit VIF. Turn on the transit gateway's route propagation feature.

Explanation

To meet the requirements of centrally managing the networking architecture while allowing each VPC to communicate with all other VPCs and on-premises networks with the least amount of operational overhead, the solution is:A. Create a transit gateway, and associate the Direct Connect connection with a new transit VIF. Turn on the transit gateway's route propagation feature.Creating a transit gateway and associating the Direct Connect connection with a new transit VIF provides a centralized and scalable solution for managing the networking architecture. The transit gateway acts as a hub for connectivity between VPCs and on-premises networks. By turning on the transit gateway's route propagation feature, routes from the on-premises network are automatically propagated to all connected VPCs.Here's why the other options are not the best fit for the given requirements:B. Creating a Direct Connect gateway and recreating private VIFs: While Direct Connect gateways can be used to simplify connections to multiple VPCs, it requires recreating the private VIFs and creating new virtual private gateways for each VPC. This introduces additional operational overhead compared to using a transit gateway.C. Creating a transit VPC and peering connections: Creating a transit VPC and establishing peering connections between all other VPCs can achieve connectivity, but it adds complexity to the networking architecture. It requires setting up and managing multiple peering connections and updating route tables for each connection, which results in more operational overhead compared to using a transit gateway.D. Creating AWS Site-to-Site VPN connections from on-premises to each VPC: While VPN connections can establish connectivity between on-premises and VPCs, creating and managing individual VPN connections for each VPC can be cumbersome. It requires configuring and maintaining multiple VPN connections, which increases operational overhead.Therefore, the solution that meets the requirements with the least amount of operational overhead is:A. Create a transit gateway, and associate the Direct Connect connection with a new transit VIF. Turn on the transit gateway's route propagation feature.