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.
An enterprise development team is preparing to release major architectural updates to a mission-critical REST API deployed on Google Cloud. The update introduces backward-incompatible changes to several request and response schemas.
The operations and API governance teams have established the following requirements:
Which API lifecycle and versioning strategy should you recommend?
/v2, leaving /v1 in the original project to isolate telemetry until decommissioningThis approach deploys each API major version into a completely separate Google Cloud project, provisioning independent Virtual Private Cloud (VPC) networks, load balancers, and gateway instances for every version release.
The two API versions had strict security compliance boundaries requiring complete infrastructure isolation, separate billing accounts, or distinct organizational ownership.
Semantic patch versioning represents internal bug fixes that carry no interface or schema changes. Header-based routing inspects custom HTTP headers (such as X-API-Version) to direct incoming traffic to different backend microservices behind a single endpoint URI.
The team were implementing an internal A/B experiment or canary deployment for bug fixes where interface contracts remained 100% identical.
/v2) alongside /v1 in a unified backend service, deploy separate OpenAPI configurations for both versions, and monitor per-version traffic in service analytics until /v1 can be safely retiredMajor API versioning via path prefixes (such as /v1 and /v2) is the standard practice for introducing backward-incompatible (breaking) changes in RESTful architectures. By maintaining distinct OpenAPI specifications or API proxies for each major version while implementing them concurrently within a single backend service, organizations can serve multiple API generations simultaneously without duplicating hosting infrastructure.

/v1 endpoints without failing due to unexpected schema modifications. Consumers migrate to the /v2 base path on their own development timelines./v1 and verify when active requests reach zero./v1, /v2) provide explicit contracts for consumer integration.This architecture balances seamless developer transition with operational simplicity. It allows development teams to release breaking innovations without impacting existing clients while giving operations clear observability to govern the API lifecycle safely.
1.1), redeploy the API over the /v1 base path, and rely on API gateway request-transformation policies to adapt breaking payload structures dynamicallyIncrementing a minor version (e.g., from 1.0 to 1.1) is intended strictly for backward-compatible updates, such as adding new optional fields or introducing new non-breaking API methods. In this pattern, the base path remains unchanged (such as /v1), and the updated configuration overwrites the active deployment.
/v1 path, API telemetry cannot reliably differentiate between migrated clients and legacy clients.The team were adding purely non-breaking changes, such as introducing a new optional query parameter or an additional GET endpoint, where existing clients require no modifications.
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