Traffic to a global HTTP(S) load balancer reaches the frontend but none of the URL map path matchers match the Host and path in the request. Where will the request be routed?

When no host rule or path matcher in a Google Cloud HTTP(S) load balancer's URL map matches the incoming request's Host header and path, the load balancer routes the request to the backend service or backend bucket specified as the default in the URL map. This ensures that all requests are handled, even if they don't explicitly match a defined rule. Dropping the connection would result in a bad user experience and is not the default behavior. Routing to the "first backend listed" is incorrect because routing is based on matching rules, not arbitrary order. Cloud DNS is used for name resolution, not for fallback traffic routing within a load balancer.