# Archive tier

> Source: Courseiva IT Certification Glossary — https://courseiva.com/glossary/archive-tier

## Quick definition

The Archive tier is a way to store data in the cloud very cheaply, but it takes a long time to get that data back when you need it. It is meant for information you want to keep for years and rarely need to look at, like old backups or compliance records. You pay a low monthly fee for storage but a higher fee when you finally need to retrieve your files.

## Simple meaning

Think of the Archive tier like putting boxes of old tax documents into a climate-controlled storage unit in a different city. You do not need those papers often, maybe once a year or less. The storage unit is very cheap per month because it is far away and the company can stack many boxes there. But when you need a specific document, you cannot just walk in and grab it. You have to submit a request, wait for a worker to find your box, and then have it shipped to you. That shipping takes hours or even a day.

In cloud computing, the Archive tier works exactly the same way. Your data lives on slow, cheap hard drives or tape-like media in a data center. You pay very little to keep it there every month. However, to read that data again, you must start a "rehydration" process. That process copies the data to a faster, online tier like Cool or Hot. During those hours, the data is unavailable. You also pay extra for the retrieval operation and any early deletion fees if you delete the data before a set time period, usually 180 days.

This tier is perfect for data that must be kept for years due to legal rules or company policies but is almost never accessed in practice. Examples include security camera footage from months ago, old email archives, or full database backups from last year. The trade-off is simple: you save a lot of money on storage, but you accept that getting the data back is slow and costs extra when it happens.

## Technical definition

The Archive tier is one of the three access tiers for Azure Blob Storage, alongside Hot and Cool. It is optimized for data that is durable but rarely accessed, with a retrieval latency of up to 15 hours for standard priority rehydration or up to 1 hour for high priority. Data stored in the Archive tier is stored offline, meaning it is not directly accessible via regular read or write operations. To access the data, you must first change the blob's access tier to Hot or Cool, a process called rehydration, which moves the data to an online tier.

From an implementation perspective, Azure stores Archive tier blobs on a separate set of storage nodes using slower, high-capacity drives and possibly magnetic tape, though Microsoft does not publicly disclose the exact media. The storage is geo-redundant by default, with options for locally redundant (LRS), zone-redundant (ZRS), or geo-zone-redundant (GZRS) storage, depending on the account configuration. The minimum storage duration for Archive tier is 180 days. If you delete or move the blob before 180 days, you incur an early deletion charge equal to the remaining days of storage cost.

Rehydration can be initiated via the Azure portal, Azure CLI, PowerShell, or SDKs using the Set Blob Tier operation. There are two rehydration priorities: Standard, which takes up to 15 hours, and High, which can complete in under 1 hour. High priority is available for blobs under 10 GB and costs more. During rehydration, the blob remains in the Archive tier until the operation completes, after which it transitions to the target tier. You cannot read or modify the blob while it is rehydrating. The rehydration process involves internal data movement, checksums for integrity, and eventual metadata update on the storage front end.

From an exam perspective for AZ-104, you should understand how to configure the Archive tier through Azure Blob Storage lifecycle management rules, which can automatically move blobs from Hot to Cool to Archive based on age. You also need to know how to estimate costs, including the monthly storage fee, the retrieval cost, and early deletion penalties. The Archive tier supports all blob types-block blobs, append blobs, and page blobs (for unmanaged disks only). However, it does not support Azure Files or disk storage for virtual machines. Knowing the difference between rehydration options and how to monitor rehydration progress using storage metrics is also exam relevant.

## Real-life example

Imagine you run a small medical clinic. By law, you must keep patient records for at least seven years after the last visit. You have paper files for thousands of patients, filling up entire rooms in your building. Office space is expensive, and those files are rarely opened after the first year. To save money, you decide to move all files older than one year into a rented shipping container in a lot outside town. The container costs very little per month compared to your prime office space. However, when a patient requests their records, you cannot just pull a folder from a filing cabinet. You must drive to the lot, unlock the container, find the right box, and bring it back to the office. That trip takes a few hours.

The Azure Archive tier works exactly this way. Your data (the patient records) is moved to inexpensive long-term storage (the shipping container) automatically after one year, using a lifecycle policy. While the data is in the Archive tier, you pay a low monthly rate for the storage space. But if you need to read that data again, you must "rehydrate" it, which is like taking that trip to the container. The data is copied back to the Hot or Cool tier, which is your fast office filing system. This rehydration takes time-up to 15 hours for standard requests, or one hour if you pay a premium for high priority. During rehydration, you cannot access the data. This is perfect for compliance data or old backups that you almost never need but must keep for years.

## Why it matters

