Exam AZ-400 topic 8 question 44 discussion

The answer is correct, https://developercommunity.visualstudio.com/content/problem/472926/how-to-connect-bitbucket-server-on-perm-not-cloud.html

Verified - its correct

Correct answer

D. a self-hosted agent E. an External Git service connection Since the Bitbucket Server is on-premises, we need to use a self-hosted agent to communicate with the server. Also, we need to create an External Git service connection in Azure DevOps to connect to the Bitbucket Server. Service hooks can be used to trigger events in Azure DevOps from Bitbucket, but they are not required for the initial integration. A deployment group and a Microsoft-hosted agent are not necessary for this scenario.

What "two" components are "required": A. deployment group - not required C. service hooks - not required, not relevant E. an External Git service connection (or, more correctly, "Other Git" service connection) - required to connect Azure Pipelines to an on-premises source control, BitBucket in this case. B. a Microsoft-hosted agent - agents need to contact source control for build jobs. When inbound internet connectivity is denied to source control, Microsoft-hosted agents will not work. So, this is a no. D. a self-hosted agent - agents on premises can contact the source control for jobs and can maintain the connectivity with Azure Pipelines for instructions without the need for inbound internet connectivity to the source control. This will work just fine for the scenario. And D is the only option left after eliminating the others. So, DE.

https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/on-premises-bitbucket?view=azure-devops "probably caused by a firewall blocking traffic from these servers" "Switch to using self-hosted agents or scale-set agents" D and E are the answers

D & E are correct answers.

correct answer

https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/on-premises-bitbucket?view=azure-devops#:~:text=Otherwise%2C%20you%20must%20set%20up%20self%2Dhosted%20agents%20that%20can%20access%20your%20on%2Dpremises%20server%20and%20fetch%20the%20code.

The hosted agent and Git connection are needed. Because of firewall, a Microsoft-hosted agent can't connect. So the answers are D and E.

If you can't talk from Azure DevOps to the bitbucket server because the firewall is blocking; then you need an internal self-hosted agent. Internal self-hosted agents initiate the connection to Az DevOPs from outside. Everybody seems to be overlooking that this is build & release pipeline. If you want to release artifacts; then you need a deployment group. So the answers are: Deployment Group & a Self-Hosted Agent.

For those of you who want to read more about "External Git service connection": https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml#sep-extgit The following URL outlines the same setup with an on-prem Bitbucket server: https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/on-premises-bitbucket?view=azure-devops#not-reachable-from-azure-pipelines Drawback in this setup: "CI and PR triggers will not work in this configuration. You can only start manual or scheduled pipeline runs."

Verified - Correct!

D+E Correctamundo dude

Should be B E: B: https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/on-premises-bitbucket?view=azure-devops Reachable from Microsoft-hosted agents Another decision you possibly have to make is whether to use Microsoft-hosted agents or self-hosted agents to run your pipelines. This often comes down to whether Microsoft-hosted agents can reach your server. To check whether they can, create a simple pipeline to use Microsoft-hosted agents and make sure to add a step to checkout source code from your server. If this passes, then you can continue using Microsoft-hosted agents. E: https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml

D. a self-hosted agent E. an External Git service connection

Verified !! answer is correct.