Your Azure DevOps project produces npm packages. To reduce the disk space consumed by older packages in Azure Artifacts, which setting should you modify?

The retention settings of the project's pipeline are the correct choice because Azure Artifacts package retention is directly managed through the retention policies configured for the build pipelines that publish those packages. These policies dictate how long build artifacts, including npm packages, are kept. By adjusting these settings, you can define rules for automatically deleting older package versions, thereby reducing storage consumption. The retention settings of the project’s release are incorrect because release retention primarily governs the lifespan of release artifacts and associated deployments, not the packages themselves in Azure Artifacts. The retention settings of the project’s tests are irrelevant as they manage test results, not package storage. The retention settings of the company pipeline is too broad; retention is typically managed at the project or pipeline level, not a company-wide setting that would override individual project needs.