Resolve Load Balancer Health Check Firewall Rule

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An organization deploys an external Application Load Balancer that routes incoming user traffic to a Managed Instance Group (MIG) of proxy instances in a custom VPC network. The proxy instances forward requests to backend services across hybrid connectivity.

During deployment verification, users receive 502 Bad Gateway errors when accessing the load balancer public IP. In the Google Cloud console, the backend proxy instances are reported as UNHEALTHY by the load balancer's HTTP health check on port 8080. After connecting via SSH to one of the proxy VMs, you verify that the proxy service is actively running and listening on 0.0.0.0:8080.

Which action should you take to resolve the health check failure?

Create an egress VPC firewall rule targeting the proxy instances that allows TCP traffic to destination IP range 0.0.0.0/0 on port 8080.

Configure a Cloud DNS private managed zone with PTR resource records mapping the proxy VM private IP addresses to the load balancer forwarding rule VIP.

Enable custom route exchange on the VPC Network Peering connection to export and import dynamic health check routes.

Create an ingress VPC firewall rule targeting the proxy instances that allows TCP traffic on port 8080 from the source IP ranges 35.191.0.0/16 and 130.211.0.0/22.

Professional Cloud DevOps Engineer

Resolve Load Balancer Health Check Firewall Rule

Related questions