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

I'm believing that applying a custom "max-age" to individual "*.html" files ("individual pages") is the solution. (remove my duplicate response)

Lambda@Edge Function: Lambda@Edge allows you to run AWS Lambda functions globally, and it can be used to customize content delivered through CloudFront. In this scenario, you can create a Lambda@Edge function that modifies the Cache-Control header in the Viewer response to include the no-cache directive for specific pages. no-cache Directive: The no-cache directive indicates that the content must be revalidated with the origin server before serving it from the CloudFront cache. By adding this directive for specific pages, you can control the TTL on a per-page basis. This approach provides flexibility and allows you to override the default TTL settings for individual pages. Options A, B, and D do not offer the same level of flexibility or control for varying TTLs for individual pages.

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Expiration.html#expiration-individual-objects "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 Expires header field lets you specify an expiration date and time using the format specified in RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1 Section 3.3.1, Full Date, for example: Sat, 27 Jun 2015 23:59:59 GMT"

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Expiration.html

I'm believing that applying a custom "max-age" to individual "*.html" files ("individual pages") is the solution.