Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 34
Question 330
A municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Acceptance evidence: Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule. This pairing is justified because under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.
Incorrect Answers
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 apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.
This action and check address the distinct objective “Investigate readiness failures separately from liveness-related restarts” instead of the stated acceptance requirement. The matching action is to apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.
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 apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.
Question 331
A library's report generator is repeatedly OOMKilled while its Pod remains scheduled on the same node. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. This resolves the issue because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. To verify, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
Incorrect Answers
This option addresses the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”, not the immediate requirement. Service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure. For the stated case, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
This option addresses the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, not the immediate requirement. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. For the stated case, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
This option addresses the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”, not the immediate requirement. The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. For the stated case, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
Question 332
A library's report generator is repeatedly OOMKilled while its Pod remains scheduled on the same node. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. It supports this action: Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. To confirm, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
Incorrect Answers
That statement explains the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” rather than the cause in this case. The deciding mechanism here is that CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
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 CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
That statement explains the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” rather than the cause in this case. The deciding mechanism here is that CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
Question 333
A library's report generator is repeatedly OOMKilled while its Pod remains scheduled on the same node. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod. This is the relevant test because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
Incorrect Answers
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, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
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, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
This check would help evaluate the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance”, but not the required result. For this case, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
Question 334
A library's report generator is repeatedly OOMKilled while its Pod remains scheduled on the same node. An engineer proposes: “Treat an OOMKilled container as a DNS connectivity problem and change Service names instead of resource settings.” What adverse outcome would be most direct?
Explanation
Correct Answer
A workload continues crashing because the root cause is memory exhaustion, not name resolution. The shortcut creates this risk because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
Incorrect Answers
That outcome concerns the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload continues crashing because the root cause is memory exhaustion, not name resolution.
That outcome concerns the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload continues crashing because the root cause is memory exhaustion, not name resolution.
That outcome concerns the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload continues crashing because the root cause is memory exhaustion, not name resolution.
Question 335
A library's report generator is repeatedly OOMKilled while its Pod remains scheduled on the same node. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Acceptance evidence: Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod. This pairing is justified because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
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 review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
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 review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
This action and check address the distinct objective “Identify reconciliation work performed by kube-controller-manager” instead of the stated acceptance requirement. The matching action is to review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
Question 336
A factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. This resolves the issue because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. To verify, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
Incorrect Answers
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, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
This option addresses the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”, not the immediate requirement. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support. For the stated case, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
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, CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
Question 337
A factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. It supports this action: Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. To confirm, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
Incorrect Answers
That statement explains the distinct objective “Use nodeSelector to place a workload on nodes with required labels” rather than the cause in this case. The deciding mechanism here is that CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
That statement explains the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” rather than the cause in this case. The deciding mechanism here is that CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
That statement explains the distinct objective “Use kubectl get and describe for distinct inspection needs” rather than the cause in this case. The deciding mechanism here is that CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
Question 338
A factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod. This is the relevant test because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
Incorrect Answers
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, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
This check would help evaluate the distinct objective “Distinguish etcd persistence from running workload data”, but not the required result. For this case, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
This check would help evaluate the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”, but not the required result. For this case, create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
Question 339
A factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. The team suggests: “Treat an OOMKilled container as a DNS connectivity problem and change Service names instead of resource settings.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. A workload continues crashing because the root cause is memory exhaustion, not name resolution. The shortcut creates this risk because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
Incorrect Answers
The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. That outcome concerns the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload continues crashing because the root cause is memory exhaustion, not name resolution.
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 a workload continues crashing because the root cause is memory exhaustion, not name resolution.
That outcome concerns the distinct objective “Externalize application configuration from an image while protecting secrets”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload continues crashing because the root cause is memory exhaustion, not name resolution.
Question 340
A factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a factory sensor aggregator runs slowly under CPU throttling despite successful Pod placement. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Acceptance evidence: Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod. This pairing is justified because CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on 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 review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test 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 review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
This action and check address the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” instead of the stated acceptance requirement. The matching action is to review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Its confirming test is to create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 35 - 10 Questions (Last Reviewed 17-Oct-2026)
- Linux Foundation KCNA Practice Test 36 - 10 Questions (Last Reviewed 16-Oct-2026)