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 operates automated, long-running data processing pipelines deployed across Compute Engine instances and Google Kubernetes Engine (GKE) clusters. These workloads continuously ingest data from Cloud Storage buckets and write analytics results into BigQuery datasets without end-user interaction. The security team previously discovered that some pipelines failed because they relied on human developer credentials that were suspended during employee offboarding.
Which identity architecture should the organization implement to ensure stable, long-term authorization independent of user account lifecycles while enforcing the principle of least privilege?
This approach uses standard human user identities managed in Cloud Identity or Google Workspace to authenticate automated processes and long-running compute workloads, bypassing security controls like two-step verification.
The requirement specifically called for provisioning interactive, named human users who log in through corporate web consoles and desktop workstations using Single Sign-On.
User-managed service account keys are long-lived cryptographic credentials (private key JSON files) generated manually and downloaded outside Google Cloud's managed key infrastructure to authenticate requests.
roles/owner) violates least-privilege principles by providing full administrative and access control over all project resources.The workload were running in a legacy on-premises data center or external environment that did not support Workload Identity Federation or token exchange mechanisms.
When services such as Compute Engine are enabled, Google Cloud automatically creates a default service account (e.g., PROJECT_NUMBER-compute@developer.gserviceaccount.com). Historically, these default accounts were automatically assigned the broad Editor role (roles/editor) on the project.
The goal was rapid, non-production prototyping where security controls, least privilege, and workload isolation were explicitly out of scope.
Google Cloud service accounts provide dedicated, non-human identities designed specifically for applications, automated processes, and long-running compute workloads. When workloads run on Google-managed compute infrastructure such as Compute Engine or Google Kubernetes Engine (GKE), service accounts serve as the identity foundation that decouples application access from human user accounts and interactive sign-in flows.
roles/storage.objectViewer and roles/bigquery.dataEditor), preventing excessive access sprawl.This approach aligns with Google Cloud's established security best practices for automated workloads, ensuring high availability, zero dependence on human credentials, and fine-grained access control.
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