You are configuring Azure resources to support a web application. You plan to deploy a public Azure Load Balancer to distribute incoming HTTP requests across three virtual machines named VM1, VM2, and VM3. The virtual machines are deployed in a single Virtual Network (VNet) but are located in different Availability Zones. VM1 and VM2 currently have Basic SKU public IP addresses assigned directly to their network interfaces. VM3 does not have a public IP address. You need to configure the load balancer and backend resources to ensure that the load balancer can successfully distribute traffic to all three virtual machines. Which two configuration actions should you perform? (Select two.)
- Create a Standard SKU public IP address for the load balancer frontend.Cevap
- Upgrade the public IP addresses of VM1 and VM2 to the Standard SKU.Cevap
- CCreate a Basic SKU public IP address for the load balancer frontend.
- DDeploy a Basic SKU Load Balancer to manage the backend pool.
Cevap
To support virtual machines in different Availability Zones, you must deploy a Standard SKU Load Balancer with a Standard SKU public IP address as its frontend. Additionally, you must upgrade the public IP addresses of the backend virtual machines (VM1 and VM2) to the Standard SKU.
To distribute traffic across virtual machines in different Availability Zones, a Standard SKU Load Balancer must be deployed. A Standard Load Balancer requires a Standard SKU public IP address for its frontend configuration. Additionally, any virtual machines in the backend pool of a Standard Load Balancer cannot use Basic SKU public IP addresses on their network interfaces, meaning the existing public IPs on the backend VMs must be upgraded to the Standard SKU.
Adım Adım Çözüm
Anahtar Kavram
Azure Load Balancer SKU capability and compatibility rules