An enterprise is designing a global web application that will be deployed across the East US and West Europe regions. The application requires global HTTP/S load balancing with SSL/TLS termination at the edge, along with regional path-based routing and Web Application Firewall (WAF) protection inside each regional virtual network. Additionally, the regional ingress points must be provisioned using a public IP configuration that is compatible with the regional load balancing service SKU. Which two services and configurations should you include in the design to meet these requirements? (Choose two.)
- Azure Front DoorAnswer
- Azure Application Gateway V2 associated with a Standard SKU public IP addressAnswer
- CAzure Traffic Manager
- DAzure Application Gateway V2 associated with a Basic SKU public IP address
Answer
The correct design should include Azure Front Door to handle global traffic routing and SSL/TLS termination at the edge, and Azure Application Gateway V2 configured with a Standard SKU public IP address to handle regional path-based routing and WAF protection.
The combination of Azure Front Door and Azure Application Gateway V2 with a Standard SKU public IP address satisfies all design constraints. Azure Front Door handles global Layer 7 traffic routing and SSL/TLS termination at the edge. Within each region, Azure Application Gateway V2 provides localized path-based routing, WAF capabilities, and SSL/TLS termination closer to the backend resources. Using a Standard SKU public IP address is mandatory for Application Gateway V2, preventing deployment errors.
Step-by-Step Solution
Key Concept
Multi-tier global and regional application load balancing using Azure Front Door and Azure Application Gateway V2 while adhering to SKU compatibility requirements.
Estimated Time:2m 0s