Azure DevOps Engineer Question 23

Why It Matters

Proper artifact retention balances regulatory compliance and cost efficiency, enabling teams to automate cleanup while safeguarding production releases.

Key Takeaways

• Global retention policy enforces 30‑day artifact cleanup across pipelines
• Production releases can be marked to retain indefinitely
• Blob storage without policies leads to uncontrolled cost growth
• Manual deletion is error‑prone and not scalable for teams
• Pipeline variables cannot enforce retention rules automatically within pipelines

Summary

The video walks through Azure DevOps certification question 23, which asks candidates to select the proper configuration for a retention strategy that keeps pipeline artifacts for 30 days while preserving production release artifacts indefinitely.

The correct answer is to set a global 30‑day retention policy and explicitly mark production releases with the “retain indefinitely” flag. This leverages Azure Pipelines’ built‑in retention framework, allowing automatic cleanup of non‑production artifacts while exempting critical releases.

The presenter dismisses alternative choices: storing artifacts in Azure Blob storage without a policy (option B) would incur unbounded storage costs; manual monthly deletions (option C) are error‑prone and unscalable; and using pipeline variables (option D) cannot enforce retention because variables only configure runtime behavior.

Adopting the global policy with selective overrides reduces operational overhead, ensures compliance with data‑retention guidelines, and prevents unexpected expense spikes—key considerations for any organization relying on continuous delivery pipelines.

Original Description

The best strategy to retain standard artifacts for 30 days while keeping production artifacts indefinitely is to set a global 30-day retention policy and manually mark production releases to be retained. Unlike using Azure Blob storage without a policy (unbounded costs), manual deletion (error-prone), or pipeline variables (not for enforcement), this approach leverages the native capability of Azure Pipelines to override global retention for specific runs. This ensures that temporary build data is automatically purged while critical deployment records remain secure and accessible for as long as needed.

#AZ400 #AzureDevOps #CICD #RetentionPolicy #CloudComputing #DevOps #TechTips #KodeKloud