GCP Associate Cloud Engineer Practice Question 91: Project Creator Role Org Folder
Google Cloud Associate Cloud Engineer · Test 10 · question 1 of 10
An organization uses a resource hierarchy with a folder named "Engineering" for all product teams. You want every member of the group eng-leads@example.com to be able to create new projects under the Engineering folder on their own, without giving them any ability to create projects anywhere else in the organization or to manage IAM policies at the organization level.
Which action should you take?
Show answer and explanation
Answer:
The Project Creator role grants the permission to create new projects under the resource it is bound to. Binding it at the Engineering folder, rather than at the organization, scopes the ability so the group can only create projects that land inside that folder, matching the requirement to limit them to Engineering while granting nothing broader.
Option A is wrong because Owner at the organization level grants far more than project creation: it includes the ability to modify IAM policy, delete resources, and manage every project in the organization. Option B is wrong for the same reason; Organization Administrator manages the organization's IAM policy and resource hierarchy itself, which the group should not be able to do. Option C is wrong because binding Project Creator at the organization lets the group create projects anywhere in the hierarchy, not just under the Engineering folder, which is broader than required.
Reference: Creating and managing projects