In real IT environments, storage costs can quickly become a huge portion of the cloud budget. Many organizations have vast amounts of data that must be retained for legal, regulatory, or business reasons, but that data is rarely accessed after a few months. Without an Archive tier, companies would pay full Hot-tier prices month after month for data that is essentially sitting dead. This would waste thousands of dollars annually. The Archive tier solves that problem by offering a storage option at roughly one-tenth the cost of Hot storage.

For IT professionals, using the Archive tier effectively means implementing lifecycle management policies that automatically transition data from Hot to Cool to Archive based on its age and access patterns. It also means planning for retrieval time: if you need to recover data from an archive, you must allow hours of lead time. This is important for disaster recovery planning and compliance audits. You cannot treat Archive tier data like a hot backup that can be restored instantly.

Another practical consideration is the early deletion fee. If you mistakenly store data in the Archive tier and then delete it after 90 days, you will be charged for the remaining 90 days of the minimum 180-day period. So understanding the cost model is crucial for budgeting. Azure also charges for data retrieval operations, and the price varies by rehydration priority. All these factors make the Archive tier a powerful cost-saving tool, but only when used with careful planning and proper automation.

## Why it matters in exams

For the Microsoft Azure Administrator exam (AZ-104), the Archive tier is a core topic under the "Manage Azure storage" objective. You are expected to understand the differences between Hot, Cool, and Archive tiers, including cost trade-offs, access latency, and lifecycle management. The exam will test your ability to configure storage accounts with the correct tier and to implement policies that move data automatically.

In exam questions, you might see a scenario where a company has compliance data that must be kept for seven years but accessed only quarterly. You would need to choose the right storage tier-likely Cool for data accessed quarterly, moving to Archive after a year of no access. You must also know that Archive tier blobs cannot be read directly; they must be rehydrated first. Questions may ask you to select the correct PowerShell command or Azure CLI command to change a blob's tier or to set up a lifecycle management rule.

Another exam angle is cost calculation. You might be given a scenario with a storage account storing 100 GB of data and asked to compute the monthly cost if the data is in Archive versus Hot. You need to know that Archive has no retrieval cost for storage itself but charges for read operations and early deletion. The exam also covers high-priority rehydration for time-sensitive retrievals, and the fact that archive storage supports block blobs and append blobs but not page blobs for managed disks.

The AZ-104 exam often includes multiple-choice questions with a single correct answer and scenario-based questions where you must select the correct combination of actions. For example, you might be asked to enable lifecycle management and then create a rule to move blobs to Archive after 180 days. You should also know how to check the status of a rehydration operation using Azure Monitor or Storage Analytics logs.

## How it appears in exam questions

The Archive tier appears in AZ-104 exam questions in several common patterns. One frequent question type is a scenario-based question where you are given storage costs and access patterns and asked to recommend the most cost-effective tier. For example: a company has 500 GB of backup data that is accessed only once a year for compliance auditing. You must choose between Hot, Cool, and Archive, considering retrieval latency and cost. The correct answer is Archive, but you must also mention that rehydration will take up to 15 hours and that early deletion charges apply if data is deleted before 180 days.

Another pattern involves lifecycle management rules. The question might describe a storage account with log files that are accessed frequently for the first 30 days, occasionally for the next 90 days, and then never again. You need to configure a rule that moves blobs from Hot to Cool after 30 days and from Cool to Archive after 120 days. The exam tests whether you know the exact syntax for the rule in JSON or using Azure Portal steps.

Command-line questions are also common. For example: "You need to change the access tier of a blob named 'backup.vhdx' in container 'archives' to Archive. Which Azure CLI command should you use?" The correct answer involves `az storage blob set-tier` with the `--tier Archive` parameter. You might also be asked how to rehydrate a blob with high priority using PowerShell, where the answer includes the `-Priority High` parameter.

Troubleshooting questions sometimes appear: a user reports that they cannot read a file stored in Archive tier. The solution is to rehydrate the blob first. Another question might show a cost spike and ask why the bill is high-the answer could be early deletion charges from moving blobs out of Archive before 180 days. Understanding these patterns helps you quickly eliminate wrong answers and focus on the correct technical decision.

## Example scenario

Your company, Contoso Ltd., has a video surveillance system that records 24/7 footage from 50 cameras. Each camera generates approximately 10 GB of video per day. That is 500 GB of new video every day, or roughly 15 TB per month. The company policy requires retaining all footage for two years for security audits. After three months, the footage is almost never accessed unless an incident occurs. Currently, all footage is stored in the Hot tier in Azure Blob Storage, costing about $0.018 per GB per month. For 15 TB of new data per month, that is roughly $270 per month just for the new storage, and the total bill grows every month as old data accumulates.

