Your company has an Azure Data Factory pipeline that ingests data from multiple sources into Azure Data Lake Storage Gen2. The pipeline uses a self-hosted integration runtime (IR) running on an on-premises Windows server. Recently, the pipeline started failing with 'Connection timed out' errors during peak hours. You suspect network congestion. You need to resolve this issue with minimal cost and without modifying the pipeline activities. What should you do?
Trap 1: Implement Azure ExpressRoute to provide dedicated bandwidth.
Overkill and costly for this issue.
Trap 2: Increase the 'Polling Interval' setting in the copy activity.
Polling interval affects status check, not connectivity.
Trap 3: Migrate the self-hosted IR to Azure-SSIS IR.
Expensive and not a direct solution for load.
- A
Implement Azure ExpressRoute to provide dedicated bandwidth.
Why wrong: Overkill and costly for this issue.
- B
Increase the 'Polling Interval' setting in the copy activity.
Why wrong: Polling interval affects status check, not connectivity.
- C
Scale out the self-hosted IR by adding more nodes to the cluster.
Distributes load and improves throughput.
- D
Migrate the self-hosted IR to Azure-SSIS IR.
Why wrong: Expensive and not a direct solution for load.