Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 32
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.
Question 311
A payments API should not place every copy in one availability zone. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. This resolves the issue because topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable. To verify, deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
Incorrect Answers
This option addresses the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”, not the immediate requirement. Kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. For the stated case, topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
This option addresses the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”, not the immediate requirement. HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself. For the stated case, topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
This option addresses the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”, not the immediate requirement. A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count. For the stated case, topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
Question 312
A payments API should not place every copy in one availability zone. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable. It supports this action: Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. To confirm, deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
Incorrect Answers
That statement explains the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” rather than the cause in this case. The deciding mechanism here is that topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
That statement explains the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” rather than the cause in this case. The deciding mechanism here is that topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
That statement explains the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts” rather than the cause in this case. The deciding mechanism here is that topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
Question 313
A payments API should not place every copy in one availability zone. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod. This is the relevant test because topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
Incorrect Answers
This check would help evaluate the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, but not the required result. For this case, deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
This check would help evaluate the distinct objective “Separate kube-scheduler decisions from kubelet execution”, but not the required result. For this case, deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
This check would help evaluate the distinct objective “Correlate application rollout revisions with error spikes”, but not the required result. For this case, deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
Question 314
A payments API should not place every copy in one availability zone. A shortcut is proposed: “Set maxSkew without checking matching labels and assume it automatically distributes every workload in the cluster.” Which technical consequence follows most closely?
Explanation
Correct Answer
The scheduler may evaluate an unintended Pod group or fail to spread the intended replicas. The shortcut creates this risk because topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
Incorrect Answers
That outcome concerns the distinct objective “Use kubectl get and describe for distinct inspection needs”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may evaluate an unintended Pod group or fail to spread the intended replicas.
That outcome concerns the distinct objective “Explain metrics, logs and traces as complementary observability signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may evaluate an unintended Pod group or fail to spread the intended replicas.
That outcome concerns the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may evaluate an unintended Pod group or fail to spread the intended replicas.
Question 315
A payments API should not place every copy in one availability zone. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Acceptance evidence: Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod. This pairing is justified because topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
Incorrect Answers
This action and check address the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend” instead of the stated acceptance requirement. The matching action is to define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Its confirming test is to deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
This action and check address the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” instead of the stated acceptance requirement. The matching action is to define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Its confirming test is to deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
This action and check address the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes” instead of the stated acceptance requirement. The matching action is to define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Its confirming test is to deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
Question 316
A public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. This resolves the issue because topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable. To verify, deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
Incorrect Answers
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, topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
This option addresses the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”, not the immediate requirement. Kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events. For the stated case, topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
This option addresses the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, not the immediate requirement. EmptyDir is initialized for a Pod and its contents can be shared among containers but do not survive the Pod's removal. For the stated case, topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
Question 317
A public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable. It supports this action: Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. To confirm, deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
Incorrect Answers
That statement explains the distinct objective “Distinguish preferred node affinity from required scheduling rules” rather than the cause in this case. The deciding mechanism here is that topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
That statement explains the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” rather than the cause in this case. The deciding mechanism here is that topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
That statement explains the distinct objective “Separate kube-scheduler decisions from kubelet execution” rather than the cause in this case. The deciding mechanism here is that topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
Question 318
A public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod. This is the relevant test because topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
Incorrect Answers
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, deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
This check would help evaluate the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, but not the required result. For this case, deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
The situation is that a public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. This check would help evaluate the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, but not the required result. For this case, deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
Question 319
A public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. The team suggests: “Set maxSkew without checking matching labels and assume it automatically distributes every workload in the cluster.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. The scheduler may evaluate an unintended Pod group or fail to spread the intended replicas. The shortcut creates this risk because topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
Incorrect Answers
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 scheduler may evaluate an unintended Pod group or fail to spread the intended replicas.
That outcome concerns the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may evaluate an unintended Pod group or fail to spread the intended replicas.
That outcome concerns the distinct objective “Use Pods as the shared network and storage execution unit”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may evaluate an unintended Pod group or fail to spread the intended replicas.
Question 320
A public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Acceptance evidence: Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod. This pairing is justified because topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
Incorrect Answers
This action and check address the distinct objective “Use Pods as the shared network and storage execution unit” instead of the stated acceptance requirement. The matching action is to define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Its confirming test is to deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
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 define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Its confirming test is to deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
This action and check address the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” instead of the stated acceptance requirement. The matching action is to define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Its confirming test is to deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 34 - 10 Questions (Last Reviewed 18-Oct-2026)