Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is standardizing its deployment process across multiple Google Kubernetes Engine (GKE) environments (development, staging, and production) to align with the Operational Excellence pillar of the Google Cloud Well-Architected Framework.
Currently, developers manually run kubectl commands from their local workstations, leading to configuration drift, deployment inconsistencies, and elevated credential sprawl.
The team wants to implement an automated CI/CD pipeline using Cloud Build that satisfies the following requirements:
container.deployments.create and container.deployments.update) without broad administrative control over the clusterWhich strategy should the cloud architect recommend?
The roles/container.admin role provides full administrative access to all Kubernetes Engine resources within a project, including managing clusters, node pools, and security policies.
roles/container.admin gives the deployment pipeline permission to delete clusters, modify node pools, and manage cluster certificates, far exceeding the necessary permissions (container.deployments.* and container.ingresses.*).The pipeline was specifically responsible for provisioning, upgrading, and tearing down the underlying GKE cluster infrastructure rather than deploying application workloads.
The Google Cloud Well-Architected Framework emphasizes separation of duties: infrastructure provisioning pipelines should remain separate from application delivery pipelines with strictly bounded IAM roles.
This approach relies on individual developers executing imperative CLI commands (kubectl run, kubectl set image, kubectl rollout) from their local command lines using downloaded JSON service account keys.
The organization were troubleshooting an emergency break-glass scenario in an isolated test sandbox where automated CI/CD infrastructure was temporarily offline.
The Operational Excellence pillar strongly discourages manual deployments from local workstations, recommending fully managed CI/CD pipelines (e.g., Cloud Build) running short-lived tokens via IAM Workload Identity.
This strategy combines Infrastructure as Code (IaC), GitOps/declarative delivery pipelines, and role-based access management to automate workload lifecycles reliably within Google Kubernetes Engine (GKE).
kubectl execution removes operator error and prevents environment drift.roles/container.developer role provides granular permissions to manage workloads—including container.deployments.create, container.deployments.update, container.deployments.rollback, and container.ingresses.create—without granting cluster administration rights.
Using declarative manifests combined with a least-privilege CI/CD service account aligns directly with the Operational Excellence pillar by replacing error-prone manual interactions with standardized, secure automation.
The roles/viewer role grants read-only permissions to inspect Google Cloud resources and cluster assets without permitting any create, update, or delete operations.
container.ingresses.get lack write permissions such as container.deployments.create, container.deployments.update, and container.ingresses.create required to apply manifests.The goal was to configure a read-only monitoring dashboard or an external compliance auditing tool that only inspects cluster resource state.
While least privilege requires minimizing permissions, it must still provide sufficient privileges for the workload. For deployment pipelines, this requires targeted write permissions on workload-level objects.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated