You have an Azure subscription that contains a virtual network named VNet1. VNet1 contains two virtual machines named VM1 and VM2. VM1 and VM2 are deployed as standalone virtual machines. VM1 has a public IP address named IP1 assigned directly to its network interface. IP1 is configured with the Basic SKU. VM2 does not have a public IP address. You provision a new public IP address named IP2 configured with the Standard SKU. You plan to create a public load balancer named LB1, use IP2 as the frontend IP configuration, and distribute inbound traffic to VM1 and VM2. You need to configure the load balancer and the virtual machines to support this configuration. Which two actions should you perform?
- Create LB1 as a Standard load balancer.Cevap
- Disassociate the public IP address IP1 from the network interface of VM1.Cevap
- CCreate LB1 as a Basic load balancer.
- DAssociate the public IP address IP1 as the frontend IP configuration for LB1.
Cevap
Create LB1 as a Standard load balancer and disassociate the public IP address IP1 from the network interface of VM1.
To deploy a public load balancer with a Standard SKU public IP frontend that distributes traffic to standalone virtual machines, you must create a Standard load balancer. Furthermore, because Standard load balancers require all instance-level public IP addresses in the backend pool to use the Standard SKU, the Basic SKU public IP address (IP1) currently assigned to the network interface of VM1 must be disassociated.
Adım Adım Çözüm
Anahtar Kavram
Standard SKU Load Balancer configuration and resource SKU compatibility constraints.