A central infrastructure operations team at a retail company needs to delegate authority to a DevOps engineer to link newly provisioned Google Cloud projects to the company's central Cloud Billing account. The solution must strictly follow the principle of least privilege by avoiding overly permissive or broad administrative access on both the billing account and the projects. Which TWO identity and access management (IAM) roles must be assigned to the DevOps engineer? (Select 2 answers)
- Billing Account User (roles/billing.user) on the central Cloud Billing accountCevap
- Project Billing Manager (roles/billing.projectManager) on the target Google Cloud projectCevap
- CBilling Account Administrator (roles/billing.admin) on the central Cloud Billing account
- DBilling Account Viewer (roles/billing.viewer) on the central Cloud Billing account
- EBilling Account Costs Manager (roles/billing.costsManager) at the Organization level
Cevap
To link a Google Cloud project to a Cloud Billing account under the principle of least privilege, two specific permissions across two separate resource levels are required: Billing Account User (roles/billing.user) granted on the Cloud Billing account, and Project Billing Manager (roles/billing.projectManager) granted on the target Google Cloud project.
Linking a project to a Cloud Billing account requires permissions on both the billing account and the project. On the billing account side, Billing Account User (roles/billing.user) grants the capability to associate projects with the billing account. On the project side, Project Billing Manager (roles/billing.projectManager) allows changing the billing account associated with the project. Together, these two roles fulfill the minimal privilege requirement.
Adım Adım Çözüm
Anahtar Kavram
Dual IAM Permission Model for Billing Account Project Linking