- A
Metric type: custom.googleapis.com, condition: metric lower bound, duration: 60s
Why wrong: Metric lower bound is not a valid condition type in Cloud Monitoring.
- B
Metric type: custom.googleapis.com, condition: metric change, duration: 60s
Why wrong: Metric change detects rate of change, not absolute values.
- C
Metric type: custom.googleapis.com, condition: metric absence, duration: 60s
Why wrong: Absence fires when data stops being reported, not when values are below threshold.
- D
Metric type: custom.googleapis.com, condition: metric threshold (below value), duration: 60s
Threshold condition with direction 'below' and duration 60s works for a value below threshold for 1 minute.
Quick Answer
The correct alert condition type is metric threshold with a below value configuration and a duration of 60 seconds. This choice is technically correct because Cloud Monitoring’s metric threshold condition evaluates a single metric against a static lower bound, and the duration parameter ensures the condition must be true for the specified period—in this case, 60 seconds—before the alert fires. Since the custom metric is published every 30 seconds, a 60-second duration requires at least two consecutive below-threshold data points, preventing false alarms from transient dips. On the Google Professional Cloud Developer exam, this scenario tests your understanding of how duration interacts with metric publishing frequency; a common trap is selecting a condition like metric absence or rate of change, which would not detect sustained low values. Remember the memory tip: “Below needs a duration to be sure”—the threshold condition alone isn’t enough; you must pair it with a duration that exceeds your metric’s publishing interval to confirm the trend.
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.
A company is using Cloud Monitoring to track custom metrics published from an on-premises application using the Monitoring API. The metrics are published every 30 seconds. The team wants to create an alert that fires if the metric goes below a threshold for more than 1 minute. Which alert condition type should they use?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Metric type: custom.googleapis.com, condition: metric threshold (below value), duration: 60s
Option D is correct because the requirement is to fire an alert when the metric value goes below a threshold for more than 1 minute. The 'metric threshold (below value)' condition type directly monitors a metric against a lower bound and evaluates the condition over the specified duration (60s) before triggering. This aligns with the need to detect sustained low values, not just a single data point.
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.
- ✗
Metric type: custom.googleapis.com, condition: metric lower bound, duration: 60s
Why it's wrong here
Metric lower bound is not a valid condition type in Cloud Monitoring.
- ✗
Metric type: custom.googleapis.com, condition: metric change, duration: 60s
Why it's wrong here
Metric change detects rate of change, not absolute values.
- ✗
Metric type: custom.googleapis.com, condition: metric absence, duration: 60s
Why it's wrong here
Absence fires when data stops being reported, not when values are below threshold.
- ✓
Metric type: custom.googleapis.com, condition: metric threshold (below value), duration: 60s
Why this is correct
Threshold condition with direction 'below' and duration 60s works for a value below threshold for 1 minute.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between 'metric absence' (no data) and 'metric threshold below' (data exists but is low), leading candidates to mistakenly choose absence when the scenario describes a value-based condition.
Detailed technical explanation
How to think about this question
Cloud Monitoring alerting policies evaluate conditions over a rolling window defined by the 'duration' field. For a threshold condition with a 60s duration, the policy requires that the metric stays below the threshold for at least two consecutive 30-second data points (since the metric is published every 30s) before firing. This prevents flapping from transient dips. The 'metric absence' condition, by contrast, uses a 'most recent' or 'missing' evaluation and does not consider the metric's value, only its presence.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Managing application performance monitoring practice questions
Targeted practice on this topic area only
- →
All PCD questions
500 questions across all exam domains
- →
Google Professional Cloud Developer study guide
Full concept coverage aligned to exam objectives
- →
PCD practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCD practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Designing highly scalable, available, and reliable cloud-native applications practice questions
Practise PCD questions linked to Designing highly scalable, available, and reliable cloud-native applications.
Building and testing applications practice questions
Practise PCD questions linked to Building and testing applications.
Deploying applications practice questions
Practise PCD questions linked to Deploying applications.
Integrating Google Cloud services practice questions
Practise PCD questions linked to Integrating Google Cloud services.
Managing application performance monitoring practice questions
Practise PCD questions linked to Managing application performance monitoring.
PCD fundamentals practice questions
Practise PCD questions linked to PCD fundamentals.
PCD scenario practice questions
Practise PCD questions linked to PCD scenario.
PCD troubleshooting practice questions
Practise PCD questions linked to PCD troubleshooting.
Practice this exam
Start a free PCD practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this PCD question test?
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: Metric type: custom.googleapis.com, condition: metric threshold (below value), duration: 60s — Option D is correct because the requirement is to fire an alert when the metric value goes below a threshold for more than 1 minute. The 'metric threshold (below value)' condition type directly monitors a metric against a lower bound and evaluates the condition over the specified duration (60s) before triggering. This aligns with the need to detect sustained low values, not just a single data point.
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 →
Last reviewed: Jun 25, 2026
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.