Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 53
Question 520
A student connects a NodePort Service to a Pod running an HTTP process on an unexpected internal port. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a student connects a NodePort Service to a Pod running an HTTP process on an unexpected internal port. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. Acceptance evidence: Inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings. This pairing is justified because a Service exposes port to clients and forwards to targetPort on selected endpoints; a mismatched targetPort can break delivery even with valid DNS and selectors.
Incorrect Answers
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 match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. Its confirming test is to inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
This action and check address the distinct objective “Explain desired state versus observed status in Kubernetes objects” instead of the stated acceptance requirement. The matching action is to match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. Its confirming test is to inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
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 match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. Its confirming test is to inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
Question 521
A university lets course assistants inspect one lab namespace without editing network policies. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. This resolves the issue because RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate. To verify, use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
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, RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
This option addresses the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, not the immediate requirement. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply. For the stated case, RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
This option addresses the distinct objective “Understand ports, targetPort and protocol mapping in a Service”, not the immediate requirement. A Service exposes port to clients and forwards to targetPort on selected endpoints; a mismatched targetPort can break delivery even with valid DNS and selectors. For the stated case, RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
Question 522
A university lets course assistants inspect one lab namespace without editing network policies. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate. It supports this action: Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. To confirm, use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
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 RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
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 RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
That statement explains the distinct objective “Correlate application rollout revisions with error spikes” rather than the cause in this case. The deciding mechanism here is that RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
Question 523
A university lets course assistants inspect one lab namespace without editing network policies. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace. This is the relevant test because RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
Incorrect Answers
This check would help evaluate the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, but not the required result. For this case, use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
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, use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
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, use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
Question 524
A university lets course assistants inspect one lab namespace without editing network policies. The change review contains this proposal: “Grant cluster-admin to a log reader because kubectl describe initially returns a forbidden error.” What risk matters most?
Explanation
Correct Answer
The subject receives unnecessary authority to alter privileged resources or unrelated namespaces. The shortcut creates this risk because RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
Incorrect Answers
That outcome concerns the distinct objective “Instrument services with OpenTelemetry context propagation”; it is not the most direct consequence of this shortcut. The relevant consequence is that the subject receives unnecessary authority to alter privileged resources or unrelated namespaces.
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 the subject receives unnecessary authority to alter privileged resources or unrelated namespaces.
That outcome concerns the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”; it is not the most direct consequence of this shortcut. The relevant consequence is that the subject receives unnecessary authority to alter privileged resources or unrelated namespaces.
Question 525
A university lets course assistants inspect one lab namespace without editing network policies. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Acceptance evidence: Use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace. This pairing is justified because RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
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 create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Its confirming test is to use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
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 create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Its confirming test is to use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
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 create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Its confirming test is to use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
Question 526
A charity wants monitoring staff to read Deployment status but not view private Secret objects. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
The situation is that a charity wants monitoring staff to read Deployment status but not view private Secret objects. Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. This resolves the issue because RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate. To verify, use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
Incorrect Answers
This option addresses the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, not the immediate requirement. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. For the stated case, RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
This option addresses the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”, not the immediate requirement. Open-source community processes provide transparent review and shared maintenance, but do not imply unreviewed external code should be merged into production. For the stated case, RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
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, RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
Question 527
A charity wants monitoring staff to read Deployment status but not view private Secret objects. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
The situation is that a charity wants monitoring staff to read Deployment status but not view private Secret objects. RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate. It supports this action: Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. To confirm, use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
Incorrect Answers
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 RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
That statement explains the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts” rather than the cause in this case. The deciding mechanism here is that RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
That statement explains the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” rather than the cause in this case. The deciding mechanism here is that RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
Question 528
A charity wants monitoring staff to read Deployment status but not view private Secret objects. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
The situation is that a charity wants monitoring staff to read Deployment status but not view private Secret objects. Use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace. This is the relevant test because RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
Incorrect Answers
This check would help evaluate the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, but not the required result. For this case, use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
This check would help evaluate the distinct objective “Use Events and pod describe for failed volume mounting”, but not the required result. For this case, use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
This check would help evaluate the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”, but not the required result. For this case, use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
Question 529
A charity wants monitoring staff to read Deployment status but not view private Secret objects. An engineer proposes: “Grant cluster-admin to a log reader because kubectl describe initially returns a forbidden error.” What adverse outcome would be most direct?
Explanation
Correct Answer
The situation is that a charity wants monitoring staff to read Deployment status but not view private Secret objects. The subject receives unnecessary authority to alter privileged resources or unrelated namespaces. The shortcut creates this risk because RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
Incorrect Answers
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 the subject receives unnecessary authority to alter privileged resources or unrelated namespaces.
The situation is that a charity wants monitoring staff to read Deployment status but not view private Secret objects. 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 the subject receives unnecessary authority to alter privileged resources or unrelated namespaces.
That outcome concerns the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”; it is not the most direct consequence of this shortcut. The relevant consequence is that the subject receives unnecessary authority to alter privileged resources or unrelated namespaces.
Question 530
A charity wants monitoring staff to read Deployment status but not view private Secret objects. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a charity wants monitoring staff to read Deployment status but not view private Secret objects. Create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Acceptance evidence: Use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace. This pairing is justified because RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate.
Incorrect Answers
This action and check address the distinct objective “Enforce workload service account token boundaries and avoid needless mounts” instead of the stated acceptance requirement. The matching action is to create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Its confirming test is to use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
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 create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Its confirming test is to use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
This action and check address the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core” instead of the stated acceptance requirement. The matching action is to create a Role with only required verbs and resource types, and bind it to the intended subject within the target namespace. Its confirming test is to use kubectl auth can-i --as a synthetic student to verify pod get allowed and secret delete denied in the specified namespace.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 51 - 10 Questions (Last Reviewed 01-Oct-2026)
- Linux Foundation KCNA Practice Test 52 - 10 Questions (Last Reviewed 30-Sep-2026)
- Linux Foundation KCNA Practice Test 53 - 10 Questions (Last Reviewed 29-Sep-2026)
- Linux Foundation KCNA Practice Test 54 - 10 Questions (Last Reviewed 28-Sep-2026)
- Linux Foundation KCNA Practice Test 55 - 10 Questions (Last Reviewed 27-Sep-2026)