An enterprise is designing a lifecycle management policy for audit logs stored in a General-purpose v2 (GPv2) Azure Blob Storage account. The logs must adhere to the following requirements:
- The logs must be frequently accessed and analyzed for the first days after creation.
- Between day and day , the logs are rarely accessed but must remain available for immediate, sub-second retrieval to support unexpected security audits.
- After days, the logs are only retained for historical compliance, can tolerate retrieval latencies of up to hours, and must be stored at the lowest possible cost.
- The logs must be automatically deleted days after creation.
Which two actions should you include in the lifecycle management policy? (Choose two.)
- Transition blobs to the Cool tier days after last modificationAnswer
- Transition blobs to the Archive tier days after last modificationAnswer
- CTransition blobs to the Archive tier days after last modification
- DTransition blobs to the Archive tier days after last modification
Answer
The correct configuration transitions blobs to the Cool tier days after modification, and transitions blobs to the Archive tier days after modification.
The correct configuration transitions blobs to the Cool tier days after modification to save costs while maintaining sub-second retrieval times, and then transitions them to the Archive tier days after modification when high retrieval latency is acceptable. This ensures that the blobs spend days in the Archive tier before deletion at day , satisfying the -day minimum retention threshold and avoiding early deletion fees.
Step-by-Step Solution
Key Concept
Azure Storage lifecycle management allows automated tier transitions (Hot to Cool, Cool to Archive) and deletion based on blob modification or creation age. The design must balance access tier latency, storage costs, and minimum retention periods (such as days for the Archive tier) to avoid early deletion penalties.