Examkin

Question

Difficulty: MediumHigh-Performing and Scalable Network Architectures

A company has deployed 15 VPCs in the us-east-1 Region to connect different microservices for an application. Currently, the VPCs are connected using a full mesh of VPC Peering connections. The company plans to add 20 more VPCs and requires centralized traffic monitoring and security filtering through a dedicated inspection VPC. The current design is becoming difficult to manage and scale. Which solution should a solutions architect recommend to simplify the network architecture while maintaining high performance and scalability?

  1. Deploy AWS Transit Gateway, attach all VPCs to the Transit Gateway, and configure routing tables to route inter-VPC traffic through the dedicated inspection VPC.Answer
  2. B
    Implement stateless Network Access Control Lists (NACLs) at the subnet level in each VPC to peer the networks and route inter-VPC traffic dynamically.
  3. C
    Set up AWS Site-to-Site VPN connections between all VPCs to secure inter-VPC traffic, relying on a single VPN tunnel per connection to scale throughput dynamically for the microservices.
  4. D
    Configure Amazon Route 53 with latency-based routing policies to resolve service endpoints directly between VPCs, allowing DNS resolution to bypass VPC routing tables.

Answer

Deploy AWS Transit Gateway, attach all VPCs to the Transit Gateway, and configure routing tables to route inter-VPC traffic through the dedicated inspection VPC.
The correct solution involves deploying AWS Transit Gateway to act as a centralized hub. Transit Gateway simplifies the network architecture by replacing a complex web of VPC Peering connections with a hub-and-spoke model. Because Transit Gateway supports transitive routing, it allows the organization to route all traffic between spoke VPCs through a dedicated inspection VPC, satisfying both the scalability and centralized security monitoring requirements.

Step-by-Step Solution

1
Identify the scalability and routing limitations of the current full mesh VPC Peering configuration.
A full mesh of 15 VPCs requires 105 peering connections, and expanding to 35 VPCs would require 595 connections, which is complex and difficult to manage. VPC Peering also does not support transitive routing, making centralized traffic inspection difficult.
Understanding the limits of VPC Peering guides the selection of a hub-and-spoke model.
2
Evaluate AWS services designed to simplify multi-VPC connectivity and support centralized traffic inspection.
AWS Transit Gateway acts as a central hub (cloud router) that supports transitive routing. Traffic can be easily directed from spoke VPCs to a central inspection VPC before reaching other spokes.
Transit Gateway simplifies the network topology from a full mesh to a hub-and-spoke model while maintaining high performance.
3
Verify that Transit Gateway meets the performance and management requirements.
Transit Gateway supports high throughput (up to 50 Gbps per VPC attachment by default) and reduces routing management overhead by using centralized route tables.
Confirming the throughput and routing features ensures the architecture scales efficiently without performance bottlenecks.

Key Concept

AWS Transit Gateway acts as a network transit hub, enabling transitive routing to simplify multi-VPC architectures and centralize traffic inspection while maintaining high performance.
Rate this question

Topics

High-Performing and Scalable Network Architectures

More questions from this topic