https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/on-premises-bitbucket?view=azure-devops "This is again probably caused by a firewall blocking traffic from these servers. You have two options in this case: Switch to using self-hosted agents or scale-set agents" "Is your Bitbucket server accessible from Azure Pipelines? Azure Pipelines periodically polls Bitbucket server for changes. If the Bitbucket server is behind a firewall, this traffic may not reach your server. See Azure DevOps IP Addresses and verify that you have granted exceptions to all the required IP addresses. These IP addresses may have changed since you have originally set up the exception rules. You can only start manual runs if you used an external Git connection and if your server is not accessible from Azure Pipelines." Answer is correct

As jay158's answer, Examtopics' answer is correct

1- Self-hosted agent: This is a software application that you install on a machine within your network (not necessarily the Bitbucket server) to run jobs and tasks for your pipelines in Azure DevOps. It can be used with the External Git service connection to interact with your Bitbucket server without requiring inbound internet access. 2- External Git service connection: This is a configuration in Azure DevOps that allows it to connect to an external Git repository like your on-premises Bitbucket server. It can be used in conjunction with a self-hosted agent to access and interact with your Bitbucket repositories behind the firewall.

A self-hosted agent: This would allow you to run build and release tasks in a self-controlled environment, which is essential if you can't allow Azure DevOps agents to directly access the Bitbucket server over the internet. A service connection to an external Git service (external git service connection): This would provide a way to connect to your Bitbucket repository from Azure DevOps without needing to open additional ports on your firewall.

Un agente autohospedado (self-hosted agent): Esto permitiría ejecutar tareas de compilación y lanzamiento en un entorno controlado por ti mismo, lo que es esencial si no puedes permitir que los agentes de Azure DevOps accedan directamente al servidor Bitbucket a través de Internet. Una conexión de servicio a un servicio Git externo (external git service connection): Esto proporcionaría una forma de conectarse a tu repositorio Bitbucket desde Azure DevOps sin necesidad de abrir puertos adicionales en tu firewall.

started today, will be back once certification is complete

https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/on-premises-bitbucket?view=azure-devops Switch to using self-hosted agents or scale-set agents. These agents can be set up within your network and hence will have access to the Bitbucket server. These agents only require outbound connections to Azure Pipelines. There is no need to open a firewall for inbound connections. Correct Answer

Given Answer is correct Service Hooks is not related to this question as per MS Document Defination. Service hooks let you run tasks on other services when events happen in your project in Azure DevOps. For example, you can create a card in Trello when a work item gets created or send a push notification to your team's mobile devices when a build fails

I would not choose Service Connection because on premis bitbuket is blocking inbound traffic from internet

1. Self-hosted agent 2. External GIT service connection https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/on-premises-bitbucket?view=azure-devops#not-reachable-from-microsoft-hosted-agents Switch to using self-hosted agents or scale-set agents. These agents can be set up within your network and hence will have access to the Bitbucket server. These agents only require outbound connections to Azure Pipelines. There is no need to open a firewall for inbound connections. Make sure that the name of the server you specified when creating the service connection is resolvable from the self-hosted agents.

yes, it's possible only with self-hosted agent https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/on-premises-bitbucket?view=azure-devops

searches are wildcards

You can integrate your on-premises Bitbucket server or another Git server with Azure Pipelines. Your on-premises server may be exposed to the Internet or it may not be. If your on-premises server is reachable from the servers that run Azure Pipelines service, then: you can set up classic build and configure CI triggers If your on-premises server is not reachable from the servers that run Azure Pipelines service, then: you can set up classic build pipelines and start manual builds you cannot configure CI triggers If your on-premises server is reachable from the hosted agents, then you can use the hosted agents to run manual, scheduled, or CI builds. Otherwise, you must set up self-hosted agents that can access your on-premises server and fetch the code. https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/on-premises-bitbucket?view=azure-devops

Why external Git Service Connection? Since Bitbucket blocks incoming connections, wouldn't setting that up fail (Azure Pipelines shouldn't be able to connect to the on-prem bitbucket which blocks inbound traffic). Just self-hosted agent (deployed on prem) should be sufficient?

Correct, self-hosted agent for on-premises and then Git service connection.

the inbound traffics are blocked , so the given answer is correct

Answer A Self-hosted agent Service hooks https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/bitbucket?view=azure-devops&tabs=classic#access-to-bitbucket-repositories