Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 28
Question 270
An insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that an insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Acceptance evidence: Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy. This pairing is justified because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
Incorrect Answers
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 use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
This action and check address the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” instead of the stated acceptance requirement. The matching action is to use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
This action and check address the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior” instead of the stated acceptance requirement. The matching action is to use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
Question 271
A community clinic wants identical front-end Pods distributed across at least two workers. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. This resolves the issue because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. To verify, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
Incorrect Answers
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, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
This option addresses the distinct objective “Explain desired state versus observed status in Kubernetes objects”, not the immediate requirement. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. For the stated case, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
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, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
Question 272
A community clinic wants identical front-end Pods distributed across at least two workers. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. It supports this action: Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. To confirm, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
Incorrect Answers
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 pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
That statement explains the distinct objective “Correlate application rollout revisions with error spikes” rather than the cause in this case. The deciding mechanism here is that pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
That statement explains the distinct objective “Explain the container runtime interface without conflating it with the control plane” rather than the cause in this case. The deciding mechanism here is that pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
Question 273
A community clinic wants identical front-end Pods distributed across at least two workers. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers. This is the relevant test because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
Incorrect Answers
This check would help evaluate the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, but not the required result. For this case, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
This check would help evaluate the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, but not the required result. For this case, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
This check would help evaluate the distinct objective “Distinguish Deployment desired state from a manually created Pod”, but not the required result. For this case, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
Question 274
A community clinic wants identical front-end Pods distributed across at least two workers. An engineer proposes: “Place all high-availability replicas on one worker and assume the ReplicaSet count alone protects against node loss.” What adverse outcome would be most direct?
Explanation
Correct Answer
A single node failure can take down all replicas despite a desired count greater than one. The shortcut creates this risk because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
Incorrect Answers
That outcome concerns the distinct objective “Recognize the kubelet role in local Pod lifecycle management”; it is not the most direct consequence of this shortcut. The relevant consequence is that a single node failure can take down all replicas despite a desired count greater than one.
That outcome concerns the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions”; it is not the most direct consequence of this shortcut. The relevant consequence is that a single node failure can take down all replicas despite a desired count greater than one.
That outcome concerns the distinct objective “Use image provenance and policy controls without trusting mutable tags”; it is not the most direct consequence of this shortcut. The relevant consequence is that a single node failure can take down all replicas despite a desired count greater than one.
Question 275
A community clinic wants identical front-end Pods distributed across at least two workers. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Acceptance evidence: Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers. This pairing is justified because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
Incorrect Answers
This action and check address the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
This action and check address the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
This action and check address the distinct objective “Explain the container runtime interface without conflating it with the control plane” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
Question 276
A college live-stream service needs to avoid putting every replica on the same machine during exams. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. This resolves the issue because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. To verify, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
Incorrect Answers
This option addresses the distinct objective “Use Pods as the shared network and storage execution unit”, not the immediate requirement. Containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit. For the stated case, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
This option addresses the distinct objective “Use image provenance and policy controls without trusting mutable tags”, not the immediate requirement. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. For the stated case, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. 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, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
Question 277
A college live-stream service needs to avoid putting every replica on the same machine during exams. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. It supports this action: Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. To confirm, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
Incorrect Answers
That statement explains the distinct objective “Diagnose cluster DNS separately from Pod network reachability” rather than the cause in this case. The deciding mechanism here is that pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
That statement explains the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” rather than the cause in this case. The deciding mechanism here is that pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
That statement explains the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” rather than the cause in this case. The deciding mechanism here is that pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
Question 278
A college live-stream service needs to avoid putting every replica on the same machine during exams. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers. This is the relevant test because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
Incorrect Answers
This check would help evaluate the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, but not the required result. For this case, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
This check would help evaluate the distinct objective “Use nodeSelector to place a workload on nodes with required labels”, but not the required result. For this case, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
This check would help evaluate the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, but not the required result. For this case, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
Question 279
A college live-stream service needs to avoid putting every replica on the same machine during exams. The change review contains this proposal: “Place all high-availability replicas on one worker and assume the ReplicaSet count alone protects against node loss.” What risk matters most?
Explanation
Correct Answer
The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. A single node failure can take down all replicas despite a desired count greater than one. The shortcut creates this risk because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
Incorrect Answers
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 a single node failure can take down all replicas despite a desired count greater than one.
That outcome concerns the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”; it is not the most direct consequence of this shortcut. The relevant consequence is that a single node failure can take down all replicas despite a desired count greater than one.
That outcome concerns the distinct objective “Distinguish ClusterRoles from Roles and binding scope”; it is not the most direct consequence of this shortcut. The relevant consequence is that a single node failure can take down all replicas despite a desired count greater than one.
Question 280
A college live-stream service needs to avoid putting every replica on the same machine during exams. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Acceptance evidence: Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers. This pairing is justified because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
Incorrect Answers
This action and check address the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
This action and check address the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
This action and check address the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 26 - 10 Questions (Last Reviewed 26-Oct-2026)
- Linux Foundation KCNA Practice Test 27 - 10 Questions (Last Reviewed 25-Oct-2026)
- Linux Foundation KCNA Practice Test 28 - 10 Questions (Last Reviewed 24-Oct-2026)
- 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)