Skip to content

Commit 62233b6

Browse files
authored
Adding questions, moving questions around
1 parent 1f3b507 commit 62233b6

File tree

1 file changed

+16
-7
lines changed

1 file changed

+16
-7
lines changed

articles/load-balancer/load-balancer-faqs.md

Lines changed: 16 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,13 +10,22 @@ ms.author: errobin
1010
---
1111
# Frequently Asked Questions
1212

13-
## Are there data throughput limits for the Load Balancer?
14-
There are no hard limits on data throughput. For public load balancers, the recommend ingress rate is 10 Gbps for Standard SKU and XXX Gbps for Basic SKU, with no egress limit. Internal load balancers have no ingress or egress throughput limits. It is important to consider the data throughput of your backend resources in all configurations.
15-
16-
## What are the different Load Balancing options in Azure?
17-
See the [load balancer technology guide](https://docs.microsoft.com/azure/architecture/guide/technology-choices/load-balancing-overview) for the available load balancing options and an in-depth explanation on the differences and recommended uses for each.
13+
## What types of Load Balancer exist?
14+
Internal load balancers which balance traffic within a VNET and external load balancers which balance traffic to and from an internet connected endpoint. For both these types, Azure offers a Basic SKU and Standard SKU which have differing functional, performance, security and health tracking capabilities.
1815

1916
## How can I upgrade from a Basic Load Balancer to a Standard Load Balancer?
20-
See the [upgrade from Basic to Standard](upgrade-basic-standard.md) article for an automated script and guidance on upgrading from Basic SKU to Standard SKU.
17+
See the [upgrade from Basic to Standard](upgrade-basic-standard.md) article for an automated script and guidance on upgrading from Basic SKU to Standard SKU.
18+
19+
## What are the different load balancing options in Azure?
20+
See the [load balancer technology guide](https://docs.microsoft.com/azure/architecture/guide/technology-choices/load-balancing-overview) for the available load balancing services and an in-depth explanation on the differences and recommended uses for each.
2121

22-
## How is the load distributed across backend instances?
22+
## Where can I find Load Balancer ARM templates?
23+
See the [list of Azure Load Balancer quickstart templates](https://docs.microsoft.com/azure/templates/microsoft.network/loadbalancers#quickstart-templates) for ARM templates of common deployments.
24+
25+
## How are inbound NAT rules different from LB rules?
26+
NAT rules are used to specify a backend resource to route traffic to. For example, configuring a specific load balancer port to send RDP traffic to a specific VM. Load balancing rules are used to specify a pool of backend resources to route traffic to, balancing the load across each instance. An example of this is routing HTTP requests on port 80 of the load balancer across a pool of web servers.
27+
28+
## How is the load distributed across backend instances?
29+
30+
## Are there data throughput limits for the Load Balancer?
31+
There are no hard limits on data throughput. For public load balancers, the recommend ingress rate is 10 Gbps for Standard SKU and XXX Gbps for Basic SKU, with no egress limit. Internal load balancers have no ingress or egress throughput limits. It is important to consider the data throughput of your backend resources in all configurations.

0 commit comments

Comments
 (0)