The correct solution is to use Cloud Monitoring dashboards, ingesting OpenTelemetry metrics into Cloud Monitoring while leveraging Cloud Logging log-based metrics from the legacy app. This approach achieves unified performance monitoring across hybrid environments because Cloud Monitoring natively supports the OpenTelemetry Protocol (OTLP), allowing traces and metrics from the new microservices to flow directly into the same platform that already receives log-based metrics from the legacy Compute Engine application. On the Google Professional Cloud Developer exam, this scenario tests your understanding of how to bridge legacy Stackdriver agents with modern OpenTelemetry instrumentation without requiring a full rewrite. A common trap is assuming you need a separate tracing backend or a proprietary agent for the new services, but Cloud Monitoring’s native OTLP ingestion eliminates that complexity. Remember the memory tip: “OTLP unifies the old and new” — OpenTelemetry Protocol lets you correlate logs and traces from both environments in a single pane of glass.
PCD Managing application performance monitoring Practice Question
This PCD practice question tests your understanding of managing application performance monitoring. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 has a legacy monolithic application running on Compute Engine that is being migrated to microservices on GKE. During the migration, they need to maintain performance monitoring across both environments. The legacy application uses Stackdriver Logging and Monitoring agents (now Ops Agent) and exports logs to Cloud Logging. The new microservices are instrumented with OpenTelemetry for traces and metrics. The team wants a unified view of performance across both environments, including distributed traces from the new services and log-based metrics from the legacy app. They also want to correlate logs and traces for troubleshooting. Which solution should they implement?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Cloud Monitoring dashboards and ingest OpenTelemetry metrics into Cloud Monitoring, while using Cloud Logging log-based metrics from legacy app.
Option C is correct because it provides a unified view by ingesting OpenTelemetry metrics into Cloud Monitoring and using Cloud Logging log-based metrics from the legacy app. Cloud Monitoring supports OpenTelemetry metrics via the OpenTelemetry Protocol (OTLP) and can correlate them with log-based metrics from the legacy app, enabling distributed tracing and log correlation in a single dashboard.
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.
✗
Keep monitoring separate and use separate dashboards for legacy and new.
Why it's wrong here
Separate dashboards do not provide a unified view and hinder correlation.
✗
Use a third-party APM tool that supports both environments.
Why it's wrong here
While possible, it's not leveraging native Google Cloud tools and may add complexity.
✓
Use Cloud Monitoring dashboards and ingest OpenTelemetry metrics into Cloud Monitoring, while using Cloud Logging log-based metrics from legacy app.
Why this is correct
This approach unifies metrics and logs from both environments, enabling correlation.
Related concept
Read the scenario before looking for a memorised answer.
✗
Rewrite the legacy app to use OpenTelemetry.
Why it's wrong here
Rewriting is costly and time-consuming, not necessary.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think rewriting the legacy app is necessary for unified monitoring, but Google Cloud's native support for OpenTelemetry and log-based metrics allows integration without code changes.
Detailed technical explanation
How to think about this question
Cloud Monitoring can ingest OpenTelemetry metrics via the Ops Agent or directly using the OpenTelemetry Collector with the Google Cloud exporter, which sends metrics and traces to Cloud Monitoring and Cloud Trace respectively. Log-based metrics from the legacy app are defined in Cloud Logging using filters on log entries, and these metrics can be visualized in Cloud Monitoring dashboards alongside OpenTelemetry metrics. The correlation between logs and traces is achieved by using a common trace ID in log entries, which Cloud Logging and Cloud Trace can link automatically when the trace context is propagated.
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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
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: Use Cloud Monitoring dashboards and ingest OpenTelemetry metrics into Cloud Monitoring, while using Cloud Logging log-based metrics from legacy app. — Option C is correct because it provides a unified view by ingesting OpenTelemetry metrics into Cloud Monitoring and using Cloud Logging log-based metrics from the legacy app. Cloud Monitoring supports OpenTelemetry metrics via the OpenTelemetry Protocol (OTLP) and can correlate them with log-based metrics from the legacy app, enabling distributed tracing and log correlation in a single dashboard.
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.