Exam AZ-400 topic 7 question 12 discussion

I think B,D,E are right answers!

B,C,D (the given answer is correct) URL:https://docs.microsoft.com/en-us/azure/developer/jenkins/deploy-to-linux-vm-using-azure-devops-services by the way, webhook is used for Jenkins + Github, not for Azure Repos.

BCD is correct

No Service Hook or webhook is needed here since there is no "event" that occurs and no event notifications needs to be sent to a subscribing service (Service hook) or an external tool such as Jenkins (webhook.

C, D, E are correct from my point of view today. Nothing states it is an Azure DevOps Server, so i'm assuming it is Azure DevOps Services. Therefore Add an TFS plugin is not was it is called today, then it would be named as an Marketplace Extension https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/jenkins?view=azure-devops

https://www.dragonspears.com/blog/ci-cd-with-jenkins-and-azure-devops-services

B, C, D are correct

B, C D are correct

B C D are correct

What should you configure as a Webhook?

Looks more accurate

E Definitely has to be part of the answer, see the link https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/jenkins?view=azure-devops

1) Create a PAT in ADO. 2) Create a service hook subscription in ADO. https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/jenkins/ 3) Add PAT to Jenkins. https://www.jenkins.io/doc/book/using/using-credentials/

Reference for B, D, E as below but it is 4 years ago. https://github.com/undergroundwires/Azure-in-bullet-points/blob/master/AZ-400%20Microsoft%20Azure%20DevOps%20Solutions/7.3.%20Jenkins.md

D. Create a personal access token (PAT) in your Azure DevOps account. (A PAT with read access to the Git repository is still needed for Jenkins to authenticate with Azure DevOps.) E. Create a service hook in Azure DevOps. (A service hook is crucial to trigger Jenkins builds upon relevant events in Azure DevOps.) C. Add the Team Foundation Server (TFS) plugin to Jenkins. (While Azure Repos is the current name for the service, the TFS plugin in Jenkins is still compatible and provides the necessary functionality to interact with Azure Repos and clone the source code.)

According with the documentation of the links: B D E https://learn.microsoft.com/es-es/azure/devops/service-hooks/services/jenkins?view=azure-devops https://azuredevopslabs.com/labs/vstsextend/jenkins/

I agree with BCD. You do not need to create service hook in Az Devops because we are not triggerring any build. Here we need to Jenkins to access source code from Version control (TFS).