Bird
Raised Fist0
Azurecloud~5 mins

Storage tiers (Hot, Cool, Archive) in Azure - Time & Space Complexity

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Time Complexity: Storage tiers (Hot, Cool, Archive)
O(n)
Understanding Time Complexity

We want to understand how the time to access or move data changes when using different storage tiers in Azure.

Specifically, how does the number of operations or delays grow when working with Hot, Cool, or Archive storage?

Scenario Under Consideration

Analyze the time complexity of accessing blobs stored in different tiers.


// Access blobs from different tiers
var hotBlob = container.GetBlobClient("hotBlob");
var coolBlob = container.GetBlobClient("coolBlob");
var archiveBlob = container.GetBlobClient("archiveBlob");

// Read data
var hotData = await hotBlob.DownloadAsync();
var coolData = await coolBlob.DownloadAsync();

// Rehydrate archive blob before reading
await archiveBlob.SetAccessTierAsync(AccessTier.Hot);
// Wait for rehydration to complete before downloading
var archiveData = await archiveBlob.DownloadAsync();

This sequence reads data from blobs in Hot, Cool, and Archive tiers, including rehydration for Archive.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

  • Primary operation: Downloading blob data from storage tiers.
  • How many times: Once per blob tier (Hot, Cool, Archive).
  • Additional operation: Archive blob requires a rehydration API call before download.
How Execution Grows With Input

As the number of blobs increases, the number of download and rehydration calls grows linearly.

Input Size (n blobs)Approx. API Calls/Operations
10~10 downloads + rehydrations for archive blobs
100~100 downloads + rehydrations for archive blobs
1000~1000 downloads + rehydrations for archive blobs

Pattern observation: The number of operations grows directly with the number of blobs accessed.

Final Time Complexity

Time Complexity: O(n)

This means the time to access data grows in direct proportion to the number of blobs you work with.

Common Mistake

[X] Wrong: "Accessing archive blobs is as fast as hot or cool blobs."

[OK] Correct: Archive blobs need extra steps like rehydration, which adds time and API calls before data can be read.

Interview Connect

Understanding how storage tier operations scale helps you design efficient cloud solutions and explain trade-offs clearly in real projects.

Self-Check

"What if we batch multiple blob downloads in parallel? How would the time complexity change?"

Practice

(1/5)
1. Which Azure Storage tier is best for data that you need to access frequently and quickly?
easy
A. Premium tier
B. Cool tier
C. Archive tier
D. Hot tier

Solution

  1. Step 1: Understand storage tier purposes

    The Hot tier is designed for data that is accessed often and requires fast retrieval.

  2. Step 2: Compare with other tiers

    Cool tier is for infrequent access, Archive is for rarely accessed data, and Premium is a performance option but not a tier for access frequency.

  3. Final Answer:

    Hot tier -> Option D

  4. Quick Check:

    Frequent access = Hot tier [OK]
Hint: Hot tier = frequent access, fastest retrieval [OK]
Common Mistakes:
  • Confusing Cool tier with Hot tier
  • Thinking Archive tier is for frequent access
  • Assuming Premium tier is a storage access tier
2. Which of the following is the correct way to specify the Archive tier for a blob in Azure Storage using Azure CLI?
easy
A. az storage account set-tier --tier Archive
B. az storage blob set-tier --tier Hot
C. az storage blob set-tier --tier Archive
D. az storage blob update --tier Cool

Solution

  1. Step 1: Identify correct command for blob tier

    The command to set a blob's tier is az storage blob set-tier.

  2. Step 2: Choose correct tier parameter

    To set the Archive tier, use --tier Archive. Setting tier on storage account level is invalid.

  3. Final Answer:

    az storage blob set-tier --tier Archive -> Option C

  4. Quick Check:

    Blob tier set with az storage blob set-tier [OK]
Hint: Use az storage blob set-tier for Archive tier [OK]
Common Mistakes:
  • Trying to set tier on storage account instead of blob
  • Using wrong command like az storage blob update
  • Confusing tier names or casing
3. Consider this Azure Storage blob lifecycle rule snippet:
{
  "rules": [
    {
      "name": "moveToCool",
      "type": "Lifecycle",
      "definition": {
        "actions": {
          "baseBlob": {
            "tierToCool": { "daysAfterModificationGreaterThan": 30 }
          }
        },
        "filters": { "blobTypes": ["blockBlob"] }
      }
    }
  ]
}

What happens to blobs older than 30 days?
medium
A. They are moved to Hot tier
B. They are moved to Cool tier
C. They are deleted
D. They are moved to Archive tier

Solution

  1. Step 1: Analyze lifecycle rule action

    The rule specifies tierToCool for blobs modified more than 30 days ago.

  2. Step 2: Understand effect on blobs

    Blobs older than 30 days are automatically moved to the Cool tier to save cost.

  3. Final Answer:

    They are moved to Cool tier -> Option B

  4. Quick Check:

    30+ days old blobs -> Cool tier [OK]
Hint: tierToCool means move blobs older than X days to Cool [OK]
Common Mistakes:
  • Assuming blobs move to Archive instead of Cool
  • Thinking blobs are deleted by this rule
  • Confusing tierToCool with tierToHot
4. You try to set the Archive tier on an entire Azure Storage account but get an error. What is the likely cause?
medium
A. Archive tier can only be set on individual blobs, not on the whole account
B. You must enable Archive tier feature in the portal first
C. Archive tier requires Premium storage account type
D. Archive tier is only for file shares, not blobs

Solution

  1. Step 1: Recall Archive tier scope

    Archive tier is applied per blob, not at the storage account level.

  2. Step 2: Understand error cause

    Trying to set Archive tier on the whole account causes an error because it's unsupported.

  3. Final Answer:

    Archive tier can only be set on individual blobs, not on the whole account -> Option A

  4. Quick Check:

    Archive tier scope = per blob [OK]
Hint: Archive tier applies only to blobs, not entire account [OK]
Common Mistakes:
  • Thinking Archive tier needs special enablement
  • Assuming Archive tier requires Premium account
  • Confusing Archive tier with file share tiers
5. A company stores large video files that are rarely accessed but must be retained for years. They want to minimize storage costs but can tolerate hours of retrieval delay. Which Azure Storage tier strategy should they use?
hard
A. Store videos directly in Archive tier
B. Store videos in Cool tier and move to Archive after 90 days
C. Store videos in Hot tier for fast access
D. Store videos in Premium tier for best performance

Solution

  1. Step 1: Identify access frequency and cost needs

    Videos are rarely accessed and cost minimization is priority, so Archive tier fits best.

  2. Step 2: Consider retrieval delay tolerance

    Archive tier retrieval can take hours, which is acceptable here.

  3. Step 3: Evaluate other options

    Hot tier is costly, Cool tier is more expensive than Archive, Premium is for performance, not cost saving.

  4. Final Answer:

    Store videos directly in Archive tier -> Option A

  5. Quick Check:

    Rare access + low cost = Archive tier [OK]
Hint: Rarely accessed + low cost = Archive tier [OK]
Common Mistakes:
  • Choosing Hot or Premium tier for rarely accessed data
  • Using Cool tier without moving to Archive
  • Ignoring retrieval delay tolerance
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard