Home › Learn › Databricks interview prep › Lakeflow Connect

Databricks interview prep · data engineering

Lakeflow Connect: managed ingestion

What Lakeflow Connect is, how it works, when to use it versus Auto Loader, federation, sharing and COPY INTO, and the hard points to know.

Maintenance commandsRow-level securityCompute choiceJoinsSkew and shuffleAQE, Photon, POCost and performance leversDeclarative and semanticAsset BundlesLakeflow ConnectUniFormVector Searchdbt and ODCSEgress and ingressMaintenance in picturesClustering and compactionMaintenance strategySlow writesBackup and recoveryTaggingQuestion bank

Defaults, limits and preview status change often. Check the current Databricks docs before quoting a number.

Connection (credentialsin Unity Catalog)Ingestion pipeline: picktables, set destinationGateway reads the source(change log fordatabases)Delta tables in UnityCatalog

A managed copy from a source into your lakehouse, kept up to date.

The idea

What it is

Lakeflow Connect is a set of managed ingestion connectors. You give a connection and a target; Databricks runs the pipeline that copies the data into Unity Catalog Delta tables and keeps it current. You write no extraction code and run no CDC infrastructure. For databases it reads the change log, so inserts, updates and deletes are captured. It runs on serverless pipeline compute and handles schema changes. It can also be set up in the UI, the API, or as a bundle.

The connector list and status change often (SaaS apps such as Salesforce, Workday, ServiceNow and Google Analytics; databases such as SQL Server; SharePoint). Check the current list.

Choose

When to use it and when not

SituationChoice
Supported SaaS app, no wish to maintain API codeLakeflow Connect: pagination, rate limits, retries and schema changes handled
Continuous replication from an operational databaseLakeflow Connect: log-based CDC, low source load, deletes captured
Small team, many sourcesLakeflow Connect: one pattern instead of many jobs
Files landing in cloud storageAuto Loader
Message streams (Kafka, Event Hubs, Kinesis)Structured Streaming connectors
Source not supportedCustom code or a third-party tool
Occasional queries, small data, freshness not criticalLakehouse Federation (query in place)
Data already shared by another platformDelta Sharing
Simple idempotent batch file loadCOPY INTO
Heavy transformation during extractionIngest raw first, transform in pipelines
Private source the connector cannot reachCheck private connectivity first
Replacing a third-party ELT toolCompare real costs for the same sources

Hard points

Questions behind the features

Practice

Questions to rehearse

  1. Lakeflow Connect versus Auto Loader: how do you choose?
  2. Connect versus Lakehouse Federation: when do you copy and when query in place?
  3. How does log-based CDC avoid hammering the source?
  4. How are deletes propagated into the Delta target?
  5. The source adds a column. What happens?
  6. How would you justify replacing Fivetran with it?
In an interview, say: Query in place when volume and freshness needs are small; copy with Connect when I need performance, history or isolation from the source.

FAQ

Questions people ask

Is it the same as Auto Loader?

No. Auto Loader ingests files from storage. Connect copies from apps and databases.

Does it capture deletes?

Database connectors read the change log, so yes. SaaS depends on the source's API.

Next

Where to go next

All Databricks interview topics · All data engineering · Databricks on this site