Question

Difficulty: MediumApplication Load Balancing and Delivery

An enterprise is designing a high-performance, multi-region web application that will be hosted in Azure. The design must satisfy the following requirements:
- Route incoming HTTPS user traffic to the nearest regional deployment to minimize latency.
- Perform SSL/TLS termination at the global edge to reduce handshake latency, but enforce end-to-end SSL encryption to the backend servers.
- Inspect and filter web traffic using a Web Application Firewall (WAF) at both the global entry point and the regional boundaries.
- Direct traffic to different backend web pools based on the URL path (e.g., routing /images/* to storage and /api/* to application servers).

Which two services should you recommend to meet these requirements? (Select two.)

  1. Azure Front DoorAnswer
  2. Azure Application GatewayAnswer
  3. C
    Azure Traffic Manager
  4. D
    Azure Load Balancer (Standard SKU)

Answer

Azure Front Door and Azure Application Gateway
Azure Front Door and Azure Application Gateway are the correct services. Azure Front Door operates at the global edge to provide SSL/TLS termination closest to the user, global HTTP/HTTPS routing, and WAF protection. Azure Application Gateway operates at the regional level, providing URL path-based routing and regional WAF inspection before directing traffic to backend application pools.

Step-by-Step Solution

1
Analyze global routing and edge security requirements.
Identify that global latency optimization, SSL/TLS termination at the edge, and global WAF require Azure Front Door.
Azure Front Door is Azure's global web load balancer that handles Layer 7 traffic at edge locations.
2
Analyze regional routing and backend integration requirements.
Identify that regional URL path-based routing and regional WAF require Azure Application Gateway.
Azure Application Gateway is a regional Layer 7 load balancer that handles application-level routing within a virtual network.
3
Evaluate other options against Layer 7 and security capabilities.
Reject Azure Traffic Manager (L3/DNS only) and Azure Load Balancer (L4 only) as they lack SSL/TLS termination, path-based routing, and WAF support.
Traffic Manager and Azure Load Balancer do not operate at the application layer (Layer 7).

Key Concept

Combining global and regional Layer 7 load balancing services to meet latency, security, and path-routing requirements.
Rate this question