← PCD·Google Cloud

Question 233 of 500

Managing application performance monitoring →hardMultiple ChoiceObjective-mapped

PCD Managing application performance monitoring Practice Question

This PCD practice question tests your understanding of managing application performance monitoring. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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

Refer to the exhibit.

Cloud Monitoring Metrics Scope:
- Project: prod-project
- Metrics: 
  - latency | resource.type="gae_app" | resource.labels.module_id="frontend" | metric: custom.googleapis.com/opentelemetry/request_latency
- Alert Policy ID: 123456789
- Condition: metric.threshold > 500 ms for 1m
- Notification Channels: email (dev-team@example.com), PagerDuty

Cloud Logging Log Entry (from frontend service):
{
  "textPayload": "Request processed",
  "severity": "INFO",
  "httpRequest": {
    "requestUrl": "https://frontend.example.com/api/checkout",
    "status": 200,
    "responseSize": "2048",
    "latency": "0.452s"
  },
  "resource": {
    "type": "gae_app",
    "labels": {
      "module_id": "frontend",
      "version_id": "v2"
    }
  }
}

Your company runs a production App Engine standard environment service (module 'frontend', version 'v2') that handles e-commerce checkout requests. You have set up an alerting policy on a custom metric 'request_latency' that fires when latency exceeds 500ms for 1 minute. Recently, customers have complained about slow checkout times, but no alert has fired. You examine the exhibit: the log entry shows a latency of 0.452s (452ms) for a request to '/api/checkout'. The custom metric is defined from OpenTelemetry instrumentation. What is the most likely reason the alert did not fire?

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.

Question 1hardmultiple choice

Read the full network assurance explanation →

Exhibit

Refer to the exhibit.

Cloud Monitoring Metrics Scope:
- Project: prod-project
- Metrics: 
  - latency | resource.type="gae_app" | resource.labels.module_id="frontend" | metric: custom.googleapis.com/opentelemetry/request_latency
- Alert Policy ID: 123456789
- Condition: metric.threshold > 500 ms for 1m
- Notification Channels: email (dev-team@example.com), PagerDuty

Cloud Logging Log Entry (from frontend service):
{
  "textPayload": "Request processed",
  "severity": "INFO",
  "httpRequest": {
    "requestUrl": "https://frontend.example.com/api/checkout",
    "status": 200,
    "responseSize": "2048",
    "latency": "0.452s"
  },
  "resource": {
    "type": "gae_app",
    "labels": {
      "module_id": "frontend",
      "version_id": "v2"
    }
  }
}

A
The alert condition uses a threshold on a metric that is not being written because the OpenTelemetry exporter is not configured for the 'frontend' module.
Why wrong: The metric is defined, but the log shows a latency value, not the metric itself.
B
The log entry does not contain the required custom metric data because the httpRequest field is not parsed by Cloud Monitoring.
Why wrong: The custom metric comes from OpenTelemetry, not from log entries.
C
The alert threshold is 500ms, and the exhibited request latency is 452ms, which is below the threshold. Individual requests may be below the threshold, so the alert does not fire.
The log shows a single request below threshold; the alert requires exceeding for 1 minute.
D
The custom metric is only emitted for version 'v1', and the current version is 'v2', so no metric data is available for the alert.
Why wrong: The metric is instrumented in code and should be emitted for all versions.

Full breakdown with real-world context →

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

✓

The alert threshold is 500ms, and the exhibited request latency is 452ms, which is below the threshold. Individual requests may be below the threshold, so the alert does not fire.

Option C is correct because the alerting policy is configured to fire when the custom metric 'request_latency' exceeds 500ms for 1 minute. The exhibited log entry shows a latency of 452ms, which is below the 500ms threshold. The alert condition is based on a metric threshold, not individual log entries, and since the metric value remains below the threshold, the alert does not trigger.

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 alert condition uses a threshold on a metric that is not being written because the OpenTelemetry exporter is not configured for the 'frontend' module.
Why it's wrong here
The metric is defined, but the log shows a latency value, not the metric itself.
✗
The log entry does not contain the required custom metric data because the httpRequest field is not parsed by Cloud Monitoring.
Why it's wrong here
The custom metric comes from OpenTelemetry, not from log entries.
✓
The alert threshold is 500ms, and the exhibited request latency is 452ms, which is below the threshold. Individual requests may be below the threshold, so the alert does not fire.
Why this is correct
The log shows a single request below threshold; the alert requires exceeding for 1 minute.
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 custom metric is only emitted for version 'v1', and the current version is 'v2', so no metric data is available for the alert.
Why it's wrong here
The metric is instrumented in code and should be emitted for all versions.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Cisco often tests the distinction between individual log entries and aggregated metric thresholds, leading candidates to mistakenly assume that any request latency near the threshold should trigger an alert, when in fact the alert condition requires sustained violation over the evaluation window.

Trap categories for this question

Command / output trap
The metric is defined, but the log shows a latency value, not the metric itself.

Detailed technical explanation

How to think about this question

OpenTelemetry instrumentation exports custom metrics directly to Cloud Monitoring via the OpenTelemetry Collector or the Google Cloud Monitoring exporter, bypassing log-based metrics. The alerting policy evaluates the metric time series over a 1-minute window, so even if some individual requests exceed 500ms, the alert only fires if the aggregated metric (e.g., mean, percentile) stays above the threshold for the entire duration. In this case, the 452ms value is below the threshold, so no alert is triggered.

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.

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.

10 questions 20 questions 30 questions 50 questions Timed 30

PCD practice-test guide →Study guide →Browse all practice tests

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: The alert threshold is 500ms, and the exhibited request latency is 452ms, which is below the threshold. Individual requests may be below the threshold, so the alert does not fire. — Option C is correct because the alerting policy is configured to fire when the custom metric 'request_latency' exceeds 500ms for 1 minute. The exhibited log entry shows a latency of 452ms, which is below the 500ms threshold. The alert condition is based on a metric threshold, not individual log entries, and since the metric value remains below the threshold, the alert does not trigger.

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.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

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.

Loading comments…

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.