- A
Legacy Cloud Logging agent integration for container logs.
Why wrong: Logs are handled by Kubernetes; sidecar not needed.
- B
Custom Prometheus exporter deployment for each microservice.
Why wrong: Not automatic; manual configuration required.
- C
Automatic generation of HTTP request metrics (e.g., request count, latency, error rate) per service.
Collects metrics for each service proxy.
- D
Cloud Endpoints API management with key validation.
Why wrong: Endpoints is a separate product, not Istio.
- E
Distributed tracing propagation and span generation without application changes.
Istio injects trace headers and sends spans to Cloud Trace.
Quick Answer
The answer is distributed tracing propagation and span generation without application changes. This is correct because Cloud Service Mesh, built on Istio, leverages Envoy sidecar proxies to automatically intercept all service-to-service traffic, generating standardized telemetry such as HTTP request metrics, latency, and error rates without requiring any code modifications to your applications. On the Google Professional Cloud Developer exam, this concept tests your understanding of how a service mesh decouples observability from application logic—a common trap is assuming you must manually instrument your code for tracing, when Istio’s sidecar handles it transparently. The search intent around cloud service mesh istio monitoring capabilities directly aligns with this automatic, proxy-driven approach to application performance management (APM). Remember the mnemonic “No Code, No Cry” for Istio monitoring: the sidecar does the heavy lifting, so your application stays clean and unchanged.
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.
Which TWO capabilities does Cloud Service Mesh (Istio) provide to help monitor application performance? (Select exactly 2.)
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
Automatic generation of HTTP request metrics (e.g., request count, latency, error rate) per service.
Option C is correct because Cloud Service Mesh (Istio) automatically generates HTTP request metrics such as request count, latency, and error rate for every service in the mesh. This is achieved through Envoy sidecar proxies that intercept all traffic and export standardized telemetry without requiring any application code changes.
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.
- ✗
Legacy Cloud Logging agent integration for container logs.
Why it's wrong here
Logs are handled by Kubernetes; sidecar not needed.
- ✗
Custom Prometheus exporter deployment for each microservice.
Why it's wrong here
Not automatic; manual configuration required.
- ✓
Automatic generation of HTTP request metrics (e.g., request count, latency, error rate) per service.
Why this is correct
Collects metrics for each service proxy.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Cloud Endpoints API management with key validation.
Why it's wrong here
Endpoints is a separate product, not Istio.
- ✓
Distributed tracing propagation and span generation without application changes.
Why this is correct
Istio injects trace headers and sends spans to Cloud Trace.
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 automatic telemetry generation (Istio's built-in Prometheus and tracing) versus manual instrumentation or separate API management tools, leading candidates to confuse Cloud Endpoints or custom exporters with Istio's native capabilities.
Detailed technical explanation
How to think about this question
Istio's telemetry is powered by Envoy's HTTP connection manager, which generates metrics like `istio_requests_total` with labels for source, destination, response code, and protocol. Distributed tracing in Istio uses the Envoy-based Zipkin or Jaeger integration, propagating trace context via B3 headers (or W3C trace context) and generating spans automatically for each hop, enabling end-to-end latency analysis without modifying application code.
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: Automatic generation of HTTP request metrics (e.g., request count, latency, error rate) per service. — Option C is correct because Cloud Service Mesh (Istio) automatically generates HTTP request metrics such as request count, latency, and error rate for every service in the mesh. This is achieved through Envoy sidecar proxies that intercept all traffic and export standardized telemetry without requiring any application code changes.
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.