Explanation:
On October 10, you can read Dep1File1.docx. = NO
Explanation: Dep1File1.docx is a blob in container1 that was uploaded on October 1 and edited on October 2.
According to the lifecycle management rule 1, any blob in container1 that has not been modified for 7 days will be moved to the archive tier. Therefore, on October 9, Dep1File1.docx will be moved to the archive tier.
Blobs in the archive tier cannot be read unless they are first rehydrated, which may take several hours or days.
Therefore, on October 10, you cannot read Dep1File1.docx unless you rehydrate it first.
On October 10, you can read File2.docx. = YES
Explanation: File2.docx is a blob in container1 that was uploaded on October 1 and edited on October 5.
According to the lifecycle management rule 1, any blob in container1 that has not been modified for 7 days will be moved to the archive tier. Therefore, on October 12, File2.docx will be moved to the archive tier.
However, on October 10, File2.docx is still in the hot tier, which means it can be read without any delay or cost.
On October 10, you can read File3.docx. = NO
Explanation: File3.docx is a blob in container1 that was uploaded on October 1 and edited on October 2.
According to the lifecycle management rule 2, any blob in container1 that has not been modified for 5 days will be deleted. Therefore, on October 7, File3.docx will be deleted from the storage account. Therefore, on October 10, you cannot read File3.docx because it no longer exists.