Storage tier optimization in Azure - Step-by-Step Execution

Process Flow - Storage tier optimization

Data arrives in Storage Account

↓

Check data access frequency

↓

Hot tier

↓

Fast access

↓

Monitor usage and move data between tiers

↓

Optimize cost and performance

Data is stored in different tiers based on how often it is accessed, balancing cost and speed.

Execution Sample

Azure

Set blob tier to Hot
Access blob frequently
Change tier to Cool if access drops
Archive blob if rarely accessed

This sequence shows how data moves between storage tiers based on access frequency.

Process Table

Step	Data Access Frequency	Action	Storage Tier	Cost Impact
1	High	Set tier to Hot	Hot	Higher cost, fast access
2	High	Access blob	Hot	Cost remains higher
3	Low	Change tier to Cool	Cool	Lower cost, slower access
4	Very Low	Archive blob	Archive	Lowest cost, slowest access
5	Access increases	Move blob to Hot	Hot	Cost increases, fast access
6	Access drops	Move blob to Cool	Cool	Cost decreases
7	Access stops	Move blob to Archive	Archive	Cost minimized

💡 Data tier changes stop when access frequency stabilizes or data is deleted.

Status Tracker

Variable	Start	After Step 1	After Step 3	After Step 4	After Step 5	After Step 7
Storage Tier	None	Hot	Cool	Archive	Hot	Archive
Cost Level	None	High	Medium	Low	High	Lowest
Access Frequency	Unknown	High	Low	Very Low	High	Stopped

Key Moments - 3 Insights

Why do we move data from Hot to Cool tier?

Because access frequency drops (see step 3 in execution_table), moving data to Cool tier reduces cost while accepting slower access.

What happens if data access increases after archiving?

Data is moved back to Hot tier for faster access and higher cost (see step 5 in execution_table).

Is Archive tier suitable for frequently accessed data?

No, Archive tier is for rarely accessed data due to slow retrieval times and is lowest cost (see step 4).

Visual Quiz - 3 Questions

Look at the execution_table, what is the storage tier after step 3?

A Hot

B Cool

C Archive

D None

💡 Hint

Check the 'Storage Tier' column at step 3 in execution_table.

At which step does the cost become lowest?

A Step 5

B Step 2

C Step 4

D Step 1

💡 Hint

Look at the 'Cost Impact' column in execution_table for the lowest cost.

If data access frequency never drops, which tier will data remain in?

A Hot

B Cool

C Archive

D None

💡 Hint

Refer to variable_tracker and execution_table steps where access frequency is high.

Concept Snapshot

Storage tier optimization:
- Hot tier: frequent access, higher cost
- Cool tier: infrequent access, lower cost
- Archive tier: rare access, lowest cost
- Move data between tiers based on usage
- Balances cost and performance

Full Transcript

Storage tier optimization in Azure means placing data in different storage tiers depending on how often it is accessed. Data accessed frequently is stored in the Hot tier for fast access but higher cost. When access drops, data moves to the Cool tier to save cost with slower access. If data is rarely accessed, it moves to the Archive tier, which is the cheapest but slowest to retrieve. This process helps balance cost and performance by monitoring data usage and adjusting storage tiers accordingly.

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