An enterprise organization is establishing a secure sandbox environment for external partners. A automated service account needs to provision new Google Cloud projects inside a designated folder named 'Partner-Sandboxes' and immediately link each new project to the organization's central Billing Account. The security policy requires enforcing the principle of least privilege without granting excessive administrative permissions across the billing account or folder resource hierarchy. Which pair of predefined IAM roles should be granted to the service account to meet these requirements?
- Project Creator (roles/resourcemanager.projectCreator) on the 'Partner-Sandboxes' folder and Billing Account User (roles/billing.user) on the target Billing AccountCevap
- BProject Creator (roles/resourcemanager.projectCreator) on the 'Partner-Sandboxes' folder and Billing Account Administrator (roles/billing.admin) on the target Billing Account
- CProject Billing Manager (roles/billing.projectManager) on the 'Partner-Sandboxes' folder and Billing Account Viewer (roles/billing.viewer) on the target Billing Account
- DFolder Editor (roles/resourcemanager.folderEditor) on the 'Partner-Sandboxes' folder and Project Billing Manager (roles/billing.projectManager) on the Organization node
Cevap
Project Creator (roles/resourcemanager.projectCreator) on the 'Partner-Sandboxes' folder and Billing Account User (roles/billing.user) on the target Billing Account
Linking a project to a Cloud Billing Account requires two distinct privileges: the permission to create or manage billing links on the target project/folder (satisfied by Project Creator on the folder) and the permission to link projects to the billing account (satisfied by Billing Account User on the billing account). This combination satisfies least privilege.
Adım Adım Çözüm
Anahtar Kavram
Two-sided permission model for linking Google Cloud projects to Cloud Billing Accounts