Why Azure Storage matters - Why It Works

Introduction

Storing data safely and accessibly is a big challenge for many apps and services. Azure Storage helps by giving you a place in the cloud to keep files, backups, and data that your apps can use anytime from anywhere.

When you want to save photos or documents from a website so users can download them later.

When you need to keep backups of your important data to avoid losing it if something breaks.

When your app needs to share data between different parts or users without using your own servers.

When you want to store logs or records that grow over time and need to be accessed quickly.

When you want a simple way to keep data safe and available without managing physical hardware.

Commands

This command creates a new Azure Storage account named 'mystorageaccount123' in the 'myResourceGroup' resource group located in East US. The Standard_LRS SKU means your data is locally redundant for safety.

Terminal

az storage account create --name mystorageaccount123 --resource-group myResourceGroup --location eastus --sku Standard_LRS

Expected Output

{

  "id": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/myResourceGroup/providers/Microsoft.Storage/storageAccounts/mystorageaccount123",

  "location": "eastus",

  "name": "mystorageaccount123",

  "resourceGroup": "myResourceGroup",

  "sku": {

    "name": "Standard_LRS"

  },

  "kind": "StorageV2",

  "statusOfPrimary": "Available"

}

→

--name - Sets the unique name for the storage account.

→

--resource-group - Specifies the resource group where the storage account will be created.

→

--sku - Defines the replication and performance type for the storage.

This command creates a container named 'mycontainer' inside the storage account. Containers are like folders where you store your files (blobs).

Terminal

az storage container create --account-name mystorageaccount123 --name mycontainer

Expected Output

True

→

--account-name - Specifies which storage account to use.

→

--name - Names the container to create.

Uploads a file named 'example.txt' from your local computer to the 'mycontainer' container in your storage account. This makes the file available in the cloud.

Terminal

az storage blob upload --account-name mystorageaccount123 --container-name mycontainer --name example.txt --file example.txt

Expected Output

Uploading blob to container mycontainer

Upload blob succeeded

→

--container-name - Specifies the container where the file will be uploaded.

→

--name - Sets the name of the file in the cloud.

→

--file - Points to the local file to upload.

Lists all files (blobs) inside the 'mycontainer' container in a readable table format so you can see what is stored.

Terminal

az storage blob list --account-name mystorageaccount123 --container-name mycontainer --output table

Expected Output

Name         BlobType    Length    LastModified

------------ ----------- --------- -------------------------

example.txt  BlockBlob  1234      2024-06-01T12:00:00+00:00

→

--output - Formats the output for easier reading.

Key Concept

Azure Storage provides a safe, easy, and scalable place in the cloud to keep your data accessible anytime and from anywhere.

Common Mistakes

Using a storage account name that is not globally unique.

Azure requires storage account names to be unique across all users, so the creation will fail if the name is taken.

Choose a unique name by adding random numbers or your company name to avoid conflicts.

Trying to upload a file to a container that does not exist.

The upload command will fail because the destination container must exist before uploading files.

Always create the container first using the container create command before uploading blobs.

Not specifying the correct resource group or location when creating the storage account.

This can cause the storage account to be created in an unexpected place or fail if the resource group does not exist.

Verify the resource group exists and specify the desired location explicitly.

Summary

Create an Azure Storage account to have a cloud space for your data.

Make containers inside the storage account to organize your files.

Upload files to containers to store your data safely in the cloud.

List files in containers to check what data you have stored.

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