Question 1

Explain the difference between Azure Data Factory (ADF) and Databricks.

Accepted Answer

ADF is an orchestration and data-movement service; Databricks is a compute platform for analytics and ML. Why it matters: ADF excels at scheduling, branching, retries, and connectors—it's the 'conductor.' Databricks excels at heavy transforms (Spark), Delta Lake, and ML—it's the 'orchestra.' Scalability: ADF scales by parallelism (activities, self-hosted IR nodes); Databricks scales via cluster sizing and auto-scaling....

Question 2

What are the key components of AWS Glue, and how do they work together?

Accepted Answer

Glue Catalog: Central metadata store (Hive-compatible)—enables querying S3 data via Athena/Redshift Spectrum without moving it. Glue Crawlers: Schema discovery and Catalog population—useful for ad-hoc sources; at scale, prefer schema-as-code to avoid crawler cost and drift. Glue ETL Jobs: Serverless Spark for transforms; auto-scaling, pay-per-DPU. Glue DataBrew: Visual prep for non-engineers. Glue Schema Registry: Schema evolution for streaming (Kafka, Kinesis)....

Question 3

What is Azure Data Factory (ADF), and what are its main components?

Accepted Answer

ADF is a cloud-native data integration service for orchestration and movement. Components: Pipelines (logical groups of activities), Activities (Copy, Lookup, Databricks, Data Flow), Datasets (structure definitions), Linked Services (connection configs), Triggers (schedule or event-based), Integration Runtime (IR—compute for execution). Flow: Linked Service -> Dataset -> Activity -> Pipeline -> Trigger....

Question 4

What is Snowflake's architecture, and why is it unique?

Accepted Answer

**Section 1 — The Context (The 'Why')**
Traditional data warehouses collapse under elastic concurrency: fixed clusters either over-provision (cost) or under-provision (queuing). Storage-compute coupling means scaling queries requires scaling storage nodes....

Question 5

What is the difference between S3 and HDFS?

Accepted Answer

S3: Object storage—durable, highly available, decoupled from compute. Pay-per-use, virtually unlimited scale. Eventual consistency (now strong for new overwrites). No data locality. HDFS: Distributed file system—block-based, colocated with compute nodes. Data locality reduces network I/O; strong consistency. Requires cluster management. Why it matters: S3 enables cloud-native, serverless patterns (Lambda, Glue, Athena); HDFS optimizes for batch processing where locality matters....

Question 6

What is the role of AWS Lambda in a data engineering pipeline?

Accepted Answer

Lambda is serverless compute for event-driven, short-lived tasks. Roles: (1) Orchestration: Trigger Glue, EMR, or Step Functions when files land (S3), events arrive (Kinesis), or schedules fire. (2) Light transforms: JSON→Parquet, small aggregations, API calls. (3) Alerts: Validate data, send Slack/PagerDuty on anomalies. Why: No server management; scale to thousands of concurrent invocations; pay per request and duration. Limitations: 15-min timeout, 10GB memory, 6MB payload (sync)....

Question 7

What is the role of the Integration Runtime (IR) in ADF?

Accepted Answer

IR is the compute layer that executes ADF activities—data movement, transformations, and external calls. Types: (1) Azure IR: Managed, cloud-native—for cloud-to-cloud copies, Data Flows, Databricks calls. No maintenance. (2) Self-hosted IR: Install on your VM or container—for on-prem, VNet, or private data sources. You manage scaling and uptime. (3) Azure-SSIS IR: For running SSIS packages in Azure. Why it matters: Data never flows through ADF; it flows through IR. Network topology (cloud vs....

Incedo Cloud & Tools Interview Questions

Companies asking these questions

All 7 Questions

More Interview Prep Guides

Get All Answers in PDF Format

Incedo Cloud & Tools Interview Questions

Companies asking these questions

All 7 Questions

More Interview Prep Guides

Get All Answers in PDF Format