Merge pull request #293418 from cozhang8/patch-9

Update components.md

Author: prmerger-automator[bot]

articles/load-balancer/components.md

@@ -40,8 +40,6 @@ Load balancer instantly reconfigures itself via automatic reconfiguration when y
 
 Backend pools support addition of instances via [network interface or IP addresses](backend-pool-management.md). VMs do not need a public IP address in order to be attached to backend pool of a public load balancer. VMs can be attached to the backend pool of a load balancer even if they are in a stopped state. You can also configure multiple backend pools with different groups of instances to a single load balancer. By creating multiple load balancing rules, each targeting a different backend pool, you can configure traffic to distribute to different sets of backend resources based on the load balancer frontend port and protocol.
 
-When considering how to design your backend pool, design for the least number of individual backend pool resources to optimize the length of management operations. There's no difference in data plane performance or scale.
-
 ## Health probes
 
 A health probe is used to determine the health status of the instances in the backend pool. During load balancer creation, configure a health probe for the load balancer to use.  This health probe determines if an instance is healthy and can receive traffic.