Home / Data Analyst practice test / Managing Data / Question

Databricks Data Analyst Associate · free practice question

A data governance team is tagging tables in Unity Catalog to support a new data classification initiative. A data steward needs to add a tag with key…

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

Updated November 10, 2026

Managing Data

A data governance team is tagging tables in Unity Catalog to support a new data classification initiative. A data steward needs to add a tag with key pii_category and value contact_info to the customers.profiles.email_address column of an existing Delta table. The steward has been granted APPLY TAG on the table, USE SCHEMA on customers.profiles, and USE CATALOG on customers, but is NOT the table owner. Additionally, a junior engineer asks whether they can tag multiple columns on the same table in a single SQL ALTER TABLE statement. Which of the following statements is CORRECT?

  1. AThe steward is not able to add the tag: APPLY TAG on a table covers the table-level object, and a separate APPLY TAG ON COLUMN privilege has to be granted for each column to be tagged. The junior engineer, however, can tag several columns in one ALTER TABLE statement with a comma-separated column list, which is the recommended approach for bulk column tagging as it reduces transaction overhead on the Unity Catalog metastore.
  2. BThe steward's privileges are sufficient: APPLY TAG on the table covers table-level and column-level tags, and together with USE SCHEMA and USE CATALOG it forms the documented minimum for a non-owner. The tag 'pii_category' = 'contact_info' is added to email_address in Catalog Explorer or with an ALTER TABLE statement. The junior engineer has to tag each column in a separate ALTER TABLE statement, unlike COMMENT, which accepts several columns.
  3. CThe steward's privileges are not sufficient: USE SCHEMA and USE CATALOG are navigation permissions that workspace users receive by default on accessible catalogs, and they play no part in the authorization check for tagging. Column tags are applied by the table owner, so a non-owner is given table ownership temporarily, applies the tags, and has ownership transferred back. The junior engineer can then tag several columns in one statement.
  4. DThe steward's privileges are sufficient, and tag keys are case-insensitive and stored in lowercase, so pii_category and PII_CATEGORY are treated as one tag. A table has no cap on its number of column tags, and the junior engineer can apply up to 50 tags across multiple columns in a single ALTER TABLE statement by adding a WHERE clause that filters the target columns by a name pattern, which avoids one statement per column.
  5. EThe steward can add the tag, and Unity Catalog encrypts the value contact_info with AES-256 before storage, as tag values on PII-related columns are classed as sensitive governance metadata; the values are then visible to users holding the VIEW ENCRYPTED METADATA privilege, while tag keys stay in plain text. The junior engineer's bulk statement succeeds once the steward approves the batch in the tag approval workflow.
Answer & explanation

Correct answer: B

WHY B: The documentation states that a non-owner adding tags to a Unity Catalog securable needs three privileges: APPLY TAG on the object, USE SCHEMA on the parent schema, and USE CATALOG on the parent catalog. The steward has all three, and APPLY TAG on a table covers both table-level and column-level tagging for that table. Tagging can be done in Catalog Explorer (on the column) or with SQL ALTER TABLE. On bulk tagging the documentation says: 'You cannot assign tags to multiple columns in a single ALTER TABLE command. You must assign tags to each column separately. This differs from the COMMENT clause, which does support multiple columns in one command.'

WHY NOT A: APPLY TAG on a table does cover column-level tagging for that table; there is no separate APPLY TAG ON COLUMN privilege. A comma-separated multi-column tag statement is also not possible: the documentation rules out tagging multiple columns in one ALTER TABLE command.

WHY NOT C: USE SCHEMA and USE CATALOG are documented as required parts of the three-privilege minimum for a non-owner, not as mere navigation rights, and they are not granted to users by default: Unity Catalog works on a least-privilege model. Ownership is not needed, and multi-column tagging in one statement is not supported.

WHY NOT D: Tag keys are case sensitive, so pii_category and PII_CATEGORY are two distinct tags. There are caps: a table can have at most 1,000 column tags across its columns, and a single securable object supports at most 50 tags. ALTER TABLE tagging has no WHERE clause for filtering columns by name pattern.

WHY NOT E: Unity Catalog does not encrypt tag values, whether or not they sit on PII-related columns. The documentation warns: 'Tag data is stored as plain text and may be replicated globally. Do not use tag names, values, or descriptors that could compromise the security of your resources.' There is no VIEW ENCRYPTED METADATA privilege, no AES-256 tag encryption, and no tag approval workflow for bulk tagging.

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 →