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 team is building a latency-sensitive, high-throughput backend microservice in a gRPC-supported language for which no official Cloud Client Library exists for your target gRPC-enabled Google Cloud API. You have the following requirements for the development lifecycle:
Which combination of tools and communication interfaces should you use?
Google APIs Explorer is an interactive, browser-based tool that allows developers to inspect API endpoints, examine parameter schemas, authenticate, and execute test calls against Google Cloud APIs without writing application code. gRPC is a high-performance, language-neutral remote procedure call framework that uses Protocol Buffers as its Interface Definition Language (IDL) over HTTP/2. When an official Cloud Client Library is unavailable for a specific programming language, developers can generate native gRPC client stubs directly from the API's .proto service definitions.
.proto files works for any gRPC-supported language that lacks a pre-built Cloud Client Library.Although Cloud Client Libraries are the recommended default—since they provide idiomatic wrappers and often use gRPC under the hood—they do not support every programming language. Generating a gRPC client from official Protocol Buffers definitions preserves maximum throughput and CPU efficiency without falling back to slower REST/JSON interfaces or legacy Google API Client Libraries.
The Google Cloud console API Dashboard is a monitoring and observability interface that displays project-level API telemetry, including traffic volume, error rates, and latency metrics. A custom JSON/REST HTTP client sends raw HTTP requests with JSON payloads directly to Google Cloud API endpoints using third-party HTTP libraries.
You would use the API Dashboard to investigate traffic spikes or elevated error rates on enabled APIs, and implement a custom JSON/REST client only when neither Cloud Client Libraries nor gRPC are viable for your environment.
To interactively explore endpoints and validate request payloads without writing code, developers use Google APIs Explorer rather than the API Dashboard. For high-throughput workloads, gRPC delivers up to 10 times higher throughput per CPU than JSON/REST.
Google API Client Libraries are an earlier generation of client libraries provided by Google to access Google APIs programmatically. Unlike modern Cloud Client Libraries, they rely on auto-generated interface code that is typically less idiomatic, though they still handle low-level HTTP communication and authentication.
npm and pip.This option would be suitable if no Cloud Client Library existed for your language, your application did not have strict throughput-per-CPU or latency requirements, and you preferred a pre-built REST wrapper over generating custom gRPC stubs.
A common misconception is conflating Google API Client Libraries with Google Cloud Client Libraries. While modern Cloud Client Libraries increasingly use gRPC under the hood, legacy Google API Client Libraries remain strictly limited to REST.
Cloud Code is a set of IDE plugins for VS Code, IntelliJ, and Cloud Shell that assists developers with browsing Cloud APIs, enabling services, and adding Cloud Client Libraries to projects. API Gateway is a managed proxy that provides API management features and HTTP/JSON-to-gRPC transcoding for customer-hosted gRPC services running on Cloud Run.
500 Internal Server Error responses.You were deploying your own gRPC service on Cloud Run that needed to accept HTTP/JSON traffic from browser clients via API Gateway, while using Cloud Code in your IDE to manage supported client libraries.
When a microservice calls a gRPC-enabled Google Cloud API directly in a language lacking an official Cloud Client Library, generating a native gRPC client from .proto definitions provides end-to-end HTTP/2 binary efficiency without intermediate transcoding.
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