The correct approach is to use Cloud Monitoring to create custom metrics for application performance and investigate recent code changes. This is the right choice because the team has already ruled out infrastructure issues, meaning the root cause lies within the application logic itself. By instrumenting the application with custom metrics—such as request latency, error rates, or throughput—you can directly correlate performance degradation with specific code deployments or logic paths, which is the essence of application performance monitoring on GKE using custom metrics. On the Google Professional Cloud Architect exam, this scenario tests your ability to distinguish between infrastructure-level monitoring (e.g., node CPU or memory) and application-level observability. A common trap is to default to scaling the cluster or checking GKE logs, but when the question explicitly states infrastructure is fine, the focus must shift to custom instrumentation. Memory tip: “If infra is fine, custom metrics define the line.”
Google PCA Ensure solution and operations reliability Practice Question
This PCA practice question tests your understanding of ensure solution and operations reliability. 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 company runs a critical application on Google Kubernetes Engine (GKE) with 5 nodes. The application experiences intermittent high latency every Friday afternoon. The team has ruled out infrastructure issues and suspects the application logic. You need to instrument the application to identify the root cause. Which approach should you take?
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 to create custom metrics for application performance and investigate recent code changes.
Option A is correct because the team has already ruled out infrastructure issues and suspects application logic. Creating custom metrics in Cloud Monitoring allows you to instrument the application with key performance indicators (e.g., request latency, error rates) and correlate them with recent code changes to pinpoint the root cause of intermittent high latency. This approach directly addresses the need to monitor application-level behavior rather than infrastructure metrics.
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.
✓
Use Cloud Monitoring to create custom metrics for application performance and investigate recent code changes.
Why this is correct
Custom metrics provide visibility into application logic performance, and correlating with code changes can pinpoint the cause.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the number of nodes in the GKE cluster to handle the load.
Why it's wrong here
Scaling up may reduce latency but does not identify the root cause of application logic issues.
✗
Enable Cloud Logging and analyze logs for error messages during the latency periods.
Why it's wrong here
Logs may not capture the intermittent latency if the application does not log performance data.
✗
Configure GKE usage metering to track resource consumption by namespace.
Why it's wrong here
Usage metering tracks resource costs, not application performance.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse operational logging (Option C) with performance monitoring, failing to recognize that intermittent latency without errors requires custom metrics to measure application-specific performance indicators.
Detailed technical explanation
How to think about this question
Custom metrics in Cloud Monitoring are created using the OpenCensus or OpenTelemetry libraries, which export metrics via the Cloud Monitoring API. These metrics can be defined with labels (e.g., function name, version) to correlate performance with specific code changes. In a real-world scenario, you might instrument a critical API endpoint to measure p99 latency and compare it across deployments to identify a regression introduced by a recent code push.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this PCA question in full detail.
Ensure solution and operations reliability — This question tests Ensure solution and operations reliability — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use Cloud Monitoring to create custom metrics for application performance and investigate recent code changes. — Option A is correct because the team has already ruled out infrastructure issues and suspects application logic. Creating custom metrics in Cloud Monitoring allows you to instrument the application with key performance indicators (e.g., request latency, error rates) and correlate them with recent code changes to pinpoint the root cause of intermittent high latency. This approach directly addresses the need to monitor application-level behavior rather than infrastructure metrics.
What should I do if I get this PCA 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 PCA 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 PCA 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.