Load Balancer vs Application Gateway decision in Azure - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Basic Differences

Which statement correctly describes a key difference between Azure Load Balancer and Azure Application Gateway?

A Azure Load Balancer operates at Layer 4 (Transport Layer) and routes traffic based on IP and port, while Application Gateway operates at Layer 7 (Application Layer) and routes traffic based on HTTP attributes.

B Azure Load Balancer is designed for web application firewall capabilities, while Application Gateway is only for TCP load balancing.

C Azure Load Balancer can inspect HTTP headers to make routing decisions, whereas Application Gateway only routes based on IP addresses.

D Azure Load Balancer supports SSL termination and cookie-based session affinity, while Application Gateway does not support these features.

💡 Hint

Think about the OSI layers each service works on and what kind of traffic they handle.

Azure Load Balancer works at Layer 4 and routes traffic based on IP and port without inspecting HTTP details. Application Gateway works at Layer 7 and can route based on HTTP headers, URLs, and supports SSL termination.

❓ Architecture

intermediate

Choosing the Right Service for SSL Termination

You need to offload SSL processing from your backend servers to improve performance. Which Azure service should you choose?

A Azure Load Balancer, because it supports SSL termination natively.

B Azure Load Balancer, because it can inspect HTTP headers for SSL offloading.

C Azure Application Gateway, because it supports SSL termination and can decrypt incoming HTTPS traffic.

D Neither service supports SSL termination; you must handle it on backend servers.

💡 Hint

Consider which service works at the application layer and can decrypt HTTPS traffic.

Azure Application Gateway supports SSL termination, allowing it to decrypt HTTPS traffic and forward it as HTTP to backend servers, reducing their load. Azure Load Balancer does not support SSL termination.

❓ scaling

advanced

Scaling Web Applications with Load Balancer vs Application Gateway

Your web application experiences sudden spikes in traffic. You want to scale efficiently and maintain session persistence. Which service and feature combination is best?

A Use Azure Application Gateway with cookie-based session affinity to maintain user sessions during scaling.

B Use Azure Load Balancer with source IP affinity to maintain session persistence during scaling.

C Use Azure Load Balancer with round-robin distribution without session affinity for better scaling.

D Use Azure Application Gateway without session affinity to maximize throughput during scaling.

💡 Hint

Think about which service supports cookie-based session affinity and why that matters for web apps.

Azure Application Gateway supports cookie-based session affinity, which helps maintain user sessions during scaling. Azure Load Balancer supports source IP affinity but is less effective for HTTP session persistence.

❓ tradeoff

advanced

Tradeoffs Between Cost and Features

You have a limited budget and need basic TCP load balancing without advanced HTTP features. Which Azure service is more cost-effective and appropriate?

A Azure Application Gateway, because it is cheaper and supports basic TCP load balancing.

B Azure Load Balancer, because it is cost-effective for simple TCP/UDP load balancing without extra features.

C Azure Application Gateway, because it offers all features at a lower price than Load Balancer.

D Neither service is suitable; you should use Azure Front Door for basic TCP load balancing.

💡 Hint

Consider which service is designed for simple transport layer load balancing and typically costs less.

Azure Load Balancer is designed for simple Layer 4 load balancing and is generally more cost-effective for TCP/UDP traffic without advanced HTTP features. Application Gateway is more expensive due to Layer 7 capabilities.

❓ estimation

expert

Estimating Capacity for Application Gateway

Your application gateway must handle 10,000 concurrent HTTPS connections with SSL termination. Each connection requires 1 Mbps bandwidth. What is the minimum bandwidth capacity you should provision to avoid bottlenecks?

A 10 Gbps, because 10,000 connections × 1 Mbps = 10,000 Mbps = 10 Gbps.

B 1 Gbps, because SSL termination reduces bandwidth by compressing data.

C 100 Mbps, because connections are multiplexed and bandwidth is shared efficiently.

D 20 Gbps, to allow for overhead and peak traffic spikes beyond 10,000 Mbps.

💡 Hint

Think about overhead, peak usage, and safety margins when estimating capacity.

While 10,000 connections × 1 Mbps equals 10 Gbps, you should provision extra capacity (e.g., double) to handle overhead, SSL processing, and traffic spikes, so 20 Gbps is safer.