Storage tier optimization in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is storage tier optimization in cloud storage?

Storage tier optimization means choosing the best storage type based on how often and how quickly you need to access your data. It helps save money and improve performance by using different storage layers for different needs.

beginner

Name the common Azure storage tiers used for blob storage.

Azure Blob Storage has Hot, Cool, and Archive tiers. Hot is for frequent access, Cool for infrequent access, and Archive for rarely accessed data that can wait for retrieval.

intermediate

How does moving data to a cooler tier save costs?

Cooler tiers cost less to store data but may charge more when you access or move data. By moving rarely used data to these tiers, you pay less overall because storage costs drop even if access costs rise a bit.

beginner

What is a real-life example of storage tier optimization?

Think of a library: new books are on the front shelves (hot tier) for easy access, older books go to back shelves (cool tier), and very old books are stored in the basement (archive tier). This saves space and effort while keeping books accessible when needed.

intermediate

What Azure feature helps automate moving data between tiers?

Azure Blob Storage lifecycle management lets you set rules to automatically move blobs between Hot, Cool, and Archive tiers based on their age or last modification time.

Which Azure Blob Storage tier is best for data accessed daily?

A Hot tier

B Cool tier

C Archive tier

D Premium tier

The Hot tier is designed for frequent access and offers the lowest latency.

What happens if you access data stored in the Archive tier?

A Data is instantly available with no extra cost

B Data is deleted automatically

C Data moves to Hot tier automatically

D Data retrieval takes time and may incur additional charges

Archive tier data must be rehydrated before use, which takes time and may cost extra.

Why use lifecycle management policies in Azure Storage?

A To automatically delete all data after 1 day

B To automatically move data between tiers based on rules

C To encrypt data at rest

D To increase storage capacity

Lifecycle management automates tier changes to optimize cost and performance.

Which tier is most cost-effective for long-term data that is rarely accessed?

A Archive tier

B Hot tier

C Cool tier

D Standard tier

Archive tier offers the lowest storage cost for rarely accessed data.

What is a key trade-off when using cooler storage tiers?

A No difference in cost or speed

B Higher storage cost but faster access

C Lower storage cost but slower or costlier access

D Data is less secure

Cooler tiers reduce storage cost but increase access latency and may have higher access fees.

Explain how storage tier optimization helps reduce cloud storage costs.

Think about how often you use your data and where it should be stored.

Describe how Azure Blob Storage lifecycle management works for tier optimization.

Imagine setting up automatic reminders to move your files to cheaper storage.

Practice

1. Which Azure Storage tier is best for data that you access very often?

easy

A. Archive tier

B. Cool tier

C. Hot tier

D. Premium tier

Solution

1. Step 1: Understand storage tiers purpose

   The Hot tier is designed for data accessed frequently, providing low latency and high throughput.

2. Step 2: Match access frequency to tier

   Since the question asks for very often access, Hot tier fits best compared to Cool (infrequent) or Archive (rare).

3. Final Answer:

   Hot tier -> Option C

4. Quick Check:

   Frequent access = Hot tier [OK]

Hint: Hot tier = frequent access, Cool = less, Archive = rare [OK]

Common Mistakes:

• Confusing Cool tier as best for frequent access
• Choosing Archive tier for active data
• Thinking Premium tier is a storage tier

2. Which Azure CLI command correctly changes a blob's tier to Cool?

easy

A. az storage blob update-tier --tier Cool --container mycontainer --blob myblob --account mystorage

B. az storage blob set-tier --tier Cool --container-name mycontainer --name myblob --account-name mystorage

C. az storage blob change-tier --tier Cool --container mycontainer --name myblob --account mystorage

D. az storage blob tier-set --tier Cool --container mycontainer --name myblob --account mystorage

Solution

1. Step 1: Recall correct Azure CLI syntax

   The correct command to set a blob's tier is az storage blob set-tier with parameters for tier, container, blob name, and account.

