⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Networking & Cloud DNS Interview Questions Scenario 15 of 55 in Networking & Cloud DNS
Staff SRE / Principal Architect [L3] Networking Staff SRE Scenario [L3]
🎯 Target Role / Context: Networking Scenario #15 (L3) · Networking

Q: You use an AWS Global Accelerator for your application. The backend is an ALB in us-east-1. How does Global Accelerator make the connection faster for a user in Australia compared to pointing their DNS directly to the ALB?

If the Australian user connects directly to the ALB, their TCP handshake and HTTP data traverse the public internet across multiple ISP hops, undersea cables, and peering points—which is slow, jittery, and packet-loss prone.

#Networking #L3 #VPC #DNS #Security
🎙️ Candidate Opening & Architectural Context
""In our multi-VPC setup, services in private subnets ran into this exact routing obstacle. The interviewer is testing: AWS network backbone, BGP Anycast, TCP termination at the edge.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? KodeKloud's Istio Service Mesh & Advanced Kubernetes Networking Course covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "In our multi-VPC setup, services in private subnets ran into this exact routing obstacle. The interviewer is testing: AWS network backbone, BGP Anycast, TCP termination at the edge.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

If the Australian user connects directly to the ALB, their TCP handshake and HTTP data traverse the public internet across multiple ISP hops, undersea cables, and peering points—which is slow, jittery, and packet-loss prone.

  • It uses Anycast IPs, so the Australian user's traffic is immediately routed to the closest AWS Edge Location in Sydney.
  • TCP Termination at the Edge: The TCP handshake completes instantly with the Sydney edge node, saving hundreds of milliseconds.
  • AWS Backbone: The data then travels from Sydney to us-east-1 strictly over AWS's dedicated, highly optimized, private fiber backbone, bypassing public internet congestion entirely.
2️⃣

Remediation & Permanent Safeguards

With Global Accelerator:

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: It uses Anycast IPs, so the Australian user's traffic is immediately routed to the closest AWS Edge Location in Sydney.."
⚡ 60-Second Elevator Pitch Talking Points
  • It uses Anycast IPs, so the Australian user's traffic is immediately routed to the closest AWS Ed...
  • TCP Termination at the Edge: The TCP handshake completes instantly with the Sydney edge node, sav...
  • AWS Backbone: The data then travels from Sydney to us-east-1 strictly over AWS's dedicated, highl...
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Confusing ALB 502 Bad Gateway (target connection reset) with 504 Gateway Timeout (upstream response timeout) when configuring Networking Global Accelerator 502 indicates the backend target closed the TCP connection prematurely or returned malformed HTTP, whereas 504 means the target failed to respond before idle timeout.
  2. Setting target deregistration delay to zero instead of allowing connection draining when configuring Networking Global Accelerator Instant target deregistration severs in-flight HTTP requests during auto-scaling scale-in or rolling deployments, causing immediate user-facing drops.
  3. Failing to query CloudWatch ELB metrics (HTTPCode_ELB_5XX vs HTTPCode_Target_5XX) during load balancer outages when configuring Networking Global Accelerator Comparing load balancer generated errors against target generated errors immediately isolates whether the issue lies in the proxy tier or application runtime.
  4. Overlooking Security Group rules on backend EC2/ECS instances that block health check traffic from the ALB when configuring Networking Global Accelerator Target instances must explicitly permit inbound HTTP/HTTPS traffic from the ALB security group on the configured container/application port.
Advertisement
Want more Networking & Cloud DNS scenarios?
Explore our complete collection of scenario-based Networking & Cloud DNS interview runbooks.
Browse All Networking & Cloud DNS Questions →