A company hosts a static website on Amazon S3.

Comprehensive and Detailed Explanation From Exact Extract of AWS CloudOps Documents:

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.

Option B can worsen the issue by increasing caching if object headers permit it. Option C is unrelated; versioning affects object history and recovery, not browser cache behavior. Option D affects payload size transfer (gzip/brotli), not cache freshness.