Which networking solution meets these requirements?

By:
On:
In: SAA-C02
Tagged:
With: 0 Comments
A company is using a VPC peering strategy to connect its VPCs in a single Region to allow for cross-communication.A recent increase in account creations andVPCs has made it difficult to maintain the VPC peering strategy, and the company expects to grow to hundreds of VPCs.There are also new requests to create site-to-site VPNs with some of the VPCs.A solutions architect has been tasked with creating a centrally managed networking setup for multiple accounts, VPCs, and VPNs.

Which networking solution meets these requirements?

Configure shared VPCs and VPNs and share to each other.

Configure a hub-and-spoke VPC and route all traffic through VPC peering.

Configure an AWS Direct Connect connection between all VPCs and VPNs.

Configure a transit gateway with AWS Transit Gateway and connect all VPCs and VPNs.

Explanations:

Shared VPCs are not a native AWS feature; they refer to a model where multiple accounts can access a single VPC, but it doesn’t simplify the management of numerous VPCs and VPNs as needed.

A hub-and-spoke model with VPC peering would still lead to management complexity with many VPCs, and it does not provide centralized control for VPN connections.

AWS Direct Connect is primarily for dedicated connections to AWS, not for managing multiple VPCs and VPNs. It doesn’t address the routing and scalability needs effectively.

A transit gateway allows for centralized management of multiple VPCs and VPN connections, enabling scalable, efficient routing of traffic without the complexity of individual VPC peering.

Leave a Reply

Your email address will not be published. Required fields are marked *

7 − four =