Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
Your development team is building high-throughput backend microservices that programmatically manage and stream data across several Google Cloud services, including Pub/Sub and Dataproc.
The team needs to establish coding and dependency standards with the following architectural requirements:
Which library selection strategy should you recommend?
Using raw HTTP requests involves manually building HTTP headers, serializing JSON payloads, generating OAuth2 access tokens via metadata servers, and parsing response bodies using built-in language HTTP modules.
The runtime environment operated under extreme memory constraints (such as an embedded IoT runtime) where importing any SDK dependencies was strictly prohibited.
Google API Client Libraries are autogenerated SDKs that expose Google Cloud APIs over standard HTTP and REST/JSON interfaces based on the Google API Discovery Service.
The organization had a strict constraint requiring all outbound communication to use raw HTTP/1.1 REST endpoints through a legacy proxy that actively inspects JSON payloads and blocks binary gRPC/HTTP2 traffic.
Generating custom clients requires downloading the public Protocol Buffer (protobuf) definitions from the googleapis GitHub repository and compiling them using protoc and language-specific gRPC plugins.
The team was developing in an esoteric programming language for which Google publishes neither a Cloud Client Library nor a Google API Client Library.
Cloud Client Libraries are the latest, recommended programmatic interfaces for calling Google Cloud APIs. They are written specifically for each supported programming language to offer idiomatic abstractions, whereas Google API Client Libraries are older, autogenerated libraries that target REST-based Discovery APIs.

This approach aligns with Google Cloud best practices by prioritizing performance and developer ergonomics through Cloud Client Libraries, while maintaining robust service coverage through Google API Client Libraries as a fallback.
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