Your company is using BigQuery as its enterprise data warehouse. Data is distributed over several Google Cloud projects. All queries on BigQuery need to be billed on a single project. You want to make sure that no query costs are incurred on the projects that contain the data. Users should be able to query the datasets, but not edit them. How should you configure users' access roles?

The correct answer ensures query costs are centralized and data access is read-only. The BigQuery Job User role on the billing project allows users to run jobs (queries) and specifies that this project will incur the associated costs. The BigQuery Data Viewer role on the data projects grants read-only access to the datasets, preventing users from modifying the data. Incorrect options: Granting BigQuery User on the billing project is insufficient as it doesn't explicitly grant permission to run jobs, which is required for querying. Granting BigQuery Data Viewer on the billing project doesn't allow for running queries. Granting BigQuery Job User on the data projects would mean query costs are billed to those projects, which contradicts the requirement to bill on a single project.