Which component is primarily responsible for observing health and removing failed instances from rotation?

Which component is primarily responsible for observing health and removing failed instances from rotation?

• A. DNS health checks
• B. CDN edge caching
• C. Health checks in the load balancer
• D. Backup tapes

Answer: (C)

Load balancer health checks monitor each backend and decide when to remove a node from rotation. The load balancer periodically probes every instance and evaluates the responses to determine if it’s healthy. If an instance fails enough checks, it’s marked unhealthy and traffic is steered away from it, so users aren’t routed to a failed service. When the instance recovers and health checks pass again, it can be brought back into rotation automatically. DNS-based health checks operate at the DNS layer and don’t dynamically exclude a specific server from an active pool, CDN edge caching doesn’t manage backend health, and backup tapes aren’t involved in live traffic routing.

Load balancer health checks monitor each backend and decide when to remove a node from rotation. The load balancer periodically probes every instance and evaluates the responses to determine if it’s healthy. If an instance fails enough checks, it’s marked unhealthy and traffic is steered away from it, so users aren’t routed to a failed service. When the instance recovers and health checks pass again, it can be brought back into rotation automatically. DNS-based health checks operate at the DNS layer and don’t dynamically exclude a specific server from an active pool, CDN edge caching doesn’t manage backend health, and backup tapes aren’t involved in live traffic routing.