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?
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.