Databricks-DE-Assoc Governance and Security Practice Question
Exhibit
{"statement": "GRANT SELECT ON TABLE sales_data TO 'data_scientists'", "catalog": "main", "schema": "prod"}Refer to the exhibit. A data engineer attempts to run the GRANT statement above in a Databricks SQL query editor. What is the most likely reason for failure?
⚠ Common exam trap
Candidates often assume that the current active catalog and schema context apply to GRANT statements, forgetting that Unity Catalog strictly mandates the full three-level namespace.
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 table must be referenced using a three-level namespace.
The command fails because Unity Catalog requires the full three-level namespace (catalog.schema.table). Without specifying 'main.prod.sales_data', the engine cannot locate the table within the hierarchical metadata store. This strict requirement ensures that all data access is explicitly scoped, preventing ambiguity in multi-catalog or multi-schema environments, which is a fundamental tenet of Unity Catalog's governance model for enterprise-grade security and asset management.
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 syntax of the GRANT statement is incorrect.
Why it's wrong here
The SQL GRANT syntax is valid for Unity Catalog. The error is not related to the command structure itself but rather the target identifier. Unity Catalog does not support unqualified table names because it needs to resolve the specific catalog and schema context to verify the user's permissions.
- ✗
The table does not exist.
Why it's wrong here
While it is possible the table is missing, the more systemic issue is the lack of a fully qualified name. In Databricks, when working with Unity Catalog, the system specifically requires the three-level path; providing only the table name results in a resolution error before checking table existence.
- ✓
The table must be referenced using a three-level namespace.
Why this is correct
Unity Catalog requires the fully qualified name (catalog.schema.table). Providing only the table name causes the operation to fail because the metastore cannot resolve the resource context. This forces explicit identification of the data, which is a security best practice to prevent unauthorized or unintended access to tables.
- ✗
The group 'data_scientists' does not exist.
Why it's wrong here
While the group might not exist, the most immediate and common error when transitioning to Unity Catalog is the namespace resolution error. The system will throw a catalog error first before it attempts to validate the existence of the user or group mentioned in the GRANT command.
About these practice questions
This Databricks-DE-Assoc question is part of Courseiva's 276-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.