Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise is deploying an automated, non-interactive data processing pipeline to a Google Kubernetes Engine (GKE) cluster. The pipeline runs scheduled nightly jobs and microservices that query BigQuery datasets and write report outputs to Cloud Storage buckets without human intervention.
Security policy requires that:
Which identity configuration should the security team implement to satisfy these requirements?
The Compute Engine default service account is the identity provisioned by default and attached to Compute Engine virtual machine instances and GKE node pool worker VMs to manage node-level infrastructure operations.
The requirement was to configure base infrastructure monitoring or node-level logging daemons that require uniform access across all physical or virtual host machines rather than distinct application workloads.
User-managed service account keys are downloadable, long-lived asymmetric cryptographic key pairs (private/public keys) that authenticate a service account to Google Cloud APIs from any environment.
Workloads were running in a legacy external on-premises environment or non-supported multi-cloud environment where Workload Identity Federation or native Google Cloud metadata endpoints were unavailable.
OAuth 2.0 user refresh tokens are credentials issued during an interactive human authentication flow (such as gcloud auth login) that allow a client application to obtain new short-lived access tokens on behalf of a human user.
A developer was executing interactive debugging commands or running local ad-hoc scripts from their personal workstation during development.
GKE Workload Identity is the recommended, best-practice mechanism for granting non-interactive, automated containerized workloads on Google Kubernetes Engine access to Google Cloud APIs. It enables a Kubernetes Service Account (KSA) running within a specific namespace to securely impersonate a Google Service Account (GSA) without requiring static credentials or JSON private keys.
$PROJECT_ID.svc.id.goog), administrators do not need to generate, manage, or store long-lived JSON service account key files in Kubernetes Secrets.roles/iam.workloadIdentityUser IAM role on the target GSA specifically to the principal member string serviceAccount:$PROJECT_ID.svc.id.goog[$NAMESPACE/$KSA_NAME].iam.gke.io/gcp-service-account=$GSA_NAME@$PROJECT_ID.iam.gserviceaccount.com annotation.Workload Identity completely eliminates the attack surface associated with credential exfiltration from local pod storage, enforces strong workload isolation across namespaces, and natively supports non-interactive execution for automated pipelines.
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 Validated