Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 47
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.
Question 461
A school enrollment Pod in admissions needs a billing Service in a different namespace. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. This resolves the issue because coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. To verify, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
Incorrect Answers
This option addresses the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”, not the immediate requirement. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. For the stated case, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
This option addresses the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, not the immediate requirement. TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute. For the stated case, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
This option addresses the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, not the immediate requirement. An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration. For the stated case, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
Question 462
A school enrollment Pod in admissions needs a billing Service in a different namespace. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. It supports this action: Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. To confirm, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
Incorrect Answers
That statement explains the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” rather than the cause in this case. The deciding mechanism here is that coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
That statement explains the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” rather than the cause in this case. The deciding mechanism here is that coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
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 coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
Question 463
A school enrollment Pod in admissions needs a billing Service in a different namespace. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces. This is the relevant test 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 check would help evaluate the distinct objective “Use labels and selectors to connect resources predictably”, but not the required result. For this case, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
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, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
This check would help evaluate the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”, but not the required result. For this case, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
Question 464
A school enrollment Pod in admissions needs a billing Service in a different namespace. The change review contains this proposal: “Assume a short Service name always resolves to another namespace's workload regardless of the client's search path.” What risk matters most?
Explanation
Correct Answer
Cross-namespace calls can fail or resolve a same-named but unrelated local Service. The shortcut creates this risk 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
That outcome concerns the distinct objective “Distinguish Deployment desired state from a manually created Pod”; it is not the most direct consequence of this shortcut. The relevant consequence is that cross-namespace calls can fail or resolve a same-named but unrelated local Service.
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 cross-namespace calls can fail or resolve a same-named but unrelated local Service.
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 cross-namespace calls can fail or resolve a same-named but unrelated local Service.
Question 465
A school enrollment Pod in admissions needs a billing Service in a different namespace. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
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 “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” 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 “Understand PersistentVolumeClaim binding to persistent storage resources” 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 describe and Events to distinguish admission, scheduling and execution errors” 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 466
An insurance sandbox uses identical api Service names in staging and production namespaces. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
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. This resolves the issue because coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. To verify, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
Incorrect Answers
The situation is that an insurance sandbox uses identical api Service names in staging and production namespaces. This option addresses the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”, not the immediate requirement. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. For the stated case, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
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, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
This option addresses the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, not the immediate requirement. Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. For the stated case, coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
Question 467
An insurance sandbox uses identical api Service names in staging and production namespaces. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
The situation is that an insurance sandbox uses identical api Service names in staging and production namespaces. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. It supports this action: Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. To confirm, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
Incorrect Answers
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 coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
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 coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
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 coreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
Question 468
An insurance sandbox uses identical api Service names in staging and production namespaces. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
The situation is that an insurance sandbox uses identical api Service names in staging and production namespaces. Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces. This is the relevant test 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
The situation is that an insurance sandbox uses identical api Service names in staging and production namespaces. 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, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
This check would help evaluate the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, but not the required result. For this case, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
This check would help evaluate the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”, but not the required result. For this case, run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
Question 469
An insurance sandbox uses identical api Service names in staging and production namespaces. An engineer proposes: “Assume a short Service name always resolves to another namespace's workload regardless of the client's search path.” What adverse outcome would be most direct?
Explanation
Correct Answer
The situation is that an insurance sandbox uses identical api Service names in staging and production namespaces. Cross-namespace calls can fail or resolve a same-named but unrelated local Service. The shortcut creates this risk 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
That outcome concerns the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”; it is not the most direct consequence of this shortcut. The relevant consequence is that cross-namespace calls can fail or resolve a same-named but unrelated local Service.
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 cross-namespace calls can fail or resolve a same-named but unrelated local Service.
That outcome concerns the distinct objective “Separate CI build verification from CD environment promotion”; it is not the most direct consequence of this shortcut. The relevant consequence is that cross-namespace calls can fail or resolve a same-named but unrelated local Service.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 49 - 10 Questions (Last Reviewed 03-Oct-2026)