Google Associate Cloud Engineer Question 246
Single answerGoogle Cloud PlatformYou are tasked with estimating the monthly cost of storing 10 TB of data in Google Cloud Storage. The data is expected to be accessed infrequently, and you want to minimize storage costs. Which storage class should you choose and how will you estimate the cost?
- A
Use Nearline storage class and calculate the cost based on storage and retrieval fees.
- B
Use Coldline storage class and calculate the cost based solely on storage fees.
- C
Use Standard storage class and calculate the cost based solely on storage fees.
- D
Use Archive storage class and calculate the cost based on storage fees and minimal retrieval costs.
Show answer and explanation
Correct answer: A
Explanation
For data that is infrequently accessed, Google Cloud Storage's Nearline class is the most cost-effective option. It provides lower storage costs than Standard class and includes retrieval fees, which need to be considered in the total cost estimation. Coldline and Archive are not ideal because Coldline is designed for even less frequent access, and Archive incurs high retrieval fees.
- A. Correct.
Nearline is designed for data that is accessed less than once a month, making it suitable for infrequent access while offering lower storage costs compared to the Standard class. Costs should consider both storage and retrieval fees due to infrequent access.
- B. Incorrect.
Coldline is suitable for data accessed less than once a year and offers even lower storage costs. However, it is not ideal for data expected to be accessed more frequently than once a year. Retrieval fees are also higher.
- C. Incorrect.
Standard storage is designed for data that is frequently accessed. It is not cost-effective for infrequently accessed data due to higher storage fees compared to Nearline and Coldline.
- D. Incorrect.
Archive storage is intended for data that is rarely accessed, such as once a year or less. While it offers the lowest storage costs, retrieval fees are significant, making it less suitable for data expected to be accessed infrequently rather than rarely.