Housing authority application servers sit behind a load balancer. What configuration ensures citizens stop hitting a node that has failed its readiness probe?
Select an answer to reveal the explanation.
Short Explanation
You can think of health checks as a bouncer who stops sending residents to a closed service window. When a housing application node fails readiness, the load balancer should automatically remove it from the pool. Sticky sessions that persist through errors, wiki guesswork, and frozen pool membership leave people hitting broken servers.
Full Explanation
Housing authority application servers stay available to citizens when health checks automatically remove unhealthy nodes from the load-balancer pool. Readiness probes detect failed processes, bad deployments, or saturated instances, and the load balancer stops forwarding new requests to those nodes until they pass again. This closed loop makes a redundant pool useful in production rather than merely decorative. Sticky sessions forced to persist when a node returns HTTP 500s fail because affinity without health-based removal pins citizens to a broken backend, turning a partial outage into a persistent personal outage. Manual wiki updates listing servers operators believe are healthy fail as an operational control: wikis lag behind reality, are not enforced in the traffic path, and cannot react in seconds. Disabling pool membership changes so failed nodes remain active fails by design: it keeps bad nodes in rotation and defeats health-based load balancing. Exam caveat: health checks must match real application readiness, such as the application’s port and path, rather than only confirming that the host responds to ICMP; otherwise, broken application processes may keep receiving traffic. Sticky sessions may still be used for stateful applications, but must not override removal of failed nodes. Practical check: fail a housing node’s readiness endpoint and confirm the load balancer marks it down and shifts traffic; restore readiness and confirm it rejoins. Verify sticky settings do not direct citizens to down nodes, and that pool membership does not depend on wiki edits.