You have three virtual machines named VM1, VM2, and VM3 in a virtual network named VNet1. VM1 and VM2 are deployed in Availability Set AS1, while VM3 is deployed as a standalone virtual machine. You have an existing Basic SKU public IP address named PublicIP1.
You need to configure a public load balancer to distribute inbound internet traffic to VM1, VM2, and VM3.
Which action should you perform?
- Deploy a Standard SKU load balancer, upgrade PublicIP1 to the Standard SKU, and add VM1, VM2, and VM3 to the backend pool.Answer
- BDeploy a Standard SKU load balancer, associate the existing Basic SKU PublicIP1 with the frontend, and add VM1, VM2, and VM3 to the backend pool.
- CDeploy a Basic SKU load balancer, associate the existing Basic SKU PublicIP1 with the frontend, and add VM1, VM2, and VM3 to the backend pool.
- DDeploy a Basic SKU load balancer, upgrade PublicIP1 to the Standard SKU, and add VM1, VM2, and VM3 to the backend pool.
Answer
Deploy a Standard SKU load balancer, upgrade PublicIP1 to the Standard SKU, and add VM1, VM2, and VM3 to the backend pool.
The correct action is to deploy a Standard SKU load balancer, upgrade the public IP address to the Standard SKU, and add all three virtual machines to the backend pool. A Standard SKU load balancer is necessary because it supports a backend pool consisting of any virtual machines in a single virtual network, including a mix of standalone VMs and availability sets. Additionally, Standard SKU load balancers require Standard SKU public IP addresses, meaning the existing Basic SKU public IP must be upgraded.
Step-by-Step Solution
Key Concept
Azure Load Balancer SKU features and IP address compatibility rules.