Google PCA Practice Question: Managing Implementation and Ensuring Solution and Operations Reliability
Your company runs a production microservices application on GKE Standard. The operations team wants to be notified when any pod in the cluster is repeatedly restarting, indicating a potential CrashLoopBackOff. They want to use Cloud Monitoring to create an alert that fires when a container restarts more than 5 times in a 10-minute window. Which metric should they use as the basis for the alerting policy?
⚠ Common exam trap
The trap here is assuming that pod status or CPU metrics can indicate restarts, when only the dedicated restart count metric provides the necessary data.
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
✓
kubernetes.io/container/restart_count
The kubernetes.io/container/restart_count metric directly tracks container restarts and is the correct choice for alerting on repeated restarts. It is a cumulative counter, so you must apply a rate or delta alignment to detect increases over time. Other metrics like CPU usage or pod status do not provide restart counts, and log-based metrics require extra setup and may be less reliable.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
kubernetes.io/container/cpu/core_usage_time
Why it's wrong here
This metric measures CPU core usage time, which indicates resource consumption but does not reflect container restarts. A container could restart due to application errors without high CPU usage, so this metric would miss the CrashLoopBackOff condition entirely. It is unsuitable for detecting restart loops.
- ✓
kubernetes.io/container/restart_count
Why this is correct
This metric is a cumulative counter that tracks the number of times a container has restarted. By using a rate or delta alignment over a 10-minute window, you can detect when restarts exceed a threshold of 5, directly matching the requirement. It is the standard metric for container restarts in GKE and is available in Cloud Monitoring without additional setup.
- ✗
kubernetes.io/pod/status
Why it's wrong here
This metric reports the phase of a pod (e.g., Running, Pending, Failed) as a gauge, not the number of restarts. While a pod in Failed phase might indicate issues, it does not provide a count of restarts within a time window, and CrashLoopBackOff pods often remain in Running phase between restarts. Thus it cannot trigger on a restart count threshold.
- ✗
logging.googleapis.com/user/restart_count
Why it's wrong here
This is not a built-in metric; it would be a user-defined log-based metric. While you could create a log-based metric from container restart logs, it requires additional configuration and may not capture all restarts reliably. The native metric is simpler and more accurate for this purpose.
Go deeper
Related to this question
Learn chapter
Google Kubernetes Engine (GKE)
Key term
Cloud Monitoring
Cloud monitoring is the process of observing, measuring, and managing an organization's cloud infrastructure and applications to ensure performance, availability, and security.
Key term
GKE Standard
GKE Standard is a Google Kubernetes Engine cluster mode where you pay for the underlying virtual machines and manage the cluster infrastructure yourself, including node pools and scaling decisions.
About these practice questions
This PCA question is part of Courseiva's 807-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
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.