A company hosts a static website on Amazon S3. An Amazon CloudFront distribution presents this site to global users. The company uses the Managed-CachingDisabled CloudFront cache policy. The company's

Question

Options

• AAdd a Cache-Control header field with max-age=0 to the S3 object.
• BChange the CloudFront cache policy to Managed-CachingOptimized.
• CDisable bucket versioning in the S3 bucket configuration.
• DEnable content compression in the CloudFront configuration.

• A
  82% (23)
• B
  4% (1)
• C
  4% (1)
• D
  11% (3)

Explanation

With the Managed-CachingDisabled policy, CloudFront is configured to minimize edge caching, so the remaining caching behavior users experience often comes from browser (client-side) caching. If users refresh and still see old content, it typically indicates the browser is allowed to reuse a cached copy without revalidating. The correct fix is to control client caching using HTTP response headers on the S3 object. Adding a Cache-Control: max-age=0 header instructs browsers that the object becomes stale immediately and should be revalidated on subsequent requests (often resulting in conditional requests using If-Modified-Since or ETag behavior). This preserves correctness--users will fetch or revalidate the latest file--without requiring heavier operational actions like frequent CloudFront invalidations or changing to an optimized caching policy that may increase edge caching.

No community discussion yet for this question.