Question

A retail company stores a BigQuery table containing customer purchase records. The table includes columns such as customer_id, purchase_amount, and a sensitive credit_card_hash column. A team of financial analysts needs to run aggregate queries on purchase_amount but must never be able to read the credit_card_hash column. Compliance requires that access controls be enforced at query time without duplicating or restructuring the table into separate tables. Which approach best meets these requirements?

Accepted Answer

Apply a policy tag from a Data Catalog taxonomy to the credit_card_hash column and use column-level access control to deny the analysts' group the Fine-Grained Reader role on that tag.

Answer

Grant the analysts the BigQuery Data Viewer role on the dataset and instruct them not to select the credit_card_hash column in their queries.

Answer

Create an authorized view that excludes credit_card_hash and copy the base table's data into a new masked table each night for the analysts.

Answer

Enable customer-managed encryption keys (CMEK) on the table and withhold the KMS decrypt permission from the analysts for the credit_card_hash column.