Practice Test 1 | Google Cloud Certified Professional Data Engineer | Dumps | Mock Test
There is a plan by the data team to migrate the data warehouse to BigQuery. After the migration is done, you are tasked to assign each user the right role to access datasets in BigQuery. You have the following teams need to access the data warehouse:
-
- Data analysts: They need read/write access to data. They should not create or delete datasets.
- Data engineers: They are admins in the data warehouse. They need full privileges on data sets.
- Dev team: They need read access only to the datasets. They can list the project’s data sets and tables.
How would you assign the roles to each team?
A. Assign admin role to data engineer group. Assign dataOwner role to data analyst group. Assign dataViewer role to dev team group.
B. Assign dataOwner role to data engineer group. Assign dataEditor role to data analyst group. Assign user role to dev team group.
C. Assign admin role to data engineer group. Assign dataEditor role to data analyst group. Assign dataViewer role to dev team group.
D. Assign dataOwner role to data engineer group. Assign dataEditor role to data analyst group. Assign dataViewer role to dev team group.
Answer: C.
Here is the table of BigQuery roles and each role’s permissions:
From the list, we can assign each group the right role:
- Data Analysts: They need read & write access to tables without permissions to create & delete data sets. Thus, editor role is assigned to this group.
- Data engineers: It’s stated they will be admins on BigQuery. Admin role should be assigned to this gorup.
- Dev team: They need read access to data and be able to list tables and datasets. Viewer role should be assigned to this group.
Answer A is incorrect: Owner role is too broad for data analysts.
Answer B is incorrect: Data engineers need admin role. User role doesn’t allow dev team to get tables data.
Answer D is incorrect: As B, data engineers need admin role.
Source(s):
BigQuery – Access Control: https://cloud.google.com/bigquery/docs/access-control
Comments are closed, but trackbacks and pingbacks are open.