A company is configuring a multi-tier Google Cloud resource hierarchy. A centralized platform infrastructure team requires authorization to provision new cloud projects exclusively within a dedicated folder named `Production-Apps` and to associate these newly created projects with the corporate Billing Account `019283-475610-892014`. The security manager mandates adhering strictly to the principle of least privilege without granting permissions over unrelated folders or full billing administration privileges. Which set of IAM role assignments must be configured for the platform infrastructure team?
- Grant Project Creator (`roles/resourcemanager.projectCreator`) on the `Production-Apps` folder and Billing Account User (`roles/billing.user`) on the Billing Account `019283-475610-892014`.Answer
- BGrant Project Creator (`roles/resourcemanager.projectCreator`) and Billing Account User (`roles/billing.user`) both directly on the `Production-Apps` folder.
- CGrant Folder Admin (`roles/resourcemanager.folderAdmin`) at the Organization node level and Billing Account Administrator (`roles/billing.admin`) on the Billing Account `019283-475610-892014`.
- DGrant Owner (`roles/owner`) on the `Production-Apps` folder and rely on resource hierarchy policy inheritance to automatically grant billing link rights.
Answer
Grant Project Creator (`roles/resourcemanager.projectCreator`) on the `Production-Apps` folder and Billing Account User (`roles/billing.user`) on the Billing Account `019283-475610-892014`.
To create projects inside a specific folder while associating them with a billing account under least-privilege constraints, two distinct role bindings are required: Project Creator (`roles/resourcemanager.projectCreator`) scoped on the destination Folder, and Billing Account User (`roles/billing.user`) scoped directly on the target Billing Account.
Step-by-Step Solution
Key Concept
Managing Google Cloud Resource Hierarchy and Billing Account IAM Scoping