An infrastructure team is deploying an automated compliance scanner inside a target Google Cloud project named `sec-audit-984`. During execution, the scanner fails because calls to the Cloud Asset API (`cloudasset.googleapis.com`) return a `SERVICE_DISABLED` error. The security administrator wants to delegate the necessary permissions to a junior engineer to enable this API on `sec-audit-984`. To strictly follow the principle of least privilege, which action should the security administrator take?
- Grant the junior engineer the Service Usage Admin role (roles/serviceusage.serviceUsageAdmin) on project sec-audit-984, and have them execute gcloud services enable cloudasset.googleapis.com --project=sec-audit-984.Cevap
- BGrant the junior engineer the Editor role (roles/editor) on project sec-audit-984, and have them execute gcloud services enable cloudasset.googleapis.com --project=sec-audit-984.
- CGrant the junior engineer the Service Usage Admin role (roles/serviceusage.serviceUsageAdmin) at the parent Organization node so the API is enabled globally across all projects.
- DGrant the junior engineer the Billing Account User role on the linked billing account, and have them submit a quota increase request for Cloud Asset API endpoints.
Cevap
Grant the junior engineer the Service Usage Admin role (roles/serviceusage.serviceUsageAdmin) on project sec-audit-984, and have them execute gcloud services enable cloudasset.googleapis.com --project=sec-audit-984.
To enable Google Cloud APIs in accordance with the principle of least privilege, administrators should grant the predefined Service Usage Admin role (roles/serviceusage.serviceUsageAdmin) scoped to the specific project. The operator can then use the gcloud CLI command 'gcloud services enable' targeting that project.
Adım Adım Çözüm
Anahtar Kavram
Enabling Cloud Service APIs using least-privilege IAM roles and gcloud CLI commands
Tahmini Süre:2m 0s