Study guide

8.2 Public and Internal Load Balancer Design

AZ-104 Microsoft Azure Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Orientation and Microsoft Learn Source Control

1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log

2 Chapter 2: Identity, RBAC, and Governance Foundations

2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab

3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization

3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab

4 Chapter 4: Storage Accounts, Access, and Data Protection

4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab

5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep

5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab

6 Chapter 6: Containers, App Service, and Platform Compute

6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab

7 Chapter 7: Virtual Networking, Routing, and Secure Access

7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab

8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting

8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab

9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery

9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab

10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs

10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab

11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path

11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths

8.2 Public and Internal Load Balancer Design

Key Takeaways Explain This Topic AI

Azure Load Balancer is a Layer 4 service that distributes TCP and UDP traffic by frontend IP, rule, backend pool, and health probe.

A public load balancer exposes a public frontend IP, while an internal load balancer uses a private frontend IP inside a VNet.

Standard Load Balancer is the normal production choice and requires explicit network security rules for traffic flow.

Load balancer design must match client location, protocol, port, availability zone, and backend placement.

Do not confuse Azure Load Balancer with Application Gateway, Traffic Manager, Front Door, or DNS round robin.

Last updated: May 2026

What Azure Load Balancer does

Azure Load Balancer distributes inbound and outbound TCP and UDP flows at Layer 4. It does not inspect HTTP paths, cookies, host headers, or TLS certificates. The administrator defines a frontend IP, a backend pool, a health probe, and one or more load balancing rules. When a client connects to the frontend IP and port, Azure distributes the flow to healthy backend instances based on the rule.

A public load balancer has a public frontend IP address. It is used when clients on the internet, or external clients routed through a public path, must reach backend resources. An internal load balancer has a private frontend IP address in a subnet. It is used when clients inside a VNet, peered VNet, VPN, or ExpressRoute-connected network need a stable private service endpoint.

  • Design question Public Load Balancer Internal Load Balancer
  • Frontend IP type Public IP address Private IP address from a subnet
  • Typical clients Internet clients or public ingress paths VNet, peered VNet, VPN, ExpressRoute clients

Common use Public TCP or UDP services, inbound NAT, outbound SNAT Private application tiers, internal appliances, database listener patterns

  • DNS record type Public DNS A record points to public IP Private DNS A record points to private frontend IP
  • Security focus Public exposure, NSGs, allowed source ranges Internal segmentation, routes, NSGs, hybrid access
  • Standard versus Basic

Standard Load Balancer is the expected production answer. It supports zone-aware and zone-redundant designs, larger scale, stronger SLA patterns when configured correctly, HA ports, and integration with Standard public IP addresses. Basic Load Balancer is legacy and limited. In new AZ-104 scenarios, choose Standard unless a question explicitly describes an existing Basic deployment.

Standard Load Balancer is secure by default in an important way: inbound traffic requires explicit NSG allowance to the backend. If a backend VM is healthy but clients cannot connect, check NSG rules before assuming the load balancer rule is broken. Public IP SKU must also match. Standard Load Balancer uses Standard public IP addresses, not Basic public IP addresses.

Choosing public or internal

Start with the client. If the client is a public user connecting to a TCP service on the internet, a public load balancer may fit. If the client is an application tier in another subnet, an on-premises client over VPN, or a VM in a peered VNet, use an internal load balancer when the service should remain private.

Scenario examples:

Scenario Likely design Why

Two Linux VMs host a public TCP service on port 443 Public Standard Load Balancer Internet clients need a public frontend.

Web tier in subnet A calls an API tier in subnet B Internal Standard Load Balancer The API endpoint should stay private.

On-premises clients over ExpressRoute call a private application Internal Standard Load Balancer plus private DNS Hybrid clients should resolve a private name to a private frontend IP.

Need URL path routing between /api and /images Application Gateway or Front Door, not Load Balancer Azure Load Balancer is Layer 4, not HTTP Layer 7.

Need global DNS-based endpoint selection Traffic Manager or Front Door, not regional Load Balancer Azure Load Balancer is regional.

Frontend IP and backend placement

The frontend IP is the address clients connect to. A public load balancer frontend uses a public IP resource. An internal load balancer frontend uses an IP from a subnet. Backend pools can contain VM NICs or IP addresses depending on the configuration. VM Scale Sets are common backend targets because they provide multiple identical instances.

Zone design matters. A zone-redundant Standard public IP can survive a single zone failure for the frontend. Backends should also be distributed across availability zones or availability sets according to the workload requirement. A zone-redundant frontend does not magically make a single backend VM highly available.

The load balancer does not install or start the application. Each backend must listen on the backend port and respond to the health probe. If the frontend listens on port 80 and the backend port is 8080, the application must listen on 8080 unless a local proxy maps it.

DNS for load-balanced services

DNS should point users to the frontend, not to individual backend VMs. For public services, create a public DNS A record that points to the public IP address or use a label on the public IP if appropriate. For internal services, create a private DNS A record that points to the internal load balancer frontend IP.

Do not create multiple A records for backend VMs as a replacement for a load balancer when the requirement includes health-based distribution. DNS round robin does not know whether the application on a VM is healthy. Azure Load Balancer uses health probes to remove unhealthy instances from rotation.

Design troubleshooting tree Need to choose a load balancing service

|-- Is the traffic HTTP or HTTPS and needs URL, host, cookie, or TLS decisions?

| |-- Yes: consider Application Gateway or Front Door.

| |-- No: continue.

|-- Is the endpoint regional TCP or UDP?

| |-- Yes: Azure Load Balancer fits.

| |-- No: consider DNS/global service options.

|-- Are clients on the internet?

| |-- Yes: public Load Balancer with public frontend IP.

| |-- No: internal Load Balancer with private frontend IP.

|-- Must backend health affect traffic distribution?

| |-- Yes: configure a health probe and rules.

| |-- No: simple DNS may be enough, but rarely for production app tiers.

Portal and CLI flow

Portal path: Azure portal > Load balancers > Create . Choose SKU, type, frontend IP configuration, backend pool, inbound rules, and probes. For a public design, create or select a Standard public IP. For an internal design, choose the VNet, subnet, and private frontend address.

  • CLI outline: az network lb create \
  • g rg-network \
  • n lb-web-public \
  • -sku Standard \
  • -public-ip-address pip-web
  • az network lb create \
  • g rg-network \
  • n lb-api-internal \
  • -sku Standard \
  • -vnet-name vnet-prod \
  • -subnet subnet-app \
  • -frontend-ip-name fe-api \
  • -private-ip-address 10.20.2.10
  • Exam traps

If the scenario says the load balancer should route based on URL path, Azure Load Balancer is not the answer. If it says TCP or UDP and regional distribution, it often is. If public users cannot connect to a Standard public load balancer, remember NSGs must allow traffic to the backends. If internal users cannot connect by name, check private DNS before changing the load balancer type.

A final practical distinction: an internal load balancer is not a security boundary by itself. It has a private IP, but NSGs, route tables, service firewalls, and segmentation still control which clients can reach it.