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?
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.
You have a blob stored in the Archive tier. What happens when you try to read this blob immediately after the request?
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.
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?
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.
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?
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.
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?
{
"rules": [
{
"name": "tiering-rule",
"type": "Lifecycle",
"definition": {
"filters": {"blobTypes": ["blockBlob"]},
"actions": {
"baseBlob": {
"tierToCool": {"daysAfterModificationGreaterThan": 30},
"tierToArchive": {"daysAfterModificationGreaterThan": 90}
}
}
}
}
]
}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.