PCNE Question 51

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose D3

  Choose D. Option D is the correct choice because setting the Cache-Control header to "private" for the specific object will instruct the CDN to bypass caching for that object. Additionally, invalidating previously cached copies ensures that the new caching instructions take effect for existing cached content.

• 1

  Option A (Ensure that the object you don't want to be cached anymore is not shared publicly) is not the best choice because CDN behavior is typically determined by Cache-Control headers rather than object permissions. Option B (Create a new storage bucket, move the object you don't want to be cached anymore inside it, and enable the private attribute) is not necessary and could be an unnecessary workaround. You can control caching behavior through Cache-Control headers without needing to create a new bucket. Option C (Add an appropriate lifecycle rule on the storage bucket containing the two objects) is not the most direct way to control caching behavior. Lifecycle rules are typically used for managing the lifecycle of objects (e.g., deleting old objects), not for controlling cache behavior.

• Chose D3

  option D, "Add a Cache-Control entry with value private to the metadata of the object you don't want to be cached anymore. Invalidate all the previously cached copies," is the correct answer because it adds a header to the object's metadata that tells the CDN not to cache the object and to always fetch it from the origin server. Invalidating previously cached copies is also important to ensure that users are not served stale or outdated content.