After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have an Azure subscription that contains the virtual machines shown in the following table.
You deploy a load balancer that has the following configurations:
✑ Name: LB1
✑ Type: Internal
✑ SKU: Standard
✑ Virtual network: VNET1
You need to ensure that you can add VM1 and VM2 to the backend pool of LB1.
Q. 1: Solution: You create a Basic SKU public IP address, associate the address to the network interface of VM1, and then start VM1.
Does this meet the goal?
- A. Yes
- B. No
Correct Answer: B
A Backend Pool configured by IP address has the following limitations:
✑ Standard load balancer only
Reference: https://docs.microsoft.com/en-us/azure/load-balancer/backend-pool-management
Does this meet the goal?
- A. Yes
- B. No
Q. 3: Solution: You create two Standard public IP addresses and associate a Standard SKU public IP address to the network interface of each virtual machine.
Does this meet the goal?
- A. Yes
- B. No
Q. 4:Solution: You disassociate the public IP address from the network interface of VM2. Does this meet the goal?
- A. Yes
- B. No
Correct Answer: A – You can only attach virtual machines that have a standard SKU public IP configuration or no public IP configuration. All IP configurations must be on the same virtual network. ALso, VMs do not have to be powered on when adding them to a backend pool. So answer should be A (Yes)
The LB needs to be a standard SKU to accept individual VMs outside an availability set or vmss. VMs do not need to have public IPs but if they do have them they have to be standard SKU. Vms can only be from a single network. When they don’t have a public IP they are assigned an ephemeral IP.
Also, when adding them to a backend pool, it doesn’t matter in which status are the VMs.
Note: Load balancer and the public IP address SKU must match when you use them with public IP addresses.