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 is deploying a public-facing RESTful API using Apigee on Google Cloud. Before launch, the architecture team must enforce security, traffic control, and observability standards at the API proxy layer without increasing response latency:
403 Forbidden for unauthorized calls.Which Apigee policy and flow configuration should the team implement?
VerifyAPIKey to validate OAuth 2.0 scopes, configure a Quota policy with a one-second interval to stop traffic spikes, enable OASValidation to mask backend errors, and attach MessageLogging to the ProxyEndpoint PreFlow.This option mixes several valid Apigee policies (VerifyAPIKey, Quota, OASValidation, and MessageLogging) in ways that conflict with their architectural roles and runtime behavior.
VerifyAPIKey checks whether an API key is valid, unrevoked, and associated with an approved API product, but it does not parse or validate OAuth 2.0 access tokens or granular scopes.Quota policy relies on distributed counters across gateway nodes, making it computationally expensive. Configuring it at one-second intervals for high-traffic burst protection degrades proxy performance; SpikeArrest is specifically engineered for smoothing sudden traffic bursts.OASValidation checks incoming requests and outgoing responses against an OpenAPI 3.0 Specification (JSON or YAML) to reject malformed schemas, rather than intercepting internal backend crashes and rewriting stack traces.MessageLogging in PreFlow executes before the backend processes the request, meaning response status codes and backend latency are unavailable and logging adds latency to the request path.VerifyAPIKey provides application identification, not user-delegated authorization scopes.Quota policies are optimized for longer intervals (hours, days, or months) tied to business SLAs.OASValidation validates API contract structure, whereas fault rules handle runtime error transformation.PostClientFlow runs asynchronously after the response reaches the client.The requirements asked only to identify developer apps with API keys, enforce monthly contractual request caps, validate payloads against an OpenAPI 3.0 schema, and log incoming request headers before target routing.
A common misconception is treating Quota and SpikeArrest as interchangeable. In production architectures, both are often used together because SpikeArrest protects backend stability second-by-second while Quota tracks long-term consumption.
JSONThreatProtection to sanitize backend database error responses.This approach relies on URL-based API key transmission, declarative API product metadata, and JSONThreatProtection, leaving critical gaps in credential security, runtime enforcement, and error handling.
403 Forbidden responses.Quota policy (and referencing the product configuration) inside the API proxy flow, callers can exceed limits unrestricted.JSONThreatProtection inspects incoming JSON payloads to block structural attacks (such as deeply nested objects, oversized arrays, or excessively long strings) before parsing, rather than rewriting internal backend crash errors.x-goog-api-key) rather than query strings.Quota policy in the proxy.JSONThreatProtection mitigates injection and parser-exhaustion threats on inbound data, not outbound exception masking.No requirements existed for OAuth 2.0 scopes, runtime quota enforcement, or observability, and the primary goal was protecting backend JSON parsers from malformed request bodies.
Developers frequently assume that setting a quota field in an Apigee API product automatically throttles requests. In reality, Apigee separates product definition (business packaging) from proxy enforcement (runtime policy execution).
BasicAuthentication, configure SpikeArrest to return HTTP 500 on traffic surges, and configure services to fail closed if external rate-limiting checks return HTTP 503.This design uses BasicAuthentication, non-standard status codes, and a fail-closed rate-limiting posture, which weakens authorization granularity, violates HTTP semantics, and harms availability.
BasicAuthentication simply Base64-encodes and decodes static username-and-password credentials. It does not support OAuth 2.0 tokens, cryptographic signature verification, or granular permission scopes.500 Internal Server Error during traffic surges misleads clients and monitoring systems into treating intentional throttling as a server crash. Rate-limited or quota-exceeded requests must return HTTP 429 Too Many Requests so clients can apply exponential backoff.500, 503, or 504 causes a minor control-plane outage to take down the entire API. Managed services should fail open to preserve availability.429 responses allow client libraries to back off gracefully instead of immediately retrying.PostClientFlow logging.A legacy internal endpoint required only HTTP Basic credential extraction and strict regulatory rules mandated blocking all traffic during any control-plane degradation.
In high-availability cloud architectures, fail-open rate limiting is a core reliability principle: because most legitimate consumers stay below their limits, temporary rate-limiter unavailability should never block normal production traffic.
OAuthV2 policy to validate scopes, combine SpikeArrest and Quota policies for traffic control, configure fault handling rules to rewrite backend errors, and attach MessageLogging with escapeJSON() to PostClientFlow.This configuration combines gateway-level security, tiered traffic management, standardized error handling, and asynchronous logging inside an Apigee API proxy. Acting as a reverse proxy in front of backend microservices, Apigee enforces these controls consistently before requests reach backend compute resources and after responses return to clients.
OAuthV2 policy verifies access tokens and checks required OAuth scopes (such as write:billing or delete:account) at the API entry point, immediately returning an HTTP 403 Forbidden status when a caller lacks sufficient permissions.SpikeArrest and Quota addresses distinct operational needs. SpikeArrest smooths sudden traffic surges from buggy clients or denial-of-service attempts, while Quota maintains distributed counters to enforce daily or monthly contractual call limits per developer app.MessageLogging policy to PostClientFlow executes logging asynchronously after the HTTP response has already been delivered to the client, while wrapping user-supplied fields in escapeJSON() prevents log injection.Quota policies directly to API product settings for flexible consumer tiers.PostClientFlow guarantees logging overhead never delays API responses.Every Apigee mechanism in this design is applied to its exact intended purpose. Unlike combining API keys alone or misusing Quota for short-term burst smoothing, pairing OAuthV2, SpikeArrest, Quota, fault rules, and PostClientFlow MessageLogging satisfies all security, reliability, and observability requirements with minimal overhead.
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