Project teams publish npm packages to Feed1 in Azure Artifacts and multiple projects consume those packages. To ensure only tested packages are available for consumption while minimizing development effort, what should you do?

The correct approach leverages Azure Artifacts views for package promotion. Creating a @release view and setting it as default ensures that only packages explicitly promoted to this view are visible for consumption by default. A release pipeline then automates the promotion of tested packages to the @release view, minimizing manual effort and ensuring quality. The other options are incorrect because: Tagging packages as release (instead of promoting to a view) doesn't restrict visibility in the same way views do. Consumers would still see all packages unless explicitly filtered. Using @default as the promotion target defeats the purpose of having a separate, curated view for tested packages. The @default view typically contains all packages, including pre-release versions.