PCDOE Implementing service monitoring strategies Practice Question
This PCDOE practice question tests your understanding of implementing service monitoring strategies. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
```
"logsBasedMetric": {
"filter": "resource.type=\"gce_instance\" AND jsonPayload.status=\"500\"",
"metricDescriptor": {
"metricKind": "DELTA",
"valueType": "INT64",
"name": "custom.googleapis.com/errors/5xx"
},
"labelExtractors": {
"instance_id": "EXTRACT(jsonPayload.instance_id)"
},
"description": "Count of 500 errors per instance"
}
```
An SRE team created the above logs-based metric. They expect it to count the number of HTTP 500 errors per instance. However, the metric shows no data. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The log entries might not have the 'status' field in jsonPayload; it could be in a different location or format.
Option B is correct because the most likely reason for a logs-based metric showing no data is that the log entries do not contain the expected 'status' field in jsonPayload, or it is located in a different field (e.g., httpRequest.status) or formatted as a string instead of an integer. Cloud Logging metrics rely on exact field paths defined in the metric descriptor; if the field is missing or misnamed, no data points are generated.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The metric kind is DELTA but should be CUMULATIVE.
Why it's wrong here
DELTA is appropriate for counting events over time; CUMULATIVE would not change the filter matching issue.
✓
The log entries might not have the 'status' field in jsonPayload; it could be in a different location or format.
Why this is correct
If the logs are structured differently, the filter will not match, resulting in no data.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The metric name does not follow the required naming convention.
Why it's wrong here
custom.googleapis.com/errors/5xx is a valid custom metric name.
✗
The labelExtractors must use regex instead of JSON path.
Why it's wrong here
EXTRACT with jsonPayload is valid; regex is not required.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that metric kind or naming conventions cause missing data, but the real issue is almost always a mismatch between the log entry's actual field structure and the metric's extraction configuration.
Detailed technical explanation
How to think about this question
Under the hood, a logs-based metric in Cloud Logging uses a filter to select log entries and then applies labelExtractors and a valueExtractor to extract numeric values from fields like jsonPayload.status. If the field path is incorrect (e.g., using 'status' when the actual field is nested under 'httpRequest.status' or is a string like '500' instead of an integer), the extraction yields null, and no time series data is written. A real-world scenario is when an application logs HTTP status codes in a nested object (e.g., 'response.status') or as a quoted string, causing the metric to silently fail.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Implementing service monitoring strategies — This question tests Implementing service monitoring strategies — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The log entries might not have the 'status' field in jsonPayload; it could be in a different location or format. — Option B is correct because the most likely reason for a logs-based metric showing no data is that the log entries do not contain the expected 'status' field in jsonPayload, or it is located in a different field (e.g., httpRequest.status) or formatted as a string instead of an integer. Cloud Logging metrics rely on exact field paths defined in the metric descriptor; if the field is missing or misnamed, no data points are generated.
What should I do if I get this PCDOE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PCDOE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCDOE exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.