4.2.1. Cloud Storage Object Management and Lifecycle Policies
💡 First Principle: Cloud Storage objects don't manage their own lifecycle by default — left alone, they accumulate indefinitely at whatever storage class they were created with, which is why lifecycle management policies exist as an automation layer specifically to prevent that accumulation from becoming a silent cost problem.
Managing and securing objects covers setting object-level or bucket-level access controls (uniform bucket-level access is the modern recommended approach over legacy per-object ACLs), and object versioning to protect against accidental overwrites or deletions. Object lifecycle management policies define rules like "transition to Coldline after 90 days" or "delete after 365 days" based on an object's age, allowing storage costs to automatically track actual access patterns over time without manual intervention.
⚠️ Exam Trap: A scenario describing a bucket accumulating years of rarely-accessed data with unnecessarily high storage costs, where nobody wants to manually manage the transition, is describing exactly the gap object lifecycle management policies close — manually re-classifying aging objects one by one doesn't scale and isn't the answer the exam is looking for.
Reflection Question: A compliance bucket needs objects automatically moved to Archive storage after one year and deleted entirely after seven. What feature configures this without any manual, recurring administrative work?
