Which Integration Runtime Connects On-Premises Linux Databases to Azure Data Factory?
You have an on-premises Linux server that contains a database named DB1. You have an Azure subscription that contains an Azure data factory named ADF1 and an Azure Data Lake Storage account named ADLS1. You need to create a pipeline in ADF1 that will copy data from DB1 to ADLS1. Which type of integration runtime should you use to read the data from DB1?
Community Votes
55% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests knowledge of IR deployment models versus source OS compatibility, with the common trap being the misconception that a Windows-only IR cannot communicate with Linux databases.
This scenario evaluates your understanding of Azure Data Factory integration runtimes for hybrid data movement. The community consensus confirms that the Self-Hosted Integration Runtime is required to securely bridge on-premises networks with Azure, even when the source database runs on Linux.
Candidates frequently select Azure-SQL Server Integration Services (SSIS) due to the false assumption that the Self-Hosted IR is strictly limited to Windows environments and cannot interact with Linux sources.
Community Discussion (11 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The Self-Hosted Integration Runtime (SHIR) is specifically designed to facilitate secure data transfer between on-premises resources and Azure cloud services. Although the SHIR agent itself must be installed on a Windows or macOS machine within the local network, it acts as a proxy capable of connecting to diverse on-premises data stores, including Linux-based SQL servers. By leveraging native ODBC and JDBC drivers, the SHIR successfully reads data from the Linux server and streams it to Azure Data Lake Storage via ADF.Why the Other Options Are Wrong
The Azure Integration Runtime operates entirely within the Microsoft cloud and lacks direct connectivity to private, on-premises networks without additional networking configurations, making it unsuitable for direct on-prem reads. Option C, the Azure-SQL Server Integration Services (SSIS), is primarily used for complex ETL transformations and package execution rather than simple data copying pipelines. While it supports on-premises connections, it introduces unnecessary complexity and licensing overhead for straightforward copy activities.Community Comment Notes
Multiple candidates noted the confusion surrounding SHIR's OS requirements, with several clarifying that while the runtime agent requires Windows, it fully supports remote Linux databases. Others incorrectly voted for SSIS based on outdated assumptions regarding Windows-only restrictions. Experienced users emphasized that ADF copy activities do not require SSIS unless custom transformation logic is explicitly requested, reinforcing the official guidance for hybrid connectivity.Official Reference
Exam Strategy
When encountering hybrid connectivity questions, always prioritize the Self-Hosted Integration Runtime for on-premises data access regardless of the source server's operating system. Focus on the deployment location of the runtime agent rather than the target database's OS, and reserve SSIS options only for explicit transformation or legacy migration scenarios.