Set Rehydration Priority in Azure Blob Archive Tier: Options and Methods
Question
Fabrikum Construction Inc uses the Azure Blob Archive tier to store petabytes of structured and semi-structured data that requires long-term storage, and high latency (around an hour) is acceptable.
The data in the archive requires an update.
To modify data in the Blob archive tier, rehydration of blobs is required.
What are the two possible ways to set the Rehydration priority in the Blob Archive tier?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answers: B and D.
The Azure Blob Archive tier is designed for long-term storage of rarely accessed data, and the data in this tier has a high latency of around an hour. If any modifications need to be made to the data stored in the Blob Archive tier, the blobs need to be rehydrated, which means the data is moved from the archive to the hot or cool tier.
Rehydration can take a while, depending on the size and number of blobs. To prioritize the rehydration process, Azure offers different rehydration options with different priorities. The following are the two possible ways to set the rehydration priority in the Blob Archive tier:
Standard Priority - This is the default rehydration option. When you select this option, Azure rehydrates the blobs as resources become available. This means that rehydration may take several hours to complete, depending on the amount of data and the available resources.
High Priority - This rehydration option moves the data to the hot or cool tier as soon as possible, but it may take longer to complete. If other processes are using resources, the rehydration may be paused temporarily until sufficient resources become available.
Therefore, A and D are the correct answers: A for Premium Priority and D for Standard Priority, while C (Dedicated Priority) and B (High Priority) are not valid options for setting rehydration priority in the Blob Archive tier.
