Home / DE Professional practice test / Data Governance / Question

Databricks Data Engineer Professional · free practice question

A data governance team wants all users in the Databricks account to be able to discover tables registered in a newly created catalog called `analytics` —…

Exam-style question on Data Governance from the free DE Professional practice test, with the answer and a full explanation below.

Updated November 16, 2026

Data Governance Medium

A data governance team wants all users in the Databricks account to be able to discover tables registered in a newly created catalog called analytics — meaning users can view the catalog, its schemas, and table names in Catalog Explorer and search results, even if they cannot yet query the data. The catalog was created via SQL. What is the MINIMUM privilege the team needs to grant, and to which principal?

  1. AGrant USE CATALOG on analytics to All account users.
  2. BGrant SELECT on analytics to All account users.
  3. CGrant BROWSE on analytics to All account users.
  4. DGrant ALL PRIVILEGES on analytics to All account users.
Answer & explanation

Correct answer: C

WHY C is correct: The BROWSE privilege on a catalog allows users to view an object's metadata — including catalog, schema, and table names — using Catalog Explorer, the schema browser, search results, and the lineage graph without granting any access to actual data. Databricks explicitly recommends granting BROWSE on catalogs to the 'All account users' group to make objects discoverable and allow all users to request access. Crucially, catalogs created via SQL statements, the REST API, or the Databricks CLI do NOT grant BROWSE by default — it must be explicitly granted. USE CATALOG is NOT required to view metadata if the user has BROWSE on the catalog.

WHY NOT A: USE CATALOG on a catalog allows a user to interact with objects within the catalog (i.e., run queries), but it does not enable discovery on its own without SELECT or other data access privileges. Granting USE CATALOG to all account users would allow them to traverse the hierarchy but not query data — however, it is a broader grant than needed and is not the targeted discovery mechanism Databricks recommends.

WHY NOT B: SELECT grants read access to data in tables and views. This is far broader and more permissive than needed for mere discoverability. Granting SELECT to all account users on the entire catalog would expose all data, violating least privilege.

WHY NOT D: ALL PRIVILEGES on a catalog grants every applicable privilege to all users on every existing and future object in the catalog. This is an extreme grant that would expose all data and enable modifications, violating fundamentally the principle of least privilege.

Take the full DE Professional practice test free →

Would you pass today?

This question is one of 60 in the free, timed Databricks Data Engineer Professional practice test. Take it and get a section-by-section score.

Start the free test →