GCP Associate Cloud Engineer Practice Question 61: IAM Group Based Access
Google Cloud Associate Cloud Engineer · Test 7 · question 1 of 10
A data analytics team has frequent membership changes as contractors rotate on and off the project every few weeks. The team needs read access to a set of BigQuery datasets, and an administrator wants to avoid updating IAM policies every time someone joins or leaves the team. What should the administrator do to grant and manage this access with the least ongoing effort?
Show answer and explanation
Answer:
Granting IAM roles to a Google Group lets the administrator set the IAM policy binding once, against the group's email address. From then on, membership changes are handled entirely through group membership in Cloud Identity or Google Workspace: adding a contractor to the group grants them access immediately, and removing them revokes it, with no change to any IAM policy. This is the standard Google Cloud recommended pattern for managing access for a team whose membership changes often.
A is wrong and insecure: sharing a single service account key among multiple people removes any per-user accountability, keys do not expire on their own, and Google explicitly discourages downloading and distributing service account keys. B works but requires editing the IAM policy on every join and every departure, which is exactly the ongoing maintenance effort the administrator wants to avoid. C changes only which role is granted, not how it is granted; a custom role bound to individual user accounts still requires an IAM policy update for every membership change. D is correct because it decouples day-to-day membership management from IAM policy changes.
Reference: Best practices for using Google groups