Storage commands in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Azure Blob Storage Container Creation

You run the command to create a new blob container in Azure Storage:

az storage container create --name mycontainer --account-name mystorageaccount --public-access blob

What is the effect of the --public-access blob option?

A The container and all blobs inside are publicly readable without authentication.

B Only the blobs inside the container are publicly readable, but the container metadata is private.

C The container is private and requires authentication for all access.

D The container is publicly writable but not readable.

💡 Hint

Think about what 'blob' level public access means compared to 'container' level.

The '--public-access blob' option allows anonymous read access to blobs within the container, but the container metadata remains private. This means users can read blobs if they know the URL but cannot list blobs or read container properties.

❓ Configuration

intermediate

Correct Azure CLI Command to Upload a File to Blob Storage

Which Azure CLI command correctly uploads a local file named report.pdf to a blob container named documents in the storage account mystorage?

A az storage container upload --name documents --file report.pdf --account-name mystorage

B az storage blob upload-file --container documents --file report.pdf --account mystorage

C az storage blob upload --container-name documents --file report.pdf --name report.pdf --account-name mystorage

D az storage blob put --container documents --file report.pdf --account-name mystorage

💡 Hint

Check the exact command and parameter names for uploading blobs.

The correct command is 'az storage blob upload' with parameters '--container-name', '--file', '--name', and '--account-name'. Other options are invalid or use wrong parameter names.

❓ Architecture

advanced

Choosing Storage Account Type for High Transaction Workloads

You need to design an Azure Storage solution for an application with very high transaction rates and low latency requirements. Which storage account type should you choose?

A Premium block blob storage account

B Blob storage account with cool access tier

C General-purpose v1 storage account

D General-purpose v2 (GPv2) storage account with standard performance

💡 Hint

Consider performance tiers and latency for storage accounts.

Premium block blob storage accounts provide low latency and high throughput, suitable for high transaction workloads. Standard accounts have higher latency and lower throughput.

❓ security

advanced

Effect of Enabling Soft Delete on Azure Blob Storage

What happens when you enable soft delete on an Azure Blob Storage container?

A Deleted blobs are retained for a configurable period and can be restored during that time.

B Deleted blobs are permanently removed immediately and cannot be recovered.

C Blobs cannot be deleted while soft delete is enabled.

D Soft delete encrypts blobs automatically at rest.

💡 Hint

Think about what 'soft delete' means in data protection.

Soft delete retains deleted blobs for a retention period, allowing recovery if deletion was accidental. It does not prevent deletion or encrypt data.

✅ Best Practice

expert

Optimizing Azure Storage Costs for Infrequently Accessed Data

You have large amounts of data that are rarely accessed but must be retained for compliance. Which Azure Storage strategy best balances cost and accessibility?

A Store data in a general-purpose v2 account using the hot access tier.

B Store data in a premium block blob storage account with cool access tier.

C Store data in a general-purpose v1 account with standard performance.

D Store data in a blob storage account using the archive access tier.

💡 Hint

Consider access frequency and cost trade-offs of storage tiers.

The archive tier is the lowest cost option for rarely accessed data but has higher latency for retrieval. It is ideal for compliance data that is infrequently read.