Controlling Cloud Storage Costs with Lifecycle Management
Short answer
B Configure an Object Lifecycle Management rule to transition objects older than two years to the Archive storage class and eventually delete them after seven years.
Question
Key Takeaways
The question tests your ability to choose automated lifecycle management over manual scripts or broader auto-classification when specific age-based transition and deletion rules are required.
Learn how to reduce Cloud Storage costs for historical data using Object Lifecycle Management rules to transition data to Archive and enforce retention policies.
Common mistake: Choosing Autoclass (C) because it reduces costs automatically. While useful, Autoclass is based on access frequency, not strict age thresholds like 'older than two years,' making OLM the more precise answer for the specified requirements.
Expert Analysis
The scenario requires managing a Cloud Storage data lake with specific retention and access patterns: historical data is rarely accessed after two years, but all data must be retained for up to seven years. The primary goal is cost control for this historical bucket.
The most appropriate solution is to use Object Lifecycle Management (OLM) rules. OLM allows you to automate the transition of objects between storage classes based on age or conditions. In this case, transitioning objects older than two years to a lower-cost class like Archive (which has a minimum retention period that fits the 7-year requirement) addresses the cost concern while ensuring compliance with the 7-year retention policy. Option B correctly describes using OLM for both transition and eventual deletion.
Option A suggests manual scripting, which is less reliable and harder to maintain than native OLM features. Option C, Autoclass, automatically moves data based on access patterns but may not provide the granular control over the 2-year threshold or the explicit move to Archive specifically as required by the question's emphasis on "historical" data management strategies often tested in exams; furthermore, Autoclass transitions to Coldline/Archive but doesn't inherently handle the specific "older than 2 years" rule as explicitly as a custom OLM rule might be interpreted in exam contexts focusing on lifecycle policies. However, the key distinction is often between manual vs automated (OLM). Between B and C, B is more specific to the stated constraints (2 years to Archive, delete after 7). Autoclass is dynamic; OLM is rule-based. Given the explicit timeframes, OLM is the precise tool.
Option D involves replication, which increases costs rather than reducing them for the primary bucket, and doesn't solve the tiering issue within the source bucket.
Therefore, configuring an Object Lifecycle Management rule is the standard best practice for automating storage class transitions and deletions based on object age.
Exam Strategy
When questions specify exact time thresholds for data access changes (e.g., 'after 2 years') and retention limits (e.g., 'delete after 7 years'), prioritize Object Lifecycle Management rules. They offer deterministic, automated behavior compared to Autoclass (which is heuristic-based) or manual scripts (which are error-prone). Always check if the chosen method satisfies both the transition AND deletion constraints.
Frequently Asked Questions
Why not use Autoclass instead of Lifecycle Management?
Can I use Compute Engine scripts for lifecycle management?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 2 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 2
-
AwesomeGCP 👍 1 Answered BB. Configure an Object Lifecycle Management rule to transition objects older than two years to the Archive storage class and eventually delete them after seven years.
-
Mohamed_Tareq 👍 1 Answered BLife cycle managment policy will be the right option as we need to transfer data between different tiers or even to delete it so B is the right option
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.