Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 48
Question 470
An insurance sandbox uses identical api Service names in staging and production namespaces. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that an insurance sandbox uses identical api Service names in staging and production namespaces. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Acceptance evidence: Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces. This pairing is justified because coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
Incorrect Answers
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 use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Its confirming test is to run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
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 use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Its confirming test is to run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
This action and check address the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” instead of the stated acceptance requirement. The matching action is to use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Its confirming test is to run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
Question 471
A charity's api Service resolves but curls time out after a teammate changes a Pod label. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. This resolves the issue because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. To verify, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
Incorrect Answers
This option addresses the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, not the immediate requirement. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. For the stated case, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
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, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
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, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
Question 472
A charity's api Service resolves but curls time out after a teammate changes a Pod label. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. It supports this action: Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. To confirm, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer 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 endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
That statement explains the distinct objective “Explain desired state versus observed status in Kubernetes objects” rather than the cause in this case. The deciding mechanism here is that endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
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 endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
Question 473
A charity's api Service resolves but curls time out after a teammate changes a Pod label. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings. This is the relevant test because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
Incorrect Answers
This check would help evaluate the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, but not the required result. For this case, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer 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, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
This check would help evaluate the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”, but not the required result. For this case, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
Question 474
A charity's api Service resolves but curls time out after a teammate changes a Pod label. The change review contains this proposal: “Change the client's DNS resolver while a Service selector matches no Pods and its EndpointSlices are empty.” What risk matters most?
Explanation
Correct Answer
Name lookup may succeed but no usable endpoint exists to receive traffic. The shortcut creates this risk because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
Incorrect Answers
That outcome concerns the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”; it is not the most direct consequence of this shortcut. The relevant consequence is that name lookup may succeed but no usable endpoint exists to receive traffic.
That outcome concerns the distinct objective “Understand ports, targetPort and protocol mapping in a Service”; it is not the most direct consequence of this shortcut. The relevant consequence is that name lookup may succeed but no usable endpoint exists to receive traffic.
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 name lookup may succeed but no usable endpoint exists to receive traffic.
Question 475
A charity's api Service resolves but curls time out after a teammate changes a Pod label. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Acceptance evidence: Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings. This pairing is justified because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
Incorrect Answers
This action and check address the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources” instead of the stated acceptance requirement. The matching action is to check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
This action and check address the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” instead of the stated acceptance requirement. The matching action is to check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
This action and check address the distinct objective “Understand readiness, liveness and startup probes as different signals” instead of the stated acceptance requirement. The matching action is to check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
Question 476
A bank's backend Pods run but fail readiness, leaving the Service without ready targets. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
The situation is that a bank's backend Pods run but fail readiness, leaving the Service without ready targets. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. This resolves the issue because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. To verify, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
Incorrect Answers
This option addresses the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”, not the immediate requirement. The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. For the stated case, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
This option addresses the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”, not the immediate requirement. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. For the stated case, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
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, endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
Question 477
A bank's backend Pods run but fail readiness, leaving the Service without ready targets. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a bank's backend Pods run but fail readiness, leaving the Service without ready targets. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. It supports this action: Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. To confirm, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
Incorrect Answers
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 endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
That statement explains the distinct objective “Investigate readiness failures separately from liveness-related restarts” rather than the cause in this case. The deciding mechanism here is that endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
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 endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
Question 478
A bank's backend Pods run but fail readiness, leaving the Service without ready targets. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a bank's backend Pods run but fail readiness, leaving the Service without ready targets. Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings. This is the relevant test because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
Incorrect Answers
This check would help evaluate the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, but not the required result. For this case, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
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, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
This check would help evaluate the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, but not the required result. For this case, compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
Question 479
A bank's backend Pods run but fail readiness, leaving the Service without ready targets. The change review contains this proposal: “Change the client's DNS resolver while a Service selector matches no Pods and its EndpointSlices are empty.” What risk matters most?
Explanation
Correct Answer
The situation is that a bank's backend Pods run but fail readiness, leaving the Service without ready targets. Name lookup may succeed but no usable endpoint exists to receive traffic. The shortcut creates this risk because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
Incorrect Answers
That outcome concerns the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”; it is not the most direct consequence of this shortcut. The relevant consequence is that name lookup may succeed but no usable endpoint exists to receive traffic.
That outcome concerns the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling”; it is not the most direct consequence of this shortcut. The relevant consequence is that name lookup may succeed but no usable endpoint exists to receive traffic.
That outcome concerns the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”; it is not the most direct consequence of this shortcut. The relevant consequence is that name lookup may succeed but no usable endpoint exists to receive traffic.
Question 480
A bank's backend Pods run but fail readiness, leaving the Service without ready targets. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a bank's backend Pods run but fail readiness, leaving the Service without ready targets. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Acceptance evidence: Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings. This pairing is justified because endpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods.
Incorrect Answers
This action and check address the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” instead of the stated acceptance requirement. The matching action is to check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
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 check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
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 check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends. Its confirming test is to compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 49 - 10 Questions (Last Reviewed 03-Oct-2026)
- Linux Foundation KCNA Practice Test 50 - 10 Questions (Last Reviewed 02-Oct-2026)