Blob containers and access levels in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a blob container with private access level.

Azure

az storage container create --name mycontainer --account-name mystorageaccount --public-access [1]

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

Aprivate

Bcontainer

Cblob

Dpublic

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'blob' or 'container' instead of 'private' makes the container publicly accessible.

Using 'public' is not a valid access level.

The private access level means the container and blobs are not accessible publicly.

2fill in blank

medium

Complete the code to set the container's access level to allow public read access for blobs only.

Azure

az storage container set-permission --name mycontainer --account-name mystorageaccount --public-access [1]

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

Anone

Bprivate

Ccontainer

Dblob

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'container' grants public read access to both blobs and container metadata.

Using 'private' disables public access.

The blob access level allows public read access to blobs but not to container metadata.

3fill in blank

hard

Fix the error in the command to create a container with public read access to blobs and container metadata.

Azure

az storage container create --name mycontainer --account-name mystorageaccount --public-access [1]

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

Ablob

Bnone

Ccontainer

Dprivate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'blob' only allows public read access to blobs, not container metadata.

Using 'private' disables public access.

The container access level allows public read access to blobs and container metadata.

4fill in blank

hard

Fill both blanks to create a container with public read access to blobs and then check its access level.

Azure

az storage container create --name mycontainer --account-name mystorageaccount --public-access [1]
az storage container show --name mycontainer --account-name mystorageaccount --query [2]

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

Ablob

Bcontainer

CpublicAccess

DaccessLevel

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'container' instead of 'blob' changes the access level.

Querying 'accessLevel' instead of 'publicAccess' returns no result.

Use blob to set public read access to blobs only, and query publicAccess to check the access level.

5fill in blank

hard

Fill all three blanks to update a container's access level to private, verify it, and then delete the container.

Azure

az storage container set-permission --name mycontainer --account-name mystorageaccount --public-access [1]
az storage container show --name mycontainer --account-name mystorageaccount --query [2]
az storage container delete --name [3] --account-name mystorageaccount

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

Aprivate

BpublicAccess

Cmycontainer

DcontainerName

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong container name in delete command.

Using incorrect query parameter for access level.

Setting access level to 'blob' or 'container' instead of 'private'.

Set access to private, query publicAccess to verify, and delete the container named mycontainer.