Question

Difficulty: HardHigh-Performing and Scalable Network Architectures

A company hosts a web application deployed across two AWS Regions: `us-east-1` and `ap-northeast-1`. The user-facing component of the application uses Application Load Balancers (ALBs) in both Regions. The company wants to minimize latency for global users by routing their traffic over the AWS private network backbone to the nearest ALB. Additionally, the backend database tier requires a secure, high-throughput connection to replicate transaction logs averaging 3 Gbps3\text{ Gbps} between VPCs in both Regions. The solution must optimize throughput and latency while maintaining high availability.

Which TWO actions should the solutions architect take to meet these requirements?

  1. Create an AWS Global Accelerator accelerator and register the Application Load Balancers in both Regions as endpoints.Answer
  2. Establish an inter-Region VPC peering connection between the database VPCs in us-east-1 and ap-northeast-1.Answer
  3. C
    Configure Amazon Route 53 with latency-based routing to resolve the application's domain name directly to the Application Load Balancers in each Region.
  4. D
    Deploy an AWS Site-to-Site VPN connection between the database VPCs in both Regions to secure and route the database replication traffic.
  5. E
    Implement stateless Network ACLs on the database subnets, allowing outbound replication traffic to the remote Region's CIDR block while blocking all inbound traffic from that CIDR block.

Answer

Registering the Application Load Balancers as endpoints in AWS Global Accelerator, and establishing an inter-Region VPC peering connection between the database VPCs.
AWS Global Accelerator minimizes latency for global users by routing their traffic over the AWS global private network backbone via Anycast IP addresses, rather than relying on the public internet. For database replication requiring 3 Gbps3\text{ Gbps} throughput between Regions, inter-Region VPC peering provides direct, high-bandwidth routing over the AWS global network backbone with no single point of failure or artificial bandwidth limitations.

Step-by-Step Solution

1
Evaluate the user-facing latency requirements.
Identify that global user traffic must be routed over the AWS private backbone to minimize latency. AWS Global Accelerator ingests traffic at the edge and carries it over the AWS global network, unlike Route 53 latency routing which resolves DNS but lets traffic flow over the public internet.
Meets the requirement to minimize latency and route user-facing traffic over the AWS private network backbone.
2
Evaluate the database replication throughput requirements.
Identify that the database requires 3 Gbps3\text{ Gbps} bandwidth. A Site-to-Site VPN tunnel has a limit of 1.25 Gbps1.25\text{ Gbps} and would be bottlenecked. Inter-Region VPC peering has no bandwidth limits and routes traffic over the AWS global network privately.
Allows high-throughput database replication without artificial limits.
3
Verify network security and stateful communication.
Confirm that blocking inbound traffic in stateless Network ACLs breaks TCP connections due to the stateless nature of NACLs, which require both inbound and outbound rules for ephemeral port communication.
Prevents network misconfigurations that disrupt database synchronization.

Key Concept

AWS Global Accelerator provides global latency optimization over the AWS backbone, and inter-Region VPC peering provides scalable, high-throughput private communication between Regions without VPN bandwidth limits.
Estimated Time:2m 0s
Rate this question