An Azure DevOps project produces npm packages consumed by multiple projects. Configure Azure Artifacts so both latest and prerelease package versions are available for consumers. What should you do?

To manage both prerelease and release versions, you need distinct views. Creating @prerelease and @release views allows for clear separation. Setting @release as the default view ensures that consumers automatically get stable versions unless they explicitly request a prerelease. A release pipeline should then promote packages to the @release view only after they have passed all necessary testing and quality gates, making them officially stable and ready for broader consumption. The other options are incorrect because: Creating only one view or using @default for releases doesn't provide the necessary distinction or control for managing different package stability levels. Tagging packages as release is not the mechanism for promoting them to a specific view; promotion is the correct action within Azure Artifacts.