Objective 4.3

PCD

Troubleshooting and observability

Objective 4.3 sits in Integrating applications with Google Cloud services, which carries 21% 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.

4-3Integrating applications with Google Cloud services

A team writes its log lines as plain strings and finds it cannot index any field for querying. What changes when the payload becomes a JSON object?

Storage moves to indexable JSON fieldsCorrect · your answerCorrect. Named fields become addressable.
The text field survives beside a second copyOnly one of the two payload fields holds the entry, never both.
Compression is applied before storageStorage encoding is unrelated to what the payload shape enables.
Routing sends it to a different bucketRouting is decided by sinks and filters, not by the payload type.

Correct.

Concept

A payload with named fields can be queried by path and indexed field by field, while an opaque string can only be searched as a whole.

Why A

A JSON payload is stored in the structured payload field, where queries can search specific paths and individual fields can be indexed. A string payload can be searched but never indexed.

Source

When the log payload is formatted as a JSON object and that object is stored in the jsonPayload field, the log entry is called a structured log . For these logs, you can construct queries that search specific JSON paths and you can index specific fields in the log payload. In contrast, when the log payload is formatted as a string and stored in the textPayload field, the log entry is unstructured . You can search the text field, but you can't index its content.

Structured logging, checked August 2026
#gcp#cloud-logging#structured-logging#observability

Now you: objective 4.3 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

4-3Integrating applications with Google Cloud services

A team's container writes to standard output on a managed runtime, and the lines show up in the log viewer without any client library. What did that?

Sample question 2 of 3

4-3Integrating applications with Google Cloud services

A team wants the level of a log line to appear as the entry's severity rather than as text buried in the payload. What has to happen?

Sample question 3 of 3

4-3Integrating applications with Google Cloud services

A team wants exceptions from its service grouped and counted by the error tracking product. Which JSON field has to carry the stack trace?

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 Integrating applications with Google Cloud services