Move File1 to New Storage Account and Set Access Tier to Archive | Azure Storage Account Solution
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have an Azure Storage account that contains two 1-GB data files named File1 and File2. The data files are set to use the archive access tier.
You need to ensure that File1 is accessible immediately when a retrieval request is initiated.
Solution: You move File1 to a new storage account. For File1, you set Access tier to Archive.
Does this meet the goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.B
Instead use the hot access tier.
The hot access tier has higher storage costs than cool and archive tiers, but the lowest access costs. Example usage scenarios for the hot access tier include:
Data that's in active use or expected to be accessed (read from and written to) frequently.
-> Data that's staged for processing and eventual migration to the cool access tier.
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-storage-tiersNo, this solution does not meet the goal.
Moving File1 to a new storage account and setting the access tier to Archive will actually make File1 less accessible immediately when a retrieval request is initiated. This is because the Archive access tier is designed for data that is rarely accessed and has a retrieval time of several hours.
To ensure that File1 is accessible immediately when a retrieval request is initiated, it should be moved to a storage account with a different access tier, such as the Hot access tier. This access tier is designed for frequently accessed data and has a retrieval time of milliseconds.
Therefore, the correct solution would be to move File1 to a new storage account and set the Access tier to Hot.