Examkin

Question

Difficulty: HardData Lifecycle Management and Retention

An enterprise is designing a data storage solution for a system that generates transactional log blobs in a General-purpose v2 Azure Storage account.

The storage design must meet the following requirements:
* Logs must be accessed frequently and immediately during the first 30 days.
* Between day 31 and day 180, access is infrequent, but any query must return results with sub-second retrieval latency.
* After 180 days, the logs must be retained for a compliance period of 5 years. During this period, retrieval latency of up to 15 hours is acceptable, and storage costs must be minimized.
* The logs must be protected against deletion and modification by all users, including administrators, during the 5-year compliance period.

Which two of the following actions should you include in the design to meet these requirements?

  1. Create a lifecycle management rule that transitions blobs to the Cool tier 30 days after creation, and to the Archive tier 180 days after creation.Answer
  2. Configure a locked time-based retention policy on the blob container.Answer
  3. C
    Create a lifecycle management rule that transitions blobs to the Archive tier 30 days after creation.
  4. D
    Create a lifecycle management rule that transitions blobs to the Archive tier 90 days after creation.

Answer

Configure a lifecycle management rule to transition blobs to the Cool tier after 30 days and the Archive tier after 180 days, and configure a locked time-based retention policy on the container.
The correct strategy combines a lifecycle policy that moves data to the Cool tier after 30 days (supporting sub-second access for infrequent queries) and to the Archive tier after 180 days (minimizing cost when high latency is acceptable). Additionally, to prevent modification or deletion by administrators, a locked time-based retention policy must be configured on the container.

Step-by-Step Solution

1
Analyze retrieval latency requirements for each phase of the data lifecycle.
Identify that the first 30 days require immediate/frequent access (Hot tier), days 31 to 180 require sub-second retrieval (Cool tier), and after 180 days, hours-long latency is acceptable (Archive tier).
This establishes the correct lifecycle transition intervals and prevents placing data in a high-latency tier prematurely.
2
Determine the immutability policy needed to meet the compliance and admin-protection requirements.
Select a locked time-based retention policy rather than a legal hold or unlocked policy.
Locked time-based retention policies strictly prevent modification and deletion of blobs by any user, including administrators, for a defined duration, which satisfies the regulatory requirement.
3
Select the correct combination of lifecycle management rules and immutability settings.
Combine the rule transitioning to Cool at 30 days and Archive at 180 days with the container-level locked time-based retention policy.
This dual-action approach meets both cost-optimization/retrieval speed and strict data compliance requirements.

Key Concept

Azure Blob Storage Lifecycle Management and Immutable Storage Policies
Rate this question

Topics

Data Lifecycle Management and Retention

More questions from this topic