How well do you know Azure Archive storage tier Question Title * 1. Does Archive storage tier provide Availability SLA Yes , 99.9 There is no availability SLA for Archive storage tier. Yes , 99.99 OK Question Title * 2. Are there any difference in scalability and performance targets with Archive storage tier in comparison to Hot and Cold storage tiers Yes , there are differences in regards to scalability and performance targets No , there are no differences in regards to scalability and performance targets OK Question Title * 3. Are there any Latency when extracting data from Azure archive storage No there are no latency when extracting data from Azure archive storage Yes , there is 10 hours latency Yes , there is 15 hours latency OK Question Title * 4. What is the status message "During rehydration" that help you to check the Archive Status blob property to confirm if the tier has changed? rehydrate-pending-to-hot or rehydrate-pending-to-cool pending-to-hot or pending-to-cool There wont be any status message OK Question Title * 5. Rehydrating several small blobs concurrently may add additional time VsLarge blob sizes are strongly recommended for optimal performance. Is the statement true or false ? True False OK Question Title * 6. Is it possible to read data from archive storage? If you need to read the data , you need to change the storage tier (change the tier of the blob to hot or cool.) You can directly change the storage directly OK Question Title * 7. Does Azure archive storage provide RA-GRS Yes , Azure archive storage provides RA-GRS No , Azure archive storage dosent provide RA-GRS OK Question Title * 8. What is Blob rehydration The process of moving Archive storage tier hot or cool is known as Rehydration. Process to change the state of the existing state of data. OK Question Title * 9. How are the write operations charged for moving blob-level tiering from hot->cool, hot->archive, or cool->archive Billed as a write of the source tier. Billed as a write of the destination tier. OK Question Title * 10. How is the read operation charged for reading blob-level tiering archive->cool, archive->hot, or cool->hot Operation is billed as a read from the source tier. Operation is billed as a read from the destination tier. OK DONE