An enterprise is designing a regional application delivery and load balancing solution in the East US region. The architecture must support two workloads deployed on Azure Virtual Machines:
1. An HTTPS web application requiring SSL/TLS termination and URL path-based routing (routing `/images/*` and `/video/*` to separate backend pools).
2. A legacy database replication service that communicates using raw TCP on port 1433 and requires low-latency, high-throughput load balancing.
All virtual machines are configured with Standard SKU Public IP addresses for administrative access.
Which two Azure load balancing services should you include in the design to meet these requirements without validation failures? (Select two.)
- Azure Application Gateway (Standard v2 SKU) to route the HTTPS web application trafficCevap
- Azure Load Balancer (Standard SKU) to route the legacy database replication trafficCevap
- CAzure Load Balancer (Basic SKU) to route the legacy database replication traffic
- DAzure Traffic Manager to route and terminate SSL/TLS for the HTTPS web application traffic
Cevap
Azure Application Gateway (Standard v2 SKU) to handle the HTTPS web application traffic and Azure Load Balancer (Standard SKU) to handle the legacy database replication traffic.
The correct solution includes Azure Application Gateway (Standard v2 SKU) and Azure Load Balancer (Standard SKU). Azure Application Gateway operates at Layer 7, satisfying the requirements for SSL/TLS termination and URL path-based routing. Azure Load Balancer operates at Layer 4, satisfying the requirement for low-latency TCP routing on port 1433. The Standard SKU Load Balancer is required to ensure compatibility with the virtual machines' Standard SKU Public IP addresses.
Adım Adım Çözüm
Anahtar Kavram
Selecting and combining Azure load balancing services based on layer capabilities (Layer 7 Application Gateway for HTTP/HTTPS routing vs. Layer 4 Load Balancer for non-HTTP TCP/UDP) and enforcing SKU alignment (Standard SKU) across public IPs and load balancers.