A smart grid utility organization is automating the provisioning of a private Google Kubernetes Engine (GKE) cluster for critical infrastructure monitoring using Terraform. The deployment pipeline must ensure secure control plane access, maintain least-privilege identity access management, and protect infrastructure deployment state from concurrency conflicts. Which two configuration actions should you include in your provisioning architecture to satisfy these requirements? (Select TWO.)
- Configure master authorized networks on the GKE private cluster to restrict control plane access strictly to designated management subnet IP ranges.Cevap
- BAssign the primitive Editor role (roles/editor) to the deployment pipeline service account to simplify resource creation across compute and network resources.
- CStore the Terraform state file on the local runner filesystem during execution to eliminate remote backend latency.
- Grant the Service Account User role (roles/iam.serviceAccountUser) to the deployment pipeline identity so it can bind runtime service accounts to node pools.Cevap
- EGrant the Service Account Admin role (roles/iam.serviceAccountAdmin) to the deployment pipeline service account so it can manage compute node service account privileges.
Cevap
Configure master authorized networks to secure the GKE private control plane endpoint, and assign the Service Account User role to the deployment pipeline identity.
Configuring master authorized networks restricts GKE control plane endpoint access exclusively to designated IP ranges, ensuring secure management access. Concurrently, granting the Service Account User role provides the necessary permissions for the provisioning pipeline to attach runtime identities to cluster nodes without granting broad administrative privileges.
Adım Adım Çözüm
Anahtar Kavram
GKE Private Cluster Provisioning & IAM Least-Privilege Execution
Tahmini Süre:2m 0s