How to optimize Cloud Storage costs when retrieval must be free?
Your team is building a data lake platform on Google Cloud. As a part of the data foundation design, you are planning to store all the raw data in Cloud Storage. You are expecting to ingest approximately 25 GB of data a day and your billing department is worried about the increasing cost of storing old data. The current business requirements are: • The old data can be deleted anytime. • There is no predefined access pattern of the old data. • The old data should be available instantly when accessed. • There should not be any charges for data retrieval. What should you do to optimize for cost?
Community Votes
78% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests understanding of Autoclass's automatic storage-class transitions and its unique property of eliminating retrieval fees, a trap that leads candidates to choose lifecycle policies that incur retrieval costs.
When designing a cost-effective data lake on Google Cloud with no retrieval fees and instant access requirements, enabling Autoclass is the recommended solution. The community overwhelmingly supports Autoclass over manual lifecycle policies because it automatically optimizes storage classes while avoiding retrieval charges.
The most common wrong answer is B, which uses Object Lifecycle Management to move data to Nearline, Coldline, and Archive. While this reduces storage costs, those storage classes charge retrieval fees, directly violating the requirement of no retrieval charges.
Community Discussion (8 comments)
- Autoclass automatically moves objects between storage classes without impacting performance or availability, nor incurring retrieval costs. - It continuously optimizes storage costs based on access patterns without the need to set specific lifecycle management policies.
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option A is correct because enabling Autoclass on the bucket automatically moves objects to colder storage classes when they are not accessed, based on actual access patterns. As noted in a community comment, Autoclass "continuously optimizes storage costs based on access patterns without the need to set specific lifecycle management policies." It also guarantees no retrieval or early deletion charges, fully satisfying the business requirement of free retrieval. The official documentation confirms that Autoclass transitions objects to Coldline after 30 days of no access and to Archive after 90 days, while automatically promoting them back to Standard on subsequent access. This meets all constraints: old data can be deleted anytime, no predefined access pattern, instant availability, and no retrieval fees.
Why the Other Options Are Wrong
Options B, C, and D all rely on Object Lifecycle Management policies that explicitly transition data to storage classes such as Nearline, Coldline, and Archive. These classes charge retrieval fees per operation, which contradicts the explicit requirement that "there should not be any charges for data retrieval." Option B is the most commonly chosen incorrect answer because it uses reasonable transition timings, but it still ignores the retrieval fee constraint. Option C incorrectly swaps Coldline and Nearline, while Option D uses shorter durations and still incurs retrieval fees. Only Autoclass offers the same cost‑saving benefits without per‑retrieval charges.
Community Comment Notes
The community clearly favors Autoclass, with comments pointing to the official documentation and highlighting its no‑retrieval-charge property. One commenter states, "Autoclass is the correct way to handle all business cases," while another explicitly mentions "nor incurring retrieval costs." A dissenting commenter argued for Option B based purely on cost reduction, but overlooked the retrieval fee requirement—a key mistake. The most useful comments reinforce that Autoclass eliminates the need for manual lifecycle rules and automatically balances cost with performance and availability, making it the ideal choice for this scenario.
Official Reference
Exam Strategy
When a question includes the phrase 'no retrieval charges,' immediately eliminate any option that uses lifecycle policies to move objects to Nearline, Coldline, or Archive, because those storage classes charge retrieval fees. Instead, look for Autoclass, which is designed to automatically optimize storage costs without retrieval fees, and remember that Autoclass transitions based on access patterns, not predefined dates.