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 financial services company exposes a customer banking API through Apigee. External third-party budgeting applications need to access customer account data and initiate transfers on behalf of end users.
Your security configuration must meet the following requirements:
read:accounts and write:transfers), returning an HTTP 403 Forbidden status code if a client lacks the required permission.Which security configuration should you implement?
In Apigee, an API key (also called a consumer key) is a unique string generated when a developer app is registered and associated with one or more API products. API products bundle API proxies, resource paths, and HTTP methods together. Attaching the VerifyAPIKey policy to a proxy checks that an incoming key is valid, active, and authorized for the requested API product and resource path.
read:accounts versus write:transfers on a per-session basis.You only needed to block anonymous traffic, track application-level usage metrics, enforce quotas per client app, or restrict entire applications to specific endpoint subsets (for example, allowing a customer mobile app to only POST while allowing an internal call-center app to DELETE), without needing to authenticate individual end users or revoke single-user sessions.
Apigee's VerifyJWT policy decodes an incoming JSON Web Token (JWT), verifies its cryptographic signature using a configured secret or public key (such as a JWKS endpoint), and validates standard claims like issuer (iss), audience (aud), and expiration (exp) before allowing the request to proceed.
VerifyJWT performs stateless cryptographic verification. Once a JWT is signed and issued, it remains valid until its exp timestamp unless you build and maintain a custom token-revocation cache or denylist.VerifyJWT only validates tokens that have already been minted; it does not provide an interactive OAuth login and consent flow to keep user credentials away from third-party apps.End users were already authenticating directly with a trusted external identity provider (such as Google, Auth0, or Okta) that cryptographically signs ID or access tokens using asymmetric private keys, and Apigee only needed to verify those issuer signatures and claims using the provider's public JWKS before forwarding requests to the backend.
The OAuth 2.0 Client Credentials grant type is a two-legged OAuth flow designed for server-to-server communication where the client application is acting entirely on its own behalf. The application sends its client ID (consumer key) and client secret (consumer secret) directly to the authorization server's token endpoint and receives an access token without any user interaction.
client_id and client_secret on a trusted backend server.read:accounts or write:transfers.The API were consumed exclusively by trusted internal microservices or B2B partner backends performing machine-to-machine operations on their own behalf (such as an automated batch-settlement service accessing a backend ledger), where no individual end-user login or delegated consent is required.
The OAuth 2.0 Authorization Code grant type (also known as three-legged OAuth) is a delegated authorization framework designed for applications that need to access protected resources on behalf of an end user. In Apigee, the OAuthV2 policy acts as both the authorization server (issuing and revoking tokens) and the resource server enforcement mechanism (VerifyAccessToken), while the ProxyEndpoint PreFlow serves as the earliest execution point for incoming API traffic.
403 Forbidden): Apigee allows you to map sensitive endpoints and actions to granular OAuth scopes (such as read:accounts and write:transfers). When the OAuthV2 policy validates scopes at runtime, any token missing the required scope is rejected with an HTTP 403 Forbidden response.OAuthV2 policy with the VerifyAccessToken operation at the beginning of the ProxyEndpoint PreFlow guarantees that invalid or unauthorized requests are terminated immediately before reaching conditional flows or backend targets.Compared to API keys (which only identify the calling app), Client Credentials (which lack end-user delegation), and self-signed JWTs (which lack user consent flows and built-in Apigee revocation), the Authorization Code grant paired with VerifyAccessToken in the PreFlow satisfies every authentication, authorization, and lifecycle requirement.
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