What should the SysOps administrator do to refresh the cache with the new images in the MOST operationally efficient way?
Create a new CloudFront distribution that has the same origin. Set the default TTL to 1 minute (60 seconds). Switch Amazon Route 53 DNS records to use the new distribution.
Instruct the marketing team to upload the new images to a different location. When the new images are uploaded, update the website to locate the new images.
Issue a CloudFront invalidation request to immediately expire the new images from the marketing team’s update.
Update the existing CloudFront distribution to reconfigure the default TTL to 1 minute (60 seconds). During submission of the new configuration, include the flag to invalidate objects in the specified path.
Explanations:
Creating a new CloudFront distribution is unnecessary and inefficient for the purpose of refreshing cached content. The existing distribution can be invalidated to update the images without needing to change DNS records or create a new setup.
Instructing the marketing team to upload images to a different location adds unnecessary complexity. It requires changes to the website to point to a new location, which is not an efficient solution when existing images can be invalidated in the cache.
Issuing a CloudFront invalidation request is the most operationally efficient way to refresh the cache. This allows the new images to be served immediately without needing to change distribution settings or create a new distribution.
While updating the default TTL could help prevent future cache issues, it does not immediately address the current problem of stale images. The best practice is to use an invalidation request to refresh the cached images right away.
If I’m correct, the answer is:
Issue a CloudFront invalidation request to immediately expire the new images from the marketing team’s update.
I draft that the answer is:
Issue a CloudFront invalidation request to immediately expire the new images from the marketing team’s update.