Question 1

Copy Large Files from On-Premises to Azure in ADF

Accepted Answer

Why it matters: On-prem to cloud bulk transfer is a common hybrid pattern; poor design causes WAN bottlenecks, cost overruns, and failed SLAs. Architectural logic: Use SHIR as a bridge—it runs in your network, so latency stays within the LAN for the source leg. Azure IR cannot reach on-prem; SHIR is mandatory. Scalability trade-offs: parallelCopies (default 4, max 256 for cloud, hardware-limited for SHIR) multiplied by DIUs drives throughput....

Question 2

On-Premises to Cloud Integration Runtime

Accepted Answer

**Why Self-Hosted IR (SHIR)**: ADF runs in Azure; on-prem data sources (SQL Server, file shares) are not directly reachable. SHIR runs on-prem, registers with ADF, executes data movement locally. **Architecture**: Install SHIR on Windows/Linux VM; requires outbound HTTPS (port 443) to Azure. Register with auth key from ADF. SHIR pulls jobs from ADF control plane; executes copy/transform on-prem. Use ExpressRoute or VPN for secure, predictable connectivity....

Question 3

What is Integration Runtime?

Accepted Answer

**Integration Runtime (IR)**: Compute infrastructure that executes ADF activities—data movement, transforms, and external calls. ADF is orchestration; IR is execution. **Types**: Azure IR (managed, cloud), Self-Hosted IR (on-prem), Azure-SSIS IR (SSIS). **Why it matters**: Every Copy activity, Data Flow, and external activity runs on an IR. IR choice determines where compute runs and what it can reach. **Scalability**: Azure IR auto-scales; SHIR scales by adding nodes....

Presidio Cloud & Tools Interview Questions

Companies asking these questions

All 3 Questions

More Interview Prep Guides

Get All Answers in PDF Format

Presidio Cloud & Tools Interview Questions

Companies asking these questions

All 3 Questions

More Interview Prep Guides

Get All Answers in PDF Format