Databricks Data Engineer Professional · Free practice question 7 of 12
Workspace-catalog binding isolation
Selby Health's prod catalog must be accessible only from the production workspace, even though development workspaces share the same Unity Catalog metastore. How should this be enforced?
- A.Revoke USE CATALOG from all users in development workspaces
- B.Create a separate metastore for the production workspace in the same region
- C.Make the catalog isolated and bind it to the production workspace only (workspace-catalog binding)
- D.Use a cluster policy in the development workspaces that blocks the catalog
Show answer and explanation
Correct answer: C. Make the catalog isolated and bind it to the production workspace only (workspace-catalog binding)
Why: Workspace-catalog binding lets an admin restrict a catalog to specific workspaces, so it cannot be accessed from other workspaces attached to the same metastore, whatever privileges users hold. Grants apply to principals, not workspaces, and the same users often work in both. A region supports one metastore per account, and cluster policies do not control catalog access.
More free Databricks Data Engineer Professional questions
- Databricks SQL alerts with notifications
- Partitioning guidance for mid-size tables
- VACUUM retention duration safety check
- SQL warehouse sizing versus scaling
- BROWSE privilege for data discovery
- UNDROP TABLE for managed tables
- Bundle generate and deployment bind
- Driver memory and toPandas
- Continuous job trigger for streaming
- Table update triggers for jobs
- Serverless environment dependencies