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.