An enterprise is modernizing a regional HR portal deployed on Azure Virtual Machines. The architecture must satisfy the following requirements:
- Load balance inbound HTTP/S traffic with SSL/TLS termination and URL-path-based routing.
- Allow backend VMs to receive traffic from the Layer 7 load balancer and use a separate Layer 4 load balancer for outbound internet access.
- Avoid configuration conflicts related to Public IP and Load Balancer SKU mismatches.
Which two actions should you perform to meet these requirements?
- Deploy Azure Application Gateway (Standard v2 SKU) to handle inbound SSL/TLS termination and URL-path-based routing.Answer
- Configure an Azure Standard Load Balancer for outbound connectivity and ensure all public IP addresses associated with the backend virtual machines are of the Standard SKU.Answer
- CConfigure an Azure Basic Load Balancer for outbound connectivity and associate it with Standard SKU public IP addresses on the backend virtual machines.
- DDeploy an Azure Traffic Manager profile to perform SSL/TLS termination and path-based routing at the DNS level.
Answer
To meet the requirements, you must deploy Azure Application Gateway (Standard v2 SKU) to handle inbound SSL/TLS termination and URL-path-based routing, and configure an Azure Standard Load Balancer for outbound connectivity ensuring all associated public IP addresses use the Standard SKU.
The correct architecture uses Azure Application Gateway for regional Layer 7 load balancing (providing SSL/TLS termination and path-based routing) and an Azure Standard Load Balancer for Layer 4 outbound connectivity. Because the load balancer and public IPs must have matching SKUs, deploying a Standard Load Balancer requires using Standard SKU public IP addresses on the backend virtual machines.
Step-by-Step Solution
Key Concept
Azure load balancer SKU matching and Layer 7 application routing rules.