An enterprise telemetry service ingests real-time IoT diagnostic data into Google Cloud Storage. Analysts perform frequent, daily query operations on the ingested data during the first 30 days. After 30 days, the data is rarely accessed but must be retained for 3 years to comply with regulatory requirements. You need to plan a storage architecture that minimizes overall storage and access costs without incurring data retrieval penalties during the initial active analysis window. Which bucket configuration should you recommend?
- Create a Cloud Storage bucket with Standard storage class as the default, and configure an Object Lifecycle Management rule to transition objects to Coldline storage after 30 days.Cevap
- BCreate a Cloud Storage bucket with Coldline storage class as the default from ingestion to achieve lower base storage rates immediately upon data creation.
- CCreate a Cloud Storage bucket with Standard storage class and configure an Object Lifecycle Management rule to transition objects to Nearline storage on day 1, and then to Standard storage after 30 days.
- DCreate a Cloud Storage bucket with Uniform Bucket-Level Access disabled, and apply per-object ACLs to force Archive storage class on files accessed during the first 30 days.
Cevap
Create a Cloud Storage bucket with Standard storage class as the default, and configure an Object Lifecycle Management rule to transition objects to Coldline storage after 30 days.
The option recommending Standard storage class by default combined with an Object Lifecycle Management rule to transition objects to Coldline storage after 30 days is correct. Standard storage has no retrieval charges for active daily analysis. Moving data to Coldline after 30 days optimizes long-term retention costs when query frequency drops.
Adım Adım Çözüm
Anahtar Kavram
Cloud Storage Storage Class Selection and Object Lifecycle Management