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 development team is building a microservices application that interacts programmatically with Google Cloud APIs, including BigQuery and Cloud Storage. The application codebase is deployed across multiple environments: developer workstations for local testing, Compute Engine instances for staging, and Google Kubernetes Engine (GKE) clusters for production.
The security architecture requires eliminating the risks associated with downloadable, long-lived service account keys and ensuring least privilege access across each deployment tier without code changes.
Which identity and authentication strategy should the team implement?
Service agent roles (such as roles/bigquery.serviceAgent or roles/container.serviceAgent) are specialized IAM roles designed exclusively for Google-managed internal service accounts to coordinate service-to-service operations. Access scopes are legacy mechanisms used on Compute Engine to limit API token capabilities for the default Compute Engine service account.
You were configuring internal Google Cloud service-to-service orchestration where the platform automatically provisions and manages the service agent principal.
gcloud auth application-default login locally, attached IAM service accounts on Compute Engine, and Workload Identity on GKE.Application Default Credentials (ADC) is a flexible authentication mechanism provided by Google Cloud client libraries that automatically detects credentials based on the application's runtime environment. Instead of requiring hardcoded paths or static tokens, ADC searches a predefined order of locations—such as local user configuration, environment variables, or platform metadata services—to seamlessly acquire short-lived OAuth 2.0 access tokens.
StorageClient(), BigQueryClient()), which transparently invoke ADC across developer machines, VMs, and Kubernetes pods.gcloud auth application-default login with bounded developer roles, Compute Engine VMs use attached service accounts via the instance metadata server, and GKE workloads leverage Workload Identity to bind Kubernetes Service Accounts (KSAs) to specific Google Service Accounts (GSAs).
ADC combined with platform-native identity binding (Compute Engine metadata service and GKE Workload Identity) adheres directly to Google Cloud security best practices. It avoids secret leakage vectors associated with static files while automating credential discovery and token refresh lifecycles without developer intervention.
A token-vending proxy is a custom middleware pattern where applications request credentials from an internal service that handles token generation and refresh flows using embedded static refresh tokens or master secrets.
You were integrating proprietary, non-standard third-party external applications that lack any native OAuth 2.0 or OIDC federation capabilities and cannot run Google Cloud SDKs.
Google Cloud APIs only accept short-lived access tokens (typically valid for 1 hour). Constructing architectural workarounds to simulate long-lived access credentials contradicts modern zero-trust security principles.
GOOGLE_APPLICATION_CREDENTIALS environment variable pointing to the file across all environments.Service account private keys are asymmetric JSON files generated directly from Cloud IAM that allow any bearer holding the file to authenticate as the associated service account from anywhere over the public internet.
The workload was running on a legacy, non-Google Cloud on-premises environment where Workload Identity Federation was strictly not supported and alternative managed federation mechanisms were unavailable.
While setting GOOGLE_APPLICATION_CREDENTIALS is one lookup mechanism used by ADC, relying on downloadable JSON service account keys is strongly discouraged when platform-native managed identities (like GKE Workload Identity) are available.
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