An external HTTP(S) load balancer is a global, proxy-based load balancer that can distribute user traffic across multiple backend instances, regions, and services. It can also handle SSL termination and provide a managed SSL certificate for your domain name. A URL map is a configuration that defines how the load balancer routes requests to the appropriate backend based on the URL path. You can use a URL map to target requests for the static content to the Cloud Storage backend, which is a bucket that serves as a backend service for the load balancer. This way, you can enhance the performance of your website by storing and serving static content from Cloud Storage, while using compute instances for dynamic content.
The other options are not correct because they either do not provide the required security, performance, or scalability. Option A is not correct because an internal HTTP(S) load balancer is a regional, proxy-based load balancer that can only distribute traffic within a private network, not to the internet. Identity-Aware Proxy is a service that provides secure access to your applications and resources, but it is not a load balancer. Option B is not correct because an external network load balancer is a regional, pass-through load balancer that can only distribute traffic based on the IP protocol data, not the HTTP(S) headers or URL paths. Therefore, it cannot handle SSL termination, provide a managed SSL certificate, or target requests to the Cloud Storage backend. Option D is not correct because installing the HTTPS certificates on the instance adds complexity and maintenance overhead, and does not leverage the benefits of the managed SSL certificate provided by the load balancer.
Reference:
External HTTP(S) Load Balancing
URL maps overview
Setting up a load balancer with backend buckets
Managed SSL certificates