HOTSPOT -
You have an Azure subscription that contains the resources in the following table.
You install the Web Server server role (IIS) on VM1 and VM2, and then add VM1 and VM2 to LB1.
LB1 is configured as shown in the LB1 exhibit. (Click the Exhibit tab.)
Rule1 is configured as shown in the Rule1 exhibit. (Click the Exhibit tab.)
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:
Manage Azure subscriptions and resources
I think this is right (VM1, VM2 same availability set = Yes, Probe1.htm on VM1 and VM2, LB1 with balance between them = Yes, If rule 1 deleted, LB1 will blance all requests between VM1 and VM2 on all ports = No) based on: 1) Basic SKU doesn't allow flexibility in Availability Sets https://docs.microsoft.com/en-us/azure/load-balancer/concepts-limitations#skus 2) Rule1 health probe looks for /Probe1.htm - if it is present on both VMs, LB1 will balance between them 3) https://docs.microsoft.com/en-gb/azure/load-balancer/load-balancer-custom-probe-overview - Basic SKU, Probe down behaviour = All probes down, all TCP flows expire.
Why you infer VM1 and VM2 are in the same Availability Set? What prevents them from being Single VMs? The first statement is something we can't actually assess with certainty from the info that's given.
In fact, you are right. BackEnd pools for Basic SKU LBs require that multiple VMs be in an Availability Set. We can deploy ONE VM that's not in an Availability Set, but not a second one. That's the error I got when trying that: "All of the selected Virtual Machines have to be in one Availability Set or only one Virtual Machine can be selected" Standard SKU LBs do not have that limitation (checked that too), but since the one in the question is a Basic SKU LB, the backend VMs must be in the same Availability Set. Therefore, second statement is TRUE.
https://docs.microsoft.com/en-us/azure/load-balancer/skus#skus Basic LoadBalancer SKU supports availability set or scale sets.
I have one query , is availability set= cluster ? and floating IP is = virtual ip of cluster ?
https://docs.microsoft.com/en-us/azure/load-balancer/skus#skus Basic LoadBalancer SKU supports availability set or scale sets.
You can't use load balancer for machines are not on the same availability set
Actually you can load balance to stand alone machines using the Standard Load balancer SKU
I have one query , is availability set= cluster ? and floating IP is = virtual ip of cluster ?
Actually you can load balance to stand alone machines using the Standard Load balancer SKU
A basic LB can not load balance single Vms.
In fact, you are right. BackEnd pools for Basic SKU LBs require that multiple VMs be in an Availability Set. We can deploy ONE VM that's not in an Availability Set, but not a second one. That's the error I got when trying that: "All of the selected Virtual Machines have to be in one Availability Set or only one Virtual Machine can be selected" Standard SKU LBs do not have that limitation (checked that too), but since the one in the question is a Basic SKU LB, the backend VMs must be in the same Availability Set. Therefore, second statement is TRUE.
https://docs.microsoft.com/en-us/azure/load-balancer/skus#skus Basic LoadBalancer SKU supports availability set or scale sets.
I have one query , is availability set= cluster ? and floating IP is = virtual ip of cluster ?
https://docs.microsoft.com/en-us/azure/load-balancer/skus#skus Basic LoadBalancer SKU supports availability set or scale sets.
You can't use load balancer for machines are not on the same availability set
Actually you can load balance to stand alone machines using the Standard Load balancer SKU
I have one query , is availability set= cluster ? and floating IP is = virtual ip of cluster ?
Actually you can load balance to stand alone machines using the Standard Load balancer SKU
agree so answer is yes,yes and no
A basic LB can not load balance single Vms.
This one may cause some confusion, but "Yes", "Yes", "No" are the correct answers.
For the Basic LB: I just made test so you have two possibilities : 1 : Add one VM 2: Add More than one VM but those VMs should be in the same Availability Set
Exam Question 12/23/2020
Explanation for the last answer (No is correct) : "If all probes for all instances in a backend pool fail, no new flows will be sent to the backend pool. Standard Load Balancer will permit established TCP flows to continue. Basic Load Balancer will terminate all existing TCP flows to the backend pool. Load Balancer is a pass through service (does not terminate TCP connections) and the flow is always between the client and the VM's guest OS and application. A pool with all probes down will cause a frontend to not respond to TCP connection open attempts (SYN) as there is no healthy backend endpoint to receive the flow and respond with an SYN-ACK." -> https://docs.microsoft.com/en-gb/azure/load-balancer/load-balancer-custom-probe-overview#tcp-connections
I think a basic lb sku doesnt support availability sets
It does. In fact, if we want to have more than one VM load-balanced, they must be in an Availability Set (or Scale Set). In a Standard SKU LB, we can have multiple standalone VMs that are not in an Availability Set, however this setup is not allowed in Basic SKU LBs.
it supports VM in a single availability or scale set.
It does: https://docs.microsoft.com/en-us/azure/load-balancer/skus#skus
Basic: Virtual machines in a single availability set or virtual machine scale set
Basic: Virtual machines in a single availability set or virtual machine scale set
Basic vs Standard regarding availibility sets???: The Standard Tier scale up a service out across 3 zones in a single region for a 99.99 percent service level agreement or SLA. The Basic Tier is limited to non-availability zone deployments. https://dynalearntech.com/learning-the-difference-between-basic-and-standard-azure-load-balancers.html
That info of yours regards Availability Zones, not Availability Sets.
Yes, Yes, No
I just added VMs that are not part of a scale set or availability set. It worked. Does question A mean that the virtual machines cannot be in different availability sets ?
YES YES NO
Update - I used a standard LB, not a basic. so my test does not count.
Basic LB only support VMs in a single availability set or VM scale set.
Basic LB only support VMs in a single availability set or VM scale set or VMs that don't belong to any set.
Basic LB only support VMs in a single availability set or VM scale set or VMs that don't belong to any set.
Try adding a rule and see what happens. I got this error { "status": "Failed", "error": { "code": "ReferencedVMsDontBelongToSameAvailabilitySet", "message": "Not all Virtual Machines vm1,vm2 indirectly referenced by the Load Balancer lb_basic1 belong to the same availability set.", "details": [] } }
i think first one is "no" because availability set will not show the number of VMs within it so these are single VMs
single vm is *not* supported on Basic LB Review https://docs.microsoft.com/en-us/azure/load-balancer/skus#skus
The basic loadbalancer can have only VMs from a VMSS or a single VM. But why are we equating availability set to Scale Set for the first question? VM1/VM2 are in same scale set and not same availability set.
you didnt read this https://docs.microsoft.com/en-us/azure/load-balancer/skus#skus it can support availability support Virtual machines in a single availability set or virtual machine scale set.
Are all the answers correct? No one had answered this yet.
Yes, is correct. Basic LB only can balance availability sets, so YYN
The answer to first question should be No. I was able to create a "basic" sku load balancer using 2 VMs that are not in any Availability sets. Maybe the basic sku does not allow VMs from two different Availability sets to be added but that does not mean that VMs have to be in the same Availability sets. They might have no Availability sets associated.
more accurate statement would be that "Both VMs belong to the same Availability set or do not belong to any availability set"
I stand corrected. The VMs must be in same Availability sets. You can add VMs that way I described but when you try to add a rule, it fails with this error -------- { "status": "Failed", "error": { "code": "ReferencedVMsDontBelongToSameAvailabilitySet", "message": "Not all Virtual Machines vm1,vm2 indirectly referenced by the Load Balancer lb_basic1 belong to the same availability set.", "details": [] } }
Yes about option 3, If SKU is basic and probe is down the TCP will expire but SKU is standard then TCP flows continue
1st answer is wrong. Basic SKU load balancer does not support Availability Zones.