Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 38
Question 370
A bank architect wants to explain why container CPU budgets and process visibility are configured separately. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
The situation is that a bank architect wants to explain why container CPU budgets and process visibility are configured separately. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Acceptance evidence: In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior. This pairing is justified because linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.
Incorrect Answers
This action and check address the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence” instead of the stated acceptance requirement. The matching action is to use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Its confirming test is to in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.
This action and check address the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” instead of the stated acceptance requirement. The matching action is to use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Its confirming test is to in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.
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 use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Its confirming test is to in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.
Question 371
A healthcare portal must deploy exactly the container tested by its validation team. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
Pin validated production images by registry digest and promote the same signed artifact across environments. This resolves the issue because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. To verify, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
Incorrect Answers
This option addresses the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion”, not the immediate requirement. A PV reclaim policy controls how underlying storage is treated after claim release; deleting the Pod and deleting the PVC are distinct events with different effects. For the stated case, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
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, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
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, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
Question 372
A healthcare portal must deploy exactly the container tested by its validation team. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. It supports this action: Pin validated production images by registry digest and promote the same signed artifact across environments. To confirm, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
Incorrect Answers
That statement explains the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” rather than the cause in this case. The deciding mechanism here is that tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
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 tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
That statement explains the distinct objective “Run images with least-privilege runtime security contexts” rather than the cause in this case. The deciding mechanism here is that tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
Question 373
A healthcare portal must deploy exactly the container tested by its validation team. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec. This is the relevant test because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
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, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
This check would help evaluate the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”, but not the required result. For this case, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
This check would help evaluate the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, but not the required result. For this case, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
Question 374
A healthcare portal must deploy exactly the container tested by its validation team. A shortcut is proposed: “Use latest for every critical Pod and assume it always refers to the tested build from last week.” Which technical consequence follows most closely?
Explanation
Correct Answer
A later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback. The shortcut creates this risk because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
Incorrect Answers
That outcome concerns the distinct objective “Understand readiness, liveness and startup probes as different signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that a later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.
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 later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.
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 later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.
Question 375
A healthcare portal must deploy exactly the container tested by its validation team. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
Pin validated production images by registry digest and promote the same signed artifact across environments. Acceptance evidence: Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec. This pairing is justified because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
Incorrect Answers
This action and check address the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling” instead of the stated acceptance requirement. The matching action is to pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
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 pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
This action and check address the distinct objective “Separate kube-scheduler decisions from kubelet execution” instead of the stated acceptance requirement. The matching action is to pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
Question 376
A school district uses an image tag reused by many builds and needs provenance during incident response. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
The situation is that a school district uses an image tag reused by many builds and needs provenance during incident response. Pin validated production images by registry digest and promote the same signed artifact across environments. This resolves the issue because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. To verify, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
Incorrect Answers
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, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
This option addresses the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”, not the immediate requirement. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. For the stated case, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
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, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
Question 377
A school district uses an image tag reused by many builds and needs provenance during incident response. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a school district uses an image tag reused by many builds and needs provenance during incident response. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. It supports this action: Pin validated production images by registry digest and promote the same signed artifact across environments. To confirm, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
Incorrect Answers
That statement explains the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point” rather than the cause in this case. The deciding mechanism here is that tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
That statement explains the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence” rather than the cause in this case. The deciding mechanism here is that tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
That statement explains the distinct objective “Distinguish service mesh traffic management from external ingress routing” rather than the cause in this case. The deciding mechanism here is that tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
Question 378
A school district uses an image tag reused by many builds and needs provenance during incident response. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a school district uses an image tag reused by many builds and needs provenance during incident response. Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec. This is the relevant test because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
Incorrect Answers
This check would help evaluate the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, but not the required result. For this case, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
This check would help evaluate the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”, but not the required result. For this case, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
This check would help evaluate the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”, but not the required result. For this case, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
Question 379
A school district uses an image tag reused by many builds and needs provenance during incident response. The change review contains this proposal: “Use latest for every critical Pod and assume it always refers to the tested build from last week.” What risk matters most?
Explanation
Correct Answer
The situation is that a school district uses an image tag reused by many builds and needs provenance during incident response. A later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback. The shortcut creates this risk because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
Incorrect Answers
That outcome concerns the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”; it is not the most direct consequence of this shortcut. The relevant consequence is that a later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.
That outcome concerns the distinct objective “Define secure release governance with staged approvals and policy verification”; it is not the most direct consequence of this shortcut. The relevant consequence is that a later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.
That outcome concerns the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”; it is not the most direct consequence of this shortcut. The relevant consequence is that a later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.
Question 380
A school district uses an image tag reused by many builds and needs provenance during incident response. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a school district uses an image tag reused by many builds and needs provenance during incident response. Pin validated production images by registry digest and promote the same signed artifact across environments. Acceptance evidence: Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec. This pairing is justified because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
Incorrect Answers
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 pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
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 pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
This action and check address the distinct objective “Understand CNCF project maturity stages without equating them to security approval” instead of the stated acceptance requirement. The matching action is to pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 38 - 10 Questions (Last Reviewed 14-Oct-2026)
- Linux Foundation KCNA Practice Test 39 - 10 Questions (Last Reviewed 13-Oct-2026)
- Linux Foundation KCNA Practice Test 40 - 10 Questions (Last Reviewed 12-Oct-2026)