Bird
Raised Fist0
Azurecloud~20 mins

Storage tier optimization in Azure - Practice Problems & Coding Challenges

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Challenge - 5 Problems
🎖️
Storage Tier Optimization Master
Get all challenges correct to earn this badge!
Test your skills under time pressure!
service_behavior
intermediate
2:00remaining
Understanding Azure Blob Storage Access Tiers

Which Azure Blob Storage access tier is best suited for data that is accessed less than once a month but requires immediate availability when accessed?

APremium tier
BHot tier
CCool tier
DArchive tier
Attempts:
2 left
💡 Hint

Think about balancing cost and access frequency for rarely accessed data.

Architecture
intermediate
2:00remaining
Choosing Storage Tiers for Backup Data

You need to design a backup solution in Azure for data that must be retained for years but is rarely accessed. Which storage tier should you choose to minimize cost while ensuring data durability?

AArchive tier
BHot tier
CCool tier
DStandard HDD managed disks
Attempts:
2 left
💡 Hint

Consider the lowest cost option for long-term retention with infrequent access.

Configuration
advanced
2:30remaining
Configuring Lifecycle Management for Blob Storage

Given the following lifecycle management rule JSON snippet, what will happen to blobs that have not been modified for 90 days?

{
  "rules": [
    {
      "name": "moveToCool",
      "type": "Lifecycle",
      "definition": {
        "filters": {
          "blobTypes": ["blockBlob"]
        },
        "actions": {
          "baseBlob": {
            "tierToCool": {"daysAfterModificationGreaterThan": 90}
          }
        }
      },
      "enabled": true
    }
  ]
}
ABlobs older than 90 days will be deleted automatically.
BBlobs older than 90 days will be moved to the Cool tier automatically.
CBlobs older than 90 days will be moved to the Archive tier automatically.
DNo action will be taken because the rule is disabled.
Attempts:
2 left
💡 Hint

Look at the action specified under tierToCool.

security
advanced
2:30remaining
Securing Data in Archive Tier

Which of the following is a best practice to ensure data security for blobs stored in the Archive tier in Azure Blob Storage?

AUse Azure Storage Service Encryption (SSE) with customer-managed keys.
BDisable encryption since Archive tier is already secure by default.
CStore data without access policies to improve retrieval speed.
DUse public access to allow easy data sharing.
Attempts:
2 left
💡 Hint

Think about encryption and control over keys for sensitive data.

Best Practice
expert
3:00remaining
Optimizing Cost with Automated Tiering

You manage a large dataset in Azure Blob Storage with varying access patterns. You want to minimize costs by automatically moving blobs between Hot, Cool, and Archive tiers based on usage. Which approach best achieves this?

AManually move blobs between tiers using Azure Portal every month.
BUse Azure Files instead of Blob Storage for automatic tiering.
CSet all blobs to Archive tier and restore them manually when needed.
DUse Azure Blob Storage lifecycle management policies with rules for tier transitions based on last modified date.
Attempts:
2 left
💡 Hint

Consider automation features provided by Azure Blob Storage.

Practice

(1/5)
1. Which Azure Storage tier is best for data that you access very often?
easy
A. Archive tier
B. Cool tier
C. Hot tier
D. Premium tier

Solution

  1. Step 1: Understand storage tiers purpose

    The Hot tier is designed for data accessed frequently, providing low latency and high throughput.
  2. Step 2: Match access frequency to tier

    Since the question asks for very often access, Hot tier fits best compared to Cool (infrequent) or Archive (rare).
  3. Final Answer:

    Hot tier -> Option C
  4. Quick Check:

    Frequent access = Hot tier [OK]
Hint: Hot tier = frequent access, Cool = less, Archive = rare [OK]
Common Mistakes:
  • Confusing Cool tier as best for frequent access
  • Choosing Archive tier for active data
  • Thinking Premium tier is a storage tier
2. Which Azure CLI command correctly changes a blob's tier to Cool?
easy
A. az storage blob update-tier --tier Cool --container mycontainer --blob myblob --account mystorage
B. az storage blob set-tier --tier Cool --container-name mycontainer --name myblob --account-name mystorage
C. az storage blob change-tier --tier Cool --container mycontainer --name myblob --account mystorage
D. az storage blob tier-set --tier Cool --container mycontainer --name myblob --account mystorage

