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?
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-tiersThe proposed solution of moving File1 to a new storage account and setting its access tier to Archive does not meet the stated goal of ensuring that File1 is accessible immediately when a retrieval request is initiated.
The archive access tier in Azure Storage is intended for data that is rarely accessed and stored for long periods of time, such as backups or historical records. When data is in the archive tier, it is not immediately available for access, as it must first be rehydrated to the hot or cool access tier before it can be accessed. This rehydration process can take several hours to complete, during which time the data is not accessible.
Therefore, setting File1's access tier to Archive would actually make it less accessible, as it would need to be rehydrated before it can be accessed. This would result in a delay before the data is available, which is the opposite of the desired goal.
To ensure that File1 is accessible immediately when a retrieval request is initiated, it should be moved to a new storage account and have its access tier set to either Hot or Cool, depending on the frequency of access. The Hot access tier is intended for data that is accessed frequently, while the Cool access tier is intended for data that is accessed less frequently but still needs to be immediately available when accessed.