Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 35
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.
Question 341
A research cluster needs one log-collection agent on each worker. What technical action should the platform team take in this situation?
Explanation
Correct Answer
Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. This resolves the issue because a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count. To verify, add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
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, a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
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 DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
This option addresses the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, not the immediate requirement. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node. For the stated case, a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
Question 342
A research cluster needs one log-collection agent on each worker. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count. It supports this action: Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. To confirm, add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
Incorrect Answers
That statement explains the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” rather than the cause in this case. The deciding mechanism here is that a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
That statement explains the distinct objective “Understand readiness, liveness and startup probes as different signals” rather than the cause in this case. The deciding mechanism here is that a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
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 DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
Question 343
A research cluster needs one log-collection agent on each worker. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment. This is the relevant test because a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
Incorrect Answers
This check would help evaluate the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions”, but not the required result. For this case, add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
This check would help evaluate the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, but not the required result. For this case, add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
This check would help evaluate the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”, but not the required result. For this case, add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
Question 344
A research cluster needs one log-collection agent on each worker. The team suggests: “Use a Deployment with replicas=3 and assume it guarantees exactly one collector on each of three worker nodes.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The scheduler could place multiple replicas together, leaving a node without the intended local collector. The shortcut creates this risk because a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
Incorrect Answers
That outcome concerns the distinct objective “Distinguish preferred node affinity from required scheduling rules”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler could place multiple replicas together, leaving a node without the intended local collector.
That outcome concerns the distinct objective “Instrument services with OpenTelemetry context propagation”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler could place multiple replicas together, leaving a node without the intended local collector.
That outcome concerns the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler could place multiple replicas together, leaving a node without the intended local collector.
Question 345
A research cluster needs one log-collection agent on each worker. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Acceptance evidence: Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment. This pairing is justified because a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
Incorrect Answers
This action and check address the distinct objective “Use SLI and SLO measures to focus reliability objectives” instead of the stated acceptance requirement. The matching action is to run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
This action and check address the distinct objective “Use an immutable image digest for exact deployment provenance” instead of the stated acceptance requirement. The matching action is to run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
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 run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
Question 346
A retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
The situation is that a retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. This resolves the issue because a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count. To verify, add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
Incorrect Answers
This option addresses the distinct objective “Distinguish preferred node affinity from required scheduling rules”, not the immediate requirement. A required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary. For the stated case, a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
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, a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
This option addresses the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling”, not the immediate requirement. Multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer. For the stated case, a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
Question 347
A retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count. It supports this action: Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. To confirm, add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
Incorrect Answers
That statement explains the distinct objective “Understand Prometheus pull-based metrics collection and exporters” rather than the cause in this case. The deciding mechanism here is that a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
That statement explains the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability” rather than the cause in this case. The deciding mechanism here is that a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
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 a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
Question 348
A retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment. This is the relevant test because a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
Incorrect Answers
This check would help evaluate the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”, but not the required result. For this case, add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
This check would help evaluate the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”, but not the required result. For this case, add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
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, add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
Question 349
A retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. The change review contains this proposal: “Use a Deployment with replicas=3 and assume it guarantees exactly one collector on each of three worker nodes.” What risk matters most?
Explanation
Correct Answer
The situation is that a retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. The scheduler could place multiple replicas together, leaving a node without the intended local collector. The shortcut creates this risk because a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
Incorrect Answers
That outcome concerns the distinct objective “Investigate readiness failures separately from liveness-related restarts”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler could place multiple replicas together, leaving a node without the intended local collector.
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 the scheduler could place multiple replicas together, leaving a node without the intended local collector.
That outcome concerns the distinct objective “Use nodeSelector to place a workload on nodes with required labels”; it is not the most direct consequence of this shortcut. The relevant consequence is that the scheduler could place multiple replicas together, leaving a node without the intended local collector.
Question 350
A retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a retail company adds branch Kubernetes nodes and wants a node-local metrics exporter automatically installed. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Acceptance evidence: Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment. This pairing is justified because a DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
Incorrect Answers
This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
This action and check address the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” instead of the stated acceptance requirement. The matching action is to run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
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 run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Its confirming test is to add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 37 - 10 Questions (Last Reviewed 15-Oct-2026)