Your application stores files on Cloud Storage by using the Standard Storage class. The application only requires access to files created in the last 30 days. You want to automatically save costs on…

Question

Options

• ACreate an object lifecycle on the storage bucket to change the storage class to Archive Storage
• BCreate a cron job in Cloud Scheduler to call a Cloud Functions instance every day to delete files
• CCreate a retention policy on the storage bucket of 30 days, and lock the bucket by using a
• DEnable object versioning on the storage bucket and add lifecycle rules to expire non-current

• A
  71% (15)
• B
  14% (3)
• C
  5% (1)
• D
  10% (2)

Explanation

Option A is correct because Cloud Storage object lifecycle policies let you automatically transition objects to cheaper storage classes (like Archive) after a specified number of days - exactly what's needed to reduce costs on files older than 30 days without deleting them or disrupting access patterns.

Option B is wrong because it deletes files entirely rather than simply reducing their storage cost; the question asks to save costs, not destroy data. A cron job + Cloud Function also adds unnecessary operational complexity.

Option C is wrong because a retention policy with a bucket lock prevents deletion or modification of objects for compliance purposes - it's a data protection feature, not a cost optimization tool. Locking a bucket actually restricts your ability to manage objects.

Option D is wrong because object versioning tracks changes to objects over time and is used for recovery/auditability. Expiring non-current versions only reduces costs from versioned overwrites, not from aging original files that simply haven't been touched.

Memory tip: Think of lifecycle policies as "automatic downgrade rules" - when an object ages past your threshold, GCS silently moves it to a cheaper tier (Nearline → Coldline → Archive). Archive is the cheapest but has the highest retrieval cost, making it perfect for files you keep but rarely touch.

No community discussion yet for this question.