An administrator is configuring a public load balancer named `LB1` to distribute incoming Internet traffic to four virtual machines in a virtual network named `VNet1`.
The virtual machines are deployed as follows:
* `VM1` and `VM2` are in `AvailabilitySet1` and located in `Zone 1`.
* `VM3` and `VM4` are standalone virtual machines and located in `Zone 2`.
The administrator has already created a Standard SKU public IP address named `Pub-IP1` to be used by the load balancer.
You need to configure `LB1` to load balance traffic across all four virtual machines.
Which configuration should you use?
- Deploy a Standard SKU load balancer, associate `Pub-IP1` with the frontend IP configuration, and configure the backend pool using the IP address configuration type.Answer
- BDeploy a Basic SKU load balancer, associate `Pub-IP1` with the frontend IP configuration, and configure the backend pool using the Network interface configuration type.
- CDeploy a Standard SKU load balancer, associate a new Basic SKU public IP address with the frontend IP configuration, and configure the backend pool using the Network interface configuration type.
- DDeploy a Basic SKU load balancer, associate a new Basic SKU public IP address with the frontend IP configuration, and configure the backend pool using the IP address configuration type.
Answer
Deploy a Standard SKU load balancer, associate `Pub-IP1` with the frontend IP configuration, and configure the backend pool using the IP address configuration type.
Deploying a Standard SKU load balancer and associating it with the Standard SKU public IP address `Pub-IP1` satisfies the SKU compatibility requirement. Configuring the backend pool using the IP address configuration type allows the load balancer to target virtual machines across different deployment patterns (standalone and availability sets) within the same virtual network.
Step-by-Step Solution
Key Concept
Azure Load Balancer SKU compatibility and backend pool configuration types
Estimated Time:1m 30s