Bird
Raised Fist0
GCPcloud~10 mins

Storage classes (Standard, Nearline, Coldline, Archive) in GCP - Interactive Code Practice

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to create a Google Cloud Storage bucket with the Standard storage class.

GCP
resource "google_storage_bucket" "my_bucket" {
  name          = "my-standard-bucket"
  location      = "US"
  storage_class = "[1]"
}
Drag options to blanks, or click blank then click option'
ANEARLINE
BARCHIVE
CCOLDLINE
DSTANDARD
Attempts:
3 left
💡 Hint
Common Mistakes
Choosing a colder storage class like Coldline or Archive for frequently accessed data.
Using Nearline which is for infrequent access but not the hottest data.
2fill in blank
medium

Complete the code to set the storage class to Nearline for infrequently accessed data.

GCP
resource "google_storage_bucket" "my_bucket" {
  name          = "my-nearline-bucket"
  location      = "US"
  storage_class = "[1]"
}
Drag options to blanks, or click blank then click option'
ANEARLINE
BCOLDLINE
CSTANDARD
DARCHIVE
Attempts:
3 left
💡 Hint
Common Mistakes
Confusing Nearline with Coldline or Archive which are for even colder data.
Using Standard which is more expensive for infrequent access.
3fill in blank
hard

Fix the error in the storage class assignment for cold data storage.

GCP
resource "google_storage_bucket" "cold_bucket" {
  name          = "my-cold-bucket"
  location      = "US"
  storage_class = "[1]"
}
Drag options to blanks, or click blank then click option'
ANEARLINE
BCOLDLINE
CSTANDARD
DARCHIVE
Attempts:
3 left
💡 Hint
Common Mistakes
Using Archive which is for data accessed very rarely and has long retrieval times.
Using Standard or Nearline which are more expensive for cold data.
4fill in blank
hard

Fill both blanks to create a bucket with Archive storage class in the ASIA location.

GCP
resource "google_storage_bucket" "archive_bucket" {
  name          = "my-archive-bucket"
  location      = "[1]"
  storage_class = "[2]"
}
Drag options to blanks, or click blank then click option'
AASIA
BUS
CARCHIVE
DSTANDARD
Attempts:
3 left
💡 Hint
Common Mistakes
Mixing up location regions like US instead of ASIA.
Using Standard or Nearline for Archive use cases.
5fill in blank
hard

Fill all three blanks to create a bucket named 'backup-bucket' in EU with Coldline storage class.

GCP
resource "google_storage_bucket" "backup_bucket" {
  name          = "[1]"
  location      = "[2]"
  storage_class = "[3]"
}
Drag options to blanks, or click blank then click option'
Abackup-bucket
BUS
CCOLDLINE
DEU
Attempts:
3 left
💡 Hint
Common Mistakes
Using US instead of EU for location.
Choosing Standard or Archive instead of Coldline for cold backups.

Practice

(1/5)
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