Exam DP-201 topic 7 question 2 discussion

Azure IR is perfectly capable of running Salesforce connection. No need for VM or SSIS runtime. Tumbling trigger will serve better here. Only the copy activity is the right answer.

I am literally working a project right now where we ingest data from salesforce to data lake. Its the Azure IR.

As suggested it seems Azure IR is also possible and this is also the only solution, because it is mentioned to use PaaS and no VMs managed by Litware. Self-hosted IR requires managing VMs, therefore => Azure IR

Based on reviewed information all the answers provided are correct.

I agree is azure IR because salesforce SaaS, but I don’t know what trigger is better. Schedule with frequency 8h fit perfectly but, at the same time Tumbling with 8h window do the same. I think the first one always trigger at these hours independently if the process was cancelled or not, and tumbling may introduce delays if process fails and has to be relaunched because next window will be 8h later than this second try. Am I right?

See https://docs.microsoft.com/en-us/azure/data-factory/copy-activity-overview#supported-data-stores-and-formats: "When you're copying data between two data stores that are publicly accessible through the internet from any IP, you can use the Azure integration runtime for the copy activity. This integration runtime is secure, reliable, scalable, and globally available. When you're copying data to and from data stores that are located on-premises or in a network with access control (for example, an Azure virtual network), you need to set up a self-hosted integration runtime." Further down on that page, Salesforce is listed as supported by Azure IR.

https://docs.microsoft.com/en-us/azure/data-factory/connector-salesforce-service-cloud: "When you copy data into Salesforce Service Cloud, the default Azure Integration Runtime can't be used to execute copy. In other words, if your source linked service doesn't have a specified integration runtime, explicitly create an Azure Integration Runtime with a location near your Salesforce Service Cloud instance." Integration runtime is Azure Trigger as schedule and activity as copy are correct

we will need Self-hosted since the salesforce is an on-premise Source. ref- https://docs.microsoft.com/en-us/azure/data-factory/connector-salesforce

the answer should be tumbling window trigger isn't it?

As it's mentioned every 8 hrs why not tumbling window trigger rather scheduled.. ?

Important When you copy data into Salesforce, the default Azure Integration Runtime can't be used to execute copy. In other words, if your source linked service doesn't have a specified integration runtime, explicitly create an Azure Integration Runtime with a location near your Salesforce instance. Associate the Salesforce linked service as in the following example. So the given answer is correct.

"When you copy data into Salesforce, the default Azure Integration Runtime can't be used to execute copy. In other words, if your source linked service doesn't have a specified integration runtime, explicitly create an Azure Integration Runtime with a location near your Salesforce instance. Associate the Salesforce linked service as in the following example." https://docs.microsoft.com/en-us/azure/data-factory/connector-salesforce

For box 1 both Azure IR and self hosted IR are correct as the data is in Salesforce and Salesforce supports both: https://docs.microsoft.com/en-us/azure/data-factory/copy-activity-overview#supported-data-stores-and-formats

IR to be used is Azure IR as mentioned here --> https://docs.microsoft.com/en-us/azure/data-factory/connector-salesforce "The integration runtime to be used to connect to the data store. If not specified, it uses the default Azure Integration Runtime"

Salesforce is a cloud data source even though there is no clear explanation from the question. Azure IR and Self-Hosted IR both will work via different approaches. Would prefer Azure IR as the answer due to simplicity. https://docs.microsoft.com/en-us/azure/data-factory/data-migration-guidance-s3-azure-storage