An organization is designing the load balancing architecture for a multi-tier web application in the East US region. The solution must meet the following requirements:
- Web Tier: Requires global distribution, SSL/TLS termination, and HTTP/S URL-path-based routing to support different backend services.
- Database Tier: Requires regional load balancing of TCP port traffic across database Virtual Machines (VMs) distributed across three availability zones. The VMs currently utilize Basic SKU Public IP addresses for legacy remote access.
You are designing the database tier load balancing solution. Which configuration should you recommend to meet the database tier requirements while preventing validation errors?
- Upgrade the VM Public IP addresses to Standard SKU and deploy an Azure Standard Load Balancer.Answer
- BDeploy an Azure Standard Load Balancer and associate the database VMs directly without modifying their Basic SKU Public IP configurations.
- CDeploy an Azure Basic Load Balancer and configure its frontend IP address to be zone-redundant to match the VM IP SKU.
- DDeploy Azure Traffic Manager to load balance the TCP port traffic directly to the VMs' Basic SKU Public IPs.
Answer
Upgrade the VM Public IP addresses to Standard SKU and deploy an Azure Standard Load Balancer.
Upgrading the VM Public IP addresses to Standard SKU and deploying an Azure Standard Load Balancer is correct because the Standard Load Balancer is required to achieve zone-redundancy and support the distribution of TCP traffic across three availability zones. However, Azure enforces SKU consistency; standard-tier resources cannot be mixed with basic-tier resources in the backend configuration. Therefore, the VMs' existing Basic SKU Public IP addresses must be upgraded to Standard SKU to match the Standard Load Balancer, avoiding validation failures during deployment.
Step-by-Step Solution
Key Concept
Azure Load Balancer SKU alignment and availability zone support.