Home / Data Analyst practice test / Securing Data / Question

Databricks Data Analyst Associate · free practice question

A data engineering lead wants to grant a team group read access to all tables in a schema — including tables that will be created in the future — without…

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

Updated November 10, 2026

Securing Data

A data engineering lead wants to grant a team group read access to all tables in a schema — including tables that will be created in the future — without needing to re-issue GRANT statements each time a new table is added. What is the correct approach in Unity Catalog?

  1. AGrant SELECT on the schema; the privilege cascades automatically to all current and future tables within it
  2. BIssue a GRANT SELECT on each table individually each time a new table is created, managed through an automation script
  3. CAssign the group the data steward role on the catalog so it automatically inherits read access to all nested schema objects
  4. DGrant SELECT on the entire catalog so all schemas and tables throughout the catalog become readable by the group simultaneously
  5. EAsk a metastore admin to configure automatic privilege inheritance settings on the schema directly via the account console user interface
Answer & explanation

Correct answer: A

WHY A: Unity Catalog uses a downward inheritance model — privileges granted on a schema automatically apply to all current and future tables, views, volumes, and functions nested within that schema. Granting SELECT on the schema is sufficient to cover all objects at the table level without re-granting. WHY NOT B: Issuing individual GRANT SELECT statements per table is valid but inefficient and defeats the purpose of the inheritance model; it also requires re-granting for every future table. WHY NOT C: There is no 'data steward' role in Unity Catalog that provides inherited read access; privileges must be granted explicitly via GRANT statements or through the ownership model. WHY NOT D: Granting SELECT on the catalog is overly permissive — it would cascade access to all schemas within the catalog, not just the target schema, violating the principle of least privilege. WHY NOT E: There is no such 'automatic privilege inheritance settings' option in the account console for schemas; inheritance is a built-in behavior of the GRANT model, not a separately configurable setting.

Take the full Data Analyst practice test free →

Would you pass today?

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

Start the free test →