An administrator deploys a Basic SKU public Azure Load Balancer to distribute traffic to two virtual machines named VM1 and VM2. VM1 is located in Availability Zone 1, and VM2 is located in Availability Zone 2. Both virtual machines are configured with Standard SKU public IP addresses. When attempting to add the network interfaces of VM1 and VM2 to the load balancer's backend pool, the virtual machines are not available for selection. Which change should the administrator implement to resolve this issue?
- AReconfigure the frontend IP configuration of the load balancer to use a Basic SKU public IP address.
- BAssociate VM1 and VM2 with a new Availability Set within the same virtual network.
- Deploy a Standard SKU public Load Balancer to replace the Basic SKU public Load Balancer.Cevap
- DDeploy Basic SKU public IP addresses on the network interfaces of VM1 and VM2.
Cevap
Deploy a Standard SKU public Load Balancer to replace the Basic SKU public Load Balancer.
Deploying a Standard SKU Load Balancer resolves both constraint violations. The Standard SKU Load Balancer supports backend pool members located in different Availability Zones and is fully compatible with Standard SKU public IP addresses configured on the virtual machines' network interfaces.
Adım Adım Çözüm
Anahtar Kavram
Azure Load Balancer SKU feature support and compatibility rules regarding Availability Zones and public IP SKUs.