Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 49
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.
Question 481
A hospital uses one public hostname with path rules for separate appointment services. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. This resolves the issue because ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. To verify, deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
Incorrect Answers
This option addresses the distinct objective “Use an immutable image digest for exact deployment provenance”, not the immediate requirement. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. For the stated case, ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
This option addresses the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”, not the immediate requirement. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy. For the stated case, ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
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, ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
Question 482
A hospital uses one public hostname with path rules for separate appointment services. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. It supports this action: Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. To confirm, deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
Incorrect Answers
That statement explains the distinct objective “Use SLI and SLO measures to focus reliability objectives” rather than the cause in this case. The deciding mechanism here is that ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
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 ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
That statement explains the distinct objective “Understand ports, targetPort and protocol mapping in a Service” rather than the cause in this case. The deciding mechanism here is that ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
Question 483
A hospital uses one public hostname with path rules for separate appointment services. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status. This is the relevant test because ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
Incorrect Answers
This check would help evaluate the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”, but not the required result. For this case, deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
This check would help evaluate the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, but not the required result. For this case, deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
This check would help evaluate the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, but not the required result. For this case, deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
Question 484
A hospital uses one public hostname with path rules for separate appointment services. A shortcut is proposed: “Create an Ingress resource in a cluster with no Ingress controller and assume the platform automatically exposes a public endpoint.” Which technical consequence follows most closely?
Explanation
Correct Answer
The route remains nonfunctional because nothing reconciles it into an application traffic proxy. The shortcut creates this risk because ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
Incorrect Answers
That outcome concerns the distinct objective “Design a release rollback trigger from measurable service signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that the route remains nonfunctional because nothing reconciles it into an application traffic proxy.
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 route remains nonfunctional because nothing reconciles it into an application traffic proxy.
That outcome concerns the distinct objective “Investigate readiness failures separately from liveness-related restarts”; it is not the most direct consequence of this shortcut. The relevant consequence is that the route remains nonfunctional because nothing reconciles it into an application traffic proxy.
Question 485
A hospital uses one public hostname with path rules for separate appointment services. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Acceptance evidence: Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status. This pairing is justified because ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
Incorrect Answers
This action and check address the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence” instead of the stated acceptance requirement. The matching action is to define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Its confirming test is to deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
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 define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Its confirming test is to deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
This action and check address the distinct objective “Diagnose cluster DNS separately from Pod network reachability” instead of the stated acceptance requirement. The matching action is to define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Its confirming test is to deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
Question 486
A retailer wants an HTTP Gateway listener but has not installed a compatible Gateway API controller. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a retailer wants an HTTP Gateway listener but has not installed a compatible Gateway API controller. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. This resolves the issue because ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. To verify, deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
Incorrect Answers
This option addresses the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”, not the immediate requirement. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. For the stated case, ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
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, ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
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, ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
Question 487
A retailer wants an HTTP Gateway listener but has not installed a compatible Gateway API controller. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a retailer wants an HTTP Gateway listener but has not installed a compatible Gateway API controller. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. It supports this action: Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. To confirm, deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
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 ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
That statement explains the distinct objective “Use annotations for tool metadata rather than workload selection” rather than the cause in this case. The deciding mechanism here is that ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
The situation is that a retailer wants an HTTP Gateway listener but has not installed a compatible Gateway API controller. That statement explains the distinct objective “Understand ports, targetPort and protocol mapping in a Service” rather than the cause in this case. The deciding mechanism here is that ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
Question 488
A retailer wants an HTTP Gateway listener but has not installed a compatible Gateway API controller. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a retailer wants an HTTP Gateway listener but has not installed a compatible Gateway API controller. Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status. This is the relevant test because ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
Incorrect Answers
This check would help evaluate the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”, but not the required result. For this case, deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
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, deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
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, deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
Question 489
A retailer wants an HTTP Gateway listener but has not installed a compatible Gateway API controller. The team suggests: “Create an Ingress resource in a cluster with no Ingress controller and assume the platform automatically exposes a public endpoint.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a retailer wants an HTTP Gateway listener but has not installed a compatible Gateway API controller. The route remains nonfunctional because nothing reconciles it into an application traffic proxy. The shortcut creates this risk because ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
Incorrect Answers
That outcome concerns the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”; it is not the most direct consequence of this shortcut. The relevant consequence is that the route remains nonfunctional because nothing reconciles it into an application traffic proxy.
That outcome concerns the distinct objective “Understand taints and tolerations as repulsion controls”; it is not the most direct consequence of this shortcut. The relevant consequence is that the route remains nonfunctional because nothing reconciles it into an application traffic proxy.
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 route remains nonfunctional because nothing reconciles it into an application traffic proxy.
Question 490
A retailer wants an HTTP Gateway listener but has not installed a compatible Gateway API controller. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a retailer wants an HTTP Gateway listener but has not installed a compatible Gateway API controller. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Acceptance evidence: Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status. This pairing is justified because ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
Incorrect Answers
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 define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Its confirming test is to deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
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 define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Its confirming test is to deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
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 define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy. Its confirming test is to deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 51 - 10 Questions (Last Reviewed 01-Oct-2026)