The answer is to create a new log-based metric that filters out health check requests and use that in the alert. This is correct because the default 'request_count' metric in Cloud Monitoring includes all HTTP requests to Cloud Run, including system health checks, which inflate the count and cause alert fatigue. By creating a log-based metric with a filter that excludes health check traffic, you isolate real user traffic, allowing the alert to trigger only on genuine demand spikes. On the Google Professional Cloud Developer exam, this scenario tests your ability to customize monitoring with log-based metrics rather than relying on built-in metrics, a common trap where candidates overlook the need to exclude infrastructure noise. A useful memory tip: think of log-based metrics as a "smart filter" that lets you monitor what matters—user requests, not system pings.
PCD Managing application performance monitoring Practice Question
This PCD practice question tests your understanding of managing application performance monitoring. 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.
Your team manages a serverless application deployed on Cloud Run. The application processes image uploads and stores metadata in Firestore. You have set up a Cloud Monitoring alert based on the 'request_count' metric for the Cloud Run service. The alert triggers when the request count exceeds 1000 requests per minute. Recently, the alert has been firing frequently, but the team notices that the application is performing well and there are no errors. The team is concerned about alert fatigue. You review the metric and notice that the request count metric is based on all HTTP requests, including health checks from the Cloud Run system. The health check requests account for about 30% of the total requests. What should you do to reduce unnecessary alerts while still monitoring real user traffic?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a new log-based metric that filters out health check requests, and use that in the alert
Option B is correct because creating a new log-based metric that filters out health check requests allows you to monitor only real user traffic. Cloud Run's system health checks (e.g., from the Cloud Run infrastructure) are included in the default 'request_count' metric, inflating the count. By using a log-based metric with a filter that excludes these health check requests, you can set an accurate alert threshold based on actual user demand, reducing alert fatigue without losing visibility into real issues.
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.
✗
Increase the alert threshold to 1500 requests per minute
Why it's wrong here
This only masks the issue and may miss real spikes.
✓
Create a new log-based metric that filters out health check requests, and use that in the alert
Why this is correct
This metric will only count user requests, reducing noise.
Related concept
Read the scenario before looking for a memorised answer.
✗
Disable health checks on the Cloud Run service
Why it's wrong here
Health checks are important for monitoring service health.
✗
Configure the existing metric to exclude health check logs
Why it's wrong here
The metric is based on all requests; you cannot exclude without a new metric.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that you can modify built-in metrics or that simply adjusting thresholds is sufficient, when in reality you must create a custom metric to filter out noise like health checks.
Detailed technical explanation
How to think about this question
Cloud Run's built-in 'request_count' metric counts all HTTP requests reaching the container, including health check requests sent by the Cloud Run infrastructure (e.g., from the 'cloud-run-hello' or 'google-cloud-run' user agents). These health checks are typically sent every few seconds to verify container readiness and liveness. A log-based metric in Cloud Logging can filter on the 'httpRequest.requestUrl' or 'jsonPayload' fields to exclude requests with paths like '/healthz' or user agents containing 'GoogleHC', allowing precise monitoring of user traffic only.
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.
Managing application performance monitoring — This question tests Managing application performance monitoring — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a new log-based metric that filters out health check requests, and use that in the alert — Option B is correct because creating a new log-based metric that filters out health check requests allows you to monitor only real user traffic. Cloud Run's system health checks (e.g., from the Cloud Run infrastructure) are included in the default 'request_count' metric, inflating the count. By using a log-based metric with a filter that excludes these health check requests, you can set an accurate alert threshold based on actual user demand, reducing alert fatigue without losing visibility into real issues.
What should I do if I get this PCD question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 PCD 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 PCD 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.