In Azure Load Balancer, what happens when a backend pool VM fails the health probe?
Think about how the load balancer ensures only healthy VMs get traffic.
The health probe checks VM health. If a VM fails, it is removed from the backend pool to avoid sending traffic to an unhealthy VM.
Which Azure CLI command correctly creates a TCP health probe on port 80 for a load balancer?
Check the protocol and port number carefully.
TCP protocol with port 80 is correct for a TCP health probe on port 80. HTTP protocol or other ports do not match the requirement.
You want to design an Azure Load Balancer backend pool to ensure high availability across two regions. Which approach is best?
Consider geographic redundancy and traffic routing.
Using separate backend pools per region with Traffic Manager allows routing users to the closest healthy region, ensuring high availability.
How can you secure Azure Load Balancer health probes to prevent unauthorized access to backend VMs?
Think about controlling network traffic to only trusted sources.
Network Security Groups can restrict probe traffic to only the load balancer's IP ranges and ports, securing backend VMs from unauthorized access.
What is the best practice for setting health probe interval and unhealthy threshold to quickly detect backend failures without causing false positives?
Balance detection speed and avoiding false alarms.
A short interval with a low threshold allows quick detection of failures while avoiding false positives from transient issues.