FirstTry

Objective 1.3

PCD

Storing and accessing data

Objective 1.3 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-3Designing highly scalable, secure, and reliable cloud-native applications

A team queries a collection and one stored document never comes back, though it plainly exists. What accounts for that on a query using an index?

The document was written after the index builtIndex building backfills existing documents rather than skipping them.
The document has no value set for that fieldCorrect · your answerCorrect. One unset field is enough to leave it out.
The document exceeds the entry size limitNo per document ceiling of that kind decides index membership here.
The document sits in a different collectionA collection mismatch would rule out the query, not one document within it.

Correct.

Concept

Membership of an index is decided per document, so absence from the index is silent: the query returns a smaller answer rather than an error.

Why B

A document appears in an index only when it has an indexed value set for every field the index names. Missing one of them keeps it out, and no query on that index will ever return it.

Source

A document is included in the index only if it has an indexed value set for every field used in the index. If the index definition refers to a field for which the document has no value set, that document won't appear in the index. In this case, the document will never be returned as a result for any query based on the index.

Firestore Standard edition index overview, checked August 2026
#gcp#firestore#indexes#queries

Now you: objective 1.3 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

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

A team expects its queries to slow as a collection grows past several million documents. What actually governs how long a query takes?

Sample question 2 of 3

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

An engineer runs a query filtering on two fields at once and it fails outright. Why was no index already waiting for it?

Sample question 3 of 3

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

A team sets an index exemption on a map field, then deletes an exemption it had placed on one of that map's subfields. What governs that subfield now?

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