Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 25
Question 240
A financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Acceptance evidence: With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied. This pairing is justified because authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.
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 grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Its confirming test is to with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
This action and check address the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” instead of the stated acceptance requirement. The matching action is to grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Its confirming test is to with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
The situation is that a financial cooperative's on-call staff must inspect Events without modifying cluster-wide security settings. This action and check address the distinct objective “Use rollout status and undo to validate and recover a Deployment release” instead of the stated acceptance requirement. The matching action is to grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities. Its confirming test is to with restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
Question 241
A hospital dashboard Pod requests more memory than any eligible node can reserve. What technical action should the platform team take in this situation?
Explanation
Correct Answer
Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. This resolves the issue because the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests. To verify, set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
Incorrect Answers
This option addresses the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, not the immediate requirement. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it. For the stated case, the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
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, the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
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, the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
Question 242
A hospital dashboard Pod requests more memory than any eligible node can reserve. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests. It supports this action: Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. To confirm, set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
Incorrect Answers
That statement explains the distinct objective “Understand taints and tolerations as repulsion controls” rather than the cause in this case. The deciding mechanism here is that the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
That statement explains the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” rather than the cause in this case. The deciding mechanism here is that the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
That statement explains the distinct objective “Configure Deployment rolling updates with availability safeguards” rather than the cause in this case. The deciding mechanism here is that the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
Question 243
A hospital dashboard Pod requests more memory than any eligible node can reserve. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
Set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it. This is the relevant test because the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
Incorrect Answers
This check would help evaluate the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, but not the required result. For this case, set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
This check would help evaluate the distinct objective “Distinguish a container image from a running container and its writable layer”, but not the required result. For this case, set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
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, set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
Question 244
A hospital dashboard Pod requests more memory than any eligible node can reserve. The team suggests: “Increase a Pod's limits only while leaving its requests unrealistic, expecting this to make node placement succeed.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The Pod remains unschedulable because requested capacity and node feasibility did not change. The shortcut creates this risk because the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
Incorrect Answers
That outcome concerns the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Pod remains unschedulable because requested capacity and node feasibility did not change.
That outcome concerns the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Pod remains unschedulable because requested capacity and node feasibility did not change.
That outcome concerns the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Pod remains unschedulable because requested capacity and node feasibility did not change.
Question 245
A hospital dashboard Pod requests more memory than any eligible node can reserve. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
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 “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” 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 “Use kubectl get and describe for distinct inspection needs” 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 “Spread replicas across failure domains with topologySpreadConstraints” 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 246
A small university cluster has spare average CPU but a large requested burst prevents one job from scheduling. Which engineering approach is the most appropriate for this cloud-native 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. This resolves the issue because the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests. To verify, set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
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 evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
This option addresses the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”, not the immediate requirement. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy. For the stated case, the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
This option addresses the distinct objective “Use nodeSelector to place a workload on nodes with required labels”, not the immediate requirement. The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. For the stated case, the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
Question 247
A small university cluster has spare average CPU but a large requested burst prevents one job from scheduling. What infrastructure principle makes the correct treatment effective?
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. The scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests. It supports this action: Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. To confirm, set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
Incorrect Answers
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 the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
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 the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
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 evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
Question 248
A small university cluster has spare average CPU but a large requested burst prevents one job from scheduling. What verification result would most convincingly distinguish a working solution from a claim?
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 an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it. This is the relevant test because the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
Incorrect Answers
This check would help evaluate the distinct objective “Understand taints and tolerations as repulsion controls”, but not the required result. For this case, set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
This check would help evaluate the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, but not the required result. For this case, set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
This check would help evaluate the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”, but not the required result. For this case, set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
Question 249
A small university cluster has spare average CPU but a large requested burst prevents one job from scheduling. The change review contains this proposal: “Increase a Pod's limits only while leaving its requests unrealistic, expecting this to make node placement succeed.” What risk matters most?
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. The Pod remains unschedulable because requested capacity and node feasibility did not change. The shortcut creates this risk because the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
Incorrect Answers
That outcome concerns the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Pod remains unschedulable because requested capacity and node feasibility did not change.
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 the Pod remains unschedulable because requested capacity and node feasibility did not change.
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 the Pod remains unschedulable because requested capacity and node feasibility did not change.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 23 - 10 Questions (Last Reviewed 29-Oct-2026)
- 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)