You need a secure, autoscaling website (scale based on instance CPU) and want to serve static content from Cloud Storage. Which components should distribute user traffic?

The External HTTP(S) Load Balancer is ideal for internet-facing web applications, providing global distribution, DDoS protection, and SSL termination. A managed SSL certificate simplifies HTTPS configuration. The URL map allows routing specific paths (e.g., /static/) directly to a Cloud Storage backend bucket, efficiently serving static content without involving compute instances. This setup also supports autoscaling based on CPU for dynamic content served by backend instances. External Network Load Balancers operate at Layer 4 and do not handle HTTP routing or SSL termination, making them unsuitable for directly serving static content from Cloud Storage or managing HTTP traffic. Internal HTTP(S) Load Balancers are for internal traffic within a VPC and not for public-facing websites. Installing HTTPS certificates on instances is less efficient and more complex than using a load balancer's managed SSL certificate, and it doesn't leverage the direct Cloud Storage integration.