exam questions

Exam Professional Cloud Network Engineer All Questions

View all questions & answers for the Professional Cloud Network Engineer exam

Exam Professional Cloud Network Engineer topic 1 question 51 discussion

Actual exam question from Google's Professional Cloud Network Engineer
Question #: 51
Topic #: 1
[All Professional Cloud Network Engineer Questions]

You have a storage bucket that contains two objects. Cloud CDN is enabled on the bucket, and both 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?

  • A. Ensure that the object you don't want to be cached anymore is not shared publicly.
  • B. Create a new storage bucket, and move the object you don't want to be checked anymore inside it. Then edit the bucket setting and enable the private attribute.
  • C. Add an appropriate lifecycle rule on the storage bucket containing the two objects.
  • 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.
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
spidrfong
Highly Voted 3 years, 11 months ago
D is correct https://cloud.google.com/cdn/docs/caching
upvoted 16 times
...
xhilmi
Most Recent 10 months, 2 weeks ago
Selected Answer: D
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.
upvoted 2 times
xhilmi
10 months, 2 weeks ago
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.
upvoted 1 times
...
...
Komal697
1 year, 7 months ago
Selected Answer: D
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.
upvoted 3 times
Komal697
1 year, 7 months ago
Option A, "Ensure that the object you don't want to be cached anymore is not shared publicly," is not the correct answer because public sharing is not related to caching. Public sharing only controls whether the object is accessible by users who have the link or if it's accessible to everyone on the internet. Option B, "Create a new storage bucket, and move the object you don't want to be checked anymore inside it. Then edit the bucket setting and enable the private attribute," is not the correct answer because creating a new bucket would cause unnecessary complexity and may not be an ideal solution for a large number of objects or frequent changes to objects. Option C, "Add an appropriate lifecycle rule on the storage bucket containing the two objects," is not the correct answer because lifecycle rules control the lifecycle of objects, such as deletion or archiving, but not caching.
upvoted 1 times
...
...
Ben756
1 year, 7 months ago
Selected Answer: D
the best option for making sure that one of the two objects will not be cached anymore is 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.
upvoted 1 times
...
spoxman
1 year, 9 months ago
Selected Answer: D
D if correct
upvoted 2 times
...
pk349
1 year, 9 months ago
• 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.
upvoted 1 times
...
AzureDP900
1 year, 11 months ago
D is right
upvoted 2 times
...
small1_small2
2 years, 2 months ago
Selected Answer: D
Answer is D, stated here https://cloud.google.com/cdn/docs/caching#preventing-caching
upvoted 4 times
...
kumarp6
2 years, 10 months ago
Answer is : D
upvoted 3 times
...
kumarp6
2 years, 10 months ago
Answer is : D
upvoted 1 times
...
Vidyasagar
3 years, 7 months ago
D is correct
upvoted 3 times
...
cesar7816
3 years, 10 months ago
Ans is D, Preventing caching Include a Cache-Control: private header in responses that should not be stored in Cloud CDN caches, or a Cache-Control: no-store header in responses that should not be stored in any cache, even a web browser's cache.
upvoted 3 times
...
[Removed]
3 years, 11 months ago
Ans - D
upvoted 1 times
...
lukedj87
3 years, 11 months ago
Should be D
upvoted 3 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago