A data engineering team connects their Snowflake environment to Unity Catalog using Lakehouse Federation. They want all query execution for Snowflake data to happen exclusively on Databricks compute, not on the Snowflake engine. Which Lakehouse Federation type achieves this?
Answer & explanation
Correct answer: E
WHY E: Catalog federation accesses table data directly from object storage using the external catalog's layout, bypassing the remote database engine entirely, so all compute runs on Databricks. WHY NOT A: Query federation pushes compute to the remote Snowflake engine via JDBC, which violates the all-Databricks requirement. WHY NOT B: Auto Loader is a file ingestion tool, not a live federation mechanism. WHY NOT D: Delta Sharing is not a pull-from-Snowflake federation protocol and does not support this reverse integration. WHY NOT C: Lakeflow Declarative Pipelines materialize data first; they do not provide live federated access.