Home / Data Analyst practice test / Securing Data

Free · 5 questions with explanations

Securing Data: Databricks Data Analyst Associate Practice Questions

Exam-style questions on Securing Data. Pick your answer, then open the explanation to see why it's right — and why the other options are wrong.

Updated November 10, 2026

1 Securing Data

A data governance administrator needs to delegate the ability to grant and revoke privileges on a Unity Catalog schema to a senior analyst. Which principals are authorized to perform this action?

  1. AAny workspace user who has been granted the MODIFY privilege on the schema that contains the object
  2. BThe account admin who provisioned the metastore, as the single principal able to change its grants
  3. CWorkspace admins of the attached workspace, who control privilege assignments across the metastore
  4. DThe metastore admin, the owner of the object, or a user holding the MANAGE privilege on the object
  5. EAny user holding the USE CATALOG privilege on the parent catalog, whatever their role on the object
Show answer & explanation

Correct answer: D

WHY D: In Unity Catalog, privileges on a securable object can be granted or revoked by the metastore admin, the owner of that object, a user with the MANAGE privilege on the object, or the owner of the catalog or schema that contains the object. This is documented in the Unity Catalog privilege model. WHY NOT A: MODIFY is a write-access privilege on data content; it does not confer the ability to manage access control grants on an object. WHY NOT B: Account admins have broad capabilities, but the authority to grant privileges is also held by object owners and MANAGE-privilege holders; it does not belong to the account admin who created the metastore alone. WHY NOT C: Workspace admins have administrative rights within their workspace, but privilege management in Unity Catalog rests with the metastore admin, object owners and users holding MANAGE, not with workspace admins as such. WHY NOT E: USE CATALOG lets a user navigate into a catalog and reach objects within it; it does not authorize changing access-control grants on objects inside that catalog.

2 Securing Data

A security team requires that all users outside the hr_analysts group see NULL instead of the actual Social Security Number values in the employees table. Which Unity Catalog approach correctly implements this column-level PII protection?

  1. AA dynamic view that applies a CASE expression to the SSN column, returning the real value to members of the approved group and NULL to the other users
  2. BA cluster-level access policy on the SQL warehouse that redacts designated sensitive column values according to workspace-level user attribute tags
  3. CA Delta Lake table property set at write time that encrypts the SSN column and limits decryption to clusters configured with the matching key
  4. DA cloud storage IAM policy on the external location that restricts file-level access to the path holding the sensitive Parquet column data files
  5. EA row filter function registered in Unity Catalog that adds a WHERE clause removing rows with non-null SSN values for users outside the group
Show answer & explanation

Correct answer: A

WHY A: Dynamic views are the Unity Catalog mechanism for column-level security, including PII masking. By wrapping the table in a view with a CASE expression that checks current_user() or is_account_group_member(), authors return NULL (or a masked placeholder) to users outside the approved group while approved users see the real values. This is the documented Databricks practice for column-level PII protection. WHY NOT B: SQL warehouse and cluster policies govern compute resource settings such as instance types and autoscaling; they are not a mechanism for column-level masking or user-based redaction at query time. WHY NOT C: Delta Lake table properties control behaviors like schema enforcement and optimized writes; they do not provide column-level access control or encryption that selectively masks values for specific users at query time. WHY NOT D: IAM policies on external locations restrict which users or service principals can reach the storage path at all. They work at the file level, not the column level, and do not mask specific column values for different groups. WHY NOT E: A row filter function removes whole rows for unauthorized users, which would block access to any row with a non-null SSN. That is row-level security, not column-level masking, and it hides the full record instead of just the sensitive column.

3 Securing Data

A data analyst references a table in a Databricks SQL query using the fully qualified identifier sales_prod.transactions.orders. Which Unity Catalog namespace level directly contains the orders table?

  1. AThe catalog, which is the top-level container that directly holds tables, views, and volumes with no level in between
  2. BThe metastore, which is the root-level registry that directly holds each table and view registered for the region
  3. CThe database layer, which is a separate construct below schemas that maps tables to Delta Lake storage locations
  4. DThe function namespace, which is a dedicated object tier placed between schemas and tables in the object hierarchy
  5. EThe schema, which is the second-level namespace that directly contains tables, views, volumes, and functions
Show answer & explanation

Correct answer: E

WHY E: Unity Catalog uses a three-level namespace, catalog.schema.table. In sales_prod.transactions.orders, sales_prod is the catalog, transactions is the schema, and orders is the table. Schemas (level two) are the containers that directly hold data objects such as tables, views, volumes, models, and functions. WHY NOT A: Catalogs are the top-level container, but they do not directly hold tables. They contain schemas, which in turn contain the data objects. WHY NOT B: The metastore is the top-level metadata container for Unity Catalog, but it sits above catalogs and does not directly hold tables or other data objects. WHY NOT C: There is no separate 'database layer' between schemas and storage in Unity Catalog; schemas serve the role that databases played in the two-level Hive metastore model. WHY NOT D: Functions are objects that live within schemas. They are not a namespace tier, and there is no 'function namespace' between schemas and tables.

4 Securing Data

A workspace admin runs DROP TABLE catalog1.schema1.customer_data in Unity Catalog. The customer_data table was created as a managed table. What happens to the underlying data files after this operation?

  1. AThe data files are deleted after a recovery period (7 days by default); until then, UNDROP TABLE can restore the table
  2. BThe data files are copied to a Databricks-owned backup bucket and kept there for 90 days before being permanently deleted
  3. COnly the table metadata entry is deleted from the metastore, but all underlying Parquet data files remain preserved in cloud storage indefinitely
  4. DThe data files are deleted immediately and permanently the moment the DROP TABLE command completes, with no way to recover them
  5. EThe data files are archived to the metastore's cold storage tier and kept until a workspace admin runs a PURGE TABLE command
Show answer & explanation

Correct answer: A

WHY A: For a Unity Catalog managed table, Unity Catalog owns both the metadata and the data files. DROP TABLE removes the table, but the files are only deleted after a recovery period — 7 days by default, configurable from 0 hours to 30 days at the catalog or schema level. Until the period expires, UNDROP TABLE restores the table. WHY NOT B: Databricks does not copy dropped tables to a separate backup bucket. WHY NOT C: Keeping the data files indefinitely after DROP TABLE is the behavior of external tables, not managed tables. WHY NOT D: Deletion is not immediate by default; the recovery period lets you UNDROP the table (only a recovery period explicitly set to 0 hours disables this). WHY NOT E: There is no cold storage tier or PURGE TABLE command; files are removed automatically when the recovery period ends.

5 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
Show 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 →