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 running containerized microservices in a Google Kubernetes Engine (GKE) cluster. Currently, these microservices access Google Cloud APIs by mounting long-lived service account private key JSON files stored as Kubernetes secrets.
The security compliance team has flagged this practice due to the severe risk of credential leakage and unauthorized key export. They require an authentication architecture that eliminates static keys and enforces least privilege access for each individual microservice workload.
Which solution should the cloud architect implement?
The node service account is the identity attached to the underlying Compute Engine virtual machines (VMs) that make up the GKE node pool. By default, applications running in pods on a node inherit access to the node's service account credentials via the instance metadata server unless Workload Identity is enabled.
You were configuring infrastructure-level logging and monitoring agents that operate strictly at the Kubernetes host node level.
Secret Manager is a secure, centralized storage system for sensitive metadata such as API keys, passwords, certificates, and arbitrary configuration strings. It provides versioning, audit logging, and fine-grained access control via Cloud IAM.
The scenario required storing third-party external API tokens, database connection passwords, or TLS private certificates that cannot use Google Cloud native identity federation.
Automated key rotation uses serverless functions or scripts to periodically generate new service account keys via the IAM API, deploy them to workloads, and delete expired keys to limit the validity window of compromised credentials.
The workload was hosted in an external, legacy on-premises environment that cannot support Workload Identity Federation or OIDC token exchange.
Workload Identity is the recommended best practice for authenticating workloads running on Google Kubernetes Engine (GKE) against Google Cloud APIs. It links a native Kubernetes Service Account (KSA) inside the cluster to a specific Google Service Account (GSA) in IAM, allowing pods to authenticate seamlessly without needing downloadable service account keys.

roles/iam.workloadIdentityUser IAM role to tightly govern which Kubernetes namespaces and service accounts can act as the GSA.Compared to managing Kubernetes secrets or node pool service accounts, Workload Identity provides strong security isolation, eliminates operational key management overhead, and ensures compliance with enterprise zero-trust security standards.
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