Databricks Machine Learning Associate Question 424
Select 3What are the benefits of creating feature store tables at the account level in Unity Catalog in Databricks compared to creating them at the workspace level?
- A
Feature store tables can be accessed across multiple workspaces, enabling better collaboration between teams.
- B
Account-level feature store tables improve model performance by optimizing feature transformation pipelines.
- C
Centralized governance and access control can be applied across workspaces for all feature store tables.
- D
Data duplication is minimized because features do not need to be replicated across multiple workspaces.
- E
Feature store tables at the account level automatically enforce stricter data quality checks compared to workspace-level tables.
Show answer and explanation
Correct answers: A, C, D
Explanation
Creating feature store tables at the account level in Unity Catalog allows teams to share and reuse features across multiple workspaces, reducing data duplication and fostering collaboration. Additionally, account-level tables benefit from centralized governance, enabling consistent access control and compliance across workspaces. However, performance improvements and data quality enforcement are not inherent benefits of account-level tables and depend on how features and pipelines are implemented.
- A. Correct.
Correct: At the account level, feature store tables are accessible across multiple workspaces, making it easier for different teams to collaborate and share features.
- B. Incorrect.
Incorrect: Account-level feature store tables do not inherently improve model performance or optimize feature transformation pipelines. These improvements depend on implementation rather than table scope.
- C. Correct.
Correct: Unity Catalog allows centralized governance and access control, ensuring consistent permissions and policies across multiple workspaces for account-level feature store tables.
- D. Correct.
Correct: By storing features at the account level, data duplication is minimized since the same features can be reused across various workspaces instead of being duplicated in each workspace.
- E. Incorrect.
Incorrect: Unity Catalog does not automatically enforce stricter data quality checks for account-level feature store tables. Data quality enforcement depends on user-defined validations and processes.