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.
A security engineer is configuring automated, server-to-server data ingestion from an external enterprise SaaS application (Salesforce) into Google Cloud services. The integration must synchronize enterprise records continuously in the background without interactive user authentication.
The organization's security policy defines the following requirements:
Which OAuth 2.0 configuration should the engineer implement to meet these requirements?
This approach uses the standard OAuth 2.0 Client Credentials flow (RFC 6749), which authenticates the client application directly using a symmetric Consumer Key (client ID) and Consumer Secret (client secret), while allowing any user in the organization to self-authorize access to the application.
The organization did not have a PKI requirement restricting symmetric credentials and wanted a simplified setup where any internal developer could self-authorize their own client instances using basic API keys and client secrets.
While the Client Credentials flow is supported for automated workloads, enterprise security standards strongly favor asymmetric JWT bearer assertions for sensitive customer data integration to mitigate secret sprawl.
The OAuth 2.0 JWT Bearer Token Flow (defined in RFC 7523) provides an automated, server-to-server authentication mechanism where a client application signs a JSON Web Token (JWT) using an asymmetric private key. The target authorization server verifies the signature against a pre-registered public X.509 certificate, eliminating the need for shared static secrets or interactive user logins.
server.key) to sign authorization assertions and uploading the corresponding public certificate (server.crt) to the external application, the integration eliminates static shared secrets (client_secret), protecting against credential leaks and interception.Manage user data via APIs and refresh_token, offline_access) ensures appropriate data extraction capabilities while the refresh token policy maintains continuous synchronization until administrative revocation.Compared to symmetric client credential flows or user-interactive authorization code flows, the JWT Bearer flow provides the strongest security posture for unattended server-to-server integrations by combining public key infrastructure (PKI) with explicit administrative pre-authorization.
The OAuth 2.0 Authorization Code flow with PKCE (RFC 7636) is an authorization grant designed for user-facing web and native mobile applications. It redirects an interactive user to an Identity Provider login and consent screen, exchanging an authorization code and cryptographic code verifier for an access token.
The application were an interactive user portal (such as Looker or a custom web app) where human analysts log in using single sign-on to query BigQuery or external APIs with their own delegated individual identity.
Automated cloud ingestion connectors running inside Google Cloud cannot interact with browser redirects and consent screens during scheduled or real-time background execution.
The OAuth 2.0 Implicit Grant flow is a legacy OAuth 2.0 pattern where access tokens are returned directly in the URI fragment of a redirection response without an intermediate authorization code exchange step.
There were a legacy legacy browser-only client that had no backend server, though modern OAuth standards have replaced this entirely with Authorization Code flow with PKCE.
Modern cloud security architectures strictly prohibit the Implicit Grant flow due to severe token exposure vulnerabilities and lack of support for robust enterprise authorization policies.
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