File shares (Azure Files) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure file share using Azure CLI.

Azure

az storage share create --name [1] --account-name mystorageaccount

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

Amyblob

Bmycontainer

Cmyfileshare

Dmydisk

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'mycontainer' which is for blob containers, not file shares.

Using 'myblob' which is for blobs, not file shares.

The az storage share create command creates a file share. The --name parameter specifies the file share name, such as myfileshare.

2fill in blank

medium

Complete the code to mount an Azure file share on a Linux machine using SMB protocol.

Azure

sudo mount -t cifs //mystorageaccount.file.core.windows.net/[1] /mnt/myfileshare -o vers=3.0,username=mystorageaccount,password=mypassword,dir_mode=0777,file_mode=0777,serverino

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

Amyfileshare

Bmycontainer

Cmyblob

Dmydisk

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'mycontainer' which is for blob storage.

Using 'myblob' which is not a file share.

The mount command requires the file share name after the storage account URL. Here, myfileshare is the correct file share name.

3fill in blank

hard

Fix the error in the Azure CLI command to upload a file to an Azure file share.

Azure

az storage file upload --share-name myfileshare --source ./localfile.txt --path [1] --account-name mystorageaccount

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

Amyblob

Bmyfileshare

Cmycontainer

DremoteFile.txt

Attempts:

3 left

💡 Hint

Common Mistakes

Using the share name as the path.

Using container or blob names instead of a file name.

The --path parameter specifies the destination file name in the file share. It should be the file name like remoteFile.txt, not a share or container name.

4fill in blank

hard

Fill both blanks to create a file share and set its quota to 100 GB using Azure CLI.

Azure

az storage share create --name [1] --account-name mystorageaccount --quota [2]

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

Aprojectfiles

B50

C100

Dbackupshare

Attempts:

3 left

💡 Hint

Common Mistakes

Setting quota to a string with units like '100GB' instead of just '100'.

Using a container name instead of a file share name.

The --name parameter is the file share name, here projectfiles. The --quota parameter sets the size limit in GB, here 100.

5fill in blank

hard

Fill all three blanks to upload a file, set metadata, and list files in an Azure file share using Azure CLI.

Azure

az storage file upload --share-name [1] --source ./data.txt --path data.txt --account-name mystorageaccount && az storage file metadata update --share-name [2] --path data.txt --metadata [3] --account-name mystorageaccount && az storage file list --share-name [1] --account-name mystorageaccount

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

Adatashare

Cenv=prod

Denv=dev

Attempts:

3 left

💡 Hint

Common Mistakes

Using different share names for upload and metadata update.

Setting metadata with spaces or incorrect format.

The file share name is datashare for upload and metadata update. Metadata is set as key=value pairs like env=prod.

Practice

1. What is the primary purpose of Azure Files in cloud infrastructure?

easy

A. To create virtual networks for Azure resources

B. To provide cloud-based file shares accessible via SMB or NFS protocols

C. To manage databases in the cloud

D. To host virtual machines in Azure

Solution

1. Step 1: Understand Azure Files functionality

   Azure Files offers file shares in the cloud that can be accessed using SMB or NFS protocols, allowing easy file sharing.

2. Step 2: Compare other options

   Options A, B, and C describe other Azure services unrelated to file sharing.

3. Final Answer:

   To provide cloud-based file shares accessible via SMB or NFS protocols -> Option B

4. Quick Check:

   Azure Files = Cloud file shares [OK]

Hint: Azure Files = cloud file shares via SMB/NFS [OK]

Common Mistakes:

• Confusing Azure Files with virtual machines
• Thinking Azure Files manages databases
• Mixing Azure Files with networking services

2. Which of the following is the correct way to set a quota for an Azure file share using Azure CLI?

easy

A. az storage file set-quota --name myshare --quota 100

B. az storage share create --name myshare --quota 100 --account-name mystorage

C. az storage account set-quota --name myshare --quota 100

D. az storage share update --name myshare --quota 100 --account-name mystorage

Solution

1. Step 1: Identify the correct Azure CLI command for setting quota

   The command to set a quota on an existing Azure file share is az storage share update.

2. Step 2: Verify command parameters

   The command requires the share name, quota size, and storage account name, matching az storage share update --name myshare --quota 100 --account-name mystorage.

3. Final Answer:

   az storage share update --name myshare --quota 100 --account-name mystorage -> Option D

4. Quick Check:

   Set quota = az storage share update [OK]

Hint: Use 'az storage share update --quota' to set file share quota [OK]

Common Mistakes:

• Using 'create' command instead of 'update'
• Confusing storage account quota with share quota
• Using incorrect command names like 'file set-quota'

3. Given the following Azure CLI commands, what will be the quota size of the file share named datafiles?

az storage share create --name datafiles --quota 50 --account-name mystorage
az storage share update --name datafiles --quota 200 --account-name mystorage

medium

A. 200 GB

B. 50 GB

C. 250 GB

D. Quota not set

Solution

1. Step 1: Analyze the initial quota setting

   The file share datafiles is created with a quota of 50 GB.

2. Step 2: Analyze the quota update command

   The quota is then updated to 200 GB using the update command, which overrides the initial quota.

3. Final Answer:

   200 GB -> Option A

4. Quick Check:

   Last quota set = 200 GB [OK]

Hint: Last quota command overrides previous quota [OK]

Common Mistakes:

• Adding quotas instead of overriding
• Assuming initial quota remains unchanged
• Ignoring the update command effect

4. You run the command az storage share update --name myshare --quota 500 --account-name mystorage but receive an error. What is the most likely cause?

medium

A. The share name contains invalid characters

B. The storage account name is missing

C. The quota value exceeds the maximum allowed size for the storage account

D. The command syntax is incorrect

Solution

1. Step 1: Check quota limits for Azure file shares

   Azure file shares have maximum quota limits depending on the storage account type. Setting a quota too large causes an error.

2. Step 2: Verify other command parts

   The share name and account name appear valid and present, and the command syntax matches the correct format.

3. Final Answer:

   The quota value exceeds the maximum allowed size for the storage account -> Option C

4. Quick Check:

   Quota too large causes error [OK]

Hint: Check quota limits before setting large sizes [OK]

Common Mistakes:

• Assuming syntax error without checking quota size
• Ignoring storage account quota limits
• Mistaking missing parameters for invalid names

5. You want to share files between multiple Azure VMs securely using Azure Files. Which of the following steps should you take to ensure secure access to the file share?

hard

A. Create an Azure file share with SMB protocol and use Azure AD authentication with role-based access control

B. Create an Azure file share with public access enabled so all VMs can connect without credentials

C. Use NFS protocol without authentication to simplify access

D. Store files locally on each VM instead of using Azure Files

Solution

1. Step 1: Identify secure access methods for Azure Files

   Azure Files supports SMB with Azure AD authentication and role-based access control to secure file shares.

2. Step 2: Evaluate other options for security

   Public access (Create an Azure file share with public access enabled so all VMs can connect without credentials) is insecure, NFS without authentication (Use NFS protocol without authentication to simplify access) is insecure, and storing files locally (Store files locally on each VM instead of using Azure Files) does not share files across VMs.

3. Final Answer:

   Create an Azure file share with SMB protocol and use Azure AD authentication with role-based access control -> Option A

4. Quick Check:

   Secure Azure Files = SMB + Azure AD + RBAC [OK]

Hint: Use SMB with Azure AD and RBAC for secure file shares [OK]

Common Mistakes:

• Enabling public access for file shares
• Using NFS without authentication
• Not using centralized file sharing