An enterprise is modernizing a web application. The application requires global HTTP/S load balancing, URL-based routing, and SSL/TLS termination at the edge. Additionally, the application requires high-availability, zone-redundant Layer 4 load balancing for custom TCP traffic on port 9000 within a single region. The backend virtual machines currently use Basic SKU Public IP addresses.
You need to design a load balancing architecture that meets these requirements while avoiding validation errors during deployment.
Which two of the following components or actions should you include in the design? (Select two.)
- Azure Front Door to manage global HTTP/S routing and SSL/TLS terminationAnswer
- Upgrade the virtual machine Public IP addresses to Standard SKU and deploy a Standard Load BalancerAnswer
- CAzure Traffic Manager to manage global URL-based routing and SSL/TLS termination
- DA Basic Load Balancer to provide zone-redundancy for the TCP port 9000 traffic
Answer
The correct design includes Azure Front Door for global HTTP/S routing and SSL/TLS termination, and upgrading the virtual machine Public IP addresses to Standard SKU combined with deploying a Standard Load Balancer.
The correct design uses Azure Front Door for the global HTTP/S web traffic because it supports SSL/TLS termination and URL-based routing. For the regional TCP traffic requiring zone redundancy, a Standard Load Balancer is required. To prevent validation errors, the backend virtual machines' Public IPs must be upgraded to Standard SKU to match the Load Balancer SKU.
Step-by-Step Solution
Key Concept
Designing a combined global and regional load balancing solution with appropriate SKU matching.