Storage tiers (Hot, Cool, Archive) in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the storage account's access tier to Hot.

Azure

storage_account = azure.storage.Account(access_tier='[1]')

Drag options to blanks, or click blank then click option'

ACold

BFreeze

CHot

DWarm

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing tiers that don't exist like 'Warm' or 'Freeze'.

Confusing Hot with Cool or Archive.

The Hot tier is used for frequently accessed data in Azure Storage accounts.

2fill in blank

medium

Complete the code to set the blob's access tier to Cool for infrequently accessed data.

Azure

blob_client.set_tier(tier='[1]')

Drag options to blanks, or click blank then click option'

ACool

BHot

CCold

DArchive

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Hot for infrequent data.

Confusing Cool with Archive.

The Cool tier is optimized for data that is infrequently accessed but requires lower latency than Archive.

3fill in blank

hard

Fix the error in setting the blob's tier to Archive for long-term storage.

Azure

blob_client.set_tier(tier='[1]')

Drag options to blanks, or click blank then click option'

ACold

BArchive

CFreeze

DDeep

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent tiers like 'Freeze' or 'Deep'.

Confusing Archive with Cool or Cold.

The Archive tier is for long-term storage of rarely accessed data with flexible latency requirements.

4fill in blank

hard

Fill both blanks to create a storage account with the Cool tier and enable blob soft delete.

Azure

storage_account = azure.storage.Account(access_tier='[1]', blob_soft_delete=[2])

Drag options to blanks, or click blank then click option'

ACool

BTrue

CFalse

DHot

Attempts:

3 left

💡 Hint

Common Mistakes

Setting soft delete to False when protection is needed.

Choosing Hot instead of Cool for the tier.

The Cool tier is for infrequently accessed data, and enabling blob soft delete helps protect against accidental deletions.

5fill in blank

hard

Fill all three blanks to set a blob's tier to Hot, enable versioning, and set access tier change to immediate.

Azure

blob_client.set_tier(tier='[1]', versioning=[2], rehydrate_priority='[3]')

Drag options to blanks, or click blank then click option'

ACool

BTrue

CStandard

DHot

Attempts:

3 left

💡 Hint

Common Mistakes

Using Cool tier for frequent access.

Disabling versioning.

Using incorrect rehydrate priority values.

Hot tier is for frequent access, versioning keeps blob versions, and 'Standard' priority means immediate access tier change.

Practice

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