You are asked to reduce storage costs. Your solution is to implement an Azure Blob Storage lifecycle management policy. You create a rule that moves all blobs older than 90 days from the Hot tier to the Cool tier, and then moves blobs older than 365 days to the Archive tier. The footage older than 365 days is rarely accessed, so waiting up to 15 hours for rehydration is acceptable. This reduces the monthly storage cost for the older data from $270 per TB per month to about $0.002 per GB per month for Archive, which is roughly $30 per TB per month. Over the two-year retention period, this saves the company tens of thousands of dollars.

In the event of an incident, the security team can initiate a rehydration of the relevant video files using high priority if needed, paying a premium for faster access. The lifecycle rule runs daily, automatically moving blobs without manual intervention. You also configure alerts to notify if any rehydration operations are unusually slow or if early deletion charges are incurred. This example shows how the Archive tier fits into a real-world scenario where massive amounts of data must be retained cheaply.

## Common mistakes

- **Mistake:** Thinking you can read data directly from the Archive tier without rehydration.
  - Why it is wrong: Archive tier blobs are stored offline. Any read operation fails until the blob is moved to Hot or Cool tier via rehydration, which takes hours.
  - Fix: Always initiate a rehydration operation before trying to access the data, and adjust your application to expect delays.
- **Mistake:** Assuming Archive tier has the same latency as Cool or Hot tier.
  - Why it is wrong: Archive tier is designed for long-term storage with high latency. Standard rehydration can take up to 15 hours, while Hot and Cool are accessible immediately.
  - Fix: Use Archive only for data that can tolerate hours of retrieval delay, and use a lifecycle policy to promote data to cooler tiers automatically.
- **Mistake:** Forgetting about the 180-day minimum storage duration and early deletion fees.
  - Why it is wrong: If you delete or move data out of Archive before 180 days, you are charged for the remaining days at the Archive rate. This can surprise users who delete data early.
  - Fix: Plan to keep data in Archive for at least 180 days, or accept the early deletion cost as part of your budget.
- **Mistake:** Applying Archive tier to data that is accessed frequently, like every week.
  - Why it is wrong: Frequent rehydrations incur high retrieval costs and slow performance, making Archive more expensive and impractical than Hot storage.
  - Fix: Use Hot or Cool tier for frequently accessed data. Archive is only cost-effective for data accessed less than once a year.

## Exam trap

{"trap":"An exam question shows a scenario where a user needs to access archived data urgently within 30 minutes and asks you to set the blob tier to Archive.","why_learners_choose_it":"Learners see that Archive is the cheapest tier and assume it can be used for any long-term storage need. They ignore the latency requirement.","how_to_avoid_it":"Always check the recovery time requirement. If access is needed in under an hour, use Cool tier or high-priority rehydration (which can take up to an hour). Archive has a standard rehydration window of up to 15 hours, so it is unsuitable for urgent access. The correct choice for fast retrieval is Cool or Hot, not Archive."}

## Commonly confused with

- **Archive tier vs Cool tier:** Cool tier is for data that is accessed infrequently, generally every few months, and has a lower storage cost than Hot but higher than Archive. Data in Cool tier is online and accessible immediately, with no rehydration delay. Archive is offline and requires hours to retrieve. (Example: Monthly sales reports that are accessed quarterly stay in Cool tier. Old tax records accessed once every five years go to Archive.)
- **Archive tier vs Hot tier:** Hot tier is for data accessed frequently, optimized for high throughput and low latency. It has the highest storage cost but no retrieval delay. Archive has the lowest storage cost but the highest latency. You would never use Hot for archival data because it wastes money. (Example: Current website images are in Hot tier. Two-year-old backup logs are in Archive tier.)
- **Archive tier vs Azure Backup (long-term retention):** Azure Backup is a service that creates and manages backup snapshots, and it can store those backups in archive storage automatically. The Archive tier is a storage layer within Blob Storage, while Azure Backup is a separate service that leverages blob storage tiers. You configure Azure Backup policies to move recovery points to archive, but the underlying storage mechanism is the same Archive tier. (Example: Azure Backup handles scheduling and retention policies. The actual data ends up in Archive tier blobs for cheap, long-term retention.)

## Step-by-step breakdown

