Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 27
Question 260
A university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker. This pairing is justified because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
Incorrect Answers
This action and check address the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” instead of the stated acceptance requirement. The matching action is to label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
This action and check address the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership” instead of the stated acceptance requirement. The matching action is to label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
This action and check address the distinct objective “Understand CSI drivers and volume attachment responsibilities” instead of the stated acceptance requirement. The matching action is to label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
Question 261
A tourism API prefers nearby nodes but should start elsewhere if a zone is temporarily full. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. This resolves the issue because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary. To verify, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
Incorrect Answers
This option addresses the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, not the immediate requirement. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. For the stated case, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
This option addresses the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”, not the immediate requirement. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior. For the stated case, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
This option addresses the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions”, not the immediate requirement. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. For the stated case, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
Question 262
A tourism API prefers nearby nodes but should start elsewhere if a zone is temporarily full. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
A required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary. It supports this action: Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. To confirm, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
Incorrect Answers
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 a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
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 a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
That statement explains the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” rather than the cause in this case. The deciding mechanism here is that a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
Question 263
A tourism API prefers nearby nodes but should start elsewhere if a zone is temporarily full. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy. This is the relevant test because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
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, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
This check would help evaluate the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”, but not the required result. For this case, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
This check would help evaluate the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, but not the required result. For this case, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
Question 264
A tourism API prefers nearby nodes but should start elsewhere if a zone is temporarily full. An engineer proposes: “Use a preferred affinity rule as a compliance guarantee that sensitive Pods can never land outside a region.” What adverse outcome would be most direct?
Explanation
Correct Answer
The scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory. The shortcut creates this risk because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
Incorrect Answers
That outcome concerns the distinct objective “Understand taints and tolerations as repulsion controls”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.
That outcome concerns the distinct objective “Use annotations for tool metadata rather than workload selection”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.
That outcome concerns the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.
Question 265
A tourism API prefers nearby nodes but should start elsewhere if a zone is temporarily full. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
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 “Spread replicas across failure domains with topologySpreadConstraints” 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 “Use nodeSelector to place a workload on nodes with required labels” 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 cloud-native portability and immutable infrastructure principles pragmatically” 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 266
An insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
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. This resolves the issue because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary. To verify, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
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, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
This option addresses the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, not the immediate requirement. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. For the stated case, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
This option addresses the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, not the immediate requirement. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. For the stated case, a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
Question 267
An insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
The situation is that an insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. A required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary. It supports this action: Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. To confirm, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
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 a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
That statement explains the distinct objective “Distinguish etcd persistence from running workload data” rather than the cause in this case. The deciding mechanism here is that a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
That statement explains the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” rather than the cause in this case. The deciding mechanism here is that a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
Question 268
An insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
The situation is that an insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy. This is the relevant test because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
Incorrect Answers
This check would help evaluate the distinct objective “Explain metrics, logs and traces as complementary observability signals”, but not the required result. For this case, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
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, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
This check would help evaluate the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, but not the required result. For this case, test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
Question 269
An insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. An engineer proposes: “Use a preferred affinity rule as a compliance guarantee that sensitive Pods can never land outside a region.” What adverse outcome would be most direct?
Explanation
Correct Answer
The situation is that an insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. The scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory. The shortcut creates this risk because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.
Incorrect Answers
That outcome concerns the distinct objective “Understand open standards and vendor-neutral community collaboration”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.
That outcome concerns the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.
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 legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 25 - 10 Questions (Last Reviewed 27-Oct-2026)
- 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)