Free Google Professional Cloud Network Engineer Actual Exam Questions - Question 5 Discussion
objects have been successfully cached. Now you want to make sure that one of the two objects will
not be cached anymore, and will always be served to the internet directly from the origin.
What should you do?
Makes sense to use headers to control caching, so D sounds right.
A, because if the object isn't public, Cloud CDN won't cache or serve it.
Guessing D here too. Cache-Control headers usually control CDN caching, so setting it to private and invalidating makes sense to stop caching without messing with access permissions.
I'm wondering about A though—if the object isn’t publicly shared, would Cloud CDN even cache it? Maybe keeping it private could stop caching without messing with headers?
Maybe D is right because Cache-Control headers are key for telling CDNs how to cache content. Adding “private” to that object’s metadata should prevent it from being cached. Plus, invalidating the existing cache ensures the old version gets removed. Options A and B don’t directly control caching behavior, and C lifecycle rules manage object expiration or deletion, not caching. So, D fits best for controlling CDN cache on a per-object basis.
This one’s a bit tricky. I think D makes the most sense since Cache-Control headers usually determine how caching works. Adding “private” should stop CDN caching that object, and invalidating the old cache clears it from CDN. But not 100% sure if that’s all or if you need to do more in Cloud CDN settings. Anyone else stuck on this?