How to Automatically Downgrade Cloud Storage Objects to Coldline?

PCSE By islever Editorial Last updated

Short answer

D Define a lifecycle policy JSON with a SetStorageClass action targeting COLDLINE, an age condition of 365 days, and matchStorageClass set to STANDARD.

Question

You are managing data in your organization's Cloud Storage buckets and are required to retain objects. To reduce storage costs, you must automatically downgrade the storage class of objects older than 365 days to Coldline storage. What should you do?
  1. Use Cloud Asset Inventory to generate a report of the configuration of all storage buckets. Examine the Lifecycle management policy settings and ensure that they are set correctly.
  2. Set up a CloudRun Job with Cloud Scheduler to execute a script that searches for and removes flies older than 365 days from your Cloud Storage.
  3. Enable the Autoclass feature to manage all aspects of bucket storage classes.
  4. Define a lifecycle policy JSON with an action on SetStorageClass to COLDLINE with an age condition of 365 and matchStorageClass STANDARD. Correct Answer

Key Takeaways

Tests precise configuration of Cloud Storage lifecycle rules, with the common trap being confusion between Autoclass automation and explicit age-based policy definitions.

Google Cloud Storage lifecycle policies automate storage class transitions to optimize costs. This page establishes that configuring a JSON lifecycle rule with age conditions and SetStorageClass actions is the correct approach.

Common mistake: Option C (Autoclass) is often chosen incorrectly because it also manages storage classes automatically, but it lacks the explicit age-based targeting required by this scenario.

Expert Analysis

Why the Answer Is Correct

Google Cloud Storage provides native lifecycle management to automate data tiering based on predefined conditions. Option D correctly specifies a JSON lifecycle rule that triggers a SetStorageClass action to COLDLINE when objects exceed a 365-day age threshold. Including matchStorageClass STANDARD ensures the rule only targets relevant objects, preventing unnecessary processing. This aligns exactly with vendor documentation for cost-optimized data retention.

Why the Other Options Are Wrong

Option A relies on Cloud Asset Inventory, which is strictly for auditing and reporting existing configurations rather than automating transitions. Option B proposes deleting files via Cloud Run, which directly violates the explicit requirement to retain all objects. Option C enables Autoclass, which dynamically shifts data based on access frequency rather than fixed calendar ages, making it unsuitable for precise 365-day downgrade mandates.

Community Comment Notes

Learners consistently validated the JSON structure and parameter logic behind the correct choice. As BPzen explained, matching the current storage class prevents redundant operations on already-downgraded files. Multiple contributors confirmed that explicit age conditions paired with SetStorageClass are the standard exam pattern for this scenario. One user simply verified the option while others emphasized the importance of reading retention constraints carefully.

Official Reference

https://cloud.google.com/storage/docs/json_api/v1/objects#lifecycle

This link opens the official vendor documentation in a new tab.

Exam Strategy

When tackling storage optimization questions, distinguish between access-driven features like Autoclass and time-driven rules like Lifecycle policies. Always verify whether the scenario demands exact age thresholds or flexible access patterns before selecting your automation method.

Frequently Asked Questions

Why not use Autoclass instead of a lifecycle policy?

Autoclass adjusts storage classes based on access patterns rather than fixed age rules, so it cannot guarantee objects move to Coldline exactly after 365 days.

Does the matchStorageClass parameter prevent errors?

Yes, it ensures the rule only applies to objects currently in STANDARD storage, avoiding redundant operations on already-downgraded or archived files.

More PCSE FAQ →

Community Votes

D
100%

100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. BPzen 👍 1 Answered D
    Create a lifecycle policy JSON: Specify an action (SetStorageClass) to move objects to COLDLINE storage. Include a condition (age) to apply the policy to objects older than 365 days. Use the matchStorageClass parameter to apply the policy only to objects currently in STANDARD storage, ensuring that objects already in lower-cost classes (e.g., COLDLINE or ARCHIVE) are not unnecessarily moved.
  2. Pime13 👍 1 Answered D
    D. Define a lifecycle policy JSON with an action on SetStorageClass to COLDLINE with an age condition of 365 and matchStorageClass STANDARD.
  3. brunolopes07 👍 1
    I think D is correct.
  4. 1e22522 👍 1 Answered D
    its D i think

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

How to Implement TLS Interception for On-Premise Traffic in GCP

S-grade

How to Secure Vertex AI Training Jobs with Regional CMEK?

S-grade

How to Alert on Suspicious Outbound Traffic Using Threat Intelligence?

S-grade

How to Securely Host Databases Without Direct Internet Access?

S-grade

← Back to PCSE Study Guide