Q55 — AWS SAA-C03 Ch.10

Question 55 of 100 | ← Chapter 10

Q655. A company has an AWS Direct Connect connection from its on-premises location to an AWS account. The AWS account has 3O 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 sill 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?

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 centrally manage 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 most suitable solution would be: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.Here's the rationale behind this solution:Option 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.A transit gateway acts as a hub that simplifies network connectivity between VPCs, on-premises networks, and other AWS services. By creating a transit gateway and associating the Direct Connect connection with a new transit VIF, you can centralize the management of networking architecture. This allows for easy communication between VPCs and on-premises networks without requiring complex peering connections or VPNs. Enabling the route propagation feature ensures that the routes from all VPCs and on-premises networks are propagated to the transit gateway, allowing for seamless communication.Option B: Create a Direct Connect gateway. Recreate the private VIFs to use the new gateway. Associate each VPC by creating new virtual private gateways.Creating a Direct Connect gateway is used to enable connectivity between Direct Connect and multiple VPCs. However, this option would require recreating the private VIFs and virtual private gateways for each VPC, which introduces additional operational overhead. Additionally, it does not provide centralized management of networking architecture or seamless communication between VPCs.Option C: Create a transit VPC. Connect the Direct Connect connection to the transit VPC. Create peering connections between all other VPCs in the region. Update the route tables. Creating a transit VPC and establishing peering connections between all other VPCs can achieve connectivity. However, it adds complexity and operational overhead by requiring the management of additional VPCs and peering connections. It does not provide as streamlined a solution as using a transit gateway.Option 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. Creating individual VPN connections from on-premises to each VPC would result in a significant increase in operational overhead, as it requires managing multiple VPN connections and ensuring the tunnels are up for each connection. This approach is not as efficient or scalable as using a transit gateway.Therefore, the most suitable solution that meets the requirements with the least amount of operational overhead is to create a transit gateway and associate the Direct Connect connection with a new transit VIF, while enabling the transit gateway's route propagation feature (Option A). This provides centralized management of networking architecture, allows for seamless communication between VPCs and on- premises networks, and reduces operational complexity.