Why Azure Storage matters - See It in Action

Why Azure Storage matters

📖 Scenario: You are working for a small company that wants to keep its important files safe and accessible from anywhere. You decide to use Azure Storage to store these files securely in the cloud.

🎯 Goal: Build a simple Azure Storage setup that creates a storage account, a container, and uploads a file. This will help you understand why Azure Storage is important for keeping data safe and easy to reach.

📋 What You'll Learn

Create an Azure Storage account with a unique name

Create a blob container inside the storage account

Upload a sample file to the blob container

Set the container access level to private

💡 Why This Matters

🌍 Real World

Azure Storage is used by companies to keep files, backups, and data safe and accessible from anywhere in the world.

💼 Career

Knowing how to set up and manage Azure Storage is a key skill for cloud administrators and developers working with Microsoft Azure.

1

Create an Azure Storage account

Write the Azure CLI command to create a storage account named mystorageaccount12345 in the resource group myResourceGroup located in eastus region with the Standard_LRS SKU.

Azure

# Your Azure CLI command here to create the storage account

Hint

Use az storage account create with the correct parameters for name, resource group, location, and SKU.

2

Create a blob container

Write the Azure CLI command to create a blob container named mycontainer inside the storage account mystorageaccount12345.

Azure

az storage account create --name mystorageaccount12345 --resource-group myResourceGroup --location eastus --sku Standard_LRS
# Your Azure CLI command here to create the blob container

Hint

Use az storage container create with the container name and storage account name.

3

Upload a file to the container

Write the Azure CLI command to upload a file named example.txt from your local machine to the blob container mycontainer in the storage account mystorageaccount12345.

Azure

az storage account create --name mystorageaccount12345 --resource-group myResourceGroup --location eastus --sku Standard_LRS
az storage container create --name mycontainer --account-name mystorageaccount12345
# Your Azure CLI command here to upload the file

Hint

Use az storage blob upload with the container name, file path, blob name, and storage account name.

4

Set container access level to private

Write the Azure CLI command to set the access level of the blob container mycontainer in the storage account mystorageaccount12345 to private.

Azure

az storage account create --name mystorageaccount12345 --resource-group myResourceGroup --location eastus --sku Standard_LRS
az storage container create --name mycontainer --account-name mystorageaccount12345
az storage blob upload --container-name mycontainer --file example.txt --name example.txt --account-name mystorageaccount12345
# Your Azure CLI command here to set container access level to private

Hint

Use az storage container set-permission with the container name, storage account name, and --public-access off to make it private.

Practice

1. What is the main purpose of Azure Storage?

easy

A. To create websites

B. To run virtual machines

C. To send emails

D. To safely store files and data in the cloud

Solution

1. Step 1: Understand Azure Storage role

   Azure Storage is designed to keep your files and data safe in the cloud.

2. Step 2: Compare with other Azure services

   Running virtual machines, creating websites, and sending emails are done by other Azure services, not storage.

3. Final Answer:

   To safely store files and data in the cloud -> Option D

4. Quick Check:

   Azure Storage = Safe cloud storage [OK]

Hint: Azure Storage = cloud safe place for files [OK]

Common Mistakes:

• Confusing storage with compute services
• Thinking Azure Storage runs applications
• Mixing storage with communication services

2. Which of the following is the correct way to create a storage container in Azure Portal?

easy

A. Go to Storage Account > Containers > + Container

B. Go to Virtual Machines > + Container

C. Go to Azure Functions > Storage > + Container

D. Go to SQL Databases > Containers > + Container

Solution

1. Step 1: Locate storage containers in Azure Portal

   Containers are created inside Storage Accounts under the Containers section.

2. Step 2: Eliminate incorrect paths

   Virtual Machines, Azure Functions, and SQL Databases do not have container creation under those menus.

3. Final Answer:

   Go to Storage Account > Containers > + Container -> Option A

4. Quick Check:

   Containers created inside Storage Account [OK]

Hint: Containers live inside Storage Accounts in Azure Portal [OK]

Common Mistakes:

• Trying to create containers under unrelated services
• Confusing containers with virtual machines
• Looking for containers in database services

3. What will happen if you try to upload a file larger than the maximum allowed size to Azure Blob Storage?

medium

A. The upload will fail with an error

B. The file will be automatically split and uploaded

C. The file will be compressed and uploaded

D. The upload will succeed without issues

Solution

1. Step 1: Understand Azure Blob Storage limits

   Azure Blob Storage has maximum file size limits depending on the blob type.

2. Step 2: Behavior on exceeding limits

   If a file exceeds the limit, the upload fails with an error; Azure does not split or compress automatically.

3. Final Answer:

   The upload will fail with an error -> Option A

4. Quick Check:

   File too large = upload error [OK]

Hint: Files over limit cause upload errors [OK]

Common Mistakes:

• Assuming Azure splits large files automatically
• Thinking Azure compresses files on upload
• Believing large files upload without issues

4. You wrote a script to upload files to Azure Storage but get an authentication error. What is the most likely cause?

medium

A. Container name is too long

B. File size too small

C. Incorrect storage account key or SAS token

D. Using HTTP instead of HTTPS

Solution

1. Step 1: Identify authentication error causes

   Authentication errors usually happen when the storage account key or SAS token is wrong or expired.

2. Step 2: Rule out other options

   File size or container name length do not cause authentication errors. Using HTTP may cause security warnings but not authentication failure.

3. Final Answer:

   Incorrect storage account key or SAS token -> Option C

4. Quick Check:

   Auth error = bad key or token [OK]

Hint: Check keys and tokens for auth errors [OK]

Common Mistakes:

• Blaming file size for auth errors
• Ignoring token expiration
• Confusing HTTP issues with authentication

5. You want to design a solution that stores user photos securely and allows fast access globally. Which Azure Storage feature should you use?

hard

A. Azure Queue Storage for photo files

B. Geo-redundant storage with Blob Storage and CDN

C. Standard disk storage attached to VMs

D. Locally redundant storage with File Storage only

Solution

1. Step 1: Identify storage needs

   Secure storage and fast global access require redundancy and content delivery.

2. Step 2: Match Azure features

   Geo-redundant storage keeps copies in multiple regions for safety. Blob Storage stores files like photos. CDN speeds up global access.

3. Step 3: Eliminate wrong options

   Locally redundant storage lacks global copies. Disk storage is for VM disks, not files. Queue Storage is for messages, not files.

4. Final Answer:

   Geo-redundant storage with Blob Storage and CDN -> Option B

5. Quick Check:

   Global fast secure files = Geo-redundant Blob + CDN [OK]

Hint: Use geo-redundant Blob Storage plus CDN for global speed [OK]

Common Mistakes:

• Choosing local redundancy for global needs
• Using disk storage for file sharing
• Confusing queue storage with file storage