Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A company runs backend services on AWS EC2 instances with IAM instance profiles and deploys applications using GitHub Actions workflows. Both environments currently rely on downloaded Google Cloud service account JSON keys to access Cloud Storage and BigQuery, creating key rotation overhead.
To eliminate long-lived keys, you need to implement keyless authentication that meets these requirements:
Which Workload Identity Federation configuration should you implement?
google.subject, and grant roles/iam.workloadIdentityUser only to specific external principal identifiers on dedicated service accounts.Workload Identity Federation enables external workloads to exchange native ambient credentials—such as AWS temporary IAM credentials and GitHub Actions OpenID Connect (OIDC) tokens—with the Google Security Token Service (STS) for short-lived Google Cloud tokens. Using separate Workload Identity Pools per provider, attribute conditions, and immutable subject mappings establishes a secure, keyless trust boundary.
GetCallerIdentity tokens (or AWS OIDC tokens) and GitHub Actions workflows exchange OIDC ID tokens for short-lived Google credentials without storing service account JSON keys.google.subject guarantees a unique, non-repudiable audit trail in Cloud Audit Logs, and granting roles/iam.workloadIdentityUser to specific principal:// or principalSet:// identifiers on dedicated service accounts limits blast radius.Unlike sharing a single pool across multiple providers or granting broad pool-wide impersonation, isolating pools, enforcing tenant-level attribute conditions, and binding specific principals to dedicated service accounts protects against spoofing, privilege escalation, and non-repudiation threats.
Workforce Identity Federation is a Google Cloud identity service that allows organizations to use an external identity provider—such as Okta, Microsoft Entra ID, or AD FS—to authenticate and authorize human users (a workforce of employees, partners, and contractors) into the Google Cloud console, gcloud CLI, and Google Cloud services without creating separate Cloud Identity or Google Workspace accounts.
GOOGLE_APPLICATION_CREDENTIALS) or automated OAuth 2.0 token exchange for server-to-server API calls.The requirement was to let human developers or data analysts sign in to the Google Cloud console and run interactive gcloud commands using their corporate single sign-on (SSO) identity provider.
roles/iam.workloadIdentityUser to all pool members (principalSet://.../POOL_ID/*) on a shared service account.This approach sets up Workload Identity Federation using a single shared Workload Identity Pool for multiple external identity providers, relies exclusively on the default OIDC issuer URL check for trust validation, and grants broad impersonation rights across the entire pool to a single shared service account.
google.subject value and become indistinguishable in Cloud Audit Logs.roles/iam.workloadIdentityUser to all pool members (/*) on a shared service account means any newly onboarded or compromised workload in the pool automatically inherits permissions for both Cloud Storage and BigQuery.google.subject values, Google Cloud IAM treats them as the same principal./*) eliminate per-application access boundaries.No production scenario makes this configuration secure; even when onboarding multiple providers, you should separate them into distinct pools, add tenant-filtering attribute conditions for multi-tenant IdPs, and bind specific principals to dedicated service accounts.
Managed workload identities allow organizations to bind strongly attested, SPIFFE-based identities to workloads running inside Google Cloud on Compute Engine and Google Kubernetes Engine (GKE). They rely on mutual TLS (mTLS) X.509 certificates provisioned and rotated automatically by Google Cloud infrastructure.
The workloads were running on Compute Engine or GKE and needed to authenticate directly to other microservices over mTLS rather than calling Google Cloud APIs from AWS and GitHub.
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