Google Professional Cloud Network Engineer Question 515
Single answerGoogle Cloud PlatformYour organization is using Cloud CDN to serve static content for a global web application. After deploying updated versions of static files, you notice that users are still receiving the old content from the cache. What is the best way to invalidate this outdated cached content across all edge locations?
- A
Use the Cloud CDN Cache Purge feature to explicitly invalidate the specific cached objects.
- B
Update the TTL (time-to-live) settings in the Cloud CDN configuration to force immediate cache expiration.
- C
Rename the updated files and update references in your web application to point to the new file names.
- D
Restart the Cloud CDN service to clear all cached content.
Show answer and explanation
Correct answer: A
Explanation
The Cloud CDN Cache Purge feature is the correct and most efficient way to invalidate outdated content across all edge locations. It allows you to target specific objects or entire caches for invalidation, ensuring users get the updated content without waiting for TTL expiration or making unnecessary changes to file names or configurations.
- A. Correct.
This is the correct method to invalidate outdated cached content in Cloud CDN. The Cache Purge feature allows you to explicitly purge specific cached files or all files with minimal disruption.
- B. Incorrect.
Updating the TTL does not immediately invalidate cached content. Cached content will still serve until the existing TTL expires naturally.
- C. Incorrect.
Renaming files can work as a workaround, but it requires updating all references in your application, which can be time-consuming and error-prone. It is not the most efficient or recommended approach.
- D. Incorrect.
Cloud CDN does not provide a 'restart' feature to clear cached content. Additionally, this is not a valid or recommended method to handle cache invalidation.