2. Step 2: Verify az storage blob set-tier --tier Cool --container-name mycontainer --name myblob --account-name mystorage matches syntax

   az storage blob set-tier --tier Cool --container-name mycontainer --name myblob --account-name mystorage uses set-tier and correct parameter names, matching Azure CLI documentation.

3. Final Answer:

   az storage blob set-tier --tier Cool --container-name mycontainer --name myblob --account-name mystorage -> Option B

4. Quick Check:

   Correct CLI command = az storage blob set-tier --tier Cool --container-name mycontainer --name myblob --account-name mystorage [OK]

Hint: Use 'az storage blob set-tier' to change tier [OK]

Common Mistakes:

• Using incorrect command verbs like update-tier
• Wrong parameter names like --container instead of --container-name
• Mixing blob and container parameters

3. Given this Azure CLI command:
az storage blob set-tier --tier Archive --container-name logs --name log1.txt --account-name mystorage
What happens to the blob log1.txt after this command?

medium

A. Blob remains in Hot tier with no change

B. Blob is deleted permanently

C. Blob is copied to another container

D. Blob is moved to Archive tier and becomes offline until rehydrated

Solution

1. Step 1: Understand Archive tier behavior

   Setting a blob to Archive tier moves it to a low-cost, offline storage. It cannot be read until rehydrated.

2. Step 2: Analyze command effect

   The command sets the tier to Archive, so the blob becomes offline and inaccessible until restored.

3. Final Answer:

   Blob is moved to Archive tier and becomes offline until rehydrated -> Option D

4. Quick Check:

   Archive tier = offline storage [OK]

Hint: Archive tier blobs are offline until rehydrated [OK]

Common Mistakes:

• Thinking Archive tier deletes the blob
• Assuming blob stays accessible immediately
• Confusing Archive with Hot tier

4. You run this command to change a blob's tier:
az storage blob set-tier --tier Hot --container-name data --name file1.csv --account-name mystorage
But you get an error saying the blob does not exist. What is the most likely cause?

medium

A. The blob name or container name is incorrect

B. The account name is invalid

C. The tier Hot is not supported

D. The Azure CLI is outdated

Solution

1. Step 1: Understand error meaning

   An error stating the blob does not exist usually means the blob or container name is wrong or the blob was deleted.

2. Step 2: Check other options

   Account name errors usually give different messages; Hot tier is valid; CLI outdated causes different errors.

3. Final Answer:

   The blob name or container name is incorrect -> Option A

4. Quick Check:

   Blob not found = wrong name [OK]

Hint: Check blob and container names first on 'not found' errors [OK]

Common Mistakes:

• Assuming tier Hot is invalid
• Blaming CLI version without checking names
• Ignoring typo in blob or container names

5. You have a large dataset stored in Azure Blob Storage. You want to minimize costs but still access some data occasionally. Which tier strategy is best?

hard

A. Store frequently accessed data in Hot tier, infrequent in Cool, and rarely accessed in Archive

B. Store all data in Archive tier and never rehydrate

C. Store all data in Cool tier regardless of access frequency

D. Store all data in Hot tier for fastest access

Solution

1. Step 1: Understand tier cost and access trade-offs

   Hot tier is expensive but fast, Cool is cheaper for infrequent access, Archive is cheapest but offline.

2. Step 2: Apply tier optimization best practice

   Using Hot for frequent, Cool for infrequent, and Archive for rare access balances cost and performance.

3. Final Answer:

   Store frequently accessed data in Hot tier, infrequent in Cool, and rarely accessed in Archive -> Option A

4. Quick Check:

   Tier data by access frequency = Store frequently accessed data in Hot tier, infrequent in Cool, and rarely accessed in Archive [OK]

Hint: Match data access frequency to tier for cost savings [OK]

Common Mistakes:

• Putting all data in Hot tier wastes money
• Never rehydrating Archive data makes it unusable
• Using only Cool tier ignores access patterns