Multiple ChoiceBeginner 45s
CDN cache invalidation for atomic deploys
You deploy a static site frequently and must avoid users mixing old HTML with new JS. Which practice is safest?
Options
- 1Content-hash filenames for assets and immutable cache headers, update HTML references
- 2Purging the entire CDN cache on every deploy while keeping asset URLs unversioned
- 3Setting a very long max-age on the HTML document so browsers cache it aggressively
- 4Serving every static asset directly from the origin with CDN caching fully disabled
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.