Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 52
Question 510
A retail order processor caches a Pod IP and loses connectivity after cluster maintenance. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a retail order processor caches a Pod IP and loses connectivity after cluster maintenance. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Acceptance evidence: Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses. This pairing is justified because pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.
Incorrect Answers
This action and check address the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” instead of the stated acceptance requirement. The matching action is to give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Its confirming test is to delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
This action and check address the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects” instead of the stated acceptance requirement. The matching action is to give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Its confirming test is to delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
This action and check address the distinct objective “Understand ports, targetPort and protocol mapping in a Service” instead of the stated acceptance requirement. The matching action is to give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Its confirming test is to delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
Question 511
An inventory service listens on port 8080 but clients call its Service on port 80. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. This resolves the issue 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. To verify, inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
Incorrect Answers
This option addresses the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”, not the immediate requirement. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support. For the stated case, 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.
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, 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.
This option addresses the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift”, not the immediate requirement. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management. For the stated case, 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.
Question 512
An inventory service listens on port 8080 but clients call its Service on port 80. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
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. It supports this action: Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. To confirm, inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
Incorrect Answers
That statement explains the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” rather than the cause in this case. The deciding mechanism here is that 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.
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 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.
That statement explains the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes” rather than the cause in this case. The deciding mechanism here is that 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.
Question 513
An inventory service listens on port 8080 but clients call its Service on port 80. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings. This is the relevant test 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 check would help evaluate the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, but not the required result. For this case, inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
This check would help evaluate the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”, but not the required result. For this case, inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
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, inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
Question 514
An inventory service listens on port 8080 but clients call its Service on port 80. An engineer proposes: “Set targetPort to the Service's external port by habit even though the application listens on a different container port.” What adverse outcome would be most direct?
Explanation
Correct Answer
Packets reach the wrong destination socket and the Service appears unavailable despite healthy Pod processes. The shortcut creates this risk 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
That outcome concerns the distinct objective “Understand CSI drivers and volume attachment responsibilities”; it is not the most direct consequence of this shortcut. The relevant consequence is that packets reach the wrong destination socket and the Service appears unavailable despite healthy Pod processes.
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 packets reach the wrong destination socket and the Service appears unavailable despite healthy Pod processes.
That outcome concerns the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”; it is not the most direct consequence of this shortcut. The relevant consequence is that packets reach the wrong destination socket and the Service appears unavailable despite healthy Pod processes.
Question 515
An inventory service listens on port 8080 but clients call its Service on port 80. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
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 “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” 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 “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” 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 “Use Pod affinity for co-location without assuming it creates networking permissions” 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 516
A student connects a NodePort Service to a Pod running an HTTP process on an unexpected internal port. What technical action should the platform team take in this situation?
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. This resolves the issue 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. To verify, inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
Incorrect Answers
This option addresses the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior”, not the immediate requirement. Microservices permit independent deployment and scaling but introduce network dependencies and data consistency challenges; a monolith can remain appropriate for smaller teams. For the stated case, 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.
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, 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.
This option addresses the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, not the immediate requirement. Pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints. For the stated case, 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.
Question 517
A student connects a NodePort Service to a Pod running an HTTP process on an unexpected internal port. What underlying Kubernetes behavior is most relevant to this technical decision?
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. 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. It supports this action: Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. To confirm, inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
Incorrect Answers
That statement explains the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” rather than the cause in this case. The deciding mechanism here is that 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.
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 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.
That statement explains the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” rather than the cause in this case. The deciding mechanism here is that 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.
Question 518
A student connects a NodePort Service to a Pod running an HTTP process on an unexpected internal port. What acceptance check most directly confirms this requirement is met?
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. Inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings. This is the relevant test 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 check would help evaluate the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”, but not the required result. For this case, inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
This check would help evaluate the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”, but not the required result. For this case, inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
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, inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.
Question 519
A student connects a NodePort Service to a Pod running an HTTP process on an unexpected internal port. The team suggests: “Set targetPort to the Service's external port by habit even though the application listens on a different container port.” Which failure should the reviewer anticipate?
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. Packets reach the wrong destination socket and the Service appears unavailable despite healthy Pod processes. The shortcut creates this risk 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
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 packets reach the wrong destination socket and the Service appears unavailable despite healthy Pod processes.
That outcome concerns the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”; it is not the most direct consequence of this shortcut. The relevant consequence is that packets reach the wrong destination socket and the Service appears unavailable despite healthy Pod processes.
That outcome concerns the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”; it is not the most direct consequence of this shortcut. The relevant consequence is that packets reach the wrong destination socket and the Service appears unavailable despite healthy Pod processes.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 50 - 10 Questions (Last Reviewed 02-Oct-2026)
- 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)