Examkin

Question

Difficulty: Very hardData Lifecycle Management and Retention

An enterprise is designing a data storage and retention strategy for a new telemetry analytics application. The application will write data to an Azure Data Lake Storage Gen2 (ADLS Gen2) account.

The data requirements are structured as follows:

PeriodAccess Frequency & LatencyRetention & Immutability
**Days 11–1010**Frequently written and analyzed. Requires sub-second, low-latency access.Must be mutable for real-time updates.
**Days 1111–9090**Rarely accessed. Must remain online for occasional queries with a retrieval latency of less than 1010 seconds.Must be protected against deletion and modification.
**Days 9191–2,5552,555 (77 years)**Not accessed. Only kept for compliance audits. Retrieval latency of up to 1515 hours is acceptable.Must be protected against deletion and modification for the first 33 years (1,0951,095 days) from creation.

You need to configure a lifecycle management policy and immutability settings that satisfy these requirements while minimizing storage costs and avoiding early deletion fees.

Which of the following configuration options should you recommend? (Select TWO).

  1. Configure a container-level time-based retention policy with a duration of 1,0951,095 days and lock the policy.Answer
  2. Configure a lifecycle management policy to transition blobs to the Cool tier 1010 days after creation, to the Archive tier 9090 days after creation, and delete them after 2,5552,555 days.Answer
  3. C
    Configure a lifecycle management policy to transition blobs to the Cold tier 1010 days after creation, to the Archive tier 9090 days after creation, and delete them after 2,5552,555 days.
  4. D
    Configure a lifecycle management policy to transition blobs directly to the Archive tier 1010 days after creation, using Standard priority rehydration for any queries.
  5. E
    Apply a container-level legal hold with a retention duration of 1,0951,095 days to protect the telemetry files from modification and deletion.

Answer

To meet the storage, latency, and immutability requirements cost-effectively, configure a locked time-based retention policy for 1,0951,095 days at the container level, and implement a lifecycle management policy that transitions blobs to the Cool tier after 1010 days, to the Archive tier after 9090 days, and deletes them after 2,5552,555 days.
The correct configurations are to apply a locked container-level time-based retention policy for 1,0951,095 days and a lifecycle policy transitioning blobs to Cool at day 1010, Archive at day 9090, and deleting at day 2,5552,555. A locked time-based retention policy ensures that the compliance mandate for 33 years (1,0951,095 days) of immutability is met. Transitioning to Cool at day 1010 provides the required low-latency access for days 1111–9090. Because the blobs spend 8080 days in Cool before moving to Archive, this exceeds the Cool tier's 3030-day minimum retention requirement, avoiding any early deletion penalties.

Step-by-Step Solution

1
Analyze the latency and access requirements for the intermediate period (days 1111–9090).
The data must be queryable in less than 1010 seconds. This rules out the Archive tier since it requires hours to rehydrate. Both Cool and Cold tiers offer millisecond-level retrieval latencies.
To determine which online tiers are viable.
2
Calculate the duration the blobs will spend in the intermediate tier to avoid early deletion charges.
The blobs transition to the intermediate tier at day 1010 and to the Archive tier at day 9090, resulting in an intermediate duration of 8080 days. Cool tier has a 3030-day minimum retention, whereas Cold tier has a 9090-day minimum retention. Using Cold tier would trigger a 1010-day early deletion penalty (90−80=1090 - 80 = 10). Therefore, the Cool tier must be used.
To optimize costs by preventing early deletion charges.
3
Identify the mechanism to enforce the 33-year compliance requirement.
A locked time-based retention policy for 1,0951,095 days (33 years) provides immutable WORM storage. A legal hold cannot be configured with a duration and requires manual removal.
To fulfill the immutability requirements without operational overhead.

Key Concept

Azure Blob Storage lifecycle management tiering constraints, minimum retention periods for Cool and Cold tiers, and container-level immutable storage policies.
Rate this question

Topics

Data Lifecycle Management and Retention

More questions from this topic