An organization is designing a Google Cloud Storage solution for storing IoT device diagnostic logs. The data access profile indicates that newly created log objects are read frequently during the first 30 days for operational troubleshooting. Between 30 and 90 days, logs are read infrequently (approximately once per month) for performance analysis. After 90 days, logs are retained for compliance purposes and accessed less than once a year. The primary objective is to minimize total cost of ownership (TCO) without incurring premature data access or retrieval cost penalties. Which Cloud Storage class configuration and Object Lifecycle Management policy should be implemented?
- Create the bucket with the Standard storage class. Configure a lifecycle rule to transition objects to Nearline storage after 30 days, and another rule to transition objects to Coldline or Archive storage after 90 days.Answer
- BCreate the bucket with the Coldline storage class as default to minimize baseline storage charges from the moment log files are created.
- CCreate the bucket with the Standard storage class. Configure a lifecycle rule to transition objects directly to Archive storage after 15 days of creation.
- DCreate the bucket with the Nearline storage class. Configure a lifecycle rule to rewrite objects to Standard storage class whenever a read request is received during the first month.
Answer
Create the bucket with the Standard storage class, transition objects to Nearline storage after 30 days, and transition objects to Coldline or Archive storage after 90 days.
Starting with Standard storage ensures no retrieval fees are charged during the high-frequency initial 30 days. Transitioning to Nearline at day 30 optimizes costs for data read once a month while meeting Nearline's 30-day minimum storage commitment. Moving to Coldline or Archive at day 90 provides the lowest possible storage rate for archival data accessed less than once per year.
Step-by-Step Solution
Key Concept
Selecting Cloud Storage Classes and Object Lifecycle Rules based on data access frequency and minimum retention durations.