A company wants to implement a distributed architecture on AWS that uses a Gateway Load Balancer (GWLB) and GWLB endpoints. The company has chosen a hub-and-spoke model. The model includes a GWLB…

Question

Options

• A
  1. An application in a spoke VPC sends traffic to the GWLB endpoint based on the VPC route
• B
  1. An application in a spoke VPC sends traffic to the GWLB endpoint based on the VPC route
• C
  1. An application in a spoke VPC sends traffic to the GWLB endpoint.
• D
  1. An application in a spoke VPC sends traffic to the GWLB.

• A
  77% (24)
• B
  13% (4)
• C
  3% (1)
• D
  6% (2)

Explanation

Gateway Load Balancer Traffic Flow Explanation

Option A is correct because in a hub-and-spoke GWLB architecture, traffic from a spoke VPC application first hits the GWLB endpoint (in the spoke VPC) based on VPC routing rules, which then tunnels the traffic to the GWLB in the centralized appliance VPC, where it's distributed to virtual appliances for inspection, before being returned through the GWLB endpoint to the internet gateway in the spoke VPC for outbound internet access. This sequence - Spoke App → GWLB Endpoint → GWLB → Virtual Appliance → GWLB Endpoint → Internet Gateway - correctly reflects how GWLB endpoints act as the local entry/exit points in spoke VPCs.

Option C is wrong because it skips critical steps in the return path, and Option D is wrong because traffic from a spoke VPC never goes directly to the GWLB - it must first pass through the locally deployed GWLB endpoint, which acts as the traffic proxy. Option B likely presents a similar sequence to A but with an incorrect ordering of the inspection or return path steps.

Memory Tip: Think "Endpoint First, Always" - in GWLB architectures, traffic always enters and exits through the GWLB Endpoint in the local VPC before reaching the centralized GWLB. The endpoint is the "on-ramp/off-ramp," while the GWLB is the "highway interchange."

No community discussion yet for this question.