Home / Data Analyst practice test / Executing queries using Databricks SQL and Databricks SQL Warehouses / Question

Databricks Data Analyst Associate · free practice question

A data engineering team connects their Snowflake environment to Unity Catalog using Lakehouse Federation. They want all query execution for Snowflake data to…

Exam-style question on Executing queries using Databricks SQL and Databricks SQL Warehouses from the free Data Analyst practice test, with the answer and a full explanation below.

Updated November 10, 2026

Executing queries using Databricks SQL and Databricks SQL Warehouses

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?

  1. AQuery federation — works by pushing SQL down to the remote database via JDBC, meaning Snowflake compute executes the remote portion of the query rather than Databricks, which does not satisfy the requirement for all-Databricks execution
  2. BAuto Loader ingestion federation — loads Snowflake export files from S3 into Delta and runs all compute on Databricks, but this requires materializing data first rather than federating live access
  3. CLakeflow Declarative Pipelines federation — reads from a Snowflake connection defined in Unity Catalog and writes results into managed Delta tables, but pipelines must materialize data before any Databricks SQL query can access it
  4. DDelta Sharing reverse connection — pulls Snowflake data into a Delta Sharing provider and allows Databricks recipients to query it, but this model still triggers Snowflake-side compute to serve the share
  5. ECatalog federation — creates a foreign catalog that accesses the Snowflake tables directly from their underlying object storage without using Snowflake's query engine, so all query execution runs entirely on Databricks compute
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.

Take the full Data Analyst practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Analyst Associate practice test. Take it and get a section-by-section score.

Start the free test →