Question 13
Domain 2: Data Ingestion & AcquisitionWhen a source is supported by both Lakehouse Federation and Lakeflow Connect, when is Lakeflow Connect generally the better choice?
Correct answer: B
Explanation
Lakeflow Connect is preferred for sources that need “higher-volume incremental ingestion and lower-latency pipelines into Databricks.” Lakehouse Federation is for querying governed external data in place, while Lakeflow Connect is built for ingestion and pipeline delivery into the Lakehouse.
Why each option is right or wrong
A. When you only need occasional ad hoc read-only queries against the source
Lakehouse Federation fits ad hoc read-only querying of governed external data in place.
B. When you need higher-volume incremental ingestion and lower-latency pipelines into Databricks
Lakehouse Federation is the governed-query option for external systems, whereas Lakeflow Connect is the ingestion-oriented service for moving data into Databricks. In the exam guide, Lakeflow Declarative Pipelines and ingestion objectives emphasize production-ready batch/streaming delivery into the Lakehouse, so when the requirement is higher-volume incremental ingestion with lower-latency delivery, the ingestion path is the better fit rather than querying data in place.
C. When you want to avoid copying any data into Databricks
Lakeflow Connect copies data into Databricks for ingestion and pipeline delivery.
D. When you only need to configure SQL alerts on foreign tables
SQL alerts monitor data quality; foreign-table configuration belongs to Lakehouse Federation.