An enterprise application requires the Secret Manager API (`secretmanager.googleapis.com`) to be activated in a target Google Cloud project named `proj-sec-app`. A service account used by a CI/CD pipeline needs to enable this API and, if necessary, submit a request to raise the default API request quota. Which approach adheres to Google Cloud security best practices and the principle of least privilege?
- Grant the service account the Service Usage Admin (`roles/serviceusage.serviceUsageAdmin`) role on `proj-sec-app` to enable the API, and submit a quota increase request via the Service Usage Quotas section in the Cloud Console.Cevap
- BGrant the service account the Owner (`roles/owner`) role at the organization level so that permissions inherit down to `proj-sec-app` to allow API management.
- CEnable the Secret Manager API directly at the organization root node using `gcloud services enable`, which automatically enables the API and scales quotas for `proj-sec-app`.
- DDeploy a new Google Cloud project whenever API request limits are reached in `proj-sec-app`, as project quotas automatically multiply without requiring formal requests.
Cevap
Grant the service account the Service Usage Admin role on the target project to enable the API and request quota increases via the Service Usage Quotas interface.
The predefined role Service Usage Admin (`roles/serviceusage.serviceUsageAdmin`) grants the precise permissions required to list, enable, disable APIs, and view or request quota increases on a project level without giving unnecessary control over other GCP services.
Adım Adım Çözüm
Anahtar Kavram
Enabling Cloud APIs with Least Privilege IAM Roles and Requesting Resource Quota Increases