Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 6 of 160
Free Preview · 160 of 533 · questions 1–160 of 533 are free. Sign up free to sync your progress across devices.
Drag & Drop Scenario
Read the scenario requirements and decide your answer. Click Check Answer below to see the marked solution.
Hotspot Solution:
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.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
This question is not clear enough for me, I have problem with the "integration" part. You definitely need "A self-hosted agent" The problem is if the "An External Git service connection" option is also counted: 1) Triggers are not available, does that count? - You can use a Other Git connection but tell Azure Pipelines not to attempt accessing this Git server from Azure Pipelines. CI and PR triggers aren't available with Other Git repositories. You can only start manual or scheduled pipeline runs. https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/on-premises-bitbucket?view=azure-devops 2) If "it can be used in conjunction with a self-hosted agent to access and interact with your Bitbucket repositories behind the firewall.", you need a self-hosted agent to use it, does that count?
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
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