Exam AZ-103 topic 4 question 17 discussion

Most people here seem to forget that Standard SKU Public IPs cannot have Dynamic assignments. If the Public IP on VM1 is set to Dynamic, that means it is a Public IP with Basic SKU (Public IPs with Standard SKU have Static assignments by default, that cannot be changed). We cannot associate Basic SKUs IPs with Standard SKUs LBs... So, top-box must be "Removing public IP address from VM1". Now, Standard LBs are secure by default (like Standard IPs), so we won't be able to connect to then without explicitly allowing such connections via NSG... So, bottom-box must be "Create and configure NSG".

I believe the answer for 1 should be "Removing public IP address from VM1" and 2 should be "Create and configure NSG".

So many people being tricked by this question. VM1 has public Ip address and sku basic and private Ip address (dynamic). So internet facing Load balancer sku "standard" requires backend pool which has private ip address type static => Answer 1: change dynamic to static Asnwer 2: create and configure NSG

Given answer correct

"Basic SKU Load Balancers use Basic SKU IP Addresses, which aren't compatible with Standard SKU Load Balancers as they require Standard SKU IP Addresses" The IP Addresses are Dynamically assigned, therefore making them, "Basic SKU." Ans1: remove Public IP Ans2: Create & configure NSG https://docs.microsoft.com/en-us/azure/aks/load-balancer-standard

Tested this today -Remove the public address from VM1 -Create and configure an NSG

Remove the public address from VM1 Create and configure an NSG

Private IP and NSG are required for a Standard LB.

I was thinking about removing the public IP address then said what is the issue if you leave the public IP to the VM as long as the LB will use another public IP and will use the VM private IP

"You can only attach virtual machines that are in the same location and on the same virtual network as the loadbalancer. Virtual machines must have a standard SKU public IP or no public IP."

Public IP SKUs and Load Balancer SKUs must match. For Standard Load Balancer , use VMs with Standard IP addresses in the backend pool. Also, you cannot reach standard lb as nothing is allowed. So NSG creation is mandatory Reference:https://docs.microsoft.com/en-us/azure/load-balancer/quickstart-load-balancer-standard-public-portal#create-backend-servers Box1: Remove public IP Box2: create and configure NSG

The answer given is correct, the VM is in Availability Set.

To add a backend pool to standard LB , you must have VMs that have static IP , otherwise you get this error: You can only attach virtual machines in your region that have a standard SKU public IP configuration or no public IP configuration. All IP configurations must be on the same virtual network. and for allowing communication for Standard LB: Standard Load Balancer is secure by default. This means Network Security Groups (NSGs) are used to explicitly permit and whitelist allowed traffic. If you do not have an NSG on a subnet or NIC of your virtual machine resource, traffic is not allowed to reach this resource. Please configure an NSG to ensure communication if needed.

I tested the first scenario. When I tried to add VM with no nsg and dynamic public ip on the back pool, no VM was available which can be added on. On the top, "You can only attach virtual machines in westus that have a standard SKU public IP configuration or no public IP configuration. All IP configurations must be on the same virtual network." was shown. Firstly, I attached NSG on the NIC of VM and still no VM was available on the backpool. Secondly, I disassociated the dynamic public ip from the VM and I can see the vm list which I can add on the backpool.

Why would you need a public IP if you have a load balancer in front of the VM? Just send traffic to the private IP.

Tried and correct answer is : 1) Remove Public IP address (In this case since the IP is dynamic and since it is dynamic it is of Basic category). A Standard load balancer cannot have Basic Public IP Address. Private IP can be Static or dynamic. 2) Create and configure NSG.

Just tested here. You should first remove the Public IP from the VM1, and then, create a NSG to VM1 First Box says: Before you create a backend pool. Here, you can only add VM 1 if the VM has a Static Public IP (Standard), that is not the case, or removing the public IP from this VM. You can enter on public IP configuration associated to VM, and dissociate it from the VM. Second box says Before you can connect to VM1 - Here you should have an NSG associated to VM1. So, based on the options, is create and configure a NSG.