Storage tier optimization in Azure - Time & Space Complexity

Time Complexity: Storage tier optimization

O(n)

Understanding Time Complexity

When we optimize storage tiers, we want to know how the time to move or access data changes as the amount of data grows.

We ask: How does the work increase when we handle more files or data size?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// Move blobs from hot to cool tier based on last access date
var blobs = container.ListBlobs();
foreach (var blob in blobs) {
  if (blob.Properties.LastAccessed < DateTime.UtcNow.AddDays(-30)) {
    blob.SetTier(AccessTier.Cool);
  }
}

This code checks each blob in a storage container and moves older blobs to a cooler, cheaper storage tier.

Identify Repeating Operations

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

• Primary operation: Checking each blob's last access date and setting its storage tier.
• How many times: Once for every blob in the container.

How Execution Grows With Input

As the number of blobs grows, the number of checks and possible tier changes grows too.

Input Size (n)	Approx. Api Calls/Operations
10	About 10 checks and possible tier changes
100	About 100 checks and possible tier changes
1000	About 1000 checks and possible tier changes

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

Final Time Complexity

Time Complexity: O(n)

This means the time to optimize storage tiers grows in a straight line as the number of blobs increases.

Common Mistake

[X] Wrong: "Changing storage tiers happens instantly for all blobs at once."

[OK] Correct: Each blob must be checked and updated individually, so time grows with the number of blobs.

Interview Connect

Understanding how operations scale with data size helps you design efficient cloud solutions and shows you think about real-world costs and delays.

Self-Check

"What if we batch update blobs instead of updating one by one? How would the time complexity change?"

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