A renewable energy company collects high-frequency sensor telemetry from thousands of wind turbines. The raw telemetry data is continuously written to Google Cloud Storage and queried frequently by operational dashboards for the first 14 days. After 14 days, the data is rarely accessed, but company compliance requires retaining all sensor data for 3 years before deletion. To minimize overall storage and retrieval costs while satisfying operational needs, how should you configure the Cloud Storage bucket?
- Set the bucket's default storage class to Standard, and configure an Object Lifecycle Management rule to transition objects to Coldline storage 14 days after creation.Answer
- BSet the bucket's default storage class to Coldline immediately upon object creation, and configure an Object Lifecycle Management rule to delete objects after 3 years.
- CSet the bucket's default storage class to Archive immediately upon object creation, and configure an Object Lifecycle Management rule to transition objects to Nearline storage after 14 days.
- DSet the bucket's default storage class to Standard, and configure an Object Lifecycle Management rule to delete objects 14 days after creation.
Answer
Configure the bucket's default storage class as Standard and use Object Lifecycle Management to transition objects to Coldline storage 14 days after creation.
Starting with Standard storage ensures that frequent queries during the first 14 days do not incur retrieval charges. Setting an Object Lifecycle Management transition to Coldline storage after 14 days minimizes long-term storage costs for data that is rarely accessed, satisfying the 3-year compliance requirement at optimal cost.
Step-by-Step Solution
Key Concept
Selecting Cloud Storage classes and Object Lifecycle Management rules based on data access patterns and retrieval cost considerations.