Explain the difference between Layer 4 and Layer 7 load balancing. Provide examples of when each would be used.
- L4: routes traffic based on IP/port (TCP/UDP)
- L7: routes based on content (HTTP headers, paths)
- L4 example: NLB; L7 example: ALB, NGINX
- 💡Think OSI model layers.
- ⚠️Confusing the OSI layers or misattributing functionalities (e.g., saying L4 does SSL termination).
- ⚠️Failing to provide concrete use-case examples, only listing technologies.
- ⚠️Not explaining the 'why' behind using one over the other (e.g., L4 for performance, L7 for intelligent routing).
- ⚠️Overlooking the trade-offs involved (L4's speed vs. L7's feature set).
- ⚠️Focusing too heavily on a single vendor's product names without explaining the general concept.
- ❓Which is better for microservices?
- ❓How does SSL termination work?
Ready to prove your AWS networking knowledge?
Practice with free Advanced Networking Specialty (ANS-C01) exam questions. Instant answers and detailed explanations — no account required.
Start free practice quizQuestions that share similar topics with this one
Deepen your knowledge with these related blog posts
From Terraform to GitOps: A Practical Migration Roadmap
A step-by-step guide to migrating from traditional Terraform workflows to GitOps, including migration patterns, common pitfalls, and practical diagrams to guide your journey.
GitOps: Monorepo vs Polyrepo - A Practical Comparison
A straightforward comparison of monorepo and polyrepo approaches for GitOps implementations. Understand the advantages, disadvantages, and when to use each strategy for your infrastructure and application deployments.
Paginated vs. Bulk API Calls: Performance, Cost, and Reliability Trade‑offs
Should you fetch many results at once or smaller batches at a time? A practical guide to the CPU, memory, network, and cloud-cost trade‑offs of paginated vs. one-shot API calls—with actionable rules of thumb.