Examkin

Question

Difficulty: EasyIncident Management and Automated Alerting

Your organization runs a web application behind a Google Cloud HTTP(S) Load Balancer. You are setting up health checks and automated alerting to ensure operational reliability. If backend database queries experience transient latency, you want to avoid cascading service failures where healthy application instances are mistakenly marked as unhealthy. Which configuration strategy should you implement for the load balancer health checks?

  1. Configure health check probes to hit a dedicated, shallow endpoint that verifies web process responsiveness without querying deep database dependencies.Answer
  2. B
    Configure health check probes to execute full end-to-end database read queries on every interval to verify total application stack health.
  3. C
    Assign the primitive Owner IAM role to the automated monitoring service account to grant it full permission to inspect and reset backend instances.
  4. D
    Rely exclusively on standard IAM permissions without implementing VPC Service Controls to prevent unauthorized data exfiltration during incident response.

Answer

Configure health check probes to hit a dedicated, shallow endpoint that verifies web process responsiveness without querying deep database dependencies.
Shallow health checks verify that the application server process itself is listening and accepting traffic without testing downstream dependencies. This design prevents transient database latency from causing the load balancer to mistakenly mark healthy compute instances as failed, avoiding cascading outages.

Step-by-Step Solution

1
Analyze the operational reliability requirement
Identified the need to prevent false health check failures during transient database latency.
Deep health checks cause load balancers to mark healthy compute instances as failing when only the underlying database is slow, triggering cascading failures.
2
Select the appropriate health check design pattern
Use a shallow HTTP endpoint (e.g., /healthz) that tests local web process availability.
Shallow endpoints ensure the load balancer only routes traffic to active server instances without overloading downstream resources.

Key Concept

Shallow vs. Deep Health Checking in Load Balancing
Rate this question

Topics

Incident Management and Automated Alerting

More questions from this topic