Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
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?
Cloud DNS private managed zones provide internal domain name resolution within specified VPC networks, allowing VM instances to resolve fully qualified domain names (FQDNs) to internal IP addresses. PTR (Pointer) records are used for reverse DNS lookups, translating IP addresses back into domain names.
The backend proxy application required reverse DNS lookups to validate the hostnames of incoming client connections against a corporate internal directory service.
VPC Network Peering allows private RFC 1918 connectivity between two distinct VPC networks. Enabling the Import custom routes and Export custom routes flags allows custom static routes and dynamic BGP routes learned from Cloud Routers or on-premises gateways to propagate across peered VPC boundaries.
35.191.0.0/16 and 130.211.0.0/22) that are resolved natively within the VM's local VPC.The issue involved workload VMs in a peered VPC or Google Cloud VMware Engine private cloud failing to route traffic back to on-premises subnets advertised over Cloud Interconnect or Cloud VPN.
In Google Cloud VPC networks, load balancers utilize distributed health checking systems that generate probe traffic originating from specific, well-defined Google Cloud IP address blocks. For Application Load Balancers, the primary source IP ranges for health check probes are 35.191.0.0/16 and 130.211.0.0/22 (along with 209.85.152.0/22 and 209.85.204.0/22 in certain proxy configurations).
8080 from 35.191.0.0/16 and 130.211.0.0/22 permits the health check probers to connect to the listening proxy process on each VM.HEALTHY and begins forwarding external traffic.Because the proxy daemon is confirmed to be running and listening locally on port 8080, the root cause of the health check failure is the VPC firewall discarding incoming probe packets. Adding this rule directly addresses the connectivity blockage at the network layer.
Egress firewall rules control outbound network connections initiated by VM instances in a VPC network toward destinations inside or outside Google Cloud. By default, every VPC network contains an implied allow egress rule (priority 65535) that permits all outbound traffic to any destination unless explicitly overridden by a custom deny rule.
A strict custom hierarchical firewall policy had been implemented to block all outbound egress traffic from VM instances, preventing backend proxies from initiating outbound connections to remote upstream database or API servers.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated