Your application stores files on Cloud Storage by using the Standard Storage class. The application only requires access to files created in the last 30 days. You want to automatically save costs on files that are no longer accessed by the application. What should you do?
The application only requires access to files created in the last 30 days. To save costs effectively, it would be best to delete files older than 30 days since they are no longer required. Creating a cron job in Cloud Scheduler to call a Cloud Functions instance every day to delete files older than 30 days will ensure that unnecessary files are removed, minimizing storage costs.
Shouldn't we delete files that are over 30 days old because they are unnecessary?
Options B and C involve deleting files, which may not be suitable if you need to retain the files for compliance or historical purposes.
I don't know the answer TBH, but the Q doesn't say anything about retaining files. It does ask to lower cost as much as possible, so deleting them would be cheaper, right?
A. Create an object lifecycle on the storage bucket to change the storage class to Archive Storage for objects with an age over 30 days.
ChatGPT says option A. creating an object lifecycle policy to transition objects older than 30 days to the Archive Storage class is the recommended solution for automatically managing costs and storage of files in Cloud Storage.
A thaan da correct
Option A, use of object lifecycle
save costs on files that are no longer accessed by the application; DELETION
Your application stores files on Cloud Storage by using the Standard Storage class. The application only requires access to files created in the last 30 days. You want to automatically save costs on files that are no longer accessed by the application. What should you do? A. Create an object lifecycle on the storage bucket to change the storage class to Archive Storage for objects with an age over 30 days. B. Create a cron job in Cloud Scheduler to call a Cloud Functions instance every day to delete files older than 30 days. C. Create a retention policy on the storage bucket of 30 days, and lock the bucket by using a retention policy lock. D. Enable object versioning on the storage bucket and add lifecycle rules to expire non-current versions after 30 days. A provides a simple, automated, and cost-effective solution for your scenario.
A is not cost-effective solution, so no longer accessed files persist instead of eliminate them
Best choice is A
B or D are correct in my opinion as A does not delete unused files (archive storage is not as cheap as deleting). C only sets a retention policy (https://cloud.google.com/storage/docs/bucket-lock) which means you can only delete files over 30 days but it does not enable automatic deletion of old files. Object Versioning preserves deleted objects as versioned, noncurrent objects that remain accessible in your bucket until explicitly removed (https://cloud.google.com/storage/docs/object-versioning).
There is no requirement listed to keep the files. Deletion is the best option.
B- Deleting the files means you no longer have to pay for storing them
Ridiculous question.
At question not to talk about any analytics or critical data for audit and so on. You need only save cost, so B is answer.
I would say A even though it doesn't mention that the files are still needed. As keeping archived version/ backups is best practise in IT generally. If the question explicitly mentioned that backups were taken using some other method or that old versions were no longer required then B would be the correct answer.