nerdexam
Microsoft

DP-203 · Question #346

You have an Azure Data Factory pipeline named pipeline1 that includes a Copy activity named Copy1. Copy1 has the following configurations: - The source of Copy1 is a table in an on-premises…

The correct answer is B. Scale up the data flow runtime of the Azure integration runtime and scale out the self-hosted. https://learn.microsoft.com/en-us/azure/data-factory/concepts-integration-runtime Azure integration runtime provides the native compute to move data between cloud data stores in a secure, reliable, and high-performance manner. You can set how many data integration units to use…

Submitted by deeparc· Mar 30, 2026Secure, monitor, and optimize data storage and data processing

Question

You have an Azure Data Factory pipeline named pipeline1 that includes a Copy activity named Copy1. Copy1 has the following configurations:

  • The source of Copy1 is a table in an on-premises Microsoft SQL Server

instance that is accessed by using a linked service connected via a self-hosted integration runtime.

  • The sink of Copy1 uses a table in an Azure SQL database that is

accessed by using a linked service connected via an Azure integration runtime. You need to maximize the amount of compute resources available to Copy1. The solution must minimize administrative effort. What should you do?

Options

  • AScale out the self-hosted integration runtime.
  • BScale up the data flow runtime of the Azure integration runtime and scale out the self-hosted
  • CScale up the data flow runtime of the Azure integration runtime.

How the community answered

(30 responses)
  • A
    10% (3)
  • B
    73% (22)
  • C
    17% (5)

Explanation

https://learn.microsoft.com/en-us/azure/data-factory/concepts-integration-runtime Azure integration runtime provides the native compute to move data between cloud data stores in a secure, reliable, and high-performance manner. You can set how many data integration units to use on the copy activity, and the compute size of the Azure IR is elastically scaled up accordingly without requiring you to explicitly adjust the size of the Azure Integration Runtime. For high availability and scalability, you can scale out the self-hosted IR by associating the logical instance with multiple on-premises machines in active-active mode.

Topics

#integration runtime#self-hosted IR#Copy activity performance#Azure IR scaling

Community Discussion

No community discussion yet for this question.

Full DP-203 Practice