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.
Your organization runs APIs on Google Kubernetes Engine (GKE) and is launching new microservices on Cloud Run. You want to standardize on Cloud Endpoints to enforce API key validation, JWT authentication, and request logging across the new serverless backends.
You have the following requirements:
Which deployment and configuration approach should you implement?
Extensible Service Proxy V2 (ESPv2) is an Envoy-based, high-performance service proxy that runs in front of OpenAPI 2.0 or gRPC API backends to enforce Cloud Endpoints policies. In remote proxy mode, ESPv2 runs as a standalone serverless Cloud Run service that intercepts incoming API traffic, integrates with Service Control and Service Management, and forwards validated requests to remote backend services.
x-google-backend extension to map specific API paths or operations to their respective remote Cloud Run service URLs.gcloud endpoints services deploy.Unlike the older NGINX-based ESP, ESPv2 is specifically built to support serverless platforms such as Cloud Run, Cloud Run functions, and App Engine standard. Combining ESPv2 remote proxy mode with x-google-backend routing provides full Cloud Endpoints standardization across serverless backends without introducing VM or cluster management overhead.
The original Extensible Service Proxy (ESP) is an NGINX-based containerized proxy designed to inject Cloud Endpoints functionality—such as authentication, API key checking, and logging—in front of containerized or VM-hosted API backends. It retrieves service configurations from Service Management and communicates with Service Control at runtime.
x-google-backend is a capability of the Envoy-based ESPv2, not the legacy ESP runtime.You were maintaining a legacy API hosted on the App Engine flexible environment, where only ESP (and not ESPv2) is supported, or running a preexisting sidecar deployment on GKE or Compute Engine.
Although both ESP and ESPv2 integrate with Service Management and Service Control, their underlying proxy architectures and supported Google Cloud compute platforms differ significantly. Choosing the NGINX-based ESP for a Cloud Run deployment results in an unsupported architecture that cannot leverage serverless remote proxying.
Deploying ESP in sidecar mode on a Compute Engine managed instance group (MIG) places a Dockerized proxy container on each VM instance directly alongside a local backend application container. Traffic arrives at the VM via Cloud Load Balancing, passes through the local ESP container on a shared Docker bridge network, and is forwarded locally to the backend container.
host field: Sidecar mode is a server-local topology meant to run alongside each instance of a backend on the same host, not as a centralized proxy fronting external Cloud Run services. Additionally, in Cloud Endpoints OpenAPI files, the host property identifies the Endpoints service hostname itself—not backend routing targets, which require x-google-backend.Your API backend itself was containerized and running directly on Compute Engine VMs, and you wanted a co-located sidecar proxy to eliminate extra proxy network hops while scaling the VM tier with a managed instance group.
While sidecar mode is ideal for GKE and Compute Engine workloads where the proxy and backend share a pod or VM, serverless platforms like Cloud Run are designed to be fronted by ESPv2 in remote proxy mode.
API Gateway is a fully managed Google Cloud service that provides secure, consistent REST API access across serverless and containerized backends such as Cloud Run, Cloud Run functions, and App Engine. Like Cloud Endpoints, API Gateway accepts OpenAPI 2.0 and OpenAPI 3.x specifications to define API surfaces, security rules, and quotas.
host property configuration: Unlike Cloud Endpoints—which requires the host field to match the hostname of the deployed ESP or ESPv2 service—API Gateway does not enforce the host property and expects it to be omitted or set to the API Gateway DNS name.You chose to migrate away from Cloud Endpoints and ESPv2 entirely to use API Gateway as a fully managed serverless gateway, omitting the Endpoints host value and removing ESPv2 containers from your architecture.
Because both Cloud Endpoints and API Gateway support OpenAPI specifications with extensions like x-google-backend, developers sometimes conflate their deployment models. When standardizing on Cloud Endpoints for Cloud Run, you deploy ESPv2 as a remote proxy rather than combining API Gateway with sidecar proxies.
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