Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 31
Question 300
A hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. Taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. Acceptance evidence: Taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration. This pairing is justified because a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.
Incorrect Answers
This action and check address the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” instead of the stated acceptance requirement. The matching action is to taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. Its confirming test is to taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.
This action and check address the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” instead of the stated acceptance requirement. The matching action is to taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. Its confirming test is to taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.
This action and check address the distinct objective “Distinguish preferred node affinity from required scheduling rules” instead of the stated acceptance requirement. The matching action is to taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. Its confirming test is to taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.
Question 301
A bank's Kubernetes workers require kernel updates without disrupting a high-availability checkout API. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. This resolves the issue because cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit. To verify, observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
Incorrect Answers
This option addresses the distinct objective “Use annotations for tool metadata rather than workload selection”, not the immediate requirement. Labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control. For the stated case, cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
This option addresses the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, not the immediate requirement. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. For the stated case, cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
This option addresses the distinct objective “Investigate readiness failures separately from liveness-related restarts”, not the immediate requirement. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ. For the stated case, cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
Question 302
A bank's Kubernetes workers require kernel updates without disrupting a high-availability checkout API. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
Cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit. It supports this action: Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. To confirm, observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
Incorrect Answers
That statement explains the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” rather than the cause in this case. The deciding mechanism here is that cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
That statement explains the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes” rather than the cause in this case. The deciding mechanism here is that cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
That statement explains the distinct objective “Use rollout status and undo to validate and recover a Deployment release” rather than the cause in this case. The deciding mechanism here is that cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
Question 303
A bank's Kubernetes workers require kernel updates without disrupting a high-availability checkout API. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility. This is the relevant test because cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
Incorrect Answers
This check would help evaluate the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, but not the required result. For this case, observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
This check would help evaluate the distinct objective “Distinguish preferred node affinity from required scheduling rules”, but not the required result. For this case, observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
This check would help evaluate the distinct objective “Understand readiness, liveness and startup probes as different signals”, but not the required result. For this case, observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
Question 304
A bank's Kubernetes workers require kernel updates without disrupting a high-availability checkout API. The change review contains this proposal: “Power off a node with the last application replica without checking disruption budgets or replacement capacity.” What risk matters most?
Explanation
Correct Answer
The planned maintenance causes avoidable downtime because no safe application replica remains available. The shortcut creates this risk because cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
Incorrect Answers
That outcome concerns the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”; it is not the most direct consequence of this shortcut. The relevant consequence is that the planned maintenance causes avoidable downtime because no safe application replica remains available.
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 the planned maintenance causes avoidable downtime because no safe application replica remains available.
That outcome concerns the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”; it is not the most direct consequence of this shortcut. The relevant consequence is that the planned maintenance causes avoidable downtime because no safe application replica remains available.
Question 305
A bank's Kubernetes workers require kernel updates without disrupting a high-availability checkout API. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Acceptance evidence: Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility. This pairing is justified because cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
Incorrect Answers
This action and check address the distinct objective “Understand Prometheus pull-based metrics collection and exporters” instead of the stated acceptance requirement. The matching action is to cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Its confirming test is to observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
This action and check address the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” instead of the stated acceptance requirement. The matching action is to cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Its confirming test is to observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
This action and check address the distinct objective “Distinguish preferred node affinity from required scheduling rules” instead of the stated acceptance requirement. The matching action is to cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Its confirming test is to observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
Question 306
A training cluster operator must drain one node while several DaemonSet and StatefulSet Pods exist. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
The situation is that a training cluster operator must drain one node while several DaemonSet and StatefulSet Pods exist. Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. This resolves the issue because cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit. To verify, observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
Incorrect Answers
This option addresses the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”, not the immediate requirement. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. For the stated case, cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
This option addresses the distinct objective “Understand taints and tolerations as repulsion controls”, not the immediate requirement. A NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node. For the stated case, cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
This option addresses the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, not the immediate requirement. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. For the stated case, cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
Question 307
A training cluster operator must drain one node while several DaemonSet and StatefulSet Pods exist. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
The situation is that a training cluster operator must drain one node while several DaemonSet and StatefulSet Pods exist. Cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit. It supports this action: Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. To confirm, observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
Incorrect Answers
That statement explains the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” rather than the cause in this case. The deciding mechanism here is that cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
That statement explains the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects” rather than the cause in this case. The deciding mechanism here is that cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
That statement explains the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance” rather than the cause in this case. The deciding mechanism here is that cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
Question 308
A training cluster operator must drain one node while several DaemonSet and StatefulSet Pods exist. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
The situation is that a training cluster operator must drain one node while several DaemonSet and StatefulSet Pods exist. Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility. This is the relevant test because cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
Incorrect Answers
This check would help evaluate the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, but not the required result. For this case, observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
This check would help evaluate the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, but not the required result. For this case, observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
This check would help evaluate the distinct objective “Understand open standards and vendor-neutral community collaboration”, but not the required result. For this case, observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
Question 309
A training cluster operator must drain one node while several DaemonSet and StatefulSet Pods exist. An engineer proposes: “Power off a node with the last application replica without checking disruption budgets or replacement capacity.” What adverse outcome would be most direct?
Explanation
Correct Answer
The situation is that a training cluster operator must drain one node while several DaemonSet and StatefulSet Pods exist. The planned maintenance causes avoidable downtime because no safe application replica remains available. The shortcut creates this risk because cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
Incorrect Answers
That outcome concerns the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”; it is not the most direct consequence of this shortcut. The relevant consequence is that the planned maintenance causes avoidable downtime because no safe application replica remains available.
That outcome concerns the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”; it is not the most direct consequence of this shortcut. The relevant consequence is that the planned maintenance causes avoidable downtime because no safe application replica remains available.
The situation is that a training cluster operator must drain one node while several DaemonSet and StatefulSet Pods exist. That outcome concerns the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”; it is not the most direct consequence of this shortcut. The relevant consequence is that the planned maintenance causes avoidable downtime because no safe application replica remains available.
Question 310
A training cluster operator must drain one node while several DaemonSet and StatefulSet Pods exist. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a training cluster operator must drain one node while several DaemonSet and StatefulSet Pods exist. Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Acceptance evidence: Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility. This pairing is justified because cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit.
Incorrect Answers
This action and check address the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts” instead of the stated acceptance requirement. The matching action is to cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Its confirming test is to observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
This action and check address the distinct objective “Separate kube-scheduler decisions from kubelet execution” instead of the stated acceptance requirement. The matching action is to cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Its confirming test is to observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
This action and check address the distinct objective “Use image provenance and policy controls without trusting mutable tags” instead of the stated acceptance requirement. The matching action is to cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Its confirming test is to observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 29 - 10 Questions (Last Reviewed 23-Oct-2026)
- Linux Foundation KCNA Practice Test 30 - 10 Questions (Last Reviewed 22-Oct-2026)
- Linux Foundation KCNA Practice Test 31 - 10 Questions (Last Reviewed 21-Oct-2026)
- Linux Foundation KCNA Practice Test 32 - 10 Questions (Last Reviewed 20-Oct-2026)
- Linux Foundation KCNA Practice Test 33 - 10 Questions (Last Reviewed 19-Oct-2026)