How to Automatically Downgrade Cloud Storage Objects to Coldline?
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?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
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.
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.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
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
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.