Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 60
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.
Question 591
A polytechnic shares one training cluster among untrusted student cohorts. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. This resolves the issue because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. To verify, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
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, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
This option addresses the distinct objective “Use labels and selectors to connect resources predictably”, not the immediate requirement. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships. For the stated case, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
This option addresses the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, not the immediate requirement. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe. For the stated case, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
Question 592
A polytechnic shares one training cluster among untrusted student cohorts. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. It supports this action: Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. To confirm, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
Incorrect Answers
That statement explains the distinct objective “Understand CSI drivers and volume attachment responsibilities” rather than the cause in this case. The deciding mechanism here is that namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
That statement explains the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” rather than the cause in this case. The deciding mechanism here is that namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
That statement explains the distinct objective “Use kubectl logs and previous container logs to isolate application crashes” rather than the cause in this case. The deciding mechanism here is that namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
Question 593
A polytechnic shares one training cluster among untrusted student cohorts. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota. This is the relevant test because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
Incorrect Answers
This check would help evaluate the distinct objective “Investigate readiness failures separately from liveness-related restarts”, but not the required result. For this case, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
This check would help evaluate the distinct objective “Use image provenance and policy controls without trusting mutable tags”, but not the required result. For this case, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
This check would help evaluate the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, but not the required result. For this case, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
Question 594
A polytechnic shares one training cluster among untrusted student cohorts. An engineer proposes: “Create two namespaces with names finance and students and declare them fully isolated without enforcing any additional security rules.” What adverse outcome would be most direct?
Explanation
Correct Answer
Teams can share unintended network and resource access while administrators believe the naming boundary is protective. The shortcut creates this risk because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
Incorrect Answers
That outcome concerns the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”; it is not the most direct consequence of this shortcut. The relevant consequence is that teams can share unintended network and resource access while administrators believe the naming boundary is protective.
That outcome concerns the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”; it is not the most direct consequence of this shortcut. The relevant consequence is that teams can share unintended network and resource access while administrators believe the naming boundary is protective.
That outcome concerns the distinct objective “Distinguish service mesh traffic management from external ingress routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that teams can share unintended network and resource access while administrators believe the naming boundary is protective.
Question 595
A polytechnic shares one training cluster among untrusted student cohorts. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Acceptance evidence: Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota. This pairing is justified because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
Incorrect Answers
This action and check address the distinct objective “Distinguish ClusterRoles from Roles and binding scope” instead of the stated acceptance requirement. The matching action is to combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
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 RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
This action and check address the distinct objective “Use an immutable image digest for exact deployment provenance” instead of the stated acceptance requirement. The matching action is to combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
Question 596
A small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. This resolves the issue because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. To verify, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
Incorrect Answers
The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. 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, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
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, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
This option addresses the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, not the immediate requirement. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. For the stated case, namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
Question 597
A small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. It supports this action: Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. To confirm, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
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 namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. That statement explains the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” rather than the cause in this case. The deciding mechanism here is that namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
That statement explains the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” rather than the cause in this case. The deciding mechanism here is that namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
Question 598
A small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota. This is the relevant test because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
Incorrect Answers
This check would help evaluate the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, but not the required result. For this case, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
This check would help evaluate the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, but not the required result. For this case, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
This check would help evaluate the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, but not the required result. For this case, test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
Question 599
A small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. The team suggests: “Create two namespaces with names finance and students and declare them fully isolated without enforcing any additional security rules.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Teams can share unintended network and resource access while administrators believe the naming boundary is protective. The shortcut creates this risk because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
Incorrect Answers
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 teams can share unintended network and resource access while administrators believe the naming boundary is protective.
That outcome concerns the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”; it is not the most direct consequence of this shortcut. The relevant consequence is that teams can share unintended network and resource access while administrators believe the naming boundary is protective.
That outcome concerns the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”; it is not the most direct consequence of this shortcut. The relevant consequence is that teams can share unintended network and resource access while administrators believe the naming boundary is protective.
Question 600
A small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Acceptance evidence: Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota. This pairing is justified because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.
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 combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
This action and check address the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers” instead of the stated acceptance requirement. The matching action is to combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
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 combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 62 - 10 Questions (Last Reviewed 16-Nov-2026)