Storage classes (Standard, Nearline, Coldline, Archive) in GCP - Step-by-Step Execution

Process Flow - Storage classes (Standard, Nearline, Coldline, Archive)

Upload Data

↓

Choose Storage Class

↓

Standard

↓

Nearline

↓

Coldline

↓

Archive

↓

Store Data with chosen class

↓

Access Data

↓

Pay access cost based on class

↓

Data retrieval or lifecycle transition

Data is uploaded and assigned a storage class based on how often it will be accessed. Each class balances cost and access speed differently.

Execution Sample

GCP

gsutil cp file.txt gs://my-bucket
# Choose storage class during bucket creation
gsutil mb -c nearline gs://my-bucket-nearline

Uploads a file to a bucket and creates a bucket with the Nearline storage class for less frequent access.

Process Table

Step	Action	Storage Class Selected	Cost Impact	Access Speed
1	Create bucket with Standard class	Standard	Higher cost	Fast access
2	Upload file to Standard bucket	Standard	Charged at Standard rates	Immediate access
3	Create bucket with Nearline class	Nearline	Lower storage cost	Slower access, retrieval fee
4	Upload file to Nearline bucket	Nearline	Charged at Nearline rates	Access slower, pay retrieval fee
5	Create bucket with Coldline class	Coldline	Even lower storage cost	Longer retrieval time, higher fee
6	Upload file to Coldline bucket	Coldline	Charged at Coldline rates	Access slower, pay retrieval fee
7	Create bucket with Archive class	Archive	Lowest storage cost	Longest retrieval time, highest fee
8	Upload file to Archive bucket	Archive	Charged at Archive rates	Access slowest, pay retrieval fee
9	Access file from Standard bucket	Standard	No retrieval fee	Fast access
10	Access file from Nearline bucket	Nearline	Retrieval fee applies	Slower access
11	Access file from Coldline bucket	Coldline	Higher retrieval fee	Slower access
12	Access file from Archive bucket	Archive	Highest retrieval fee	Slowest access
13	Exit	-	-	-

💡 All storage classes and access scenarios covered, process ends.

Status Tracker

Variable	Start	After Step 1	After Step 3	After Step 5	After Step 7	Final
Storage Class	None	Standard	Nearline	Coldline	Archive	Archive
Cost per GB	N/A	High	Medium	Low	Lowest	Lowest
Access Speed	N/A	Fast	Slower	Slower	Slowest	Slowest
Retrieval Fee	N/A	None	Yes	Higher	Highest	Highest

Key Moments - 3 Insights

Why does Nearline have lower storage cost but higher retrieval fees?

Nearline is designed for data accessed less often. The execution_table rows 3 and 10 show lower storage cost but retrieval fees apply when accessing data.

Is data access speed the same for all storage classes?

No, as shown in execution_table rows 2, 6, and 12, Standard offers fast access while Archive is slowest due to its design for long-term storage.

Can I change the storage class after uploading data?

Yes, but it involves lifecycle management and possibly additional costs. This is implied in the concept_flow where data retrieval or lifecycle transition happens after storage.

Visual Quiz - 3 Questions

Look at the execution_table, what storage class is selected at step 5?

A Standard

B Coldline

C Nearline

D Archive

💡 Hint

Check the 'Storage Class Selected' column at step 5 in the execution_table.

At which step does accessing data from the Archive class occur?

A Step 8

B Step 10

C Step 12

D Step 9

💡 Hint

Look for 'Access file from Archive bucket' in the Action column of the execution_table.

If you want the fastest access with no retrieval fees, which storage class should you choose?

A Standard

B Nearline

C Coldline

D Archive

💡 Hint

Refer to the 'Access Speed' and 'Retrieval Fee' columns for Standard in the execution_table rows 2 and 9.

Concept Snapshot

Storage classes in GCP balance cost and access speed:
- Standard: high cost, fast access, no retrieval fee
- Nearline: lower cost, slower access, retrieval fee applies
- Coldline: lower cost, longer retrieval, higher retrieval fee
- Archive: lowest cost, slowest access, highest retrieval fee
Choose based on how often you access your data.

Full Transcript

This visual execution trace shows how Google Cloud Storage classes work. First, you create buckets with a chosen storage class: Standard, Nearline, Coldline, or Archive. Each class has different costs and access speeds. Standard is for frequent access with higher cost and no retrieval fees. Nearline and Coldline are for less frequent access with lower storage costs but retrieval fees and slower access. Archive is for long-term storage with the lowest cost but slowest access and highest retrieval fees. The execution table walks through creating buckets, uploading files, and accessing data, showing cost and speed differences. The variable tracker summarizes how storage class, cost, access speed, and retrieval fees change over steps. Key moments clarify common confusions about cost trade-offs and access speeds. The quiz tests understanding by referencing specific steps and data in the tables. This helps beginners see how storage classes affect their data storage and retrieval in GCP.

