An administrator is configuring load balancing for a web application in an Azure subscription. The environment contains the following resources:
- A virtual network named VNet1 that has a single subnet named Subnet1.
- A virtual machine named VM1 deployed in Availability Zone 1. VM1 has a network interface named NIC1 connected to Subnet1. NIC1 has a Basic SKU public IP address named VM1-PIP assigned to its IP configuration.
- A virtual machine named VM2 deployed in Availability Zone 1. VM2 has a network interface named NIC2 connected to Subnet1 with no public IP address.
- A virtual machine named VM3 deployed in Availability Zone 2. VM3 has a network interface named NIC3 connected to Subnet1 with no public IP address.
You deploy a public Azure Load Balancer named LB1 using the Standard SKU. You associate LB1 with a Standard SKU public IP address named LB-PIP.
When you attempt to add VM1, VM2, and VM3 to the backend pool of LB1, the configuration fails with a SKU mismatch error.
Which action should you perform to successfully add all three virtual machines to the backend pool of LB1?
- ARecreate the load balancer as a Basic SKU load balancer and configure its frontend to use a Basic SKU public IP address.
- BPlace VM1, VM2, and VM3 into a new Availability Set and associate the Availability Set with the Standard load balancer's backend pool.
- CCreate a new subnet in VNet1, move VM3 to the new subnet, and then associate the subnet with the backend pool of the load balancer.
- Dissociate the Basic SKU public IP address from the network interface of VM1, or upgrade it to a Standard SKU public IP address.Cevap