Why Azure Storage matters - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a storage account in Azure using the Azure CLI.

Azure

az storage account create --name [1] --resource-group MyResourceGroup --location eastus --sku Standard_LRS

Drag options to blanks, or click blank then click option'

Amystorageaccount123

Beastus

CMyResourceGroup

DStandard_LRS

Attempts:

3 left

💡 Hint

Common Mistakes

Using the location or resource group name as the storage account name.

Using uppercase letters in the storage account name.

The --name parameter specifies the unique name of the storage account. It must be globally unique.

2fill in blank

medium

Complete the code to upload a file to an Azure Blob Storage container using Azure CLI.

Azure

az storage blob upload --account-name mystorageaccount123 --container-name mycontainer --name myfile.txt --file [1]

Drag options to blanks, or click blank then click option'

Amystorageaccount123

Bmyfile.txt

Cmycontainer

Dblob

Attempts:

3 left

💡 Hint

Common Mistakes

Using the container name instead of the file path.

Using the storage account name instead of the file path.

The --file parameter specifies the local file path to upload.

3fill in blank

hard

Fix the error in the Azure CLI command to list blobs in a container.

Azure

az storage blob list --account-name mystorageaccount123 --container-name [1] --output table

Drag options to blanks, or click blank then click option'

Amyfile.txt

Bmystorageaccount123

Cmycontainer

Dblob

Attempts:

3 left

💡 Hint

Common Mistakes

Using a file name instead of the container name.

Using the storage account name instead of the container name.

The --container-name parameter requires the container's name, not a file or account name.

4fill in blank

hard

Fill both blanks to create a new Azure Blob container with public access disabled.

Azure

az storage container create --name [1] --account-name mystorageaccount123 --public-access [2]

Drag options to blanks, or click blank then click option'

Amycontainer

Bblob

Coff

Dprivate

Attempts:

3 left

💡 Hint

Common Mistakes

Setting public access to 'blob' which allows public read access.

Using an invalid container name.

The --name parameter sets the container name. The --public-access parameter set to 'private' disables public access.

5fill in blank

hard

Fill all three blanks to generate a SAS token for a blob with read permission valid for 1 hour.

Azure

az storage blob generate-sas --account-name mystorageaccount123 --container-name mycontainer --name myfile.txt --permissions [1] --expiry [2] --https-only [3]

Drag options to blanks, or click blank then click option'

Ar

B2024-12-31T23:59Z

Ctrue

Dw

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'w' permission which allows write access instead of read.

Setting expiry to a past date.

Setting https-only to 'false' or omitting it.

--permissions 'r' means read access. --expiry sets the token expiry time in UTC ISO format. --https-only set to 'true' ensures secure access.

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