1. **Create or identify a storage account** — You need a general-purpose v2 storage account in Azure. This account type supports all access tiers, including Archive. The storage account can be located in any region, and you should choose replication based on your durability needs.
2. **Upload data as a block blob or append blob** — Archive tier supports block blobs and append blobs but not page blobs for managed disks. Upload your file using Azure Portal, AzCopy, or SDK. You can set the tier to Archive at upload time, or upload to Hot/Cool and then change the tier later.
3. **Set the blob's access tier to Archive** — Use the Set Blob Tier operation via Portal, CLI, or PowerShell. Once the tier is set to Archive, the blob is moved to offline storage. You cannot read it directly anymore. The blob's metadata remains available for listing and tier settings.
4. **Rehydrate the blob when access is needed** — Change the blob's tier back to Hot or Cool using the same Set Blob Tier operation. Choose standard priority (up to 15 hours) or high priority (up to 1 hour, for blobs under 10 GB). The blob stays in Archive during rehydration and becomes available after the operation completes.
5. **Automate tier changes with lifecycle management** — Create a lifecycle management rule in the storage account that moves blobs from Hot to Cool after a certain number of days, and from Cool to Archive after more days. This automates cost savings without manual intervention.
6. **Monitor costs and rehydration status** — Use Azure Monitor to track storage costs and rehydration success. Check for early deletion charges and rehydration failures. Alerts can be set for unusual activity, like frequent rehydrations that might indicate an incorrect tier choice.

## Practical mini-lesson

As an Azure administrator, you will frequently need to balance storage cost against accessibility. The Archive tier is your cheapest option, but it forces a trade-off: retrieval time. In practice, you should never manually move blobs to Archive one by one. Instead, configure lifecycle management policies at the storage account level. These policies evaluate all blobs in a container or folder and automatically change their tier based on age or last modified date.

When writing a lifecycle rule, you define a rule set in JSON that specifies the actions, such as "move to Cool after 30 days" and "move to Archive after 365 days." The rule set also includes filters to apply only to certain blob types or prefixes. For example, you can target only blobs in the "logs" container that have the prefix "archive/" to move them to Archive after 90 days. This fine-grained control prevents accidental archiving of active data.

One key operational concern is rehydration performance. If you have a compliance audit requiring access to archived data, you need to plan ahead. Standard rehydration can take up to 15 hours, so you might start the process the night before. High priority reduces this to under an hour but costs more and has a 10 GB blob size limit. Always test rehydration with a sample blob to understand actual times in your region, as performance varies.

Another practical issue is early deletion. If a business requirement changes and you need to delete archived data after only 60 days, you will pay an early deletion fee equivalent to the remaining 120 days of Archive storage cost. To avoid this, either commit to the 180-day minimum or calculate the penalty into your project budget. You can track these charges in the Azure cost analysis reports under the "Data stored" and "Early deletion" meters.

Finally, security is important. Archive tier blobs are encrypted at rest by default using Azure Storage Service Encryption (SSE). You can also use customer-managed keys or Azure Policy to enforce archiving rules. Remember that while the blob is offline, it cannot be accessed by any user or service, including Azure Backup. This makes Archive tier safe for sensitive data that must be retained but rarely viewed.

## Memory tip

Think AAA: Archive is Absolutely for Ancient data. If you need it within a day, think Cool, not Archive.

## FAQ

**Can I write data directly to the Archive tier?**

Yes, you can set the access tier to Archive when uploading a blob using Azure Portal, CLI, or SDK. The data is immediately stored offline.

**How long does rehydration take?**

Standard priority rehydration can take up to 15 hours. High priority rehydration can complete in under 1 hour but is limited to blobs under 10 GB and costs more.

**What happens if I delete a blob from Archive before 180 days?**

You incur an early deletion charge equal to the remaining days of the 180-day minimum storage period, prorated at the Archive storage rate.

**Does the Archive tier support all blob types?**

It supports block blobs and append blobs. Page blobs used for managed disks are not supported in the Archive tier.

**Can I use Archive tier with Azure Backup?**

Yes, Azure Backup can move recovery points to Archive tier for long-term retention, but the underlying storage is still Blob Storage Archive tier.

**Is data in Archive tier encrypted?**

Yes, data is encrypted at rest using Azure Storage Service Encryption (SSE) by default. You can also use customer-managed keys.

## Summary

The Archive tier is a cost-effective storage option in Azure Blob Storage for data that is rarely accessed and can tolerate retrieval delays of hours. It offers the lowest storage cost among the three access tiers but requires rehydration to make data available again. This tier is ideal for long-term compliance, archival backups, and historical logs.

For IT professionals and AZ-104 exam candidates, understanding the Archive tier means knowing its cost structure, rehydration mechanics, lifecycle management integration, and when to choose it over Cool or Hot tiers. Common pitfalls include forgetting about rehydration latency, early deletion fees, and applying it to frequently accessed data. The exam tests you on scenario-based decisions, lifecycle rule configuration, and troubleshooting storage access issues.

Remember the trade-off: you save money on storage, but you pay in time and retrieval costs. Use lifecycle policies to automate tier transitions and always plan for rehydration windows. The Archive tier is a powerful tool for managing cloud storage budgets, but only when used correctly.

---

Practice questions and the full interactive page: https://courseiva.com/glossary/archive-tier