Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 44
Question 430
A school learning platform reports traffic failures while Pods are Running but their readiness checks fail. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a school learning platform reports traffic failures while Pods are Running but their readiness checks fail. Configure readiness to stop sending Service traffic to an unready Pod, liveness to restart an unhealthy container and startup to allow slow initialization. Acceptance evidence: Delay a synthetic app response and compare EndpointSlice readiness with restart counts under controlled probe settings. This pairing is justified because readiness affects endpoint eligibility while liveness can cause restarts; a startup probe defers other probe checks until initialization succeeds.
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 configure readiness to stop sending Service traffic to an unready Pod, liveness to restart an unhealthy container and startup to allow slow initialization. Its confirming test is to delay a synthetic app response and compare EndpointSlice readiness with restart counts under controlled probe settings.
This action and check address the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” instead of the stated acceptance requirement. The matching action is to configure readiness to stop sending Service traffic to an unready Pod, liveness to restart an unhealthy container and startup to allow slow initialization. Its confirming test is to delay a synthetic app response and compare EndpointSlice readiness with restart counts under controlled probe settings.
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 configure readiness to stop sending Service traffic to an unready Pod, liveness to restart an unhealthy container and startup to allow slow initialization. Its confirming test is to delay a synthetic app response and compare EndpointSlice readiness with restart counts under controlled probe settings.
Question 431
A transit app compiles a Go service and wants a minimal image for edge deployments. What technical action should the platform team take in this situation?
Explanation
Correct Answer
Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. This resolves the issue because multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer. To verify, compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
Incorrect Answers
This option addresses the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”, not the immediate requirement. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior. For the stated case, multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
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, multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
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, multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
Question 432
A transit app compiles a Go service and wants a minimal image for edge deployments. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
Multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer. It supports this action: Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. To confirm, compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
Incorrect Answers
That statement explains the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects” rather than the cause in this case. The deciding mechanism here is that multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
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 multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
That statement explains the distinct objective “Distinguish a container image from a running container and its writable layer” rather than the cause in this case. The deciding mechanism here is that multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
Question 433
A transit app compiles a Go service and wants a minimal image for edge deployments. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
Compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts. This is the relevant test because multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
Incorrect Answers
This check would help evaluate the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, but not the required result. For this case, compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
This check would help evaluate the distinct objective “Distinguish preferred node affinity from required scheduling rules”, but not the required result. For this case, compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
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, compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
Question 434
A transit app compiles a Go service and wants a minimal image for edge deployments. The team suggests: “Publish the entire compiler toolchain and test credentials inside the runtime image for convenience.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The deployed artifact grows, may leak build credentials and exposes unnecessary packages. The shortcut creates this risk because multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
Incorrect Answers
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 the deployed artifact grows, may leak build credentials and exposes unnecessary packages.
That outcome concerns the distinct objective “Understand Prometheus pull-based metrics collection and exporters”; it is not the most direct consequence of this shortcut. The relevant consequence is that the deployed artifact grows, may leak build credentials and exposes unnecessary packages.
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 the deployed artifact grows, may leak build credentials and exposes unnecessary packages.
Question 435
A transit app compiles a Go service and wants a minimal image for edge deployments. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Acceptance evidence: Compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts. This pairing is justified because multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
Incorrect Answers
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 separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Its confirming test is to compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
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 separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Its confirming test is to compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
This action and check address the distinct objective “Build meaningful alert rules and route notifications through Alertmanager” instead of the stated acceptance requirement. The matching action is to separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Its confirming test is to compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
Question 436
A university Dockerfile accidentally copies a private development configuration into a public runtime layer. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
The situation is that a university Dockerfile accidentally copies a private development configuration into a public runtime layer. Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. This resolves the issue because multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer. To verify, compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
Incorrect Answers
The situation is that a university Dockerfile accidentally copies a private development configuration into a public runtime layer. 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, multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
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, multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
This option addresses the distinct objective “Use SLI and SLO measures to focus reliability objectives”, not the immediate requirement. A service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk. For the stated case, multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
Question 437
A university Dockerfile accidentally copies a private development configuration into a public runtime layer. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a university Dockerfile accidentally copies a private development configuration into a public runtime layer. Multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer. It supports this action: Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. To confirm, compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
Incorrect Answers
That statement explains the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior” rather than the cause in this case. The deciding mechanism here is that multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
That statement explains the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” rather than the cause in this case. The deciding mechanism here is that multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
That statement explains the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” rather than the cause in this case. The deciding mechanism here is that multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
Question 438
A university Dockerfile accidentally copies a private development configuration into a public runtime layer. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a university Dockerfile accidentally copies a private development configuration into a public runtime layer. Compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts. This is the relevant test because multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
Incorrect Answers
The situation is that a university Dockerfile accidentally copies a private development configuration into a public runtime layer. 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, compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
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, compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
This check would help evaluate the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior”, but not the required result. For this case, compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
Question 439
A university Dockerfile accidentally copies a private development configuration into a public runtime layer. The change review contains this proposal: “Publish the entire compiler toolchain and test credentials inside the runtime image for convenience.” What risk matters most?
Explanation
Correct Answer
The situation is that a university Dockerfile accidentally copies a private development configuration into a public runtime layer. The deployed artifact grows, may leak build credentials and exposes unnecessary packages. The shortcut creates this risk because multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
Incorrect Answers
That outcome concerns the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”; it is not the most direct consequence of this shortcut. The relevant consequence is that the deployed artifact grows, may leak build credentials and exposes unnecessary packages.
That outcome concerns the distinct objective “Distinguish a container image from a running container and its writable layer”; it is not the most direct consequence of this shortcut. The relevant consequence is that the deployed artifact grows, may leak build credentials and exposes unnecessary packages.
That outcome concerns the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”; it is not the most direct consequence of this shortcut. The relevant consequence is that the deployed artifact grows, may leak build credentials and exposes unnecessary packages.
Question 440
A university Dockerfile accidentally copies a private development configuration into a public runtime layer. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a university Dockerfile accidentally copies a private development configuration into a public runtime layer. Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Acceptance evidence: Compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts. This pairing is justified because multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
Incorrect Answers
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 separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Its confirming test is to compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
This action and check address the distinct objective “Use namespaces as organizational scopes without treating them as firewalls” instead of the stated acceptance requirement. The matching action is to separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Its confirming test is to compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
This action and check address the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” instead of the stated acceptance requirement. The matching action is to separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Its confirming test is to compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 42 - 10 Questions (Last Reviewed 10-Oct-2026)
- Linux Foundation KCNA Practice Test 43 - 10 Questions (Last Reviewed 09-Oct-2026)
- Linux Foundation KCNA Practice Test 44 - 10 Questions (Last Reviewed 08-Oct-2026)
- Linux Foundation KCNA Practice Test 45 - 10 Questions (Last Reviewed 07-Oct-2026)
- Linux Foundation KCNA Practice Test 46 - 10 Questions (Last Reviewed 06-Oct-2026)