AZ-104 Implement and Manage Storage Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Move blobs not modified for 30 days: Transition to cool tier

  Why this is correct

  The cool tier is optimized for data that has not been accessed for 30 days, offering lower storage costs than hot tier while retaining near-instant retrieval. A lifecycle management rule with a "transition to cool" action after 30 days aligns with Azure's recommended tiering pattern. It is a common practice to move infrequently accessed blobs to cool to reduce storage expenses without sacrificing availability.

• ✓

  Move blobs not modified for 90 days: Transition to archive tier

  Why this is correct

  Archive is the lowest-cost tier designed for long-term retention where retrieval latency of up to 15 minutes is acceptable. Since 90 days without modification indicates cold data, transitioning to archive at that point minimizes cost. The rule should specify "transition to archive" after 90 days from last modification, which is a valid and cost-effective policy.

• ✓

  Delete blobs after 365 days: Delete blob

  Why this is correct

  The appropriate action to remove a blob after one year is the "delete blob" action in a lifecycle management policy. Deleting blobs that have no business need beyond a year saves all associated storage and access costs. It is not a tier transition but a direct deletion, ensuring compliance with data retention policies.

• ✗

  Move blobs not modified for 30 days: Transition to archive tier

  Why it's wrong here

  Archive is for data that is rarely accessed and can tolerate rehydration delays of hours, typically used for blobs older than 90 days. Moving a 30-day-old blob to archive would incur high rehydration costs if access is needed and is overly aggressive. A 30-day threshold is better suited for cool tier, as archive is meant for much longer retention, not initial tiering.

• ✗

  Move blobs not modified for 90 days: Transition to cool tier

  Why it's wrong here

  Cool tier is appropriate for data with a 30-day retention window, but by 90 days the access patterns usually justify the even lower cost of archive. Placing 90-day-old blobs in cool would keep them at a higher storage price than necessary. The lifecycle should progress to archive at 90 days, not cool, to optimize cost.

• ✗

  Delete blobs after 365 days: Transition to cool tier

  Why it's wrong here

  Deleting a blob requires a "delete blob" action; transitioning to cool only changes the storage tier, not the blob's existence. A "transition to cool" after 365 days would leave the blob in storage indefinitely, incurring ongoing costs. For a one-year retention policy, the correct action is deletion, not tiering.

Go deeper

Related to this question