Exam AZ-700 topic 3 question 35 discussion

N - Tested in lab and confirmed once 1 backend pool has been configured you cannot add another backend pool on a different VNET, the original VNET is always selected. Y - VM1 is on VNET2 N - rule 1 is TCP/80, not 443 (HTTPS)

Y - VM4 is in another Vnet. A backend pool can only contain resources from one virtual network. Y - Backend pool Virtual Network is Vnet2. VM1 is in Vnet2 N - Load balancing rule: rule1 (Tcp/80) is HTTP not HTTPS

for First statement: No. The search results indicate that to add VM4 to the existing load balancer LB1, you do not need to create a new backend pool. This is because VM4 is in a different virtual network (Vnet3) than the existing backend pool (Vnet2), and the backend pool configuration is set to "NIC", which means it is based on the network interface of the VMs, not their IP addresses. Therefore, the backend resources do not need to be in the same virtual network as the load balancer for IP-based load balancers. The load balancer can load balance traffic to backend resources in different virtual networks, as long as the network interfaces of those resources are configured correctly.

NYN N - multiple backend pools, mix of IP backend pool or NIC backend pool, but they must be in the same VNET as the Lodabalancer and it's not possible to change this VNet once LB is created and deployed Y - both in samebackednpool in vnet2 N - LB rule is for port 80 and NOT 443

YYN - The backend resources must be in the same virtual network as the load balancer for IP based LBs - You can configure IP based and NIC based backend pools for the same load balancer. You can’t create a single backend pool that mixes backed addresses targeted by NIC and IP addresses within the same pool. https://learn.microsoft.com/en-us/azure/load-balancer/backend-pool-management#limitations

N - you can have multiple backend pools, mix of IP backend pool or NIC backend pool, but they must be in the same VNET than the Lodabalancer (in fact same vnat than the first frontend IP chosen at deployment: then you can't create another Frontend IP in a different VNet or remove all frontend IP; So it's not possible to change this VNet once LB is deployed). Backend pools must be in the same VNet than the Frontend IP. So in facts a Loadbalancer cannot span multiple vnets. (all tested in lab) (may change with cross-region load balancer which is still in preview https://learn.microsoft.com/fr-fr/azure/load-balancer/cross-region-overview) Y - Loadbalancer backend pool is in VNet2 so following the explanations above, all the VMS in the pool are in VNet 2. So VM1 which is in this backend pool is in VNet2. N - Load Balancing rule is set for port 80 wich is the default HTTP port. HTTPS is 443. so HTTPS connections will not be handled by this Loadbalancer.

The fist answer is no because VM4 exists in VNET3/Subnet3, so it can never be added to LB1, even as a 2nd backend pool. We can see the LB has a private address, meaning it is an internal LB. When you create the ILB, it assigns the FE configuration to a VNET/Subnet of your choosing. When you go to the backend pool page, the Virtual Network is always hardcoded to the VNET your FE is assigned to. When you click on "+ Add a backend pool", you get the Add backend pool page, which states: IP configurations IP configurations associated to virtual machines and virtual machine scale sets must be in same location as the load balancer and be in the same virtual network. The answer to question 1 also confirms that the 2nd answer is Yes, as the VMs need to be in the same VNET as the LB Virtual Network which the question defines as VNET2. The 3rd answer is no, because the inbound rule is for HTTP (Port 80) only. No HTTPS (Port 443).

NYN is the correct answer: It is important to note that the backend pool configuration for backend1 is set to "NIC", which means that the load balancer is configured to load balance traffic between the network interfaces associated with the virtual machines (VMs) in the backend pool. In order to add VM4 to LB1, you would need to create a new NIC for VM4 that is associated with a subnet in the same virtual network as the existing backend pool, Vnet2. This would allow LB1 to load balance traffic between the NICs associated with all the VMs in the backend pool, including VM4.

Provided answer is correct. NYN. 1. You cant add the vm to the loadbalancer because IP configurations associated to virtual machines and virtual machine scale sets must be in same location as the load balancer and be in the same virtual network. 2. True because of the previous sentence 3. No https is not in the rule

I think it's N Y N. 1. It says the backend pool is NIC based, and I can't find anything saying that resources in a NIC based backend pool have to be in the same VNET. If it were IP-based, that is directly stated in this link: https://learn.microsoft.com/en-us/azure/load-balancer/backend-pool-management#limitations I assume that link would say if it were also a requirement for NIC based backend pools. 2. VM1 is in the backend pool, which is assigned to VNET2. 3. rule1 is on port 80, which is HTTP. HTTPS requires port 443.

Y Y N 1) A VM on a different Vnet cannot be added on a backend LB on VNET2 | VM4 on VNET 3 2) VM1 is connected in VNET 2 3) Watch out the rule is on "HTTP" = 80 port not on "HTTPS" = 443

Yes Yes No. To add VM4 to LB1, you must create a new backend pool. Yes. In order to add VM4 to LB1, you must create a new backend pool that includes VM4's network interface (vm4981) in Vnet3/Subnet3. VM1 is connected to VNET2. Yes. VM1 is a part of the backend pool "backend1" which is associated with the virtual network Vnet2. Connections to https://10.3.0.7 will be load balanced between VM1, VM2, and VM3. No. The load balancing rule "rule1" is configured to load balance traffic on TCP port 80, not HTTPS (TCP port 443). Therefore, connections to https://10.3.0.7 will not be load balanced by LB1.

Backend hosts have to be in the same vnet - https://stackoverflow.com/questions/66529619/can-azure-internal-loadbalancer-have-backends-belonging-to-different-subnets-in

N Y N - Backend resources must be in the same virtual network as the load balancer for IP based load balancers https://learn.microsoft.com/en-us/azure/load-balancer/backend-pool-management#limitations. 1, Since Vms in the current backed pool are in Vnet2 we can asume that load balancer is also in vnet2. Hence vms from Vnet3 cant be added as backend resources = N. 2, VM must be in the same vnet as load balancers backend pool so it must be in vnet2 = Y. 3, Https defaults to port 443 and there is not load balancing rule for port 443 = N

A backend pool can only contain resources from one virtual network. HTTPS is using port tcp 443