To support a web application, you plan to configure a public Azure Load Balancer named App-LB. You have three virtual machines: Web-VM1, Web-VM2, and Web-VM3. Web-VM1 is deployed in Availability Zone 1. Web-VM2 is deployed in Availability Zone 2. Web-VM3 is a standalone virtual machine with no zone redundancy. All three virtual machines are located in the same virtual network and subnet. Each virtual machine has a Basic SKU public IP address assigned to its primary network interface. You need to configure App-LB to distribute incoming internet traffic to the three virtual machines. The solution must ensure that traffic can be distributed across all three virtual machines. Which two actions should you perform? (Select two.)
- Deploy the load balancer using the Standard SKU.Answer
- Associate Standard SKU public IP addresses with the virtual machines' network interfaces.Answer
- CDeploy the load balancer using the Basic SKU and group the virtual machines within an Availability Set.
- DConfigure the backend pool of a Basic SKU load balancer by targeting the virtual network and subnet directly.
Answer
Deploy the load balancer using the Standard SKU, and associate Standard SKU public IP addresses with the virtual machines' network interfaces.
To support virtual machines deployed across different Availability Zones (Zone 1 and Zone 2) and a standalone virtual machine, you must deploy a Standard SKU Load Balancer. Basic Load Balancers only support virtual machines within a single Availability Set or Scale Set. Furthermore, all public IP addresses associated with the network interfaces of virtual machines in a Standard Load Balancer's backend pool must also be of the Standard SKU; Basic SKU public IP addresses are incompatible and will block standard load balancing configuration.
Step-by-Step Solution
Key Concept
Azure Load Balancer SKU compatibility and backend pool constraints
Estimated Time:2m 0s