the question is about what we ve to do first i thing the correct answer is A cause for basic lb we ve to meet 2 criteria's the 2 vm has to be in same subnet, as well as the 2 vm as to be in availability set
but in the question : Create an internal Basic Azure Load Balancer named LB1 and connect the load balancer to VNET1/Subnet1, mentioned Basic LB so C is correct again confused on vnet1/subnet1 (in this case again A is correct ans)
C) is correct.
for a basic loadbalancer, only the Availability Set is needed, therefore you need to redeploy the VMs. They may stay in different subnets - verified in lab. LB and VM1 into VNet1/Subnet1, VM2 into Vnet1/subnet2
Answer C is correct because,
You cannot load balance multiple VMs that are not in the same availability set in Basic Internal Load balancer.
Answer A is also correct as for an Internal load balancer, both LB and VMs should be in same subnet. But first thing to do here is to add both VMs to same availability zone and on process of creating same availability zone, you can create VMs in same subnet as LB.
To add VM1 and VM2 to the backend pool of LB1, the first step you should take is to ensure that both virtual machines are connected to the same virtual network and subnet that LB1 is associated with. Therefore, the correct action to take first would be:
A. Connect VM2 to VNET1/Subnet1.
This ensures that both VM1 and VM2 are in the same network segment as LB1, allowing them to be added to LB1’s backend pool1.
accorrding to Azure documentatioon, Basic Load Balancer only supports within-zone load balancer, and the back end poos needs to be a scale set or availability set. So the given answer is correct, connect VM2 to VNET1/Subnet1.
https://learn.microsoft.com/en-us/azure/load-balancer/skus
The Points are "the LB's SKU" AND "What should you do FIRST?" ....
The Lb is basic LB. We have two important requirements here: The machines must be in a VMSS or Availability Set AND deployed into the subnet.
AGAIN: "What should you do FIRST?"
To satisfy all requirements you MUST recreate all VMs in an availability set (possible only during the creation) AND you can choose the same subnet for all VMs during the process.
OK, You could move the VM to another subnet (creating a new NIC attached to the subnet and removing the first one) without recreating it but can´t migrate the VM to an Availability set without recreating it.
Moving to another is incomplete and you would be required to recreate VMs to satisfy the second requirement.
The answer is Letter A because the requirement "What should you do FIRST?".
Since it is saying Basic Load Balancer, the Scale Set should be set up, the first step to set up Scale Set is to have the VMs in the same Subnet.
Below is my conversation with GPT:
Me:
talking about Scale sets, is it a requirement for VMs to be in the same subnet?
ChatGPT
For Azure Virtual Machine Scale Sets (VMSS), it is indeed a requirement for all instances within a scale set to be deployed into the same subnet. When you create a VMSS, you specify the subnet during the initial configuration, and the VMSS manager then places each VM instance into that subnet.
This question is missing the SKU of the LB.
If LB is standard , Opt A and C is correct.
if LB is Basic, Opt C is correct.
May be Opt C is the Wise Choice.
Wrong. Basic Load Balancer -> Backend pool endpoints -> Virtual machines in a single availability set or virtual machine scale set. https://learn.microsoft.com/en-us/azure/load-balancer/skus
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
HMO
Highly Voted 2 years, 5 months agotunaparker
Highly Voted 2 years, 1 month agoleopouhela
Most Recent 6 months, 2 weeks ago090200f
8 months, 2 weeks ago090200f
8 months, 2 weeks agoMSExpertGER
8 months, 3 weeks agoForkbeard
9 months, 2 weeks agoIssa_adhi
9 months, 3 weeks agoMysystemad
10 months, 4 weeks agotashakori
11 months, 3 weeks agoLZNJ
1 year agopcman
1 year, 2 months agopcman
1 year, 2 months agoMehrannn
1 year, 3 months agoViggy1212
1 year, 4 months agommarkiew
1 year, 4 months agoayoubhem
1 year, 5 months agohidefo6963
1 year, 5 months agoKverma7
1 year, 6 months agolulzsec2019
1 year, 7 months agoPakawat
1 year, 8 months ago