AWS Certified Advanced Networking Specialty Practice Exam

What design change should be recommended for a transit VPC architecture experiencing bandwidth saturation?

1. Increase the size of instance types deployed in the transit VPC

2. Leverage VPC peering connections between VPCs across regions

3. Enable enhanced Networking across all instances

4. Implement NAT gateways to reduce traffic load

The correct answer is: Leverage VPC peering connections between VPCs across regions

In a transit VPC architecture experiencing bandwidth saturation, leveraging VPC peering connections between VPCs across regions is an effective design change. VPC peering allows for direct, low-latency communication between separate VPCs, which can help distribute and balance traffic load more efficiently. This means that instead of routing all traffic through the transit VPC, resources in different VPCs can communicate with each other directly, potentially reducing congestion and improving overall performance. Furthermore, VPC peering is advantageous because it seamlessly connects VPCs without the need for additional gateways or VPN connections, leading to better resource utilization and lower latency. This is critical in a scenario where bandwidth is saturated, as optimizing the routes for network traffic can alleviate the bottleneck and enhance data flow between VPCs. In contrast, some alternatives, such as increasing instance types or enabling enhanced networking, may help with performance but do not directly address traffic routing and congestion issues. NAT gateways can further complicate traffic flows and may introduce additional costs and latency. Therefore, recommending VPC peering aligns best with effectively managing and alleviating bandwidth saturation in a transit VPC architecture.