Question

A media company serves large static video thumbnails and JavaScript bundles from a global external HTTP(S) Load Balancer backed by a Cloud Storage bucket. Monitoring shows high origin egress costs and elevated tail latency for users in distant regions. Cloud CDN is enabled, but the cache hit ratio is only 22%. Investigation reveals the origin responses include 'Cache-Control: no-store' on many objects and that unique query string parameters (used for analytics tracking) are appended to nearly every asset URL. What is the MOST effective way to reduce origin egress cost and improve latency?

Accepted Answer

Set appropriate 'Cache-Control: public, max-age' headers on cacheable objects and configure the Cloud CDN cache key policy to exclude the analytics query string parameters.

Answer

Increase the Cloud Storage bucket's storage class to Standard in multiple regions and add more backend buckets to the load balancer.

Answer

Enable Cloud CDN negative caching and raise the default TTL to the maximum value regardless of the origin's Cache-Control headers.

Answer

Switch the load balancer to a regional external load balancer closer to the majority of users to shorten the network path.