Exam Associate Cloud Engineer All Questions

View all questions & answers for the Associate Cloud Engineer exam

Exam Associate Cloud Engineer topic 1 question 250 discussion

Actual exam question from Google's Associate Cloud Engineer

Question #: 250
Topic #: 1

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

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

Show Suggested Answer

Suggested Answer: D 🗳️

by shiowbah at Dec. 30, 2023, 6:53 a.m.

Comments

Submit Cancel

Cynthia2023

Highly Voted 11 months, 2 weeks ago

Selected Answer: D

- Object Versioning: Enabling object versioning on the Cloud Storage bucket allows you to store up to five revisions of the same invoice document. This satisfies the requirement for keeping multiple versions of each document for corrections. - Lifecycle Conditions: Google Cloud Storage allows you to define lifecycle conditions for objects within a bucket. These conditions can automatically change the storage class of objects when they meet certain criteria, such as age. After 365 days, you can automatically move documents to lower-cost storage classes like Nearline, Coldline, or Archive, which reduces storage costs while still retaining the data. - Version Management and Deletion: The lifecycle rules can also be configured to manage the number of object versions retained and to delete old versions or objects, ensuring compliance with the five-year retention requirement.

upvoted 7 times

Cynthia2023

11 months, 2 weeks ago

Why B is not correct: Lifecycle rules in Google Cloud Storage can be used to manage the deletion of old versions of objects. However, it's important to note that lifecycle rules alone do not set the number of versions to keep; they can only delete versions based on age or other criteria. Lifecycle rules in Google Cloud Storage do not have a direct setting to limit the number of object versions (like keeping only the last five versions). Object versioning in Google Cloud Storage keeps all versions of an object until they are explicitly deleted (either manually or through lifecycle rules).

upvoted 5 times

...

TanTran04

Most Recent 8 months, 3 weeks ago

Selected Answer: D

Follow D

upvoted 1 times

...

sukouto

9 months, 2 weeks ago

Selected Answer: B

I believe the answer is actually B, and D won't cut it. D does not address the need "Documents must be kept for five years." A retention policy is required, otherwise someone can just delete a document. Someone else suggested that you can't set object versioning with life cycle rules, but that's not quite true. https://cloud.google.com/storage/docs/lifecycle You can, but it does require object versioning to be enabled... So none of these answers are ideal, but I think the omission of setting a retention policy explicitly misses the first requirement stated.

upvoted 2 times

sukouto

9 months, 1 week ago

Upon further reading, it seems Retention Policies and Object Versioning are mutually exclusive, meaning B cannot cover the second requirement. https://cloud.google.com/storage/docs/object-versioning It's not explicitly stated, but it is implied that Object Versioning can prevent total deletion (i.e. deleting a live version of an object moves it to a non-current version). I guess the answer will have to be D

upvoted 5 times

...

JB28

11 months, 1 week ago

The correct answer is **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**. Here's why: - **Object versioning** allows you to keep up to five revisions of the same invoice document. - **Lifecycle conditions** can be used to automatically change the storage class of objects older than 365 days to a lower-cost storage tier. - You can also set the number of versions to keep and automatically delete old files, which helps to manage storage costs effectively. This approach aligns with Google-recommended practices and helps to minimize operational and development costs.

upvoted 4 times

...

Gocool28

11 months, 2 weeks ago

Obvious answer is D

upvoted 1 times

1826c27

4 months, 1 week ago

why not B mr Obvious? "Documents must be kept for five years." - how does D cover this requirement?

upvoted 1 times

...

KelvinToo

11 months, 3 weeks ago

Selected Answer: D

Per ChatGPT, Option D aligns with Google-recommended practices for managing objects in Cloud Storage, including versioning, lifecycle management, and cost optimization, making it the best choice for the given scenario.

upvoted 1 times

1826c27

4 months, 1 week ago

Per my grandma, Option A aligns with Google-recommended practices for managing objects in Cloud Storage, including versioning, lifecycle management, and cost optimization, making it the best choice for the given scenario.

upvoted 1 times

...

shiowbah

11 months, 3 weeks ago

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.

upvoted 1 times

...