A financial services company uses a General-purpose v2 (GPv2) storage account to store transactional record files. The files are frequently accessed during the first 30 days after creation to process active client requests. Between day 31 and day 365, the records are rarely accessed but must remain online to support regulatory compliance audits that require a retrieval latency of less than one second. After one year (365 days), the records must be permanently deleted. Which lifecycle management policy rule configuration meets these requirements while minimizing storage costs?
- Transition the blobs to the Cool tier 30 days after creation, and delete the blobs 365 days after creation.Cevap
- BTransition the blobs to the Archive tier 30 days after creation, and delete the blobs 365 days after creation.
- CTransition the blobs to the Cool tier 30 days after creation, transition the blobs to the Archive tier 90 days after creation, and delete the blobs 365 days after creation.
- DTransition the blobs to the Archive tier immediately after creation, and delete the blobs 365 days after creation.
Cevap
Transition the blobs to the Cool tier 30 days after creation, and delete the blobs 365 days after creation.
Transitioning the blobs to the Cool tier 30 days after creation and deleting them after 365 days satisfies all constraints. The Cool tier offers lower storage costs than the Hot tier while keeping the data online and accessible within milliseconds, ensuring compliance audits requiring sub-second latency are successful. Deletion at day 365 aligns with the retention rules.
Adım Adım Çözüm
Anahtar Kavram
Azure Blob Storage lifecycle management policies automate tier transitions and deletion. While Hot and Cool tiers are online and offer sub-second retrieval times, the Archive tier is offline and requires a rehydration process that takes several hours. Therefore, data with low-latency access requirements must not be transitioned to the Archive tier.
Tahmini Süre:1m 30s