Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 46
Question 450
A regional retailer deploys networking add-ons and needs to distinguish CNI setup from Service object configuration. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a regional retailer deploys networking add-ons and needs to distinguish CNI setup from Service object configuration. Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names. Acceptance evidence: Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP. This pairing is justified because Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
Incorrect Answers
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 check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names. Its confirming test is to deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
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 check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names. Its confirming test is to deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
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 check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names. Its confirming test is to deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
Question 451
A transit API needs an internal PostgreSQL endpoint and a separately published public front end. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. This resolves the issue because service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure. To verify, create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
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, service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
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, service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
This option addresses the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core”, not the immediate requirement. CNCF projects address different layers of a cloud-native platform and interoperability does not turn them into interchangeable cluster control-plane components. For the stated case, service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
Question 452
A transit API needs an internal PostgreSQL endpoint and a separately published public front end. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
Service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure. It supports this action: Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. To confirm, create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
Incorrect Answers
That statement explains the distinct objective “Distinguish the CNI Pod network from Service discovery and routing” rather than the cause in this case. The deciding mechanism here is that service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
That statement explains the distinct objective “Use nodeSelector to place a workload on nodes with required labels” rather than the cause in this case. The deciding mechanism here is that service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
That statement explains the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” rather than the cause in this case. The deciding mechanism here is that service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
Question 453
A transit API needs an internal PostgreSQL endpoint and a separately published public front end. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration. This is the relevant test because service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
Incorrect Answers
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, create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
This check would help evaluate the distinct objective “Explain desired state versus observed status in Kubernetes objects”, but not the required result. For this case, create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
This check would help evaluate the distinct objective “Understand ports, targetPort and protocol mapping in a Service”, but not the required result. For this case, create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
Question 454
A transit API needs an internal PostgreSQL endpoint and a separately published public front end. A shortcut is proposed: “Change an internal database Service to unrestricted NodePort because another Pod cannot resolve its DNS name.” Which technical consequence follows most closely?
Explanation
Correct Answer
The change unnecessarily exposes a data service externally while the original DNS problem remains unresolved. The shortcut creates this risk because service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
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 change unnecessarily exposes a data service externally while the original DNS problem remains unresolved.
That outcome concerns the distinct objective “Separate kube-scheduler decisions from kubelet execution”; it is not the most direct consequence of this shortcut. The relevant consequence is that the change unnecessarily exposes a data service externally while the original DNS problem remains unresolved.
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 the change unnecessarily exposes a data service externally while the original DNS problem remains unresolved.
Question 455
A transit API needs an internal PostgreSQL endpoint and a separately published public front end. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Acceptance evidence: Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration. This pairing is justified because service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
Incorrect Answers
This action and check address the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods” instead of the stated acceptance requirement. The matching action is to use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Its confirming test is to create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
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 use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Its confirming test is to create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
This action and check address the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior” instead of the stated acceptance requirement. The matching action is to use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Its confirming test is to create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
Question 456
A museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. This resolves the issue because service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure. To verify, create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
Incorrect Answers
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, service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
This option addresses the distinct objective “Separate kube-scheduler decisions from kubelet execution”, not the immediate requirement. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers. For the stated case, service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
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, service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
Question 457
A museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. Service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure. It supports this action: Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. To confirm, create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
Incorrect Answers
That statement explains the distinct objective “Recognize the kubelet role in local Pod lifecycle management” rather than the cause in this case. The deciding mechanism here is that service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
That statement explains the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods” rather than the cause in this case. The deciding mechanism here is that service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
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 service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
Question 458
A museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration. This is the relevant test because service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
Incorrect Answers
The situation is that a museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. This check would help evaluate the distinct objective “Understand ports, targetPort and protocol mapping in a Service”, but not the required result. For this case, create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
This check would help evaluate the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”, but not the required result. For this case, create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
This check would help evaluate the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, but not the required result. For this case, create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
Question 459
A museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. The team suggests: “Change an internal database Service to unrestricted NodePort because another Pod cannot resolve its DNS name.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. The change unnecessarily exposes a data service externally while the original DNS problem remains unresolved. The shortcut creates this risk because service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
Incorrect Answers
That outcome concerns the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”; it is not the most direct consequence of this shortcut. The relevant consequence is that the change unnecessarily exposes a data service externally while the original DNS problem remains unresolved.
That outcome concerns the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”; it is not the most direct consequence of this shortcut. The relevant consequence is that the change unnecessarily exposes a data service externally while the original DNS problem remains unresolved.
The situation is that a museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. 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 change unnecessarily exposes a data service externally while the original DNS problem remains unresolved.
Question 460
A museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a museum accidentally makes its internal cache service accessible on node ports while debugging client resolution. Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Acceptance evidence: Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration. This pairing is justified because service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
Incorrect Answers
This action and check address the distinct objective “Distinguish the CNI Pod network from Service discovery and routing” instead of the stated acceptance requirement. The matching action is to use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Its confirming test is to create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
This action and check address the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” instead of the stated acceptance requirement. The matching action is to use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Its confirming test is to create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
This action and check address the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” instead of the stated acceptance requirement. The matching action is to use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Its confirming test is to create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 44 - 10 Questions (Last Reviewed 08-Oct-2026)
- Linux Foundation KCNA Practice Test 45 - 10 Questions (Last Reviewed 07-Oct-2026)
- Linux Foundation KCNA Practice Test 46 - 10 Questions (Last Reviewed 06-Oct-2026)
- Linux Foundation KCNA Practice Test 47 - 10 Questions (Last Reviewed 05-Oct-2026)
- Linux Foundation KCNA Practice Test 48 - 10 Questions (Last Reviewed 04-Oct-2026)