Storage commands in Azure - Time & Space Complexity

Time Complexity: Storage commands

O(n)

Understanding Time Complexity

When working with storage commands in Azure, it's important to understand how the time to complete tasks changes as you work with more files or data.

We want to know how the number of storage operations grows when we upload or list many files.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

// Upload multiple files to Azure Blob Storage
for (int i = 0; i < n; i++) {
    blobClients[i].Upload(filePath[i]);
}

// List all blobs in the container
var blobs = containerClient.GetBlobs();
foreach (var blob in blobs) {
    Console.WriteLine(blob.Name);
}
    

This sequence uploads n files one by one, then lists all blobs in the container.

Identify Repeating Operations

• Primary operation: Uploading each file with blobClient.Upload().
• How many times: Exactly n times, once per file.
• Secondary operation: Listing blobs with GetBlobs(), which retrieves metadata for all blobs.
• How many times: One time, but it processes all blobs in the container.

How Execution Grows With Input

As the number of files n increases, the number of upload calls grows directly with n. Listing blobs also grows with n because it returns all blob metadata.

Input Size (n)	Approx. Api Calls/Operations
10	10 uploads + listing 10 blobs
100	100 uploads + listing 100 blobs
1000	1000 uploads + listing 1000 blobs

Pattern observation: The total operations grow roughly in direct proportion to n.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete these storage commands grows linearly as you add more files.

Common Mistake

[X] Wrong: "Uploading multiple files is just one operation regardless of how many files there are."

[OK] Correct: Each file upload is a separate API call and takes time, so total time grows with the number of files.

Interview Connect

Understanding how storage operations scale helps you design efficient cloud solutions and answer questions about performance in real projects.

Self-Check

"What if we uploaded files in parallel instead of one by one? How would the time complexity change?"

Practice

1. What does the Azure CLI command az storage account create do?

easy

A. Lists all storage accounts in your subscription

B. Deletes an existing storage account

C. Creates a new storage account in Azure

D. Uploads a file to a storage container

Solution

1. Step 1: Understand the command purpose

   The command az storage account create is used to create a new storage account in Azure.

2. Step 2: Compare with other options

   Other options describe deleting, listing, or uploading, which are different commands.

3. Final Answer:

   Creates a new storage account in Azure -> Option C

4. Quick Check:

   Create storage account = Creates new account [OK]

Hint: Create means make new storage account [OK]

Common Mistakes:

• Confusing create with delete
• Thinking it lists accounts
• Mixing upload with account creation

2. Which of the following is the correct syntax to list blobs in a container using Azure CLI?

easy

A. az storage account list --container mycontainer

B. az storage blob list --container-name mycontainer

C. az storage blob upload --container mycontainer

D. az storage container list --blob-name myblob

Solution

1. Step 1: Identify the command to list blobs

   The command to list blobs is az storage blob list with the container name specified.

2. Step 2: Check option syntax correctness

   az storage blob list --container-name mycontainer uses correct command and parameter --container-name. Other options misuse commands or parameters.

3. Final Answer:

   az storage blob list --container-name mycontainer -> Option B

4. Quick Check:

   List blobs = az storage blob list [OK]

Hint: List blobs uses 'az storage blob list' with container name [OK]

Common Mistakes:

• Using container list instead of blob list
• Mixing upload command with list
• Wrong parameter names

3. What will be the output of the following command if the container photos has three blobs named img1.jpg, img2.jpg, and img3.jpg?

az storage blob list --container-name photos --output table

medium

A. A table listing img1.jpg, img2.jpg, img3.jpg blobs

B. An error saying container not found

C. A list of storage accounts

D. An empty list with no blobs

Solution

1. Step 1: Understand the command and container contents

   The command lists blobs in the container named 'photos'. The container has three blobs: img1.jpg, img2.jpg, img3.jpg.

2. Step 2: Predict the output format

   The --output table option formats the output as a table showing blob names.

3. Final Answer:

   A table listing img1.jpg, img2.jpg, img3.jpg blobs -> Option A

4. Quick Check:

   List blobs with table output = table of blob names [OK]

Hint: List blobs shows all files in container as table [OK]

Common Mistakes:

• Expecting error when container exists
• Confusing blobs with storage accounts
• Assuming empty output incorrectly

4. You run the command az storage blob upload --container-name docs --file report.pdf but get an error. What is the most likely cause?

medium

A. The file report.pdf does not exist locally

B. The command syntax is incorrect

C. The container docs does not exist

D. Missing the storage account connection string or credentials

Solution

1. Step 1: Check command requirements

   The upload command requires authentication details like connection string or account key to access storage.

2. Step 2: Analyze common error causes

   Missing credentials is the most common cause of upload failure, even if file and container exist.

3. Final Answer:

   Missing the storage account connection string or credentials -> Option D

4. Quick Check:

   Upload error usually means missing credentials [OK]

Hint: Upload needs credentials; missing them causes errors [OK]

Common Mistakes:

• Assuming file missing without checking
• Ignoring authentication requirements
• Thinking syntax is wrong when it is correct

5. You want to automate backing up files from your local folder backup to an Azure blob container named backup-container. Which sequence of commands correctly achieves this?

hard

A. 1) az storage container create --name backup-container
2) az storage blob upload-batch --source backup --destination backup-container

B. 1) az storage account create --name backup-container
2) az storage blob upload --file backup

C. 1) az storage blob list --container-name backup-container
2) az storage blob download --container-name backup-container

D. 1) az storage container delete --name backup-container
2) az storage blob upload-batch --source backup --destination backup-container

Solution

1. Step 1: Create the container if it does not exist

   The command az storage container create creates the container named 'backup-container'.

2. Step 2: Upload all files from local folder to container

   The command az storage blob upload-batch uploads all files from the local 'backup' folder to the container.

3. Final Answer:

   1) az storage container create --name backup-container 2) az storage blob upload-batch --source backup --destination backup-container -> Option A

4. Quick Check:

   Create container then batch upload = backup done [OK]

Hint: Create container first, then upload batch files [OK]

Common Mistakes:

• Trying to upload without container
• Confusing account creation with container
• Deleting container before upload