Databricks-GenAI-Assoc Governance Practice Question
Exhibit
CREATE TABLE main.finance.reports AS SELECT * FROM raw_data; GRANT SELECT ON TABLE main.finance.reports TO `analyst_group`; -- Later, a user drops the table and re-creates it. -- The analyst group can no longer query the table.
Refer to the exhibit. Why did the analyst group lose access after the table was recreated?
⚠ Common exam trap
Candidates mistakenly believe that object permissions persist even if the underlying table is dropped and recreated, forgetting that Unity Catalog treats a new table as a distinct object ID.
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 new table is a different object, so the GRANT statement must be repeated.
In Unity Catalog, privileges are bound to the specific object ID. When a table is dropped and re-created, it becomes a new object with a new unique identifier. The previous GRANT statements, which were associated with the original object ID, do not automatically apply to the new table. This mechanism protects against security drift by ensuring that every new object must have its permissions explicitly managed.
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 catalog owner needs to refresh the table metadata.
Why it's wrong here
Refreshing metadata does not propagate permissions to new objects. The issue is not related to metadata freshness but rather the fundamental way Unity Catalog handles object identity; each re-creation generates a distinct object that inherits no permissions from its predecessor.
- ✗
The analyst group needs to be re-added to the schema permissions.
Why it's wrong here
While schema permissions remain, table-specific permissions are lost. Re-adding the group to the schema would not restore the specific SELECT privilege on the new table object, because that privilege is tied to the specific table object that was deleted and replaced.
- ✓
The new table is a different object, so the GRANT statement must be repeated.
Why this is correct
Unity Catalog treats the newly created table as a entirely new resource with a fresh identity. Any permissions applied to the previous version of the table do not carry over to the replacement, requiring administrators to re-issue GRANT commands for the new object.
- ✗
The user who recreated the table is not the catalog owner.
Why it's wrong here
Ownership does not solve the underlying issue of permission binding. Even if the catalog owner recreated the table, the previous SELECT permissions for the analyst group would remain lost. Permissions are object-specific, not attached to the user who performed the DDL operation.
About these practice questions
One of 330 original Databricks-GenAI-Assoc practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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-GenAI-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-GenAI-Assoc exam.