Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is migrating its sensitive analytics data warehouse to BigQuery. Under regulatory compliance standards and the cloud shared responsibility model, the organization must enforce strict data ownership and least privilege access governance:
Which Identity and Access Management (IAM) role configuration should the organization implement?
roles/editor) role, grant business analysts the BigQuery Studio Admin (roles/bigquery.studioAdmin) role, and assign Cloud Data Fusion Service Agent roles to pipeline runners.This option relies on basic (primitive) IAM roles (roles/editor) for the governance team and administrative studio roles (roles/bigquery.studioAdmin) for analysts, alongside misconfigured service agent roles.
roles/editor role provides broad edit permissions across virtually all Google Cloud services in the project (such as Compute Engine, Cloud Storage, and VPC networks), which severely violates the constraint against granting broad project-level infrastructure permissions.roles/bigquery.studioAdmin role grants administrative management over BigQuery Studio assets and workflows rather than restricting users to read-only query execution.roles/editor) lack fine-grained data access controls.The governance team were full cloud infrastructure administrators managing all non-IAM cloud services in a development environment.
roles/bigquery.admin) role at the project level, grant business analysts the Dataplex Storage Data Owner (roles/dataplex.storageDataOwner) role, and grant custom users the DLP API Service Agent role.This configuration grants full administrative authority over BigQuery at the project level to the governance team, assigns Dataplex storage ownership to analysts, and applies DLP service agent roles to end users.
roles/bigquery.admin role provides complete administrative control over all BigQuery resources and jobs across the entire project, exceeding the specific dataset ownership scope required.roles/dataplex.storageDataOwner role grants data ownership and management permissions over storage assets rather than providing restricted, read-only analytical query execution in BigQuery.roles/dlp.serviceAgent to custom users violates core IAM security principles, as service agent roles are specifically intended for internal platform service agents.roles/bigquery.admin grants global project-level control over all BigQuery configurations and jobs.roles/dataplex.storageDataOwner provides ownership rights that violate read-only analyst boundaries.The Data Governance team required full project-level administration of all BigQuery configurations and jobs, and analysts managed Dataplex lake assets.
roles/bigquery.dataEditor) role, grant business analysts the BigQuery User (roles/bigquery.user) role, and grant the Cloud Dataflow Service Agent role to the analytics team service account.This configuration uses the BigQuery Data Editor role for governance administrators and the broader BigQuery User role for analysts, while assigning a service agent role directly to a custom user-managed service account.
roles/bigquery.dataEditor role allows modifying, appending, and deleting tables within a dataset, but it does not allow modifying dataset access permissions or managing dataset-level metadata. The Data Governance team cannot fulfill its ownership obligations.roles/bigquery.user role includes permissions to create new datasets within the project, which exceeds the read-only querying requirements of business analysts.roles/dataflow.serviceAgent) are internal roles designed solely for Google-managed service agents and should never be assigned to custom user-managed service accounts or human principals.roles/bigquery.dataEditor lacks dataset access control management.roles/bigquery.user grants dataset creation rights across the project.The governance team only needed to edit table data without managing access policies, and analysts needed permission to create personal datasets in the project.
roles/bigquery.dataOwner) role, grant business analysts the BigQuery Data Viewer (roles/bigquery.dataViewer) and BigQuery Job User (roles/bigquery.jobUser) roles, and maintain service agent roles strictly for Google-managed service agents.BigQuery predefined IAM roles provide granular access control specifically tailored to data assets, separating administrative duties from analytical querying tasks. The BigQuery Data Owner (roles/bigquery.dataOwner) role gives full control over dataset configuration, data contents, and access permissions at the dataset level without granting broad Google Cloud project-level permissions like roles/owner or roles/editor.
roles/bigquery.dataOwner allows the governance team to read, update, create, and delete tables and datasets, as well as configure access control lists (ACLs) on datasets, ensuring complete data ownership and authority.roles/bigquery.dataViewer enables analysts to view dataset contents and schemas, while roles/bigquery.jobUser provides the required permissions to execute query jobs and spend project query slots without giving table modification rights.roles/bigquery.jobUser) distinct from data viewing privileges (roles/bigquery.dataViewer).This configuration aligns perfectly with the shared responsibility model. It establishes precise data governance boundaries while preventing over-privileged access across cloud analytics resources.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated