Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 26
Question 250
A small university cluster has spare average CPU but a large requested burst prevents one job from scheduling. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a small university cluster has spare average CPU but a large requested burst prevents one job from scheduling. Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. Acceptance evidence: Set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it. This pairing is justified because the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
Incorrect Answers
This action and check address the distinct objective “Understand taints and tolerations as repulsion controls” instead of the stated acceptance requirement. The matching action is to set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. Its confirming test is to set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
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 set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. Its confirming test is to set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
This action and check address the distinct objective “Diagnose cluster DNS separately from Pod network reachability” instead of the stated acceptance requirement. The matching action is to set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. Its confirming test is to set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
Question 251
A media service needs to run on the small set of verified SSD-backed workers. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. This resolves the issue because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. To verify, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
Incorrect Answers
This option addresses the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”, not the immediate requirement. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. For the stated case, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
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, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
This option addresses the distinct objective “Run images with least-privilege runtime security contexts”, not the immediate requirement. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised. For the stated case, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
Question 252
A media service needs to run on the small set of verified SSD-backed workers. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. It supports this action: Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. To confirm, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
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 the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
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 the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
That statement explains the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” rather than the cause in this case. The deciding mechanism here is that the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
Question 253
A media service needs to run on the small set of verified SSD-backed workers. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker. This is the relevant test 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 check would help evaluate the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, but not the required result. For this case, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
This check would help evaluate the distinct objective “Use Pods as the shared network and storage execution unit”, but not the required result. For this case, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
This check would help evaluate the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”, but not the required result. For this case, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
Question 254
A media service needs to run on the small set of verified SSD-backed workers. The change review contains this proposal: “Put disk=ssd on a node metadata record that has no SSD and assume labeling physically upgrades the disk.” What risk matters most?
Explanation
Correct Answer
A scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory. The shortcut creates this risk because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
Incorrect Answers
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 scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.
That outcome concerns the distinct objective “Distinguish etcd persistence from running workload data”; it is not the most direct consequence of this shortcut. The relevant consequence is that a scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.
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 scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.
Question 255
A media service needs to run on the small set of verified SSD-backed workers. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
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 “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” 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 “Run images with least-privilege runtime security contexts” 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 “Select DaemonSet for node-local agents rather than Deployment replica counts” 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 256
A university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. Which engineering approach is the most appropriate for this cloud-native 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. This resolves the issue because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. To verify, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
Incorrect Answers
This option addresses the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, not the immediate requirement. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. For the stated case, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
This option addresses the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, not the immediate requirement. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable. For the stated case, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
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, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
Question 257
A university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. What infrastructure principle makes the correct treatment effective?
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. The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. It supports this action: Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. To confirm, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
Incorrect Answers
That statement explains the distinct objective “Understand ports, targetPort and protocol mapping in a Service” rather than the cause in this case. The deciding mechanism here is that the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. That statement explains the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” rather than the cause in this case. The deciding mechanism here is that the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
That statement explains the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” rather than the cause in this case. The deciding mechanism here is that the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
Question 258
A university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. What verification result would most convincingly distinguish a working solution from a claim?
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 one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker. This is the relevant test because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
Incorrect Answers
The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. This check would help evaluate the distinct objective “Use Pods as the shared network and storage execution unit”, but not the required result. For this case, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
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, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
This check would help evaluate the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, but not the required result. For this case, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
Question 259
A university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. The change review contains this proposal: “Put disk=ssd on a node metadata record that has no SSD and assume labeling physically upgrades the disk.” What risk matters most?
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. A scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory. The shortcut creates this risk because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
Incorrect Answers
The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. 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 scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.
That outcome concerns the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”; it is not the most direct consequence of this shortcut. The relevant consequence is that a scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.
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 a scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 24 - 10 Questions (Last Reviewed 28-Oct-2026)
- 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)