Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 10
Question 90
A university deploys several bare Pods and wonders why no replacement is created after one is deleted. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Acceptance evidence: Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod. This pairing is justified because a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.
Incorrect Answers
This action and check address the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling” instead of the stated acceptance requirement. The matching action is to use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
This action and check address the distinct objective “Use SLI and SLO measures to focus reliability objectives” instead of the stated acceptance requirement. The matching action is to use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. This action and check address the distinct objective “Distinguish etcd persistence from running workload data” instead of the stated acceptance requirement. The matching action is to use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
Question 91
A city ticketing app shows two ReplicaSets during a staged rollout. What technical action should the platform team take in this situation?
Explanation
Correct Answer
Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. This resolves the issue because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. To verify, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
Incorrect Answers
This option addresses the distinct objective “Identify reconciliation work performed by kube-controller-manager”, not the immediate requirement. The controller manager runs controllers that observe API resources and make changes so current state moves toward desired state. For the stated case, a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
This option addresses the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, not the immediate requirement. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node. For the stated case, a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
This option addresses the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, not the immediate requirement. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects. For the stated case, a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
Question 92
A city ticketing app shows two ReplicaSets during a staged rollout. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. It supports this action: Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. To confirm, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
Incorrect Answers
That statement explains the distinct objective “Design a release rollback trigger from measurable service signals” rather than the cause in this case. The deciding mechanism here is that a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
That statement explains the distinct objective “Distinguish Deployment desired state from a manually created Pod” rather than the cause in this case. The deciding mechanism here is that a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
That statement explains the distinct objective “Understand taints and tolerations as repulsion controls” rather than the cause in this case. The deciding mechanism here is that a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
Question 93
A city ticketing app shows two ReplicaSets during a staged rollout. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain. This is the relevant test because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
Incorrect Answers
This check would help evaluate the distinct objective “Use Events and pod describe for failed volume mounting”, but not the required result. For this case, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
This check would help evaluate the distinct objective “Separate kube-scheduler decisions from kubelet execution”, but not the required result. For this case, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
This check would help evaluate the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, but not the required result. For this case, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
Question 94
A city ticketing app shows two ReplicaSets during a staged rollout. The team suggests: “Change labels on an unrelated Pod to manipulate replica counts without reviewing immutable selector expectations.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior. The shortcut creates this risk because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
Incorrect Answers
That outcome concerns the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”; it is not the most direct consequence of this shortcut. The relevant consequence is that controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.
That outcome concerns the distinct objective “Separate kube-scheduler decisions from kubelet execution”; it is not the most direct consequence of this shortcut. The relevant consequence is that controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.
That outcome concerns the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”; it is not the most direct consequence of this shortcut. The relevant consequence is that controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.
Question 95
A city ticketing app shows two ReplicaSets during a staged rollout. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain. This pairing is justified because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
Incorrect Answers
This action and check address the distinct objective “Identify reconciliation work performed by kube-controller-manager” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
This action and check address the distinct objective “Use rollout status and undo to validate and recover a Deployment release” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
This action and check address the distinct objective “Apply GitOps reconciliation with a version-controlled desired state” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
Question 96
A medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
The situation is that a medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. This resolves the issue because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. To verify, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
Incorrect Answers
This option addresses the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, not the immediate requirement. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image. For the stated case, a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
This option addresses the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”, not the immediate requirement. A namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces. For the stated case, a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
This option addresses the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”, not the immediate requirement. Cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit. For the stated case, a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
Question 97
A medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
The situation is that a medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. It supports this action: Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. To confirm, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
Incorrect Answers
That statement explains the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” rather than the cause in this case. The deciding mechanism here is that a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
That statement explains the distinct objective “Use labels and selectors to connect resources predictably” rather than the cause in this case. The deciding mechanism here is that a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
That statement explains the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster” rather than the cause in this case. The deciding mechanism here is that a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
Question 98
A medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
The situation is that a medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain. This is the relevant test because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
Incorrect Answers
This check would help evaluate the distinct objective “Identify reconciliation work performed by kube-controller-manager”, but not the required result. For this case, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
This check would help evaluate the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, but not the required result. For this case, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
This check would help evaluate the distinct objective “Define secure release governance with staged approvals and policy verification”, but not the required result. For this case, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
Question 99
A medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. An engineer proposes: “Change labels on an unrelated Pod to manipulate replica counts without reviewing immutable selector expectations.” What adverse outcome would be most direct?
Explanation
Correct Answer
The situation is that a medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior. The shortcut creates this risk because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
Incorrect Answers
That outcome concerns the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”; it is not the most direct consequence of this shortcut. The relevant consequence is that controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.
That outcome concerns the distinct objective “Distinguish Deployment desired state from a manually created Pod”; it is not the most direct consequence of this shortcut. The relevant consequence is that controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.
That outcome concerns the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”; it is not the most direct consequence of this shortcut. The relevant consequence is that controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.
Question 100
A medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain. This pairing is justified because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
Incorrect Answers
This action and check address the distinct objective “Separate CI build verification from CD environment promotion” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
This action and check address the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
This action and check address the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 8 - 10 Questions (Last Reviewed 13-Nov-2026)
- Linux Foundation KCNA Practice Test 9 - 10 Questions (Last Reviewed 12-Nov-2026)
- Linux Foundation KCNA Practice Test 10 - 10 Questions (Last Reviewed 11-Nov-2026)
- Linux Foundation KCNA Practice Test 11 - 10 Questions (Last Reviewed 10-Nov-2026)
- Linux Foundation KCNA Practice Test 12 - 10 Questions (Last Reviewed 09-Nov-2026)