An organization is deploying a high-throughput, non-HTTP TCP-based telemetry application on Azure Virtual Machines in a single region. The virtual machines require direct inbound internet access and are configured with Standard SKU public IP addresses on their network interfaces. You need to design a load balancing solution to distribute incoming TCP traffic across the virtual machines. The design must minimize complexity and avoid validation errors during deployment. Which two configuration components should you include in the load balancing design?
- A Standard SKU Azure Load BalancerCevap
- A Standard SKU public IP address for the load balancer's frontend IP configurationCevap
- CA Basic SKU Azure Load Balancer
- DA Basic SKU public IP address for the load balancer's frontend IP configuration
Cevap
The design must include a Standard SKU Azure Load Balancer and a Standard SKU public IP address for the load balancer's frontend IP configuration.
The correct configurations are a Standard SKU Azure Load Balancer and a Standard SKU public IP address for the frontend. Since the backend Virtual Machines are already configured with Standard SKU public IP addresses, the Azure Load Balancer must also be a Standard SKU to prevent SKU mismatch errors. Furthermore, a Standard SKU Azure Load Balancer requires its frontend IP configuration to use a Standard SKU public IP address.
Adım Adım Çözüm
Anahtar Kavram
Azure Load Balancer SKU compatibility and resource constraints when mixing Basic and Standard SKUs.