Answer: self-hosted integration runtime

## Explanation To copy data from an on-premises Linux database server to Azure Data Lake Storage using Azure Data Factory, the **self-hosted integration runtime** is the optimal choice for the following reasons: ### Why Self-Hosted Integration Runtime (Option A) is Correct: 1. **On-Premises Connectivity**: The self-hosted integration runtime is specifically designed to connect to on-premises data sources, including databases hosted on Linux servers. It acts as a bridge between your on-premises environment and Azure cloud services. 2. **Network Connectivity**: The self-hosted IR can be installed on a Windows machine within the same network as the Linux database server, enabling secure connectivity without requiring the database to be directly exposed to the internet. 3. **Database Driver Support**: The self-hosted IR supports various database connectors and drivers that can connect to databases regardless of the underlying operating system. The IR communicates with the database using standard database protocols (like ODBC, JDBC), not through OS-level integration. 4. **Security and Performance**: Data remains within the corporate network during transfer, and the self-hosted IR provides optimal performance for on-premises to cloud data movement. ### Why Other Options Are Less Suitable: - **Azure Integration Runtime (Option B)**: This runtime operates entirely within Azure's cloud infrastructure and cannot directly access on-premises resources without additional networking configurations like VPN or ExpressRoute. It's designed for cloud-to-cloud data movement. - **Azure-SSIS Integration Runtime (Option C)**: While technically capable of connecting to on-premises databases, Azure-SSIS is primarily designed for running SQL Server Integration Services packages and represents an over-engineered solution for a simple data copy operation. It's more complex to set up and manage compared to the self-hosted IR for basic data movement tasks. ### Best Practice Considerations: The self-hosted integration runtime follows Azure Data Factory best practices for hybrid data movement scenarios, providing the most straightforward and efficient solution for copying data from on-premises databases to Azure cloud storage while maintaining security and performance requirements.

Author: LeetQuiz Editorial Team