Merge pull request #113635 from anavinahar/patch-242

Update components.md

Author: PRMerger14

articles/load-balancer/components.md

@@ -26,6 +26,14 @@ The IP address of the load balancer. It's the point of contact for clients. Thes
 
 The selection of the IP address determines the **type** of load balancer created. Private IP address selection creates an internal load balancer. Public IP address selection creates a public load balancer.
 
+|  | Public Load Balancer  | Internal Load Balancer |
+| ---------- | ---------- | ---------- |
+| Frontend IP configuration| Public IP address | Private IP address|
+| Description | A public load balancer maps the public IP and port of incoming traffic to the private IP and port of the VM. Load balancer maps traffic the other way around for the response traffic from the VM. You can distribute specific types of traffic across multiple VMs or services by applying load balancing rules. For example, you can spread the load of web request traffic across multiple web servers.| An internal load balancer distributes traffic to resources that are inside a virtual network. Azure restricts access to the frontend IP addresses of a virtual network that are load balanced. Front-end IP addresses and virtual networks are never directly exposed to an internet endpoint. Internal line-of-business applications run in Azure and are accessed from within Azure or from on-premises resources. |
+| SKUs supported | Basic, Standard | Basic, Standard |
+
+![Tiered load balancer example](./media/load-balancer-overview/load-balancer.png)
+
 ## Backend pool
 
 The group of virtual machines or instances in a virtual machine scale set that is serving the incoming request. To scale cost-effectively to meet high volumes of incoming traffic, computing guidelines generally recommend adding more instances to the backend pool.