Q: 2
You are the project owner of a GCP project and want to delegate control to colleagues to manage buckets and files in Cloud Storage. You want to follow Google-recommended practices. Which IAM roles should you grant your colleagues?
Options
Discussion
B
B imo, A is too broad and C doesn't handle bucket-level permissions.
C , since Storage Object Admin is usually enough for handling all files in existing buckets. Seen similar picks in practice tests and the official exam guide talks about limiting scope. I might be missing something if bucket-level changes are needed, but seems right for just letting them manage files. Disagree?
C , since Storage Object Admin lets them work with files. Saw a question like this in some exam reports.
A is wrong, B. Storage Admin lets your coworkers manage both buckets and files, which is what you need here. Project Editor gives way too much access. Almost sure B's the safest pick if you want to follow Google's best practices.
Probably B since "Storage Admin" covers both bucket and object management, which is what the question actually asks for. Project Editor's way too broad, and C or D don't handle buckets. Sometimes people forget about the scope difference.
B , that's what the official guide suggests if you want full bucket and object management without giving away extra project permissions. C and D don't cover bucket-level stuff. Saw similar wording in a practice set. If you're prepping, focus on understanding the IAM predefined roles for Storage.
C? Saw a similar question on a practice exam, went with Storage Object Admin.
I don’t think Project Editor (A) is right here, since it gives way more permissions than needed, not just Storage. Storage Admin (B) is scoped to buckets and files, so that lines up with least privilege best practice. It’s a common trap to pick A for convenience.
B tbh, Project Editor (A) is way too broad since it gives access to pretty much everything in the project. Google recommends role-based access like Storage Admin for this exact use case. A is a trap.
Be respectful. No spam.