Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 57
Question 560
A university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a university catalog service needs DNS and a single database endpoint but should deny unrelated lab Pods. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Acceptance evidence: Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed. This pairing is justified because networkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.
Incorrect Answers
This action and check address the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts” instead of the stated acceptance requirement. The matching action is to combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.
This action and check address the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” instead of the stated acceptance requirement. The matching action is to combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.
This action and check address the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” instead of the stated acceptance requirement. The matching action is to combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Its confirming test is to test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.
Question 561
A municipal platform validates vendor containers before moving them into production. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Require approved image registries, signature or digest verification and patch ownership when admitting production container images. This resolves the issue because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. To verify, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
Incorrect Answers
This option addresses the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, not the immediate requirement. TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute. For the stated case, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
This option addresses the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, not the immediate requirement. An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration. For the stated case, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
This option addresses the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, not the immediate requirement. ClusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole. For the stated case, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
Question 562
A municipal platform validates vendor containers before moving them into production. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. It supports this action: Require approved image registries, signature or digest verification and patch ownership when admitting production container images. To confirm, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
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 image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
That statement explains the distinct objective “Use namespaces as organizational scopes without treating them as firewalls” rather than the cause in this case. The deciding mechanism here is that image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
That statement explains the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” rather than the cause in this case. The deciding mechanism here is that image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
Question 563
A municipal platform validates vendor containers before moving them into production. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results. This is the relevant test because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
Incorrect Answers
This check would help evaluate the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, but not the required result. For this case, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
This check would help evaluate the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, but not the required result. For this case, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
This check would help evaluate the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, but not the required result. For this case, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
Question 564
A municipal platform validates vendor containers before moving them into production. An engineer proposes: “Permit unsigned images from any public registry because container isolation makes supply-chain review unnecessary.” What adverse outcome would be most direct?
Explanation
Correct Answer
An untrusted dependency or replaced tag can run within otherwise well-configured Pods. The shortcut creates this risk because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
Incorrect Answers
That outcome concerns the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”; it is not the most direct consequence of this shortcut. The relevant consequence is that an untrusted dependency or replaced tag can run within otherwise well-configured Pods.
That outcome concerns the distinct objective “Use SLI and SLO measures to focus reliability objectives”; it is not the most direct consequence of this shortcut. The relevant consequence is that an untrusted dependency or replaced tag can run within otherwise well-configured Pods.
That outcome concerns the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”; it is not the most direct consequence of this shortcut. The relevant consequence is that an untrusted dependency or replaced tag can run within otherwise well-configured Pods.
Question 565
A municipal platform validates vendor containers before moving them into production. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Require approved image registries, signature or digest verification and patch ownership when admitting production container images. Acceptance evidence: Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results. This pairing is justified because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
Incorrect Answers
This action and check address the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
This action and check address the distinct objective “Use Pods as the shared network and storage execution unit” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
This action and check address the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
Question 566
A hospital discovers that a third-party image tag was changed after its release approval. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
The situation is that a hospital discovers that a third-party image tag was changed after its release approval. Require approved image registries, signature or digest verification and patch ownership when admitting production container images. This resolves the issue because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. To verify, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
Incorrect Answers
This option addresses the distinct objective “Use Events and pod describe for failed volume mounting”, not the immediate requirement. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. For the stated case, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
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, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
This option addresses the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, not the immediate requirement. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. For the stated case, image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
Question 567
A hospital discovers that a third-party image tag was changed after its release approval. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
The situation is that a hospital discovers that a third-party image tag was changed after its release approval. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. It supports this action: Require approved image registries, signature or digest verification and patch ownership when admitting production container images. To confirm, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
Incorrect Answers
That statement explains the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” rather than the cause in this case. The deciding mechanism here is that image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
That statement explains the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations” rather than the cause in this case. The deciding mechanism here is that image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
That statement explains the distinct objective “Explain desired state versus observed status in Kubernetes objects” rather than the cause in this case. The deciding mechanism here is that image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
Question 568
A hospital discovers that a third-party image tag was changed after its release approval. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
The situation is that a hospital discovers that a third-party image tag was changed after its release approval. Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results. This is the relevant test because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
Incorrect Answers
This check would help evaluate the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability”, but not the required result. For this case, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
This check would help evaluate the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, but not the required result. For this case, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
This check would help evaluate the distinct objective “Distinguish preferred node affinity from required scheduling rules”, but not the required result. For this case, deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
Question 569
A hospital discovers that a third-party image tag was changed after its release approval. A shortcut is proposed: “Permit unsigned images from any public registry because container isolation makes supply-chain review unnecessary.” Which technical consequence follows most closely?
Explanation
Correct Answer
The situation is that a hospital discovers that a third-party image tag was changed after its release approval. An untrusted dependency or replaced tag can run within otherwise well-configured Pods. The shortcut creates this risk because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
Incorrect Answers
That outcome concerns the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”; it is not the most direct consequence of this shortcut. The relevant consequence is that an untrusted dependency or replaced tag can run within otherwise well-configured Pods.
The situation is that a hospital discovers that a third-party image tag was changed after its release approval. That outcome concerns the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”; it is not the most direct consequence of this shortcut. The relevant consequence is that an untrusted dependency or replaced tag can run within otherwise well-configured Pods.
That outcome concerns the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”; it is not the most direct consequence of this shortcut. The relevant consequence is that an untrusted dependency or replaced tag can run within otherwise well-configured Pods.
Question 570
A hospital discovers that a third-party image tag was changed after its release approval. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
The situation is that a hospital discovers that a third-party image tag was changed after its release approval. Require approved image registries, signature or digest verification and patch ownership when admitting production container images. Acceptance evidence: Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results. This pairing is justified because image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity.
Incorrect Answers
This action and check address the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
This action and check address the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
This action and check address the distinct objective “Use annotations for tool metadata rather than workload selection” instead of the stated acceptance requirement. The matching action is to require approved image registries, signature or digest verification and patch ownership when admitting production container images. Its confirming test is to deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 55 - 10 Questions (Last Reviewed 27-Sep-2026)
- Linux Foundation KCNA Practice Test 56 - 10 Questions (Last Reviewed 26-Sep-2026)
- Linux Foundation KCNA Practice Test 57 - 10 Questions (Last Reviewed 21-Nov-2026)
- Linux Foundation KCNA Practice Test 58 - 10 Questions (Last Reviewed 20-Nov-2026)
- Linux Foundation KCNA Practice Test 59 - 10 Questions (Last Reviewed 19-Nov-2026)