You store source code in a Git repository in Azure Repos. You use a third-party continuous integration (CI) tool to control builds.
What will Azure DevOps use to authenticate with the tool?
Click on the arrows to vote for the correct answer
A. B. C. D.B
Personal access tokens (PATs) give you access to Azure DevOps and Team Foundation Server (TFS), without using your username and password directly.
https://docs.microsoft.com/en-us/azure/devops/repos/git/auth-overviewAzure DevOps will use a personal access token (PAT) to authenticate with the third-party CI tool. A PAT is a form of authentication that provides access to resources in Azure DevOps without using a password. It is a unique identifier that is used to access Azure DevOps services via APIs.
When setting up the integration between Azure DevOps and the third-party CI tool, the PAT will be generated from the Azure DevOps portal and provided to the CI tool. This token will grant the CI tool access to the Azure Repos Git repository and allow it to retrieve the source code for the builds.
Certificate authentication is a method of authentication that uses a digital certificate to verify the identity of a user or system. This method is typically used for secure communication between systems and is not directly related to accessing Azure DevOps services.
Shared Access Signature (SAS) token is a form of authentication that provides restricted access to specific Azure resources. It is commonly used to provide temporary access to a specific resource, such as a storage account or blob, without granting full access to the underlying Azure subscription.
NTLM authentication is a legacy form of authentication that is commonly used in Windows environments. It is not related to accessing Azure DevOps services and is typically used for securing communication between Windows systems.
In summary, the correct answer is B, a personal access token (PAT), as it is the authentication method used by Azure DevOps to authenticate with third-party CI tools.