You are configuring a public Azure Load Balancer named LB-App to distribute incoming traffic across three virtual machines: VM-A, VM-B, and VM-C. The virtual machines are deployed in the same region, are connected to the same virtual network, and are not configured in an Availability Set or Virtual Machine Scale Set. You have already created a Basic SKU public IP address named IP-Web to serve as the frontend. You need to complete the load balancer configuration so that all three virtual machines can receive traffic. Which action should you perform?
- Deploy LB-App as a Standard SKU load balancer, create a Standard SKU public IP address for the frontend, and add the virtual machines to the backend pool.Cevap
- BDeploy LB-App as a Basic SKU load balancer, associate it with the existing IP-Web frontend, and add the virtual machines to the backend pool.
- CDeploy LB-App as a Standard SKU load balancer, associate it with the existing IP-Web frontend, and add the virtual machines to the backend pool.
- DDeploy LB-App as a Basic SKU load balancer, configure IP-Web as the frontend, and associate each virtual machine with a different subnet in the virtual network.
Cevap
Deploy the load balancer as a Standard SKU, create a Standard SKU public IP address for the frontend, and add the virtual machines to the backend pool.
Deploying the load balancer as Standard SKU and creating a Standard SKU public IP address is correct because Standard SKU load balancers support standalone virtual machines in their backend pool, and they require a matching Standard SKU frontend public IP address.
Adım Adım Çözüm
Anahtar Kavram
Azure Load Balancer SKU compatibility and backend pool configuration constraints