Storage tier optimization in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the storage account's access tier to hot.

Azure

az storage account update --name myStorageAccount --resource-group myResourceGroup --access-tier [1]

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

Ahot

Bcool

Carchive

Dstandard

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'cool' or 'archive' which are for less frequent access.

The --access-tier parameter sets the storage tier. 'hot' is for frequently accessed data.

2fill in blank

medium

Complete the code to create a lifecycle management rule that moves blobs to the cool tier after 30 days.

Azure

az storage account management-policy create --account-name myStorageAccount --resource-group myResourceGroup --policy '{"rules": [{"name": "moveToCool", "enabled": true, "type": "Lifecycle", "definition": {"actions": {"baseBlob": {"tierToCool": {"daysAfterModificationGreaterThan": [1], "filters": {"blobTypes": ["blockBlob"]}}}]}'

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

A15

B90

C30

D60

Attempts:

3 left

💡 Hint

Common Mistakes

Using 15 or 60 days which do not match the requirement.

The rule moves blobs to the cool tier after 30 days of no modification.

3fill in blank

hard

Fix the error in the lifecycle policy JSON to correctly archive blobs after 180 days.

Azure

"actions": {"baseBlob": {"tierToArchive": {"daysAfterModificationGreaterThan": [1]

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

A30

B365

C90

D180

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 30 or 90 days which are too short for archiving.

Archiving blobs after 180 days is the correct setting for long-term storage.

4fill in blank

hard

Fill both blanks to define a lifecycle rule that deletes blobs after 365 days and moves them to archive after 180 days.

Azure

"actions": {"baseBlob": {"tierToArchive": {"daysAfterModificationGreaterThan": [1], "delete": {"daysAfterModificationGreaterThan": [2]

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

A180

B365

C90

D30

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the numbers or using incorrect days.

The rule moves blobs to archive after 180 days and deletes them after 365 days.

5fill in blank

hard

Fill all three blanks to create a lifecycle policy that moves blobs to cool after 30 days, archive after 90 days, and deletes after 365 days.

Azure

"actions": {"baseBlob": {"tierToCool": {"daysAfterModificationGreaterThan": [1], "tierToArchive": {"daysAfterModificationGreaterThan": [2], "delete": {"daysAfterModificationGreaterThan": [3]

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

A30

B90

C365

D180

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the order or using wrong day values.

The lifecycle policy moves blobs to cool after 30 days, archive after 90 days, and deletes after 365 days.