Storage commands in Azure - Step-by-Step Execution

Process Flow - Storage commands

Start: User wants to manage storage

↓

Choose storage command type

↓

Create Storage Account

↓

List Storage Accounts

↓

Upload Blob

↓

Download Blob

↓

Delete Blob

↓

Delete Storage Account

↓

Command executes

↓

Check command result

↓

Success or Error message

↓

End

User picks a storage command to run, executes it, then checks the result for success or error.

Execution Sample

Azure

az storage account create --name mystorageacct --resource-group mygroup --location eastus
az storage container create --account-name mystorageacct --name mycontainer
az storage blob upload --account-name mystorageacct --container-name mycontainer --name file.txt --file ./file.txt

Creates a storage account and uploads a file as a blob to a container.

Process Table

Step	Command	Action	Result	Notes
1	az storage account create --name mystorageacct --resource-group mygroup --location eastus	Create storage account named mystorageacct	Storage account 'mystorageacct' created	Storage account ready for use
2	az storage container create --account-name mystorageacct --name mycontainer	Create container named mycontainer	Container 'mycontainer' created	Container ready to hold blobs
3	az storage blob upload --account-name mystorageacct --container-name mycontainer --name file.txt --file ./file.txt	Upload file.txt as blob	Blob 'file.txt' uploaded	File stored in container
4	az storage blob list --account-name mystorageacct --container-name mycontainer	List blobs in container	Shows 'file.txt'	Verify upload success
5	az storage blob download --account-name mystorageacct --container-name mycontainer --name file.txt --file ./downloaded.txt	Download blob to local file	Blob downloaded as downloaded.txt	File retrieved successfully
6	az storage blob delete --account-name mystorageacct --container-name mycontainer --name file.txt	Delete blob file.txt	Blob 'file.txt' deleted	Blob removed from container
7	az storage account delete --name mystorageacct --resource-group mygroup --yes	Delete storage account	Storage account 'mystorageacct' deleted	Clean up resources
8	-	-	-	Execution ends: all commands run successfully

💡 All storage commands executed in sequence with success or resource cleanup

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	After Step 7
Storage Account	None	mystorageacct created	mystorageacct exists	mystorageacct exists	mystorageacct exists	mystorageacct exists	mystorageacct exists	mystorageacct deleted
Container	None	None	mycontainer created	mycontainer exists	mycontainer exists	mycontainer exists	mycontainer exists	mycontainer gone
Blob file.txt	None	None	None	file.txt uploaded	file.txt listed	file.txt downloaded	file.txt deleted	None

Key Moments - 3 Insights

Why do we need to create a container before uploading a blob?

Blobs are stored inside containers. Step 2 creates the container so step 3 can upload the blob inside it, as shown in execution_table rows 2 and 3.

What happens if we try to download a blob that does not exist?

The command would fail with an error because the blob is missing. In the execution_table, step 5 succeeds only because the blob exists from step 3.

Why delete the storage account at the end?

Deleting the storage account (step 7) cleans up all resources to avoid extra costs, as shown in the variable_tracker where the account is removed after step 7.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What action is performed?

A Create a storage container

B Download a blob

C Upload a file as a blob

D Delete a blob

💡 Hint

Check the 'Action' column in execution_table row 3

At which step is the blob 'file.txt' deleted?

A Step 4

B Step 6

C Step 5

D Step 7

💡 Hint

Look at the 'Command' and 'Result' columns in execution_table row 6

If the storage account is deleted at step 7, what happens to the container and blobs?

A Both container and blobs are deleted

B Only blobs remain

C They remain accessible

D Only container remains

💡 Hint

Refer to variable_tracker showing resource states after step 7

Concept Snapshot

Azure Storage Commands Quick Guide:
- Create storage account: az storage account create
- Create container: az storage container create
- Upload blob: az storage blob upload
- Download blob: az storage blob download
- Delete blob: az storage blob delete
- Delete storage account: az storage account delete
Commands run sequentially to manage storage resources safely.

Full Transcript

This visual execution shows how Azure storage commands run step-by-step. First, a storage account is created. Then a container is made inside it. Next, a file is uploaded as a blob into the container. We list blobs to confirm upload, then download the blob to local storage. After that, the blob is deleted. Finally, the storage account is deleted to clean up. Variables track the existence of the storage account, container, and blob through each step. Key moments clarify why containers are needed before blobs, what happens if blobs are missing, and why cleanup matters. The quiz tests understanding of actions at each step and resource lifecycle. This helps beginners see how storage commands affect cloud resources in order.

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