AZ400-Q: retire obsolete pipeline dependencies

An organization keeps old pipeline artifacts, templates, and package dependencies indefinitely “just in case.” The build estate is costly and confusing. What strategy is best?

  • A) Delete everything immediately.
  • B) Never change retention because history is useful.
  • C) Hide old dependencies from developers.
  • D) Define ownership, usage/audit requirements, retention and deprecation windows, migration paths, and controlled cleanup with exceptions for active investigations. ✓

Answer: D. Pipeline maintenance requires intentional lifecycle management, not indiscriminate deletion or indefinite accumulation.

Why not the others: Immediate deletion risks recovery/audit; permanence and hiding do not solve cost or confusion.

pipeline-retention · pipeline-maintenance · build-artifact