1
Design High-Performing Architectures
hard
Based on the exhibit, a static asset distribution site uses Amazon CloudFront with an S3 origin. The assets are versioned by filename, but the cache hit ratio remains low after each release. Which CloudFront change is the best way to improve cache reuse without changing the origin objects?
Exhibit
CloudFront distribution settings excerpt: - Cache policy: custom - Headers included in cache key: Authorization, CloudFront-Viewer-Country - Query strings included in cache key: all - Cookies included in cache key: none Origin request sample: GET /app.8f3a2c1.js?v=20260428 HTTP/1.1 Host: d123.cloudfront.net Authorization: Bearer eyJhbGciOi... User-Agent: Mozilla/5.0 CloudFront analytics: - CacheHitRate: 18% - OriginFetches: spike immediately after each deploy - Origin bytes out: high for unchanged JS and CSS files