An enterprise architecture team is auditing a newly migrated Google Cloud environment and identified two significant areas of technical debt: application service accounts were assigned primitive Owner roles, and Terraform state files are currently stored locally on developer workstations. Which TWO actions should the architecture team take to mitigate this technical debt? (Select TWO answers.)
- Replace primitive Owner roles on service accounts with fine-grained predefined or custom roles.Cevap
- Migrate local Terraform state files to a remote Cloud Storage backend with object versioning enabled.Cevap
- CGrant the Service Account Admin role to application service accounts to resolve permission management bottlenecks.
- DProvision a dedicated Google Kubernetes Engine (GKE) cluster to host local state files and lock daemons.
Cevap
The architecture team should replace primitive Owner roles on service accounts with fine-grained predefined or custom roles, and migrate local Terraform state files to a Cloud Storage backend with object versioning enabled.
Mitigating technical debt in cloud architectures requires replacing overly permissive primitive IAM roles with fine-grained predefined or custom roles, and migrating local infrastructure state files to a secure Cloud Storage backend with versioning enabled.
Adım Adım Çözüm
Anahtar Kavram
Assessing and Mitigating Technical Debt in Cloud Architectures