A static website is stored in an Amazon S3 bucket and delivered through a CloudFront distribution that has a default TTL of 86,400 seconds. After uploading new site files to S3, visitors still receive the previous content. The SysOps admin needs the updated site to appear for users immediately. What action accomplishes this?

The correct action is to submit an invalidation request for the outdated objects on the CloudFront distribution. CloudFront caches content at edge locations for the duration of its TTL (Time To Live). Even after new files are uploaded to S3, CloudFront continues serving the cached, older version until the TTL expires. An invalidation request forces CloudFront to remove the specified objects from its cache, prompting it to fetch the latest version from the origin (S3) on subsequent requests. Changing the DNS CNAME TTL would only affect how long DNS resolvers cache the CloudFront distribution's IP address, not the content cached by CloudFront itself. Provisioning a new CloudFront distribution is an overly complex and time-consuming solution for simply updating content. Modifying DNS to point directly to the S3 bucket would bypass CloudFront entirely, losing the benefits of CDN caching, security, and performance, and potentially exposing the S3 bucket publicly in a way that is not best practice for static site hosting.