Your company's logo is published as an image file across multiple websites that are hosted by your company. You have implemented Cloud CDN; however, you want to improve the performance of the cache…

Question

Options

• AConfigure custom cache keys for the backend service that holds the image file, and clear the Host
• BConfigure the default time to live (TTL) as 0 for the image file.
• CConfigure versioned URLs for each domain to serve users the image file before the cache entry
• DConfigure Cloud Storage as a custom origin backend to host the image file, and select multi-

• A
  72% (18)
• B
  4% (1)
• C
  8% (2)
• D
  16% (4)

Explanation

By default, Cloud CDN uses the full request URL including the Host header as part of its cache key. Because the same logo image is served from multiple different hostnames (different company websites), each hostname generates a separate cache entry for the same file - lowering the cache hit ratio. Configuring a custom cache key that excludes (clears) the Host header causes Cloud CDN to treat requests for the same path from any hostname as cache hits against a single shared entry, dramatically improving the cache hit ratio. Setting TTL to 0 (option B) or using versioned URLs (option C) would not address the multi-hostname problem. Using Cloud Storage as a custom origin (option D) is unrelated to cache key optimization.

No community discussion yet for this question.