Solution

  1. Step 1: Recall correct Azure CLI syntax

    The correct command to set a blob's tier is az storage blob set-tier with parameters for tier, container, blob name, and account.
  2. Step 2: Verify az storage blob set-tier --tier Cool --container-name mycontainer --name myblob --account-name mystorage matches syntax

    az storage blob set-tier --tier Cool --container-name mycontainer --name myblob --account-name mystorage uses set-tier and correct parameter names, matching Azure CLI documentation.
  3. Final Answer:

    az storage blob set-tier --tier Cool --container-name mycontainer --name myblob --account-name mystorage -> Option B
  4. Quick Check:

    Correct CLI command = az storage blob set-tier --tier Cool --container-name mycontainer --name myblob --account-name mystorage [OK]
Hint: Use 'az storage blob set-tier' to change tier [OK]
Common Mistakes:
  • Using incorrect command verbs like update-tier
  • Wrong parameter names like --container instead of --container-name
  • Mixing blob and container parameters
3. Given this Azure CLI command:
az storage blob set-tier --tier Archive --container-name logs --name log1.txt --account-name mystorage
What happens to the blob log1.txt after this command?
medium
A. Blob remains in Hot tier with no change
B. Blob is deleted permanently
C. Blob is copied to another container
D. Blob is moved to Archive tier and becomes offline until rehydrated

Solution

  1. Step 1: Understand Archive tier behavior

    Setting a blob to Archive tier moves it to a low-cost, offline storage. It cannot be read until rehydrated.
  2. Step 2: Analyze command effect

    The command sets the tier to Archive, so the blob becomes offline and inaccessible until restored.
  3. Final Answer:

    Blob is moved to Archive tier and becomes offline until rehydrated -> Option D
  4. Quick Check:

    Archive tier = offline storage [OK]
Hint: Archive tier blobs are offline until rehydrated [OK]
Common Mistakes:
  • Thinking Archive tier deletes the blob
  • Assuming blob stays accessible immediately
  • Confusing Archive with Hot tier
4. You run this command to change a blob's tier:
az storage blob set-tier --tier Hot --container-name data --name file1.csv --account-name mystorage
But you get an error saying the blob does not exist. What is the most likely cause?
medium
A. The blob name or container name is incorrect
B. The account name is invalid
C. The tier Hot is not supported
D. The Azure CLI is outdated

Solution

  1. Step 1: Understand error meaning

    An error stating the blob does not exist usually means the blob or container name is wrong or the blob was deleted.
  2. Step 2: Check other options

    Account name errors usually give different messages; Hot tier is valid; CLI outdated causes different errors.
  3. Final Answer:

    The blob name or container name is incorrect -> Option A
  4. Quick Check:

    Blob not found = wrong name [OK]
Hint: Check blob and container names first on 'not found' errors [OK]
Common Mistakes:
  • Assuming tier Hot is invalid
  • Blaming CLI version without checking names
  • Ignoring typo in blob or container names
5. You have a large dataset stored in Azure Blob Storage. You want to minimize costs but still access some data occasionally. Which tier strategy is best?
hard
A. Store frequently accessed data in Hot tier, infrequent in Cool, and rarely accessed in Archive
B. Store all data in Archive tier and never rehydrate
C. Store all data in Cool tier regardless of access frequency
D. Store all data in Hot tier for fastest access

Solution

  1. Step 1: Understand tier cost and access trade-offs

    Hot tier is expensive but fast, Cool is cheaper for infrequent access, Archive is cheapest but offline.
  2. Step 2: Apply tier optimization best practice

    Using Hot for frequent, Cool for infrequent, and Archive for rare access balances cost and performance.
  3. Final Answer:

    Store frequently accessed data in Hot tier, infrequent in Cool, and rarely accessed in Archive -> Option A
  4. Quick Check:

    Tier data by access frequency = Store frequently accessed data in Hot tier, infrequent in Cool, and rarely accessed in Archive [OK]
Hint: Match data access frequency to tier for cost savings [OK]
Common Mistakes:
  • Putting all data in Hot tier wastes money
  • Never rehydrating Archive data makes it unusable
  • Using only Cool tier ignores access patterns