CloudFront serves images and CSS.
Avoid splitting the cache for query strings that do not change the content.
Which setting is most appropriate?
Use a CloudFront cache policy that includes only required query strings, headers, and cookies in the cache key.
Detailed explanation
An overly varied key fragments the cache and lowers hit rate.
An overly varied key fragments the cache and lowers hit rate.
DNS TTL does not define the CloudFront cache key.
DNS TTL does not define the CloudFront cache key.
A focused cache key improves hit rate for equivalent content.
A focused cache key improves hit rate for equivalent content.
S3 lifecycle management is not a CloudFront cache policy.
S3 lifecycle management is not a CloudFront cache policy.
Check official documentation
Compare the following points with the official documentation.
CloudFront cache policiesの公式説明を確認する。
What to confirm
DNS TTLとCDNキャッシュキーの違いを説明できる。
Key points
- CloudFront cache policy
- Cache key
- Query string
Notes
- Environment: AWS公式SOA-C03試験ガイドとAWS公式ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Hit-rate trade-off
A narrower key increases reuse but must still include attributes that change the response.
DNS versus CDN
Route 53 TTL controls DNS caching; CloudFront policy controls edge-object selection.