Practice

1. Which Google Cloud Storage class is best for data you need to access frequently and quickly?

easy

A. Standard

B. Nearline

C. Coldline

D. Archive

Solution

1. Step 1: Understand access frequency for each storage class

   Standard is designed for frequent access, Nearline for monthly, Coldline for quarterly, and Archive for rare access.

2. Step 2: Match frequent access requirement

   Since the question asks for frequent and quick access, Standard is the best fit.

3. Final Answer:

   Standard -> Option A

4. Quick Check:

   Frequent access = Standard [OK]

Hint: Frequent access? Choose Standard storage class [OK]

Common Mistakes:

• Choosing Archive for frequent access
• Confusing Nearline with Standard
• Thinking Coldline is for frequent data

2. Which storage class should you specify in the bucket creation command to store data accessed about once a month?

easy

A. gsutil mb -c coldline gs://my-bucket

B. gsutil mb -c nearline gs://my-bucket

C. gsutil mb -c archive gs://my-bucket

D. gsutil mb -c standard gs://my-bucket

Solution

1. Step 1: Identify the storage class for monthly access

   Nearline is designed for data accessed about once a month.

2. Step 2: Match the correct gsutil command syntax

   The command to create a bucket with Nearline storage class is 'gsutil mb -c nearline gs://my-bucket'.

3. Final Answer:

   gsutil mb -c nearline gs://my-bucket -> Option B

4. Quick Check:

   Monthly access = Nearline [OK]

Hint: Nearline = monthly access, use '-c nearline' in command [OK]

Common Mistakes:

• Using '-c coldline' for monthly access
• Using '-c archive' for monthly access
• Confusing command syntax with bucket name

3. You have a bucket with Coldline storage class. You upload a 10 GB file and access it immediately. What is true about the cost and access speed?

medium

A. Low storage cost, slower access speed with retrieval fee

B. High storage cost, slow access speed

C. Low storage cost, fast access speed

D. High storage cost, fast access speed

Solution

1. Step 1: Understand Coldline storage characteristics

   Coldline offers low storage cost but is designed for infrequent access, so access speed is slower and retrieval fees apply.

2. Step 2: Analyze immediate access impact

   Accessing data immediately in Coldline means paying retrieval fees and experiencing slower access compared to Standard.

3. Final Answer:

   Low storage cost, slower access speed with retrieval fee -> Option A

4. Quick Check:

   Coldline = low cost + slower access + retrieval fee [OK]

Hint: Coldline is cheap storage but slow and costly to access [OK]

Common Mistakes:

• Assuming Coldline has fast access speed
• Thinking Coldline has no retrieval fees
• Confusing Coldline with Standard class

4. A user created a bucket with the command gsutil mb -c standard gs://archive-data but wants to store rarely accessed data. What is the best fix?

medium

A. Delete and recreate bucket with -c archive option

B. Change storage class to Coldline using gsutil setclass coldline

C. Use gsutil rewrite -s archive gs://archive-data/** to change storage class

D. No fix needed; Standard is best for rare access

Solution

1. Step 1: Identify the problem with initial bucket creation

   The bucket was created with Standard class, which is costly for rarely accessed data.

2. Step 2: Find the correct method to change storage class without deleting bucket

   Using gsutil rewrite -s archive gs://archive-data/** changes storage class of existing objects to Archive without bucket recreation.

3. Final Answer:

   Use gsutil rewrite -s archive gs://archive-data/** to change storage class -> Option C

4. Quick Check:

   Change storage class with gsutil rewrite [OK]

Hint: Use gsutil rewrite to change storage class without bucket deletion [OK]

Common Mistakes:

• Deleting bucket unnecessarily
• Using non-existent gsutil setclass command
• Thinking Standard is best for rare access

5. A company wants to archive 100 TB of data that is accessed less than once a year but must be retrievable within hours if needed. Which storage class should they choose and why?

hard

A. Standard, because it offers fastest access

B. Nearline, because it balances cost and monthly access

C. Coldline, because it is cheaper and supports quarterly access

D. Archive, because it is lowest cost and retrieval is within hours

Solution

1. Step 1: Analyze access frequency and retrieval time needs

   Data is accessed less than once a year, so very rare access. Retrieval must be within hours.

2. Step 2: Match storage class to access pattern and retrieval speed

   Archive class is designed for rare access with lowest cost and retrieval times within hours, fitting the requirement.

3. Step 3: Compare with other classes

   Standard is costly, Nearline is for monthly access, Coldline is for quarterly access, so Archive is best.

4. Final Answer:

   Archive, because it is lowest cost and retrieval is within hours -> Option D

5. Quick Check:

   Rare yearly access + hours retrieval = Archive [OK]

Hint: Rare yearly access + hours retrieval? Choose Archive [OK]

Common Mistakes:

• Choosing Coldline for yearly access
• Assuming Archive retrieval takes days
• Picking Standard for cost savings