Databricks-DE-Pro Data Governance Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Automatically import all Hive Metastore permissions during migration.

  Why it's wrong here

  Automatically migrating old permissions is dangerous as it carries over outdated and potentially insecure access policies. Migration is an opportunity to clean up permissions, implement consistent naming conventions, and apply the principle of least privilege, which is far more beneficial than replicating legacy flaws into the new governance system.

• ✓

  Implement a role-based access control (RBAC) model in Unity Catalog.

  Why this is correct

  RBAC is the gold standard for enterprise governance. By creating functional roles and assigning them to groups in Unity Catalog, you ensure that permissions are consistent, easy to manage, and auditable. This approach scales much better than assigning permissions to individual users and avoids the complexity of manual, ad-hoc access management.

• ✗

  Grant every user 'ADMIN' access to simplify the migration process.

  Why it's wrong here

  Granting administrative access to all users is a massive security risk that violates every principle of data governance. It exposes sensitive data, increases the risk of accidental deletion or corruption, and makes compliance auditing impossible. Security should always be a primary consideration, and simplicity should never be prioritized over safety.

• ✗

  Use the metastore owner's credentials for all data access.

  Why it's wrong here

  Relying on a single set of credentials for all data access violates the principle of accountability and makes it impossible to identify which individual or process performed specific actions. Each user or service principal should have their own identity, allowing for detailed audit logs and granular, secure access management in Unity Catalog.