A company wants data quality scans to run with least privilege, respect row-level and column-level access policies, provide clearer audit attribution, and centralize processing charges directly under BigQuery. What should the team configure?

Question

Accepted Answer

B. Use a custom execution identity for the data quality scans. A custom execution identity can improve least-privilege access, work better with row-level and column-level policies, make audit attribution clearer, and unify billing under BigQuery. Keeping the default service agent does not provide the same fine-grained control and audit clarity described in the scenario.

A company wants data quality scans to run with least privilege, respect row-level and column-level access policies, provide clearer audit attribution, and centralize processing charges directly under BigQuery. What should the team configure?

Related Questions

Discussion