A cloud security administrator at a global freight logistics company needs to authorize a DevOps engineer to link a newly provisioned project, `logistics-telematics-prod`, to the enterprise central Cloud Billing Account (`01A2B3-4C5D6E-7F8990`). The task must adhere strictly to Google Cloud least-privilege guidelines. Place the administrative authorization and CLI execution steps in the correct sequential order required to successfully perform this billing link.
- 1Grant the DevOps engineer the Billing Account User role (roles/billing.user) on the central Cloud Billing Account resource.
- 2Grant the DevOps engineer the Project Billing Manager role (roles/resourcemanager.projectBillingManager) on the logistics-telematics-prod project.
- 3Authenticate to the Google Cloud CLI using the DevOps engineer's user credentials.
- 4Execute gcloud billing projects link logistics-telematics-prod --billing-account 01A2B3-4C5D6E-7F8990.
Cevap
The correct sequence begins by granting the Billing Account User role on the central Cloud Billing Account resource, followed by granting the Project Billing Manager role on the target project resource, authenticating to the gcloud CLI with the engineer's credentials, and finally executing the gcloud billing projects link command.
Linking a Google Cloud project to a Cloud Billing Account requires permissions on both the billing account resource and the project resource. Under least-privilege principles, the user needs Billing Account User (roles/billing.user) on the billing account and Project Billing Manager (roles/resourcemanager.projectBillingManager) on the project. Once both roles are assigned, authenticating and executing the gcloud billing projects link command completes the process.
Adım Adım Çözüm
Anahtar Kavram
Least-privilege IAM configuration for linking projects to Cloud Billing Accounts