A fintech company is setting up a new Google Cloud project named `payment-clearing-dev` for a team of external contractors. A cloud administrator needs to grant an external contractor the minimum necessary IAM permissions required to link this newly created project to the company's central Cloud Billing Account. The contractor should not have administrative control over the billing account or overall ownership of the project. Following Google Cloud least-privilege best practices, which configuration of roles should be granted to the contractor?
- Grant the Billing Account User role (roles/billing.user) on the Cloud Billing Account, and grant the Project Billing Manager role (roles/billing.projectManager) on the project.Cevap
- BGrant the Billing Account Administrator role (roles/billing.admin) on the Cloud Billing Account, and grant the Owner role (roles/owner) on the project.
- CGrant the Billing Account Viewer role (roles/billing.viewer) on the Cloud Billing Account, and grant the Project Billing Manager role (roles/billing.projectManager) on the project.
- DGrant the Billing Account User role (roles/billing.user) at the parent Organization level only, relying on policy inheritance to automatically grant project-level billing linkage rights.
Cevap
Grant the Billing Account User role (roles/billing.user) on the Cloud Billing Account, and grant the Project Billing Manager role (roles/billing.projectManager) on the project.
Linking a Google Cloud project to a billing account requires two distinct sets of permissions: `roles/billing.user` granted on the Cloud Billing Account (which grants permission to attach projects to that billing account) and `roles/billing.projectManager` granted on the target Project (which permits attaching a billing account to that project). This combination enforces the principle of least privilege.
Adım Adım Çözüm
Anahtar Kavram
Two-Sided IAM Permissions for Project Billing Linkage