Question

Your company runs a single web property behind a global external Application Load Balancer. The frontend serves under one hostname, www.example.com. Requests to paths starting with /api/ must be routed to a backend service backed by a Kubernetes NEG cluster, requests to /static/ must go to a Cloud Storage backend bucket, and all other requests must go to a default backend service running the main web app. All three backends already exist and pass health checks. What is the correct way to implement this routing on the load balancer?

Accepted Answer

Create a URL map with a host rule for www.example.com and a path matcher containing path rules for /api/* and /static/*, plus a defaultService for all other traffic.

Answer

Create three separate forwarding rules, each with its own target proxy pointing at one of the backends, and use firewall rules to steer traffic by path.

Answer

Configure three backend services on a single backend service group and let the health checks determine which backend receives each path.

Answer

Create three global external Application Load Balancers sharing the same anycast IP, one per backend, and route by DNS.