A mobile gaming software development team stores daily automated crash log bundles in a Google Cloud Storage bucket. Developers frequently inspect and analyze these crash logs during the first 14 days following an application release. After 14 days, the logs are rarely accessed, but company compliance requires preserving them for 365 days before permanent deletion. The team wants to minimize storage and access costs without manual administration. Which bucket configuration should you implement?
- Set the default bucket storage class to Standard. Add an Object Lifecycle Management rule to set the storage class to Nearline after 14 days, and another rule to delete objects after 365 days.Answer
- BSet the default bucket storage class to Coldline. Add an Object Lifecycle Management rule to set the storage class to Standard after 14 days, and another rule to delete objects after 365 days.
- CSet the default bucket storage class to Archive. Add an Object Lifecycle Management rule to set the storage class to Nearline after 14 days, and another rule to delete objects after 365 days.
- DSet the default bucket storage class to Nearline. Keep all objects in Nearline storage for 365 days without any lifecycle transition rules, then delete objects manually.
Answer
Set the default bucket storage class to Standard, configure an Object Lifecycle Management rule to transition objects to Nearline storage after 14 days, and add a rule to delete objects after 365 days.
The correct strategy starts with Standard storage class to avoid data retrieval charges while engineers actively inspect log files during the first two weeks. Using an Object Lifecycle Management rule to transition files to Nearline storage after 14 days optimizes storage costs for the remaining period, and setting a deletion rule at 365 days enforces compliance automatically.
Step-by-Step Solution
Key Concept
Selecting Cloud Storage classes based on data access frequency and configuring Object Lifecycle Management transition rules.
Estimated Time:1m 30s