Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Exam Associate Cloud Engineer Topic 3 Question 78 Discussion

Actual exam question for Google's Associate Cloud Engineer exam
Question #: 78
Topic #: 3
[All Associate Cloud Engineer Questions]

You need to migrate invoice documents stored on-premises to Cloud Storage. The documents have the following storage requirements:

* Documents must be kept for five years.

* Up to five revisions of the same invoice document must be stored, to allow for corrections.

* Documents older than 365 days should be moved to lower cost storage tiers.

You want to follow Google-recommended practices to minimize your operational and development costs. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Jeanice at Mar 20, 2024, 06:23 PM

Limited Time Offer

25%

Off

Get Premium Associate Cloud Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Estrella
6 months ago
I prefer option D), enabling object versioning and using lifecycle conditions to manage document retention
upvoted 0 times
...
Annita
6 months ago
But what about option A), using Cloud Scheduler to move or delete documents based on metadata?
upvoted 0 times
...
Dick
6 months ago
I agree, enabling retention policies and using lifecycle rules seems like the best approach
upvoted 0 times
...
Benton
6 months ago
I think the answer is B)
upvoted 0 times
...
Michal
7 months ago
That's true. Using Cloud Scheduler to invoke a Cloud Functions instance based on metadata sounds efficient.
upvoted 0 times
...
Shawna
7 months ago
I believe enabling object versioning on the bucket could also be a good option.
upvoted 0 times
...
Belen
7 months ago
But what about using lifecycle rules to change the storage classes and set the number of versions?
upvoted 0 times
...
Michal
7 months ago
I think we should enable retention policies on the bucket and use Cloud Scheduler to move or delete documents based on metadata.
upvoted 0 times
...
Dortha
8 months ago
Hmm, I was considering option D at first. The object versioning seems useful, but you're right, the lifecycle rules in option B are probably the way to go. Gotta keep it efficient!
upvoted 0 times
...
Veda
8 months ago
I was also thinking option B. It's nice and comprehensive, and I like that it uses the built-in lifecycle rules instead of relying on external scheduling or functions. Keeps it simple.
upvoted 0 times
...
Annelle
8 months ago
Yeah, I agree with Vanda. Option B looks like the cleanest solution. Enabling retention policies, changing storage classes, and managing versions and deletions - that should handle everything we need.
upvoted 0 times
Roxane
7 months ago
Agreed. It's the Google-recommended practice to minimize our costs.
upvoted 0 times
...
Rana
7 months ago
Let's go with Option B then. It seems like the most comprehensive solution.
upvoted 0 times
...
Peggie
8 months ago
That's true. It covers all the storage requirements we have.
upvoted 0 times
...
Sherly
8 months ago
And we can set up lifecycle rules to move older documents to lower cost tiers.
upvoted 0 times
...
German
8 months ago
It also covers the requirement for storing up to five revisions of the same document.
upvoted 0 times
...
Tasia
8 months ago
Yes, I agree. Enabling retention policies and managing storage classes seems efficient.
upvoted 0 times
...
Fabiola
8 months ago
I think Option B is the way to go.
upvoted 0 times
...
...
Vanda
8 months ago
This is a tricky one. We need to make sure we're following Google's best practices to minimize costs. I'm leaning towards option B - it seems to cover all the requirements in a straightforward way.
upvoted 0 times
...

Save Cancel