You use Azure Artifacts to host NuGet packages that you create.
You need to make one of the packages available to anonymous users outside your organization. The solution must minimize the number of publication points.
What should you do?
Click on the arrows to vote for the correct answer
A. B. C. D.B
Azure Artifacts introduces the concept of multiple feeds that you can use to organize and control access to your packages.
Packages you host in Azure Artifacts are stored in a feed. Setting permissions on the feed allows you to share your packages with as many or as few people as your scenario requires.
Feeds have four levels of access: Owners, Contributors, Collaborators, and Readers.
https://docs.microsoft.com/en-us/azure/devops/artifacts/feeds/feed-permissions?view=vsts&tabs=new-navThe correct answer is D. Publish the package to a public NuGet repository.
Explanation:
Azure Artifacts is a service provided by Azure DevOps that allows developers to store and manage binary packages such as NuGet, npm, and Maven packages. Azure Artifacts can be used to host both private and public package feeds.
To make a package available to anonymous users outside your organization, the best option is to publish the package to a public NuGet repository. This will make the package available to anyone who wants to use it, without the need for authentication or access to your Azure Artifacts feed.
Option A, changing the feed URL of the package, is not a viable solution because it would require anonymous users to have access to your organization's Azure Artifacts feed. This is not a secure or practical solution.
Option B, creating a new feed for the package, would not minimize the number of publication points. In fact, it would add an additional publication point, making it more difficult to manage and maintain your packages.
Option C, promoting the package to a release view, would not make the package available to anonymous users outside your organization. It would simply make it easier for authorized users within your organization to find and use the package.
Therefore, the best option is to publish the package to a public NuGet repository, such as the official NuGet Gallery. This will make the package available to anyone who wants to use it, without the need for authentication or access to your Azure Artifacts feed.