Exam DP-203 topic 2 question 110 discussion

According to Microsoft, AutoResolveIntegrationRuntime will attempt to use the sink location to get an IR in the same region (or the closest available) to execute the Copy activity, not the source location. I would go with the region of data factory, since that is the default option when the sink's location is not detectable. Source: https://learn.microsoft.com/en-us/azure/data-factory/concepts-integration-runtime#azure-ir-location

1. upon publishing changes to the service 2. in the region of data factory

- Upon publishing the changes. - In the region of the source database.

1. upon saving the changes ( refer to the warning message in the screenshot given in the question ) 2. In the region of data factory. ( https://learn.microsoft.com/en-us/azure/data-factory/concepts-integration-runtime#azure-ir-location) Azure IR location You can set the location region of an Azure IR, in which case the activity execution or dispatch will happen in the selected region. The default is to auto-resolve the Azure IR in the public network. With this option: For copy activity, a best effort is made to automatically detect your sink data store's location, then use the IR in either the same region, if available, or the closest one in the same geography, otherwise; if the sink data store's region is not detectable, the IR in the instance's region is used instead.

Once you make a changes it needs to make a pull request then merge the changes in the main pipeline then you will be able to see the changes in this case merging into collaboration branch is the right answer

For Linked Services, changes are published immediately unless you use key vault, which means basically upon saving. "Changes to Linked Services are published immediately, unless you use Key Vault. This can mean a branch change to a Linked Service could impact other branch tests. The reason for this is credential protection. While "Live-Mode" retrieves definitions from the back-end, "Github" or "Devops" mode construct the definitions from the repository. Putting credentials into repository code is a very bad idea. This is why, without Key Vault, credentials are stored and encrypted in Data Factory back end." https://learn.microsoft.com/en-us/answers/questions/568057/advanced-feature-branch-development

upon publishing changes to the service

the first one should be "upon publishing changes to the service" . See https://learn.microsoft.com/en-us/azure/data-factory/source-control

Shouldn't we choose the 'upon saving the changes' option in the first dropdown? Link: https://learn.microsoft.com/en-us/azure/data-factory/source-control#stale-publish-branch

I did not manage to find a clear answer to this one, but based on cross-reading a few articles, I think "in the region of data factory" should be the correct answer, and this article explains it a bit better than the others I found: https://asankap.wordpress.com/2021/10/26/why-you-shouldnt-use-auto-resolve-integration-runtime-in-azure-data-factory-or-synapse/

When using the AutoResolveIntegrationRuntime with a Copy activity in Azure Data Factory that uses a linked service as the source, the copy operation will be performed in the region of the source data store. The AutoResolveIntegrationRuntime is a system-assigned integration runtime that automatically routes data movement and activity dispatch to the optimal region based on the location of the source and sink data stores. When using a linked service as the source, the service will attempt to detect the location of the source data store and use an Integration Runtime in the same region to perform the copy operation.

For copy activity, a best effort is made to automatically detect your sink data store's location, then use the IR in either the same region, if available, or the closest one in the same geography, otherwise; if the sink data store's region is not detectable, the IR in the instance's region is used instead.

correct