A company has deployed an internal HTTP Load Balancer (ILB) in us-west1 within a Shared VPC. The host project contains the ILB's forwarding rule and the backend service. The backend instances are Compute Engine VMs running in a service project in us-east1. The health checks for the ILB are consistently failing with 'unhealthy' status. The firewall rules in the host project allow ingress from the Google Cloud health checker ranges (130.211.0.0/22 and 35.191.0.0/16) on TCP port 80 to all VMs in the VPC. The backend VMs are running a web server listening on port 80. What is the most likely cause of the health check failures?
Trap 1: The health checker firewall rule is not applied to the service…
Firewall rules in the host project apply to all VMs in the VPC, including those in service projects.
Trap 2: The backend VMs are not in the same project as the ILB.
Shared VPC allows backend VMs in different service projects; this is not an issue.
Trap 3: The backend VMs do not have the correct IAM permissions for the ILB.
IAM permissions are not required for backends to respond to health checks.
- A
The ILB's forwarding rule and backends are in different regions.
ILB requires backends to be in the same region as the forwarding rule; otherwise health checks fail.
- B
The health checker firewall rule is not applied to the service project.
Why wrong: Firewall rules in the host project apply to all VMs in the VPC, including those in service projects.
- C
The backend VMs are not in the same project as the ILB.
Why wrong: Shared VPC allows backend VMs in different service projects; this is not an issue.
- D
The backend VMs do not have the correct IAM permissions for the ILB.
Why wrong: IAM permissions are not required for backends to respond to health checks.