Configuring a Cost-Effective Cloud Storage Archiving Solution

Archiving Data in a Cloud Storage Bucket

Question

You want to configure a solution for archiving data in a Cloud Storage bucket.

The solution must be cost-effective.

Data with multiple versions should be archived after 30 days.

Previous versions are accessed once a month for reporting.

This archive data is also occasionally updated at month-end.

What should you do?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

B.

https://cloud.google.com/storage/docs/managing-lifecycles

To configure a cost-effective solution for archiving data in a Cloud Storage bucket, you can add a bucket lifecycle rule. This rule can specify when data should be moved to a lower-cost storage class (such as Nearline or Coldline Storage) after a certain period. The answer to this question will depend on the specific requirements outlined.

In this case, the data has multiple versions and should be archived after 30 days. Previous versions are accessed once a month for reporting, and the archive data is occasionally updated at month-end.

Option A: Add a bucket lifecycle rule that archives data with newer versions after 30 days to Coldline Storage.

  • This option archives data with newer versions after 30 days to Coldline Storage. Coldline Storage is a lower-cost storage class that is designed for long-term data retention and is accessed less frequently than Nearline Storage. Since the previous versions are accessed once a month for reporting, this option may not be the best choice as it may incur additional retrieval costs.

Option B: Add a bucket lifecycle rule that archives data with newer versions after 30 days to Nearline Storage.

  • This option archives data with newer versions after 30 days to Nearline Storage. Nearline Storage is a lower-cost storage class that is designed for data that is accessed less frequently, but still requires low latency access. This option is a good choice since the previous versions are accessed once a month for reporting.

Option C: Add a bucket lifecycle rule that archives data from regional storage after 30 days to Coldline Storage.

  • This option archives data from regional storage after 30 days to Coldline Storage. Since the data is accessed once a month for reporting, this option may not be the best choice as it may incur additional retrieval costs.

Option D: Add a bucket lifecycle rule that archives data from regional storage after 30 days to Nearline Storage.

  • This option archives data from regional storage after 30 days to Nearline Storage. Since the data is accessed once a month for reporting, this option is a good choice as it balances cost-effectiveness and accessibility.

Therefore, the best option for this scenario would be to add a bucket lifecycle rule that archives data with newer versions after 30 days to Nearline Storage, which is Option B.