You have been asked to set up Object Lifecycle Management for objects stored in storage buckets.
The objects are written once and accessed frequently for 30 days.
After 30 days, the objects are not read again unless there is a special need.
The objects should be kept for three years, and you need to minimize cost.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
https://books.google.com.pk/books?id=q0nhDwAAQBAJ&pg=PA52&lpg=PA52&dq=Set+up+a+policy+that+uses+Nearline+storage+for+30+days+andObject Lifecycle Management allows you to manage the lifecycle of objects stored in Cloud Storage buckets. It provides a way to automatically transition storage classes or delete objects based on rules that you define. In this scenario, the objects are written once and accessed frequently for 30 days. After 30 days, the objects are not read again unless there is a special need. The objects should be kept for three years, and you need to minimize cost.
Option A suggests setting up a policy that uses Nearline storage for 30 days and then moves to Archive storage for three years. Nearline storage is designed for data that is accessed less frequently, and has a lower storage cost than Standard storage. Archive storage is designed for long-term data archival and is the lowest-cost storage class, but it has higher access costs than Standard and Nearline storage. Therefore, using Nearline storage for 30 days and then moving to Archive storage would help minimize the cost of storage for the objects. However, this option does not account for the fact that the objects may be accessed again within the first year, which would incur high access costs in Archive storage.
Option B suggests setting up a policy that uses Standard storage for 30 days and then moves to Archive storage for three years. Standard storage is designed for frequently accessed data and has a higher storage cost than Nearline storage. Using Standard storage for the first 30 days would incur higher storage costs, but it may be more appropriate if the objects need to be accessed frequently during this time. However, as mentioned before, if the objects are not accessed again within the first year, using Archive storage would incur high access costs.
Option C suggests setting up a policy that uses Nearline storage for 30 days, then moves to Coldline for one year, and then moves to Archive storage for two years. Coldline storage is designed for data that is accessed very infrequently and has a lower storage cost than Archive storage but higher access costs than Nearline storage. Using Nearline storage for the first 30 days and then transitioning to Coldline storage for the first year would help minimize the storage cost of the objects while still allowing for access if needed. After one year, the objects can then transition to Archive storage for the remaining two years, as it is unlikely they will be accessed frequently at that point.
Option D suggests setting up a policy that uses Standard storage for 30 days, then moves to Coldline for one year, and then moves to Archive storage for two years. Similar to option C, using Standard storage for the first 30 days would incur higher storage costs, but it may be more appropriate if the objects need to be accessed frequently during this time. After 30 days, the objects can transition to Coldline storage for the first year, and then transition to Archive storage for the remaining two years.
Overall, option C seems to be the most cost-effective solution while still allowing for access to the objects if needed. Using Nearline storage for the first 30 days and then transitioning to Coldline storage for the first year would help minimize the storage cost of the objects while still allowing for access if needed. After one year, the objects can then transition to Archive storage for the remaining two years, as it is unlikely they will be accessed frequently at that point.