Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
A data analytics team is onboarding a new data analyst who needs to run SQL query jobs and view table data in BigQuery within a specific Google Cloud project. The team's security policy requires following the principle of least privilege by avoiding overly permissive access across other Google Cloud resources in the project.
Which IAM role approach should the administrator use to grant the required access?
The Editor (roles/editor) role is a legacy basic role that grants extensive read, write, modify, and delete permissions for almost all resources across all Google Cloud services in a project.
A lead developer required comprehensive write access across all services within a dedicated non-production sandbox project to rapidly prototype and manage multi-service architectures.
The Viewer (roles/viewer) role is a legacy basic role (primitive role) that grants broad read-only access across almost all Google Cloud services and resources residing within the assigned project.
bigquery.jobs.create). The Viewer role alone does not provide sufficient permissions to run BigQuery jobs in the project.A stakeholder required global, project-wide read-only visibility into all Google Cloud infrastructure components and configurations for general auditing without executing compute or analytics jobs.
The Writer (roles/writer) role is a broad basic role that contains read permissions plus state-modifying and creation permissions across most Google Cloud services.
An administrative user needed generic write capabilities across a wide spectrum of Google Cloud services where predefined roles or fine-grained access boundaries were not applicable.
Predefined roles in Google Cloud are granular, service-specific Identity and Access Management (IAM) roles created and maintained by Google. Unlike basic roles, which apply broadly across all Google Cloud services in a project, predefined roles bundle specific permissions tailored to distinct job functions and individual services like BigQuery, Cloud Storage, or Vertex AI.
roles/bigquery.jobUser) grants the exact permissions required to run query jobs (bigquery.jobs.create), while BigQuery Data Viewer (roles/bigquery.dataViewer) permits viewing datasets and tables without exposing unrelated services.
Using predefined roles directly aligns with Google Cloud security best practices. Basic roles grant sweeping permissions across hundreds of cloud services simultaneously, which violates enterprise governance and the principle of least privilege.
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