PROFESSIONAL-CLOUD-ARCHITECT Question #116: Real Exam Question with Answer & Explanation

Question

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?

Options

• AAdd all users to a group. Grant the group the role of BigQuery user on the billing project and
• BAdd all users to a group. Grant the group the roles of BigQuery dataViewer on the billing project
• CAdd all users to a group. Grant the group the roles of BigQuery jobUser on the billing project and
• DAdd all users to a group. Grant the group the roles of BigQuery dataViewer on the billing project

Explanation

BigQuery User: (roles/bigquery.user) When applied to a dataset, this role provides the ability to read the dataset's metadata and list tables in the dataset. When applied to a project, this role also provides the ability to run jobs, including queries, within the project. A principal with this role can enumerate their own jobs, cancel their own jobs, and enumerate datasets within a project. <b>Additionally, allows the creation of new datasets within the project; the creator is granted the BigQuery Data Owner role(roles/bigquery.dataOwner) on these new datasets.</b> Lowest-level resources where you can grant this role: Dataset BigQuery Job User: (roles/bigquery.jobUser) Provides permissions to run jobs, including queries, within the project. Lowest-level resources where you can grant this role: Project Source: https://cloud.google.com/bigquery/docs/access-control

No community discussion yet for this question.