Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A company is configuring IAM access for two teams in Google Cloud to align with security best practices and the principle of least privilege:
Which combination of IAM role types should be used for Team A and Team B?
Predefined roles are fine-grained roles created and managed directly by Google Cloud. They bundle permissions tailored to specific services or job functions (for example, BigQuery Data Viewer). In contrast, custom roles are user-defined IAM roles that allow organizations to select and package specific supported IAM permissions into a single role to enforce strict least privilege.
This approach directly satisfies all constraints for both teams:
storage.objects.get and compute.instances.start).Using a predefined role for Team A avoids the ongoing administrative burden of tracking new BigQuery permissions manually. Using a custom role for Team B ensures that automated workloads have strictly the minimum access required to execute their scripts, preventing privilege creep and lateral movement risks.
This option creates a user-managed custom role for the BigQuery analysts (Team A) and assigns a basic role (such as Viewer or Editor) to the automation service accounts (Team B).
This choice reverses the required strategies for both groups:
This option would be suitable if Team A needed a non-standard set of BigQuery permissions that Google's predefined roles did not accommodate, and Team B required broad, unrestricted access across all resources in a non-production test project.
When predefined roles already satisfy a job function's operational needs, creating a custom role unnecessarily increases administrative overhead because every future feature update requires manual intervention.
This option assigns a basic role (such as Viewer) to Team A and creates a tailored custom role for Team B.
While creating a custom role for Team B correctly addresses their need for an exact, minimal permission set, assigning a basic role to Team A fails critical security and operational criteria:
roles/bigquery.dataViewer or roles/bigquery.user) should be used instead to limit access strictly to BigQuery assets.This configuration would be correct if Team A were general project auditors who legitimately required view-only access to every resource and service across the entire Google Cloud project, rather than focused access limited to BigQuery datasets.
Predefined roles are structured with the naming convention roles/SERVICE.ROLE_NAME (such as roles/bigquery.dataViewer), allowing administrators to grant granular access per service, unlike basic roles (roles/viewer, roles/editor, roles/owner).
Basic roles (historically known as primitive roles) consist of Owner, Editor, and Viewer, as well as Admin, Writer, and Reader. They provide broad, coarse-grained access across all Google Cloud services in a project. Predefined roles provide granular access defined by Google for specific services.
This configuration fails both team requirements:
roles/viewer) to Team A grants read access across virtually every Google Cloud service in the project (including Cloud Storage, Compute Engine, Cloud SQL, and Secret Manager), which violates the requirement for granular access limited to BigQuery.This option would be appropriate if Team A were working in a temporary sandbox or development project where broad, project-wide read access was desirable, and if Team B's access requirements perfectly matched an off-the-shelf predefined role.
Google Cloud strongly discourages granting basic roles in production environments because they grant excessive authority and directly violate 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