A cloud administrator needs to grant an external automated system temporary access to collect metrics from Compute Engine instances within a Google Cloud project. To adhere to Google Cloud security standards, the administrator must avoid generating and downloading long-lived service account JSON keys. Which implementation strategy should the administrator select?
- Create a dedicated service account with the predefined Monitoring Viewer role and configure Workload Identity Federation to issue short-lived credentials to the external system.Cevap
- BCreate a service account with the Monitoring Viewer role, export a JSON private key, and store the key in Google Cloud Secret Manager for the external service to retrieve.
- CCreate a service account, assign it the primitive Owner role at the project level, and configure short-lived service account impersonation for the external system.
- DGrant the external system's identity the Monitoring Viewer role at the organization level, expecting explicit deny policies on unneeded child projects to restrict access.
Cevap
Create a dedicated service account with the predefined Monitoring Viewer role and configure Workload Identity Federation to issue short-lived credentials to the external system.
The correct strategy uses a dedicated service account bound strictly to the required predefined role (Monitoring Viewer) and uses Workload Identity Federation to grant short-lived access without creating long-lived private key files.
Adım Adım Çözüm
Anahtar Kavram
Service Account Management and Secure Authentication Best Practices