Venture into the world of Azure Infrastructure, where design meets functionality. Harness your skills and gain mastery over complex cloud structures to ace the AZ-305 Designing Microsoft Azure Infrastructure Solutions exam!
Gauge your current knowledge
Gauge your current knowledge
Azure offers four main services that move user traffic to the right resources: Azure Load Balancer, Application Gateway, Traffic Manager, and Front Door. Each service works at a different level of the networking model and handles different types of traffic. Choosing the right one depends on whether you need to balance traffic within a single region, protect a web application, or route users across the world.
Azure Load Balancer operates at Layer 4 of the networking model, which means it handles TCP and UDP traffic without looking at what the data actually says. It delivers high throughput with low latency and can distribute traffic across virtual machines within a single region. The service includes health probes that check whether each backend server is working; if a server fails its check, the load balancer stops sending traffic to it. Azure Load Balancer does not terminate SSL connections or provide session affinity beyond basic source IP tracking.
Application Gateway works at Layer 7, which means it can understand HTTP and HTTPS requests and make routing decisions based on the URL path, host header, or other application-level information. This service terminates SSL connections at the gateway, which offloads the encryption work from your backend servers and improves performance. It supports cookie-based session affinity, ensuring that a user who logs in continues talking to the same server during their session. Application Gateway also includes a Web Application Firewall that blocks common attacks like SQL injection and cross-site scripting.
Traffic Manager is a DNS-based routing service that does not proxy traffic between users and your resources. Instead, it responds to DNS queries with the IP address of the best endpoint based on routing methods like priority, weighted round-robin, performance, or geographic location. When one region fails, Traffic Manager can direct users to a backup region automatically, providing cross-region failover without maintaining active connections. Because it only handles DNS lookups, it adds minimal latency and works with any type of backend service.
Front Door is a global HTTP/HTTPS reverse proxy that terminates TLS connections at edge locations close to users. It combines traffic routing, SSL offloading, caching for static content, and Web Application Firewall protection in a single service. Front Door can accelerate both dynamic and static content by serving cached files from edge locations while forwarding application requests to the nearest healthy backend. Like Traffic Manager, it provides cross-region routing but does so by proxying requests rather than simply returning DNS records.
The decision between these services follows a clear pattern based on your requirements. Use Azure Load Balancer when you need to distribute UDP or TCP traffic at high scale within a single region and do not require SSL termination or application-layer routing. Choose Application Gateway when building a web application that needs SSL offloading, cookie-based sessions, path-based routing, or WAF protection. Select Traffic Manager for DNS-level failover across regions when you want simple, low-latency routing without proxying. Pick Front Door when you need global HTTP routing with caching, TLS termination at the edge, and built-in security at scale.
StudyCerts
StudyCerts