Deal of The Day! 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 Associate Cloud Engineer Exam - Topic 3 Question 78 Discussion

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?
B) Enable retention policies on the bucket, use lifecycle rules to change the storage classes of the objects, set the number of versions, and delete old files.
A) Enable retention policies on the bucket, and use Cloud Scheduler to invoke a Cloud Function to move or delete your documents based on their metadata.
C) Enable object versioning on the bucket, and use Cloud Scheduler to invoke a Cloud Functions instance to move or delete your documents based on their metadata.
D) Enable object versioning on the bucket, use lifecycle conditions to change the storage class of the objects, set the number of versions, and delete old files.

Google Associate Cloud Engineer Exam - 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:

0/2000 characters
Submit Cancel
Tyisha
9 months ago
Isn't there a risk of losing documents with option A? Just a thought.
upvoted 0 times
...
Quentin
10 months ago
I think D is better, it has more control over versions.
upvoted 0 times
...
Anjelica
10 months ago
Wait, can you really use lifecycle rules for versioning? Sounds tricky.
upvoted 0 times
...
Camellia
10 months ago
I agree, B covers all the requirements nicely!
upvoted 0 times
...
Mertie
10 months ago
Option B seems like the best choice for this scenario.
upvoted 0 times
...
Daniel
10 months ago
I believe option B is the most straightforward since it covers retention and versioning without needing extra functions. But I could be wrong!
upvoted 0 times
...
Blondell
11 months ago
I'm a bit confused about whether we should use Cloud Scheduler or just rely on lifecycle rules. I thought option A might work, but it seems more complicated.
upvoted 0 times
...
Vanesa
11 months ago
I remember practicing a similar question where we had to manage document versions. I feel like option D might be the right approach since it mentions both versioning and lifecycle conditions.
upvoted 0 times
...
Linsey
11 months ago
I think we need to focus on the retention policies and lifecycle rules, but I'm not sure if option B is the best choice.
upvoted 0 times
...
Luis
11 months ago
This seems straightforward, but I want to double-check the Google-recommended practices they mentioned. I'll need to make sure my solution aligns with their best practices.
upvoted 0 times
...
Malcolm
11 months ago
Okay, the key things I need to focus on are the retention policy, version control, and storage tiering. I think option B looks like the best approach to meet all those requirements.
upvoted 0 times
...
Georgene
11 months ago
Hmm, I'm a bit confused about the storage tier requirements. I'll need to read through the question carefully to make sure I understand all the details.
upvoted 0 times
...
Cyndy
11 months ago
This looks like a pretty straightforward Cloud Storage management question. I think I can handle this one.
upvoted 0 times
...
Maybelle
11 months ago
I'm feeling pretty confident about this one. The question is giving us all the information we need to set up the appropriate Cloud Storage policies and lifecycle rules.
upvoted 0 times
...
Laquita
11 months ago
Whoa, this is a tough one. I'm a little confused, but I'll give it my best shot and try to apply what I've learned in class.
upvoted 0 times
...
Kirk
11 months ago
This question seems straightforward, I think I can handle it.
upvoted 0 times
...
Estrella
2 years ago
I prefer option D), enabling object versioning and using lifecycle conditions to manage document retention
upvoted 0 times
...
Annita
2 years ago
But what about option A), using Cloud Scheduler to move or delete documents based on metadata?
upvoted 0 times
...
Dick
2 years ago
I agree, enabling retention policies and using lifecycle rules seems like the best approach
upvoted 0 times
...
Benton
2 years ago
I think the answer is B)
upvoted 0 times
...
Michal
2 years ago
That's true. Using Cloud Scheduler to invoke a Cloud Functions instance based on metadata sounds efficient.
upvoted 0 times
...
Shawna
2 years ago
I believe enabling object versioning on the bucket could also be a good option.
upvoted 0 times
...
Belen
2 years ago
But what about using lifecycle rules to change the storage classes and set the number of versions?
upvoted 0 times
...
Michal
2 years 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
2 years 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
2 years 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
2 years 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
2 years ago
Agreed. It's the Google-recommended practice to minimize our costs.
upvoted 0 times
...
Rana
2 years ago
Let's go with Option B then. It seems like the most comprehensive solution.
upvoted 0 times
...
Peggie
2 years ago
That's true. It covers all the storage requirements we have.
upvoted 0 times
...
Sherly
2 years ago
And we can set up lifecycle rules to move older documents to lower cost tiers.
upvoted 0 times
...
German
2 years ago
It also covers the requirement for storing up to five revisions of the same document.
upvoted 0 times
...
Tasia
2 years ago
Yes, I agree. Enabling retention policies and managing storage classes seems efficient.
upvoted 0 times
...
Fabiola
2 years ago
I think Option B is the way to go.
upvoted 0 times
...
...
Vanda
2 years 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