Cloud Storage Bucket Retention Policy for Data Compliance
Short answer
B Set a bucket retention policy to enforce a mandatory minimum retention period for all objects in the Cloud Storage bucket.
Question
Key Takeaways
The question tests the difference between storage classes (cost/access), versioning (history), and retention policies (mandatory deletion prevention). The trap is confusing 'Archive' storage with 'retention'.
Learn how to enforce a mandatory three-year data retention period in Google Cloud Storage using bucket retention policies for compliance and governance.
Common mistake: Candidates often choose C (Archive) because it implies long-term storage, but Archive is just a cheaper tier with higher retrieval costs; it does not prevent deletion. Others might choose D (Versioning), which preserves history but doesn't stop deletion of the latest version or old versions without additional locks.
Expert Analysis
Retention Policy: A bucket retention policy sets a mandatory minimum retention period for all objects in the bucket. This ensures that data cannot be deleted or overwritten until the specified duration (e.g., three years) has elapsed, directly satisfying the requirement to save data for at least three years.
Temporary Object Holds vs Retention Policies: Temporary object holds are per-object and manual. They do not enforce a global three-year rule automatically for historical data.
Storage Class vs Retention: Changing the storage class to Archive affects cost and access latency, not retention duration. Archive data can still be deleted before three years if no retention policy is set.
Object Versioning: Enabling object versioning keeps previous versions of objects but does not prevent deletion of the current version or old versions unless combined with other policies like WORM (Write Once Read Many) via retention policies.
Official Reference
https://cloud.google.com/storage/docs/bucket-lock
This link opens the official vendor documentation in a new tab.
Exam Strategy
When dealing with data compliance questions, distinguish between 'access tiers' (Standard, Nearline, Coldline, Archive) and 'retention rules' (Retention Policies, Object Holds). If the requirement mentions 'minimum time', 'cannot delete', or 'compliance', look for Retention Policies. If it mentions 'cheaper long-term storage', look for Archive/Nearline/Coldline. Always check if the requirement applies to the whole bucket (Bucket Retention Policy) or specific objects (Object Holds).
Frequently Asked Questions
What is the difference between a bucket retention policy and an object hold?
Can I delete data from a bucket with a retention policy before the retention period ends?
Discussion 1 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 1
-
Terralogiq 👍 1 Answered BA bucket retention policy lets you set a minimum retention duration (e.g 3 years) so objects can't be deleted or overwritten until that time passes. A is per-object and manual, C just changes storage cost/access tier not retention, D just keeps old versions around but doesn't prevent deletion. https://cloud.google.com/storage/docs/bucket-lock
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All ADP Questions
Access 65 questions with complete answers and detailed explanations.
View Full ADP Practice Test →