The answer is to configure liveness probes to restart unhealthy containers, alongside enabling Cloud Monitoring for metrics collection and defining readiness probes for traffic management. This trio ensures application performance monitoring and reliability on GKE because liveness probes automatically restart containers that have entered a broken state, while Cloud Monitoring provides native visibility into resource utilization and custom metrics, and readiness probes prevent traffic from reaching pods that are not yet ready to serve. On the Google Professional Cloud Developer exam, this tests your understanding of Kubernetes health checks and observability integration, often appearing as a scenario where a team must distinguish between probes that maintain container lifecycle versus those that control service routing. A common trap is confusing liveness probes with readiness probes—remember that liveness keeps the container alive, while readiness decides if it receives traffic. A useful memory tip is “Liveness for life, readiness for requests.”
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.
A DevOps team is deploying a critical application on GKE. To ensure application performance monitoring and reliability, which three actions should they take? (Choose three.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable Cloud Monitoring to collect container metrics
A is correct because Cloud Monitoring (formerly Stackdriver) integrates natively with GKE to collect container metrics such as CPU, memory, disk, and network usage, as well as custom metrics via the Monitoring agent. This provides the visibility needed for performance monitoring and reliability without additional configuration overhead.
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.
✓
Enable Cloud Monitoring to collect container metrics
Why this is correct
Cloud Monitoring provides visibility into resource usage and enables alerting on performance issues.
Related concept
Read the scenario before looking for a memorised answer.
✗
Enable Cloud Debugger in production to debug code
Why it's wrong here
Cloud Debugger can impact performance and is not recommended for production use.
✓
Configure readiness probes to send traffic only to ready pods
Why this is correct
Readiness probes prevent traffic to pods that are not ready, ensuring stability.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use Cloud Profiler to continuously profile CPU usage
Why it's wrong here
Cloud Profiler is useful for optimizing performance but is not a core requirement for reliability.
✓
Configure liveness probes to restart unhealthy containers
Why this is correct
Liveness probes help maintain application health by restarting failing containers.
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 monitoring (Cloud Monitoring), health checks (readiness/liveness probes), and profiling (Cloud Profiler) — the trap is that candidates may select Cloud Profiler as a monitoring action, but it is a continuous profiling tool for optimization, not a reliability or monitoring action.
Detailed technical explanation
How to think about this question
Readiness probes in GKE use HTTP GET, TCP socket, or exec commands to determine if a pod is ready to serve traffic; if the probe fails, the pod is removed from the Service's endpoints, preventing traffic loss. Liveness probes similarly use these methods but restart the container on failure, ensuring self-healing. Both probes are configured in the pod spec under `spec.containers.livenessProbe` and `readinessProbe`, with parameters like `initialDelaySeconds`, `periodSeconds`, and `failureThreshold` to fine-tune behavior.
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 healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
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: Enable Cloud Monitoring to collect container metrics — A is correct because Cloud Monitoring (formerly Stackdriver) integrates natively with GKE to collect container metrics such as CPU, memory, disk, and network usage, as well as custom metrics via the Monitoring agent. This provides the visibility needed for performance monitoring and reliability without additional configuration overhead.
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.