Home / ML Associate practice test / Databricks Machine Learning / Question

Databricks Machine Learning Associate · free practice question

A company has three Databricks workspaces for development, staging, and production. Multiple teams need to discover and reuse governed feature tables across…

Exam-style question on Databricks Machine Learning from the free ML Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Databricks Machine Learning

A company has three Databricks workspaces for development, staging, and production. Multiple teams need to discover and reuse governed feature tables across those workspaces without recreating them locally. Why is storing feature tables in Unity Catalog generally preferable to legacy workspace-level Feature Store tables?

  1. AWorkspace-level feature tables are preferable, as they are queryable from each workspace by default, whereas Unity Catalog feature tables stay hidden outside the workspace where they were first created
  2. BWorkspace-level feature tables are preferable, as lineage, permissions, and discovery are more granular there, while Unity Catalog limits a table to one owner and blocks cross-workspace sharing by design
  3. CUnity Catalog feature tables are preferable for teams without centralized governance needs, as account-level feature tables are harder to discover and are not taggable or searchable in the Databricks UI
  4. DUnity Catalog feature tables are preferable, as they provide centralized governance, lineage, and cross-workspace access through the metastore and are easier to share than workspace-scoped feature assets
  5. ENeither is preferable in practice, as account-level and workspace-level feature tables are stored with identical sharing, privilege, and model-serving behavior in current Databricks releases
Answer & explanation

Correct answer: D

WHY D: Unity Catalog feature tables are governed centrally and can be accessed across workspaces attached to the same metastore, with lineage and consistent privileges.

WHY NOT A: The sharing behavior is the opposite: workspace-level tables are scoped to one workspace, and Unity Catalog tables are the ones visible across workspaces.

WHY NOT B: Unity Catalog improves governance and sharing rather than weakening it; it does not block cross-workspace sharing.

WHY NOT C: Unity Catalog is the choice for centralized governance, and UC feature tables can be discovered, searched, and tagged.

WHY NOT E: There are meaningful governance and cross-workspace differences between the two.

Take the full ML Associate practice test free →

Would you pass today?

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

Start the free test →