Exam AWS Certified SysOps Administrator - Associate topic 1 question 99 discussion

A! You can control how long your files stay in a CloudFront cache before CloudFront forwards another request to your origin. Reducing the duration allows you to serve dynamic content. Increasing the duration means that your users get better performance because your files are more likely to be served directly from the edge cache. A longer duration also reduces the load on your origin. To change the cache duration for an individual file, you can configure your origin to add a Cache-Control header with the max-age or s-maxage directive, or an Expires header to the file. https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Expiration.html

By adding a Cache-Control header with max-age=0 to the S3 object, you instruct CloudFront to revalidate the content on every request. When a user refreshes the page, CloudFront checks with S3 to ensure it has the latest version of the file. This approach ensures that users receive the most up-to-date content.

I think this question is wrong. By having the cache policy set to Managed-CachingDisabled all files will be fetched every time. This is also true of A if we have Managed-CachingOptimized. The answer is probably A but it shouldn't make a difference in this case.

link in the comments section states: The Cache-Control max-age directive lets you specify how long (in seconds) that you want an object to remain in the cache before CloudFront gets the object again from the origin server. The minimum expiration time CloudFront supports is 0 seconds. The maximum value is 100 years. And the company continue using the Managed- CachingDisabled CloudFront cache policy.

You should disable Cache in Browser with Cache-Control: max-age=0.

aaaaaaaa

Would it not be B since Caching is already Disabled?

A is the answer.