An operations team is auditing security compliance for a project in Google Cloud. During the audit, they discover that a developer generated a user-managed JSON service account key for local testing, which violates the organization's credential management policy. The team needs to immediately neutralize this specific compromised credential file without disabling the service account itself, as other production workloads rely on the service account. Which action should the operations team take?
- Delete the specific user-managed key using the gcloud iam service-accounts keys delete command or Google Cloud Console.Cevap
- BDisable the service account, export a new JSON key file, and re-enable the service account.
- CRemove the IAM role bindings from the parent resource hierarchy folder to override key validity.
- DDemote the service account's permission level from Project Owner to Project Viewer so that existing keys expire.
Cevap
Delete the specific user-managed key using the gcloud iam service-accounts keys delete command or Google Cloud Console.
Deleting the specific service account key directly revokes the public/private key pair associated with the JSON file without altering the service account identity or disrupting other resources using different authentication mechanisms.
Adım Adım Çözüm
Anahtar Kavram
Service Account Key Lifecycle and Management