Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 39
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.
Question 381
A manufacturer stores proprietary service images in a private registry restricted by project. What technical action should the platform team take in this situation?
Explanation
Correct Answer
Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. This resolves the issue because image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. To verify, deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
Incorrect Answers
This option addresses the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, not the immediate requirement. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller. For the stated case, image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
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, image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
This option addresses the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms”, not the immediate requirement. Linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine. For the stated case, image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
Question 382
A manufacturer stores proprietary service images in a private registry restricted by project. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. It supports this action: Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. To confirm, deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
Incorrect Answers
That statement explains the distinct objective “Design a release rollback trigger from measurable service signals” rather than the cause in this case. The deciding mechanism here is that image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
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 image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
That statement explains the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” rather than the cause in this case. The deciding mechanism here is that image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
Question 383
A manufacturer stores proprietary service images in a private registry restricted by project. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
Deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token. This is the relevant test because image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
Incorrect Answers
This check would help evaluate the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, but not the required result. For this case, deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
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, deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
This check would help evaluate the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”, but not the required result. For this case, deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
Question 384
A manufacturer stores proprietary service images in a private registry restricted by project. The team suggests: “Write the registry password into a Dockerfile RUN command so every user can pull the image without cluster configuration.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
A leaked image layer or build log can disclose credentials and grant unwanted registry access. The shortcut creates this risk because image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
Incorrect Answers
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 leaked image layer or build log can disclose credentials and grant unwanted registry access.
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 a leaked image layer or build log can disclose credentials and grant unwanted registry access.
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 a leaked image layer or build log can disclose credentials and grant unwanted registry access.
Question 385
A manufacturer stores proprietary service images in a private registry restricted by project. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
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 least-privilege kubectl authentication and authorization during routine administration” 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 “Investigate readiness failures separately from liveness-related restarts” 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 “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence” 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 386
A financial service team sees ImagePullBackOff because its namespace lacks valid image pull credentials. What technical action should the platform team take in this situation?
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. This resolves the issue because image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. To verify, deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
Incorrect Answers
This option addresses the distinct objective “Distinguish Deployment desired state from a manually created Pod”, not the immediate requirement. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. For the stated case, image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
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, image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
This option addresses the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”, not the immediate requirement. RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate. For the stated case, image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
Question 387
A financial service team sees ImagePullBackOff because its namespace lacks valid image pull credentials. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a financial service team sees ImagePullBackOff because its namespace lacks valid image pull credentials. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. It supports this action: Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. To confirm, deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
Incorrect Answers
That statement explains the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance” rather than the cause in this case. The deciding mechanism here is that image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
That statement explains the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” rather than the cause in this case. The deciding mechanism here is that image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
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 image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
Question 388
A financial service team sees ImagePullBackOff because its namespace lacks valid image pull credentials. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a financial service team sees ImagePullBackOff because its namespace lacks valid image pull credentials. Deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token. This is the relevant test because image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
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, deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
This check would help evaluate the distinct objective “Use an immutable image digest for exact deployment provenance”, but not the required result. For this case, deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
This check would help evaluate the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”, but not the required result. For this case, deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
Question 389
A financial service team sees ImagePullBackOff because its namespace lacks valid image pull credentials. The team suggests: “Write the registry password into a Dockerfile RUN command so every user can pull the image without cluster configuration.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a financial service team sees ImagePullBackOff because its namespace lacks valid image pull credentials. A leaked image layer or build log can disclose credentials and grant unwanted registry access. The shortcut creates this risk because image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
Incorrect Answers
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 leaked image layer or build log can disclose credentials and grant unwanted registry access.
That outcome concerns the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”; it is not the most direct consequence of this shortcut. The relevant consequence is that a leaked image layer or build log can disclose credentials and grant unwanted registry access.
That outcome concerns the distinct objective “Use an immutable image digest for exact deployment provenance”; it is not the most direct consequence of this shortcut. The relevant consequence is that a leaked image layer or build log can disclose credentials and grant unwanted registry access.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 41 - 10 Questions (Last Reviewed 11-Oct-2026)