Exam Associate Cloud Engineer topic 1 question 248 discussion

It seems we need to select ones with cheapest cost instead of deleting them.

The question is badly worded - because they didn't tell us what they intend to do with the files afterwards. I choose A anyway, because with lifecycle management you can delete files after 30 days, and using other services in this situation is really unnecessary..

It is cheaper to delete the files as there is no requirement to keep them.

This is the same logic as Microsoft: when you have 2 options: one needs to pay and the other is free, choose the one with fee. That is the right answer.

Cloud Storage lifecycle management, you can automatically transition objects between storage classes based on certain conditions, such as age. Since your application only requires access to files created in the last 30 days, you can set a lifecycle rule to move files that are older than 30 days to Archive Storage, which offers the lowest storage costs but is designed for infrequent access.

This option utilizes Cloud Storage's built-in object lifecycle management feature, which can automatically transition files older than 30 days to Archive Storage, thereby saving storage costs without requiring manual management. In comparison, option B is feasible but more complex and does not align with best practices.

B is correct

A A is Correct because it suggests changing the storage class to Archive Storage for objects with an age of over 30 days through a lifecycle rule on the storage bucket. This is a cost-effective solution because Google Cloud Storage offers different storage classes with varying costs. The "Archive Storage" class is designed for infrequently accessed data and comes at a lower cost compared to the standard storage class. Using a lifecycle rule to transition objects older than 30 days to the Archive Storage class helps save costs by utilizing a more cost-efficient storage class for older data.

Another classic annoyingly vague question, but I would have to go with A because 'normally' you would keep files for longer than 30 days. If it is ok to delete, then B

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.

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.

Ridiculous question.

B- Deleting the files means you no longer have to pay for storing them

There is no requirement listed to keep the files. Deletion is the best option.

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).

Best choice is A

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.