FirstTry

Objective 1.1

PCD

Designing high-performing applications and APIs

Objective 1.1 sits in Designing highly scalable, secure, and reliable cloud-native applications, which carries 32% of the Cloud Developer exam. The questions below are original, written from the official objective title above, and each explanation cites the Google Cloud page it rests on.

Objective title verbatim from the official objectives. Google Cloud exam page ↗

A worked example

Shown solved, with the whole explanation open: this is what every question here carries.

1-1Designing highly scalable, secure, and reliable cloud-native applications

A team ships backward compatible additions to a published API surface and asks what the version identifier should now read. What does the versioning rule require?

A new major version numberA fresh major number is reserved for a surface change that breaks existing callers.
An incremented minor version numberGoogle APIs do not carry a minor number in the path; v1.1 is the form they deliberately omit.
A patch suffix on the versionSomething like v1.4.2 never appears in a Google API path or package.
The same major version, unchangedCorrect · your answerCorrect. A backwards-compatible change keeps the major version, so callers keep the identifier they already send.

Correct.

Concept

A public identifier that moves on every internal edit forces callers to migrate for edits that could never break them.

Why D

Google API interfaces carry a major version number and nothing finer. Minor and patch numbers are never exposed, and compatible functionality arrives in place under the number already published.

Source

However, unlike in traditional semantic versioning, Google APIs must not expose minor or patch version numbers. For example, Google APIs use v1 , not v1.0 , v1.1 , or v1.4.2 . From a user's perspective, major versions are updated in place with minor/patch equivalent changes, and users receive new functionality without migration.

AIP-185 API Versioning, checked August 2026
#gcp#api-design#versioning#compatibility

Now you: objective 1.1 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

1-1Designing highly scalable, secure, and reliable cloud-native applications

An engineer publishing a new API needs to know where its major version number belongs. Which placement does the guidance require?

Sample question 2 of 3

1-1Designing highly scalable, secure, and reliable cloud-native applications

A client application has to call the old and the new version of one API at the same time while it moves across. What does the guidance require of those versions?

Sample question 3 of 3

1-1Designing highly scalable, secure, and reliable cloud-native applications

A team publishes alpha, beta and stable channels under channel based versioning. What must hold between the surfaces that beta and stable expose?

Full Cloud Developer question bank coming

We’re writing the complete bank from the official objectives right now. Leave your email and we’ll tell you when it ships, nothing else, ever.

Read the sources

These are the official pages the questions above cite. Reading them is studying the objective from the primary source, which is what the explanations point you toward anyway.

More objectives in Designing highly scalable, secure, and reliable cloud-native applications