Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 40
Question 390
A financial service team sees ImagePullBackOff because its namespace lacks valid image pull credentials. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a financial service team sees ImagePullBackOff because its namespace lacks valid image pull credentials. Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Acceptance evidence: Deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token. This pairing is justified because image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
Incorrect Answers
This action and check address the distinct objective “Use metrics, logs and traces together when investigating cross-service latency” instead of the stated acceptance requirement. The matching action is to use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Its confirming test is to deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
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 use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Its confirming test is to deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
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 use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Its confirming test is to deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
Question 391
A small museum's new image runs a batch script and exits instead of serving HTTP requests. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Inspect image default command and Pod command or args settings to determine what executable starts in the container. This resolves the issue because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. To verify, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
Incorrect Answers
This option addresses the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, not the immediate requirement. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. For the stated case, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
This option addresses the distinct objective “Use kubectl get and describe for distinct inspection needs”, not the immediate requirement. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. For the stated case, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
This option addresses the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, not the immediate requirement. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. For the stated case, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
Question 392
A small museum's new image runs a batch script and exits instead of serving HTTP requests. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. It supports this action: Inspect image default command and Pod command or args settings to determine what executable starts in the container. To confirm, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
Incorrect Answers
That statement explains the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes” rather than the cause in this case. The deciding mechanism here is that the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
That statement explains the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs” rather than the cause in this case. The deciding mechanism here is that the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
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 the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
Question 393
A small museum's new image runs a batch script and exits instead of serving HTTP requests. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting. This is the relevant test because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
Incorrect Answers
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, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
This check would help evaluate the distinct objective “Distinguish preferred node affinity from required scheduling rules”, but not the required result. For this case, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
This check would help evaluate the distinct objective “Explain metrics, logs and traces as complementary observability signals”, but not the required result. For this case, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
Question 394
A small museum's new image runs a batch script and exits instead of serving HTTP requests. An engineer proposes: “Increase ReplicaSet count to fix a container that immediately exits because its startup arguments are invalid.” What adverse outcome would be most direct?
Explanation
Correct Answer
More replicas fail the same way because the process configuration, not desired replica count, caused the exit. The shortcut creates this risk because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
Incorrect Answers
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 more replicas fail the same way because the process configuration, not desired replica count, caused the exit.
That outcome concerns the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”; it is not the most direct consequence of this shortcut. The relevant consequence is that more replicas fail the same way because the process configuration, not desired replica count, caused the exit.
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 more replicas fail the same way because the process configuration, not desired replica count, caused the exit.
Question 395
A small museum's new image runs a batch script and exits instead of serving HTTP requests. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Inspect image default command and Pod command or args settings to determine what executable starts in the container. Acceptance evidence: Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting. This pairing is justified because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
Incorrect Answers
This action and check address the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” instead of the stated acceptance requirement. The matching action is to inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
This action and check address the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” instead of the stated acceptance requirement. The matching action is to inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
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 inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
Question 396
A university lab accidentally overrides the entrypoint of a known-good container image. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. Inspect image default command and Pod command or args settings to determine what executable starts in the container. This resolves the issue because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. To verify, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
Incorrect Answers
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, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
This option addresses the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”, not the immediate requirement. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints. For the stated case, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. This option addresses the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, not the immediate requirement. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. For the stated case, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
Question 397
A university lab accidentally overrides the entrypoint of a known-good container image. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. It supports this action: Inspect image default command and Pod command or args settings to determine what executable starts in the container. To confirm, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
Incorrect Answers
That statement explains the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” rather than the cause in this case. The deciding mechanism here is that the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
That statement explains the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” rather than the cause in this case. The deciding mechanism here is that the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
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 the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
Question 398
A university lab accidentally overrides the entrypoint of a known-good container image. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting. This is the relevant test because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
Incorrect Answers
This check would help evaluate the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling”, but not the required result. For this case, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
This check would help evaluate the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”, but not the required result. For this case, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
This check would help evaluate the distinct objective “Use labels and selectors to connect resources predictably”, but not the required result. For this case, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
Question 399
A university lab accidentally overrides the entrypoint of a known-good container image. A shortcut is proposed: “Increase ReplicaSet count to fix a container that immediately exits because its startup arguments are invalid.” Which technical consequence follows most closely?
Explanation
Correct Answer
The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. More replicas fail the same way because the process configuration, not desired replica count, caused the exit. The shortcut creates this risk because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
Incorrect Answers
That outcome concerns the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”; it is not the most direct consequence of this shortcut. The relevant consequence is that more replicas fail the same way because the process configuration, not desired replica count, caused the exit.
That outcome concerns the distinct objective “Design a release rollback trigger from measurable service signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that more replicas fail the same way because the process configuration, not desired replica count, caused the exit.
That outcome concerns the distinct objective “Identify reconciliation work performed by kube-controller-manager”; it is not the most direct consequence of this shortcut. The relevant consequence is that more replicas fail the same way because the process configuration, not desired replica count, caused the exit.
Question 400
A university lab accidentally overrides the entrypoint of a known-good container image. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. Inspect image default command and Pod command or args settings to determine what executable starts in the container. Acceptance evidence: Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting. This pairing is justified because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
Incorrect Answers
This action and check address the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” instead of the stated acceptance requirement. The matching action is to inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
This action and check address the distinct objective “Distinguish a container image from a running container and its writable layer” instead of the stated acceptance requirement. The matching action is to inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
This action and check address the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior” instead of the stated acceptance requirement. The matching action is to inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 41 - 10 Questions (Last Reviewed 11-Oct-2026)
- Linux Foundation KCNA Practice Test 42 - 10 Questions (Last Reviewed 10-Oct-2026)