You need to design a solution for global load balancing based on the URL path being requested. You need to ensure operations reliability and end-to-end in- transit encryption based on Google best practices. What should you do?

An HTTPS load balancer with URL Maps is the correct choice because it directly supports global load balancing based on URL paths and provides end-to-end in-transit encryption. HTTPS load balancers inherently handle SSL termination and re-encryption to backends, ensuring data is encrypted throughout its journey. URL Maps allow for sophisticated routing decisions based on the requested URL path, fulfilling the specific requirement. "Create a cross-region load balancer with URL Maps" is too generic; while cross-region is implied by global, it doesn't specify the HTTPS protocol needed for encryption. "Create appropriate instance groups and instances. Configure SSL proxy load balancing" is incomplete; SSL proxy load balancing is for specific TCP/SSL traffic, not HTTP/S path-based routing, and doesn't specify the global aspect or URL Maps. "Create a global forwarding rule. Configure SSL proxy load balancing" also misses the mark; a global forwarding rule is a component, but SSL proxy load balancing is not appropriate for HTTP/S path-based routing.