You plan to use a NuGet package in a project in Azure DevOps. The NuGet package is in a feed that requires authentication.
You need to ensure that the project can restore the NuGet package automatically.
What should the project use to automate the authentication?
Click on the arrows to vote for the correct answer
A. B. C. D.B
The Azure Artifacts Credential Provider automates the acquisition of credentials needed to restore NuGet packages as part of your .NET development workflow. It integrates with MSBuild, dotnet, and NuGet(.exe) and works on Windows, Mac, and Linux. Any time you want to use packages from an Azure Artifacts feed, the
Credential Provider will automatically acquire and securely store a token on behalf of the NuGet client you're using.
https://github.com/Microsoft/artifacts-credproviderThe correct answer to this question is B. an Azure Artifacts Credential Provider.
Azure Artifacts Credential Provider is an extension that can be installed on a machine or a build agent. It enables Azure DevOps to automatically authenticate with the NuGet feed during the build process, without requiring the user to enter credentials manually. The extension stores the credentials securely in the Credential Manager of the machine.
When using a NuGet feed that requires authentication, you can configure your build pipeline to use the Azure Artifacts Credential Provider to automatically authenticate. The following steps need to be taken:
Install the Azure Artifacts Credential Provider extension on the machine or build agent that will run the build process.
Create a Personal Access Token (PAT) in Azure DevOps that has access to the NuGet feed.
Add the PAT as a secret variable in the build pipeline.
Configure the NuGet restore step in the pipeline to use the Azure Artifacts Credential Provider.
By following these steps, the build process will be able to automatically authenticate with the NuGet feed using the PAT stored in the Credential Manager by the Azure Artifacts Credential Provider.
Option A, an Azure Automation account, is not relevant to this scenario as it is a service that enables you to automate the deployment and management of resources in Azure.
Option C, an Azure Active Directory (Azure AD) account that has multi-factor authentication (MFA) enabled, is not a recommended option as it may not work with some build agents that do not support MFA.
Option D, an Azure Active Directory (Azure AD) service principal, is used for authenticating applications or services rather than users. While it is possible to use a service principal for authentication in this scenario, it is not the recommended approach as it requires additional configuration and maintenance.