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?
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?
To make a NuGet package available to anonymous users outside your organization while minimizing the number of publication points, the best solution is to publish the package to a public NuGet repository. This approach leverages an established public platform, ensuring easy and anonymous access without adding the complexity of managing multiple publication points.
The only possible correct answer is: Publish the package to a public NuGet repository. This is because to use the public feed feature in Azure DevOps, the project itself must be public: "Public feeds are project-scoped feeds that live inside a public project. You cannot convert an existing organization-scoped feed into a project-scoped feed or a public feed." https://docs.microsoft.com/en-us/azure/devops/artifacts/tutorials/share-packages-publicly?view=azure-devops
Nothing is mentioned in the question that the project is private.
You need to make one of the packages available to anonymous users outside your organization.
Examtopic's answer is correct. refer the link shared by droy89's
totally agree with you
On second thought perhaps the answer provided is correct. In fact, we don't have anything to be sure that the project is private. It could easily be public and use a Feed with scope = organization. In such a case it would be enough to create a new public feed to solve the problem and satisfy the requirement "The solution must minimize the number of publication points".
This is correct. If a project is private the its feed is private. If a project is public, the feed also becomes public. Questions says only one package needs to be made public
Correct
B is the answer. https://learn.microsoft.com/en-us/azure/devops/artifacts/tutorials/share-packages-publicly?view=azure-devops&tabs=nuget Azure Artifacts provides an easy way to share packages to users outside your organization and even external customers using public feeds. Packages that are stored in public feeds can be restored and installed by anyone on the Internet.
GPT: However, if security is a concern, you can also consider creating a release view in Azure Artifacts. Release views provide a way to promote packages to a production environment while controlling access to those packages. You can create a release view and grant anonymous users access to the view, then promote the package to the view. This would make the package available to anonymous users outside your organization while still maintaining some level of control over who can access the package. Option A is incorrect because changing the feed URL of the package would not make it available to anonymous users outside your organization. Option B is incorrect because creating a new feed for the package would not make it available to anonymous users outside your organization. Option C is incorrect because promoting the package to a release view would not make it available to anonymous users outside your organization.
To make a NuGet package available to anonymous users outside your organization using Azure Artifacts, you should publish the package to a public NuGet repository. Option D is correct. Explanation: Azure Artifacts is a private package repository used for sharing code within an organization. It is not designed to be used as a public package repository. If you need to make a package available to anonymous users outside your organization, you can publish the package to a public NuGet repository like nuget.org or create a new feed for the package and then publish it to the new feed.
GPT4 D. Publish the package to a public NuGet repository. Azure Artifacts doesn't currently support anonymous access (as of my knowledge cut-off in September 2021). As such, the best way to make a NuGet package available to anonymous users would be to publish the package to a public repository, such as nuget.org, where anyone can access it. The other options (A, B, and C) all involve manipulation within Azure Artifacts, which still would not allow for anonymous access. Changing the feed URL or creating a new feed doesn't allow anonymous access, and promoting the package to a release view also doesn't grant anonymous access. Remember to always double check the Azure documentation or the Azure portal itself for updates, as Azure is a rapidly evolving service and changes may have occurred since my training data was last updated in September 2021.
Creating a new feed for the package would also make it available to anonymous users outside your organization, but it would require you to create a new publication point. This would add an additional layer of complexity to managing and maintaining your packages, as you would need to keep track of two separate feeds. If you only need to make one package available to anonymous users, then creating a new feed is a viable option. However, if you need to make multiple packages available to anonymous users, then it is more efficient to publish them to a public NuGet repository.
if it's more complex to create new feed than publishing package, then why you choose it ? (why b instead of d ?)
It should be "D" NuGet package repository Public repository hosted externally No authentication required to anyone(available to anonymous users outside your organization) One publication point (minimize the number of publication points) New Feed for the Package Private view within Azure Artifacts, Authentication required to external users, Organizing packages for different projects or teams. Release View in Azure Artifacts Private view within Azure Artifacts, Authentication required to external users, Managing package visibility through various environments/stages.
For those picking B, I wonder why because it literally doesn't mention anything about the feed being public or not
The answer is B. D is not the answer because to Publish the package to a public NuGet repository: While this would make the package publicly accessible, it doesn't involve Azure Artifacts. Plus, the goal is to minimize publication points, and using external public repositories may add complexity.
Note that publishing to a public repository, e.g. nuget.org doesn't necessarily increase the number of publication points, because nuget.org is the main goto for public dependencies. Therefore it is likely that's already being used. In contrast, creating a new feed will at least add one extra publication point.
Minimized Publication Points: Leveraging an existing public repository eliminates the need for additional infrastructure or configuration within Azure Artifacts, keeping the number of publication points to a minimum. Public Accessibility: Public repositories like nuget.org are readily accessible by anonymous users searching for NuGet packages.
Why isn't C the correct answer?
Because promoting to a release view doesn't mean it will be public to anonymous users
Answer is B To share your packages publicly, you can simply share your feed URL e.g. https://dev.azure.com/<ORGANIZATION_NAME>/<PROJECT-NAME>/_artifacts/feed/<FEED_NAME> or share individual packages with package badges. As long as your project is kept public, anyone can view and download packages from your public feed. Anonymous users won't be able to create new feeds or access the recycle bin. Reference: https://learn.microsoft.com/en-us/azure/devops/artifacts/tutorials/share-packages-publicly?view=azure-devops&tabs=nuget
https://devblogs.microsoft.com/devops/share-packages-publicly-from-azure-artifacts-public-preview/#:~:text=NuGet%2C%20npm%2C%20Maven%2C%20and,the%20top%20of%20the%20UI.
D for me
Correct D
The correct answer is D: Publish the package to a public NuGet repository. 🚀 Here’s why: NuGet Package Repository (Public): Hosting the package in a public NuGet repository makes it accessible to anyone, including anonymous users outside your organization. No authentication is required, which meets the goal of external accessibility. Minimizing Publication Points: By using a public NuGet repository, you maintain just one publication point. No need for additional feeds or complex setups. Other Options Explained: New Feed for the Package: While creating a new feed is an option, it introduces unnecessary complexity and additional publication points. Release View in Azure Artifacts: Release views are useful for managing package visibility within different environments, but they don’t address the requirement for external accessibility.