Explanation:
The correct approach to managing an incident with an unhealthy node in a load balancer pool, following Google-recommended practices, involves ensuring minimal impact on users and maintaining service availability. Option A is correct because it emphasizes the importance of communication with the incident team, assessing the capacity of remaining nodes to handle the increased load before removing the unhealthy node, and ensuring new nodes are healthy before draining traffic from the unhealthy node. This approach minimizes risk by ensuring the service can handle the traffic without the unhealthy node before removing it. Option B is also correct as it similarly prioritizes communication, adds a new node to ensure capacity before removing the unhealthy node, and ensures the new node is healthy before serving traffic, thus maintaining service availability and minimizing user impact. Both options A and B adhere to best practices by focusing on communication, capacity planning, and ensuring node health before making changes to the load balancer pool.
Ultimate access to all questions.
No comments yet.
As the Operations Lead handling an incident with your service, you observe that a single node is returning 5xx errors for all requests while the service typically operates at 70% capacity. Customer support cases have also increased. To minimize user impact and adhere to Google-recommended practices, how should you proceed to remove the faulty node from the load balancer pool for isolation and investigation?
A
B
C
D