An enterprise is designing a data storage and retention strategy for three distinct datasets in Azure Blob Storage:
* Audit reports: These reports are accessed frequently for the first 30 days after generation. Between 30 and 180 days, they are accessed occasionally and must be available immediately with sub-second retrieval latency. After 180 days, they are rarely accessed, and a retrieval latency of up to 15 hours is acceptable. The reports must be deleted after 3 years ( days).
* Transactional ledger data: This data must be stored in a write-once, read-many (WORM) state to meet strict compliance regulations. The data cannot be modified or deleted for 7 years ( days) and is queried by an automated auditing system that requires real-time (sub-second) access.
* Temporary debug logs: These logs are generated daily and are only kept for 45 days to assist in active troubleshooting. They are rarely accessed, but when they are, a retrieval latency of up to 15 hours is acceptable.
You need to design a storage tiering and retention solution that minimizes costs while meeting all regulatory and performance requirements.
Which two configurations should you include in the design? (Select TWO)
- Configure a lifecycle management policy for the audit reports container to transition blobs to the Cool tier after 30 days, transition them to the Archive tier after 180 days, and delete them after 1095 days.Cevap
- Configure a locked time-based retention policy on the ledger data container with a retention period of 2555 days.Cevap
- CConfigure a lifecycle management policy for the audit reports container to transition blobs to the Archive tier after 30 days, using high-priority rehydration to satisfy the sub-second retrieval requirement.
- DConfigure a lifecycle management policy for the temporary debug logs container to transition blobs to the Archive tier after 10 days and delete them after 45 days.