A streaming app stores language-specific audio/video in paths like /fr/video, /en/audio, etc. Use URL maps to route audio and video to separate storage backends and minimize operational overhead. Which approach do you recommend?

Rearranging directories to /video/ and /audio/ allows for simple, explicit path rules in the URL map. This minimizes operational overhead because the rules are straightforward and easy to manage, directly mapping to distinct storage backends. The option to rearrange directories and create DNS hostnames adds unnecessary complexity and operational overhead; DNS is for host resolution, not path-based routing within a single service. Keeping the directory structure and using regex path rules like \/[a-z]{2}\/video would work but introduces more complexity and potential for errors compared to simple path prefixes, increasing operational overhead. Keeping the directory structure and using path rules like //video is not a valid or standard URL map path matcher syntax for prefix matching in most cloud load balancers; typically acts as a wildcard for a single segment, not an arbitrary path prefix.