Databricks-DE-Assoc Governance and Security Practice Question
Exhibit
GRANT USAGE ON CATALOG main TO `data_analysts_group`; GRANT USAGE ON SCHEMA main.sales TO `data_analysts_group`; GRANT SELECT ON TABLE main.sales.orders TO `data_analysts_group`;
Refer to the exhibit. A user who is a member of 'data_analysts_group' reports they cannot see the 'orders' table in the Catalog Explorer. What is the most likely cause?
⚠ Common exam trap
Candidates focus solely on table-level permissions and overlook the requirement for 'USAGE' privileges on the parent catalog and schema, which are mandatory for object discovery in the UI.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The user lacks the 'USAGE' privilege on the parent objects.
In Unity Catalog, the 'USAGE' privilege is a mandatory prerequisite for navigating any parent object. Even if the user has SELECT access on the table, they must also hold USAGE on the parent catalog and schema to traverse the hierarchy and discover the table. Without these permissions, the object remains invisible to the user in the UI, even if they have technical access to the underlying data records.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The user lacks the 'SELECT' privilege.
Why it's wrong here
The exhibit shows the SELECT privilege was explicitly granted to the group. Assuming the user is a member of the group, they should possess the permission. The failure to see the table in the UI is typically a visibility or navigational issue, not a lack of data access privilege.
- ✓
The user lacks the 'USAGE' privilege on the parent objects.
Why this is correct
Unity Catalog requires USAGE on the catalog and schema to navigate to the table. If these permissions were missing, the user would not be able to traverse the path to the table in Catalog Explorer, even if they had SELECT permissions on the table itself. This is a common security configuration error.
- ✗
The table is not registered in the Hive Metastore.
Why it's wrong here
Unity Catalog is distinct from the Hive Metastore. Once an object is in Unity Catalog, it is governed by Unity Catalog's own security model. Whether or not it exists in the legacy Hive Metastore is irrelevant to the visibility of the table within the Unity Catalog governance framework.
- ✗
The group does not exist in the workspace.
Why it's wrong here
If the group did not exist, the GRANT statements themselves would have failed during execution. Since the statements were provided as a successful configuration context, we must assume the group exists and is valid. The issue is strictly related to the hierarchical permission requirements for navigation and object discovery.
About these practice questions
Courseiva writes every Databricks-DE-Assoc question from scratch — 276 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DE-Assoc practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DE-Assoc exam.