Google Exam Associate-Cloud-Engineer Topic 1 Question 80 Discussion

Actual exam question for Google's Google Associate Cloud Engineer exam

Question #: 80
Topic #: 1

[All Google 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?

AEnable retention policies on the bucket, and use Cloud Scheduler to invoke a Cloud Function to move or delete your documents based on their metadata.

BEnable 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.

CEnable 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.

DEnable 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.

Show Suggested Answer

Suggested Answer: B

by Judy at Apr 21, 2024, 10:12 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Beckie

4 months ago

I think enabling retention policies and using lifecycle rules to manage storage classes and versions would be a comprehensive solution.

upvoted 0 times

...

Lezlie

5 months ago

That's true, object versioning could be useful for tracking revisions. Maybe a combination of both would be ideal.

upvoted 0 times

...

Delmy

5 months ago

But wouldn't enabling object versioning be a better option for keeping track of revisions?

upvoted 0 times

...

Beckie

5 months ago

I agree, it seems like the most efficient way to meet the storage requirements.

upvoted 0 times

...

Lezlie

5 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

...

Pearlene

6 months ago

That also sounds like a good option to follow Google-recommended practices.

upvoted 0 times

...

Tequila

6 months ago

I would go with enabling object versioning and using Cloud Scheduler to move or delete documents based on metadata.

upvoted 0 times

...

Cyril

6 months ago

That could work too. We could set the number of versions to keep as well.

upvoted 0 times

...

Pearlene

6 months ago

But what about using lifecycle rules to change storage classes and delete old files?

upvoted 0 times

...

Cyril

6 months ago

I think we should enable retention policies on the bucket and use Cloud Scheduler to move or delete documents.

upvoted 0 times

Luther

5 months ago

Agreed, enabling retention policies and using Cloud Scheduler is the way to go.

upvoted 0 times

...

Shakira

5 months ago

Let's set up the Cloud Function to handle the document movements efficiently.

upvoted 0 times

...

Adelle

5 months ago

Great idea, let's go with enabling retention policies and using Cloud Scheduler.

upvoted 0 times

...

Mitzie

6 months ago

We can also use lifecycle rules to ensure old files are moved to lower cost storage tiers.

upvoted 0 times

...

Muriel

6 months ago

I think that option will help us minimize our operational costs as well.

upvoted 0 times

...

Izetta

6 months ago

I agree, that seems like the best option to meet our storage requirements.

upvoted 0 times

...

Alecia

6 months ago

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.

upvoted 0 times

...