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?
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.