GCP Professional Cloud Architect Practice Question

Your team is developing a Java microservice deployed on Cloud Run that must regularly scan several multi-million-object Cloud Storage buckets and write each object's metadata to Cloud Spanner. A developer suggests invoking the Cloud Storage JSON REST API with custom HTTP requests, manually retrieving OAuth 2.0 tokens from the metadata server, paging through nextPageToken values, and coding bespoke exponential-backoff retries. To align with Google Cloud API access best practices while minimizing future maintenance effort and risk, what should you recommend?

Reject the proposal and require using the official Cloud Storage Java client library, which provides automatic Application Default Credentials handling, pagination, and robust retry logic out of the box.
Approve the design but require embedding a long-lived service-account key in the container image instead of using the metadata server for authentication.
Approve the proposed design because direct REST calls avoid external dependencies and offer better scalability than client libraries.
Reject the proposal and migrate the workload to a Compute Engine VM that runs curl commands in a startup script to perform the same operations.

Report Issue

Answer Description

Using the Google Cloud Storage Java client library is the preferred approach because Google-maintained client libraries encapsulate many cross-cutting concerns for you. They automatically obtain and refresh Application Default Credentials when the service runs on Cloud Run, so there is no need to hand-roll token-management logic. The library also automatically handles paginated list results and applies proven, configurable retry and backoff policies for transient errors, greatly reducing custom code and the likelihood of bugs. Continuing with raw REST calls (options approving the proposal) would leave the team responsible for security-sensitive auth code and complex pagination and retry logic, increasing maintenance overhead. Replacing Cloud Run with a VM that executes curl commands does not address these concerns and adds operational burden. Therefore, insisting on the official Cloud Storage Java client library is the solution that best follows Google Cloud's guidance for accessing APIs via client libraries.

Ask Bash

Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.