Question 39

Explanation

In Data Factory, an activity defines the action to be performed. A linked service defines a target data store or a compute service. An integration runtime provides the bridge between the activity and linked services.

Self-hosted integration runtime

A self-hosted integration runtime is capable of:

• Running copy activity between a cloud data stores and a data store in private network.

• Dispatching the following transform activities against compute resources in on-premises or Azure Virtual Network:

  • HDInsight Hive activity (BYOC-Bring Your Own Cluster)

  • HDInsight Pig activity (BYOC)

  • HDInsight MapReduce activity (BYOC)

  • HDInsight Spark activity (BYOC)

  • HDInsight Streaming activity (BYOC)

  • Machine Learning Batch Execution activity

  • Machine Learning Update Resource activities

  • Stored Procedure activity

  • Data Lake Analytics U-SQL activity

  • Custom activity (runs on Azure Batch)

  • Lookup activity

  • Get Metadata activity.

The self-hosted integration runtime is logically registered to the Azure Data Factory and the compute resource used to support its functionality as provided by you. Therefore there is no explicit location property for self-hosted IR. When used to perform data movement, the self-hosted IR extracts data from the source and writes into the destination.