AZ-305 ยท Internet connectivity and load balancing
Azure Load Balancer Standard: Layer 4 building blocks
Azure Load Balancer Standard: public vs internal, zone-redundant frontends, health probes, HA ports, outbound rules, global (cross-region) load balancer.
Key points
- Layer 4 pass-through for TCP/UDP; public or internal frontend, zone-redundant.
- Health probes: NSGs must allow the AzureLoadBalancer service tag.
- HA ports: port 0, protocol All, internal Standard only; scales out NVAs.
- Outbound rules: up to 64,000 SNAT ports per frontend IP, multiples of 8, idle 4-120 min; NAT Gateway preferred.
- Global tier: static anycast IP over regional public load balancers; client IP kept; no internal frontends.
Source: https://learn.microsoft.com/en-us/azure/load-balancer/outbound-rules
Practice questions
On which kind of load balancer can you create an HA ports load-balancing rule?
- A public Standard load balancer
- An internal Standard load balancer
- A global (cross-region) load balancer
- An Application Gateway Standard_v2
Show answer
Answer: B. An internal Standard load balancer
HA ports rules are supported only on an internal Standard load balancer. A public load balancer, a global load balancer and Application Gateway do not offer them.
Which statements about the global (cross-region) tier of Azure Load Balancer are true?
- Its back-end pool contains regional public Standard load balancers
- It provides a static anycast public IP address
- The original client IP address reaches the back-end VMs
- It can use an internal (private) frontend IP
- It supports outbound rules for SNAT
Show answer
Answer: A. Its back-end pool contains regional public Standard load balancers, B. It provides a static anycast public IP address, C. The original client IP address reaches the back-end VMs
The global tier exposes a static anycast public IP, its back-end pool holds regional public Standard load balancers, and as a Layer 4 pass-through it preserves the client IP. It does not support internal frontends, and outbound rules are not supported on it - use outbound rules on the regional load balancers or NAT Gateway.
Health probes come from inside the Azure platform, so an NSG that denies the AzureLoadBalancer service tag has no effect on which VMs receive new flows.
Show answer
Answer: False
False. If an NSG blocks probe traffic from the AzureLoadBalancer tag, the probes fail, the VMs are marked unavailable and the load balancer stops sending them new flows. Keep the default rule or allow the tag explicitly.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
