The development teams in your company want to manage resources from their local environments. You have been asked to enable developer access to each team's Google Cloud projects. You want to maximize

Question

Options

• AAdd the users to their projects, assign the relevant roles to the users, and then provide the users
• BAdd the users to their projects, assign the relevant roles to the users, and then provide the users
• CCreate groups, add the users to their groups, assign the relevant roles to the groups, and then
• DCreate groups, add the users to their groups, assign the relevant roles to the groups, and then

• A
  11% (4)
• B
  5% (2)
• C
  81% (30)
• D
  3% (1)

Explanation

Google's IAM best practices explicitly recommend managing access through groups rather than assigning roles to individual users. By creating groups, adding developers to their respective team groups, and assigning IAM roles to the groups, you gain several advantages: onboarding a new developer only requires adding them to a group (no IAM policy changes needed), offboarding is handled by removing them from the group, and auditing is simpler. Options A and B assign roles directly to individual users, which becomes unmanageable at scale and is explicitly an anti-pattern per Google's recommendations. Option D likely describes a similar group-based approach but with a less efficient access method (e.g., service account keys vs. the recommended gcloud CLI / Application Default Credentials), making C the better answer.

No community discussion yet for this question.