Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 59
Question 580
A research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Acceptance evidence: With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests. This pairing is justified because TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
Incorrect Answers
This action and check address the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations” instead of the stated acceptance requirement. The matching action is to require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Its confirming test is to with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
The situation is that a research laboratory has a copied kubeconfig that disables TLS verification because of an outdated CA bundle. This action and check address the distinct objective “Understand CSI drivers and volume attachment responsibilities” instead of the stated acceptance requirement. The matching action is to require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Its confirming test is to with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
This action and check address the distinct objective “Design a release rollback trigger from measurable service signals” instead of the stated acceptance requirement. The matching action is to require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Its confirming test is to with synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
Question 581
A financial services public web front end never needs the Kubernetes API after startup. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. This resolves the issue because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. To verify, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
Incorrect Answers
This option addresses the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, not the immediate requirement. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image. For the stated case, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
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, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
This option addresses the distinct objective “Use image provenance and policy controls without trusting mutable tags”, not the immediate requirement. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. For the stated case, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
Question 582
A financial services public web front end never needs the Kubernetes API after startup. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. It supports this action: Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. To confirm, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
Incorrect Answers
That statement explains the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” rather than the cause in this case. The deciding mechanism here is that mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
That statement explains the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” rather than the cause in this case. The deciding mechanism here is that mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
That statement explains the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions” rather than the cause in this case. The deciding mechanism here is that mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
Question 583
A financial services public web front end never needs the Kubernetes API after startup. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable. This is the relevant test because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
Incorrect Answers
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, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
This check would help evaluate the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, but not the required result. For this case, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
This check would help evaluate the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”, but not the required result. For this case, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
Question 584
A financial services public web front end never needs the Kubernetes API after startup. The change review contains this proposal: “Mount a broad administration token into every nginx container solely because it is the cluster default.” What risk matters most?
Explanation
Correct Answer
One application vulnerability can expose a credential allowing changes unrelated to its actual business function. The shortcut creates this risk because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
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 one application vulnerability can expose a credential allowing changes unrelated to its actual business function.
That outcome concerns the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”; it is not the most direct consequence of this shortcut. The relevant consequence is that one application vulnerability can expose a credential allowing changes unrelated to its actual business function.
That outcome concerns the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”; it is not the most direct consequence of this shortcut. The relevant consequence is that one application vulnerability can expose a credential allowing changes unrelated to its actual business function.
Question 585
A financial services public web front end never needs the Kubernetes API after startup. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Acceptance evidence: Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable. This pairing is justified because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
Incorrect Answers
This action and check address the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” instead of the stated acceptance requirement. The matching action is to give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Its confirming test is to run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
This action and check address the distinct objective “Distinguish preferred node affinity from required scheduling rules” instead of the stated acceptance requirement. The matching action is to give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Its confirming test is to run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
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 give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Its confirming test is to run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
Question 586
A school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
The situation is that a school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. This resolves the issue because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. To verify, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
Incorrect Answers
This option addresses the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, not the immediate requirement. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid. For the stated case, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
This option addresses the distinct objective “Identify reconciliation work performed by kube-controller-manager”, not the immediate requirement. The controller manager runs controllers that observe API resources and make changes so current state moves toward desired state. For the stated case, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
This option addresses the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, not the immediate requirement. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. For the stated case, mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
Question 587
A school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
The situation is that a school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. It supports this action: Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. To confirm, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
Incorrect Answers
That statement explains the distinct objective “Distinguish ClusterRoles from Roles and binding scope” rather than the cause in this case. The deciding mechanism here is that mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
That statement explains the distinct objective “Externalize application configuration from an image while protecting secrets” rather than the cause in this case. The deciding mechanism here is that mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
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 mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
Question 588
A school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
The situation is that a school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable. This is the relevant test because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
Incorrect Answers
This check would help evaluate the distinct objective “Understand CSI drivers and volume attachment responsibilities”, but not the required result. For this case, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
The situation is that a school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. This check would help evaluate the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”, but not the required result. For this case, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
This check would help evaluate the distinct objective “Define secure release governance with staged approvals and policy verification”, but not the required result. For this case, run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
Question 589
A school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. A shortcut is proposed: “Mount a broad administration token into every nginx container solely because it is the cluster default.” Which technical consequence follows most closely?
Explanation
Correct Answer
The situation is that a school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. One application vulnerability can expose a credential allowing changes unrelated to its actual business function. The shortcut creates this risk because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
Incorrect Answers
That outcome concerns the distinct objective “Understand open standards and vendor-neutral community collaboration”; it is not the most direct consequence of this shortcut. The relevant consequence is that one application vulnerability can expose a credential allowing changes unrelated to its actual business function.
That outcome concerns the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that one application vulnerability can expose a credential allowing changes unrelated to its actual business function.
That outcome concerns the distinct objective “Use image provenance and policy controls without trusting mutable tags”; it is not the most direct consequence of this shortcut. The relevant consequence is that one application vulnerability can expose a credential allowing changes unrelated to its actual business function.
Question 590
A school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
The situation is that a school district's batch worker calls only an external image service and should not receive unnecessary cluster credentials. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Acceptance evidence: Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable. This pairing is justified because mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse.
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 give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Its confirming test is to run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
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 give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Its confirming test is to run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
This action and check address the distinct objective “Use image provenance and policy controls without trusting mutable tags” instead of the stated acceptance requirement. The matching action is to give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Its confirming test is to run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 60 - 10 Questions (Last Reviewed 18-Nov-2026)
- Linux Foundation KCNA Practice Test 61 - 10 Questions (Last Reviewed 17-Nov-2026)