Why Storage account creation in Azure? - Purpose & Use Cases

The Big Idea

What if you could create perfect cloud storage in seconds instead of minutes or hours?

The Scenario

Imagine you need to create a place to store your files and data in the cloud. Doing this by clicking through many screens and filling forms every time feels like filling out a long paper form repeatedly.

The Problem

Manually creating storage accounts is slow and easy to make mistakes. You might forget a setting or choose the wrong options. This can cause problems later, like losing data or paying more than needed.

The Solution

Using automated storage account creation lets you set up storage quickly and correctly every time. You write a simple script or use a template that does all the work for you, saving time and avoiding errors.

Before vs After

✗ Before

Go to portal > Storage accounts > Create > Fill details > Review > Create

✓ After

az storage account create --name mystorage --resource-group mygroup --location eastus --sku Standard_LRS

What It Enables

You can create many storage accounts quickly and reliably, making your cloud projects faster and safer.

Real Life Example

A company launching a new app needs multiple storage accounts for images, backups, and logs. Automating creation saves days of work and ensures all accounts have the right settings.

Key Takeaways

Manual creation is slow and error-prone.

Automation speeds up setup and reduces mistakes.

Reliable storage accounts help your cloud projects succeed.

Practice

1. What is the main purpose of an Azure Storage Account?

easy

A. To store and manage data in the cloud

B. To run virtual machines

C. To host websites

D. To monitor network traffic

Solution

1. Step 1: Understand the role of a storage account

   An Azure Storage Account is designed to hold data like files, blobs, and tables securely in the cloud.

2. Step 2: Compare with other Azure services

   Running virtual machines, hosting websites, and monitoring network traffic are handled by other Azure services, not storage accounts.

3. Final Answer:

   To store and manage data in the cloud -> Option A

4. Quick Check:

   Storage account = cloud data storage [OK]

Hint: Storage account = cloud folder for data [OK]

Common Mistakes:

• Confusing storage account with virtual machines
• Thinking storage account hosts websites
• Mixing storage with monitoring services

2. Which Azure CLI command correctly creates a storage account named mystorage123 in resource group mygroup located in eastus with SKU Standard_LRS and kind StorageV2?

easy

A. az storage account new --name mystorage123 --resource-group mygroup --location eastus --sku Standard_LRS --kind StorageV2

B. az storage create --account-name mystorage123 --group mygroup --region eastus --sku Standard_LRS --type StorageV2

C. az storage account create --name mystorage123 --resource-group mygroup --location eastus --sku Standard_LRS --kind StorageV2

D. az create storage account --name mystorage123 --resource-group mygroup --location eastus --sku Standard_LRS --kind StorageV2

Solution

1. Step 1: Identify the correct Azure CLI command syntax

   The correct command to create a storage account is az storage account create with parameters for name, resource group, location, SKU, and kind.

2. Step 2: Check parameter names and values

   az storage account create --name mystorage123 --resource-group mygroup --location eastus --sku Standard_LRS --kind StorageV2 uses the correct parameter names and values matching Azure CLI documentation.

3. Final Answer:

   az storage account create --name mystorage123 --resource-group mygroup --location eastus --sku Standard_LRS --kind StorageV2 -> Option C

4. Quick Check:

   Correct CLI syntax = az storage account create --name mystorage123 --resource-group mygroup --location eastus --sku Standard_LRS --kind StorageV2 [OK]

Hint: Use 'az storage account create' with correct flags [OK]

Common Mistakes:

• Using wrong command verbs like 'create' vs 'new'
• Incorrect parameter names like '--group' instead of '--resource-group'
• Mixing up SKU or kind parameter values

3. What will happen if you run this Azure CLI command?

az storage account create --name mystorage123 --resource-group mygroup --location eastus --sku Premium_LRS --kind BlobStorage

medium

A. Creates a Blob Storage account with premium performance

B. Creates a general purpose v2 storage account

C. Creates a storage account with standard performance

D. Fails because BlobStorage kind does not support Premium_LRS SKU

Solution

1. Step 1: Understand SKU and kind compatibility

   BlobStorage kind supports only Standard performance SKUs, not Premium_LRS.

2. Step 2: Predict command behavior

   Using Premium_LRS SKU with BlobStorage kind causes the command to fail due to incompatible parameters.

3. Final Answer:

   Fails because BlobStorage kind does not support Premium_LRS SKU -> Option D

4. Quick Check:

   BlobStorage + Premium_LRS = failure [OK]

Hint: Match SKU and kind compatibility before creating [OK]

Common Mistakes:

• Assuming all SKUs work with all kinds
• Thinking BlobStorage supports premium SKUs
• Ignoring error messages from CLI

4. You tried to create a storage account with this command:

az storage account create --name mystorage123 --resource-group mygroup --location eastus --sku Standard_LRS --kind StorageV2

But you get an error saying the name is already taken. What should you do to fix this?

medium

A. Change the storage account name to a unique one

B. Change the resource group name

C. Change the location to another region

D. Change the SKU to Premium_LRS

Solution

1. Step 1: Understand storage account name uniqueness

   Storage account names must be globally unique across Azure.

2. Step 2: Identify the cause of the error

   The error indicates the chosen name is already used by someone else.

3. Step 3: Fix by changing the name

   Changing the name to a unique one resolves the conflict and allows creation.

4. Final Answer:

   Change the storage account name to a unique one -> Option A

5. Quick Check:

   Unique name needed = Change the storage account name to a unique one [OK]

Hint: Storage account names must be unique globally [OK]

Common Mistakes:

• Changing resource group instead of name
• Changing location or SKU won't fix name conflict
• Ignoring error details about name uniqueness

5. You want to create a storage account optimized for storing large amounts of unstructured data with high durability and geo-redundancy. Which combination of SKU and kind should you choose?

hard

A. SKU: Premium_LRS, Kind: BlobStorage

B. SKU: Standard_GRS, Kind: StorageV2

C. SKU: Standard_LRS, Kind: FileStorage

D. SKU: Standard_ZRS, Kind: StorageV1

Solution

1. Step 1: Identify requirements for unstructured data and durability

   StorageV2 kind supports blobs and unstructured data with advanced features.

2. Step 2: Choose SKU with geo-redundancy

   Standard_GRS provides geo-redundant storage for high durability across regions.

3. Step 3: Match SKU and kind

   Standard_GRS with StorageV2 is the best fit for large unstructured data with geo-redundancy.

4. Final Answer:

   SKU: Standard_GRS, Kind: StorageV2 -> Option B

5. Quick Check:

   Geo-redundant + unstructured data = SKU: Standard_GRS, Kind: StorageV2 [OK]

Hint: Use Standard_GRS SKU with StorageV2 kind for geo-redundant blobs [OK]

Common Mistakes:

• Choosing Premium SKU without geo-redundancy
• Using FileStorage kind for blobs
• Selecting StorageV1 which is legacy