Storage tiers (Hot, Cool, Archive) in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Azure Storage Tier Costs

You have a large amount of data that you rarely access but need to keep for compliance. Which Azure storage tier is the most cost-effective for this scenario?

A Hot tier, because it offers the lowest access latency.

B Archive tier, because it has the lowest storage cost but higher access latency.

C Cool tier, because it balances cost and access frequency.

D Premium tier, because it provides the highest performance.

💡 Hint

Think about storage cost versus access frequency and latency.

The Archive tier is designed for data that is rarely accessed and can tolerate high latency. It offers the lowest storage cost, making it ideal for compliance data that must be retained but not frequently read.

❓ service_behavior

intermediate

Accessing Data in Archive Tier

You have a blob stored in the Archive tier. What happens when you try to read this blob immediately after the request?

A The blob must be rehydrated to Hot or Cool tier first, causing a delay before access.

B The blob is instantly available for reading with no delay.

C The blob is automatically moved to Hot tier before reading.

D The read request fails because Archive tier blobs cannot be read.

💡 Hint

Consider the nature of Archive tier and how data access works.

Blobs in the Archive tier are offline and require rehydration to Hot or Cool tier before they can be read. This process takes time, causing a delay before the data is accessible.

❓ Architecture

advanced

Designing a Cost-Effective Storage Solution

You need to design a storage solution for a company that has three types of data: frequently accessed, infrequently accessed, and archival data. Which combination of Azure storage tiers should you use to optimize cost and performance?

A Use Hot tier for frequently accessed data, Cool tier for infrequently accessed data, and Archive tier for archival data.

B Use Cool tier for all data to balance cost and access.

C Store all data in Hot tier for simplicity and performance.

D Use Archive tier for all data to minimize cost.

💡 Hint

Think about matching data access patterns to storage tiers.

Using Hot tier for frequent access ensures low latency, Cool tier reduces cost for infrequent access, and Archive tier minimizes cost for long-term archival data. This combination balances cost and performance effectively.

❓ security

advanced

Data Retention and Compliance with Storage Tiers

A company must retain data for 7 years to meet compliance. They want to ensure data cannot be deleted or modified during this period. Which Azure feature combined with storage tiers supports this requirement?

A Use Hot tier with soft delete enabled.

B Use Archive tier with lifecycle management policies.

C Use Cool tier with access tier change enabled.

D Use immutable blob storage with legal hold or time-based retention policies.

💡 Hint

Think about preventing data changes or deletion for compliance.

Immutable blob storage allows setting legal holds or time-based retention policies that prevent data from being deleted or modified, ensuring compliance during the retention period regardless of storage tier.

✅ Best Practice

expert

Optimizing Cost with Lifecycle Management Policies

You want to automatically move blobs between Hot, Cool, and Archive tiers based on their last modified date to optimize costs. Which lifecycle management rule configuration correctly implements this?

Azure

{
  "rules": [
    {
      "name": "tiering-rule",
      "type": "Lifecycle",
      "definition": {
        "filters": {"blobTypes": ["blockBlob"]},
        "actions": {
          "baseBlob": {
            "tierToCool": {"daysAfterModificationGreaterThan": 30},
            "tierToArchive": {"daysAfterModificationGreaterThan": 90}
          }
        }
      }
    }
  ]
}

A Move blobs to Hot tier after 30 days and to Cool tier after 90 days of no modification.

B Move blobs to Archive tier after 30 days and to Cool tier after 90 days of no modification.

C Move blobs to Cool tier after 30 days and to Archive tier after 90 days of no modification.

D Move blobs to Cool tier after 90 days and to Archive tier after 30 days of no modification.

💡 Hint

Check the order and timing of tier transitions in the lifecycle policy.

The lifecycle policy moves blobs first to Cool tier after 30 days, then to Archive tier after 90 days, optimizing cost by gradually moving less accessed data to cheaper tiers.