nerdexam
Google

ASSOCIATE-CLOUD-ENGINEER · Question #307

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

The correct answer is D. Enable object versioning on the bucket, use lifecycle conditions to change the storage class of the. Option D is correct because object versioning natively handles the requirement for storing up to five revisions of the same document, and lifecycle conditions (not custom code) can automatically transition objects to lower-cost storage classes (e.g., Nearline, Coldline, Archive)

Submitted by amina.ke· Mar 30, 2026Planning and configuring a cloud solution

Question

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?

Options

  • AEnable retention policies on the bucket, and use Cloud Scheduler to invoke a Cloud Function to
  • BEnable retention policies on the bucket, use lifecycle rules to change the storage classes of the
  • CEnable object versioning on the bucket, and use Cloud Scheduler to invoke a Cloud Functions
  • DEnable object versioning on the bucket, use lifecycle conditions to change the storage class of the

How the community answered

(25 responses)
  • A
    4% (1)
  • B
    8% (2)
  • C
    24% (6)
  • D
    64% (16)

Explanation

Option D is correct because object versioning natively handles the requirement for storing up to five revisions of the same document, and lifecycle conditions (not custom code) can automatically transition objects to lower-cost storage classes (e.g., Nearline, Coldline, Archive) after 365 days - all without any custom development, which directly satisfies the "minimize operational and development costs" constraint.

Options A and C are wrong for the same reason: both rely on Cloud Scheduler + Cloud Functions to manage storage tier transitions. This introduces custom code, added operational overhead, and higher costs when native lifecycle rules can accomplish the same thing automatically.

Option B is wrong because retention policies and object versioning serve different purposes. Retention policies prevent objects from being deleted before a set period - they do not create or manage multiple revisions of the same file. Only object versioning stores multiple versions (revisions) of a document as it changes.

Memory tip: Think of it as two separate needs requiring two separate native GCS features - Revisions → Versioning, Cost tiering → Lifecycle conditions. Whenever an answer swaps either of these for a Cloud Function, it's adding unnecessary complexity and is almost certainly wrong on a Google Cloud exam.

Topics

#Cloud Storage#Object Versioning#Lifecycle Management#Cost Optimization

Community Discussion

No community discussion yet for this question.

Full ASSOCIATE-CLOUD-ENGINEER Practice