- A
kube_deployment_status_replicas_ready
This metric shows ready replicas, enabling comparison with desired replicas.
- B
kube_deployment_spec_replicas
Why wrong: This shows desired replicas, but alone doesn't show health.
- C
kube_node_status_condition
Why wrong: Node-level metric, not deployment health.
- D
kube_pod_container_status_running
Why wrong: This is a pod-level metric, not deployment-level.
KCNA Cloud Native Observability Practice Question
This KCNA practice question tests your understanding of cloud native observability. 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.
A developer wants to monitor the health of a Kubernetes deployment by checking if the number of ready replicas matches the desired replicas. Which metric from kube-state-metrics should they query?
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
kube_deployment_status_replicas_ready
Option A is correct because `kube_deployment_status_replicas_ready` directly exposes the number of ready replicas for a Deployment, which can be compared against `kube_deployment_spec_replicas` to determine if the desired state matches the actual healthy state. This metric is emitted by kube-state-metrics, which generates Prometheus-compatible metrics from Kubernetes API objects, making it the standard choice for monitoring Deployment health.
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.
- ✓
kube_deployment_status_replicas_ready
Why this is correct
This metric shows ready replicas, enabling comparison with desired replicas.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
kube_deployment_spec_replicas
Why it's wrong here
This shows desired replicas, but alone doesn't show health.
- ✗
kube_node_status_condition
Why it's wrong here
Node-level metric, not deployment health.
- ✗
kube_pod_container_status_running
Why it's wrong here
This is a pod-level metric, not deployment-level.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates might confuse metrics that show pod state (like `kube_pod_container_status_running`) with Deployment-level readiness, not realizing that a pod can be running but not ready, and that the correct metric must reflect the Deployment's own status field.
Trap categories for this question
Command / output trap
This shows desired replicas, but alone doesn't show health.
Detailed technical explanation
How to think about this question
Under the hood, kube-state-metrics watches the Kubernetes API for Deployment objects and exposes `kube_deployment_status_replicas_ready` from the Deployment's `.status.readyReplicas` field, which is updated by the ReplicaSet controller based on pod readiness probe results. In a real-world scenario, a mismatch between `kube_deployment_status_replicas_ready` and `kube_deployment_spec_replicas` can indicate issues like resource constraints, failing readiness probes, or a misconfigured rolling update strategy, enabling proactive alerting.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
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.
- →
Cloud Native Observability — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Native Observability practice questions
Targeted practice on this topic area only
- →
All KCNA questions
997 questions across all exam domains
- →
Kubernetes and Cloud Native Associate KCNA study guide
Full concept coverage aligned to exam objectives
- →
KCNA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related KCNA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Kubernetes Fundamentals practice questions
Practise KCNA questions linked to Kubernetes Fundamentals.
Container Orchestration practice questions
Practise KCNA questions linked to Container Orchestration.
Cloud Native Architecture practice questions
Practise KCNA questions linked to Cloud Native Architecture.
Cloud Native Observability practice questions
Practise KCNA questions linked to Cloud Native Observability.
Cloud Native Application Delivery practice questions
Practise KCNA questions linked to Cloud Native Application Delivery.
KCNA fundamentals practice questions
Practise KCNA questions linked to KCNA fundamentals.
KCNA scenario practice questions
Practise KCNA questions linked to KCNA scenario.
KCNA troubleshooting practice questions
Practise KCNA questions linked to KCNA troubleshooting.
Practice this exam
Start a free KCNA 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 KCNA question test?
Cloud Native Observability — This question tests Cloud Native Observability — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: kube_deployment_status_replicas_ready — Option A is correct because `kube_deployment_status_replicas_ready` directly exposes the number of ready replicas for a Deployment, which can be compared against `kube_deployment_spec_replicas` to determine if the desired state matches the actual healthy state. This metric is emitted by kube-state-metrics, which generates Prometheus-compatible metrics from Kubernetes API objects, making it the standard choice for monitoring Deployment health.
What should I do if I get this KCNA 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 11, 2026
This KCNA practice question is part of Courseiva's free CNCF 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 KCNA 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.