Cloud Load Balancing Questions and Answers for Viva

Answer-1: A target group routes requests to one or more registered targets like EC2 instances or IP addresses.

Answer-2: DNS-based load balancing distributes traffic by resolving a domain name to multiple IP addresses.

Answer-3: Round-robin distributes requests sequentially to each server in the pool.

Answer-4: It directs traffic to the server with the fewest active connections.

Answer-5: Weighted load balancing assigns traffic based on predefined server weights, giving more traffic to higher-capacity servers.

Answer-6: By distributing traffic across multiple instances and zones, preventing single points of failure.

Answer-7: To continuously monitor server availability and performance to ensure traffic is sent only to healthy instances.

Answer-8: Yes, most cloud load balancers support both HTTP and HTTPS traffic.

Answer-9: A CDN caches content globally to improve delivery speed, often working alongside load balancers for traffic distribution.

Answer-10: By evenly distributing incoming traffic, allowing applications to scale horizontally.

Answer-11: Connection draining allows existing connections to a server to complete before removing the server from the load balancer?s pool.

Answer-12: ELB is AWS's load balancing service that automatically distributes incoming application traffic across multiple targets.

Answer-13: Google Cloud Load Balancing is a fully distributed, software-defined managed service that scales traffic across multiple backend instances.

Answer-14: Azure Load Balancer is a Layer 4 load balancer that distributes incoming network traffic to Azure virtual machines.

Answer-15: They support SSL/TLS termination, DDoS protection, and integration with firewalls and WAFs (Web Application Firewalls).

Answer-16: By distributing traffic to resources across multiple geographic regions for improved performance and redundancy.

Answer-17: Proxy protocol passes client connection information like IP addresses to backend servers.

Answer-18: By enabling sticky sessions based on cookies or IP address so subsequent requests from the same client go to the same backend.

Answer-19: Hardware load balancers are physical devices, while software load balancers run on commodity hardware or in cloud environments.

Answer-20: Metrics include request count, latency, healthy/unhealthy host counts, and error rates.

Answer-21: Some cloud load balancers support UDP, but support varies by provider.

Answer-22: Proper load balancing can reduce latency by routing traffic to the nearest or least loaded server.

Answer-23: Load balancers improve fault tolerance by detecting failed instances and rerouting traffic to healthy ones.

Answer-24: A load balancing algorithm where servers receive requests in proportion to their assigned weights.

Answer-25: By automatically redirecting traffic away from failed or overloaded instances to healthy ones.

Answer-26: The frequency at which load balancers check the status of backend servers.

Answer-27: Many modern cloud load balancers support HTTP/2 to improve performance and multiplexing.

Answer-28: A listener is a process that checks for connection requests using a specified protocol and port.

Answer-29: By distributing the load across available instances and triggering autoscaling to add resources.

Answer-30: Active-active uses multiple load balancers simultaneously, while active-passive uses one active and one standby for failover.

Answer-31: Load balancing is the process of distributing network or application traffic across multiple servers to ensure reliability and performance.

Answer-32: It ensures high availability, fault tolerance, and scalability of cloud applications by evenly distributing workloads.

Answer-33: Common types include Layer 4 (Transport Layer), Layer 7 (Application Layer), global load balancing, and internal load balancing.

Answer-34: Layer 4 load balancing operates at the transport layer using IP addresses and TCP/UDP ports to distribute traffic.

Answer-35: Layer 7 load balancing works at the application layer, making routing decisions based on HTTP headers, URLs, cookies, or content.

Answer-36: A load balancer is a device or service that distributes incoming network or application traffic across multiple backend resources.

Answer-37: AWS Elastic Load Balancer (ELB), Azure Load Balancer, Google Cloud Load Balancing.

Answer-38: ALB is a Layer 7 load balancer that routes traffic based on application-level information such as HTTP headers and URL paths.

Answer-39: NLB is a Layer 4 load balancer designed for ultra-high performance, handling millions of requests per second with low latency.

Answer-40: Global Load Balancer distributes traffic across geographically dispersed data centers or regions.

Answer-41: Load balancers regularly probe backend instances with health checks to route traffic only to healthy targets.

Answer-42: It is a method to route requests from the same client to the same backend server to maintain session state.

Answer-43: Improved availability, scalability, fault tolerance, and better user experience.

Answer-44: Autoscaling automatically adjusts the number of servers based on load, and load balancers distribute traffic to these dynamically scaled resources.

Answer-45: Commonly supported protocols include HTTP, HTTPS, TCP, UDP, and SSL.

Answer-46: SSL termination means decrypting SSL/TLS traffic at the load balancer to reduce overhead on backend servers.

Answer-47: Public load balancers route external traffic, whereas internal load balancers handle traffic within a private network or VPC.

Answer-48: Cross-zone load balancing distributes traffic evenly across all registered instances in different availability zones.

Answer-49: A reverse proxy forwards client requests to backend servers and can perform load balancing to distribute traffic.

Answer-50: They detect unhealthy servers and reroute traffic to healthy servers to ensure continuous service availability.