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 runs continuous integration and deployment (CI/CD) pipelines on an external cloud platform. Workloads running in these external pipelines need to deploy container images and update infrastructure in Google Cloud.
Company security policies strictly prohibit creating, downloading, and storing long-lived service account key files due to the risk of credential leakage.
What should you do to configure secure, keyless authentication for these external workloads?
Workload Identity Federation is Google Cloud's recommended mechanism for granting on-premises and external multi-cloud workloads access to Google Cloud resources without managing long-lived service account keys. It leverages Security Token Service (STS) and IAM to establish a trust relationship with external identity providers (IdPs) supporting OpenID Connect (OIDC) or SAML 2.0.
google.subject, attribute.repository).roles/iam.workloadIdentityUser role on a target service account specifically to the mapped external principal set (principalSet://iam.googleapis.com/...) ensures only authorized external workloads can impersonate the service account.
Workload Identity Federation provides a direct, cloud-native standard for keyless authentication across heterogeneous environments, aligning perfectly with security best practices and the principle of least privilege.
Service account keys are asymmetric, long-lived cryptographic credentials (typically formatted as downloadable JSON files) that allow any entity possessing the private key to authenticate as the associated Google Cloud service account directly.
The external environment lacked an OpenID Connect (OIDC) or SAML identity provider and had no capability to integrate with federated token exchange mechanisms.
This approach relies on granting overly broad primitive permissions (roles/editor) to Google Cloud default service accounts and establishing a network-layer tunnel (Cloud VPN) to route external traffic to Google Cloud API endpoints.
The requirement was to provide private RFC 1918 network connectivity to private VM instances inside a VPC without traversing the public internet.
Workforce Identity Federation allows human users (such as employees, contractors, and partners) to authenticate to Google Cloud services and the Google Cloud console using an external identity provider (like Microsoft Entra ID or Okta).
Human developers and operations engineers needed single sign-on access to the Google Cloud console using their corporate identity provider credentials.
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