Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 50
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.
Question 491
A university needs test Pods isolated from research databases except for an approved metrics path. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. This resolves the issue because networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support. To verify, check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
Incorrect Answers
This option addresses the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, not the immediate requirement. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller. For the stated case, networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
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, networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
This option addresses the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”, not the immediate requirement. A StorageClass defines how storage is provisioned and may use WaitForFirstConsumer to delay provisioning until scheduling requirements are known. For the stated case, networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
Question 492
A university needs test Pods isolated from research databases except for an approved metrics path. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support. It supports this action: Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. To confirm, check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
Incorrect Answers
That statement explains the distinct objective “Explain metrics, logs and traces as complementary observability signals” rather than the cause in this case. The deciding mechanism here is that networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
That statement explains the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs” rather than the cause in this case. The deciding mechanism here is that networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
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 networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
Question 493
A university needs test Pods isolated from research databases except for an approved metrics path. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection. This is the relevant test because networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
Incorrect Answers
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, check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
This check would help evaluate the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”, but not the required result. For this case, check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
This check would help evaluate the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, but not the required result. For this case, check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
Question 494
A university needs test Pods isolated from research databases except for an approved metrics path. An engineer proposes: “Write a default-deny NetworkPolicy and claim all cross-namespace traffic is blocked without testing plugin enforcement.” What adverse outcome would be most direct?
Explanation
Correct Answer
Sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy. The shortcut creates this risk because networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
Incorrect Answers
That outcome concerns the distinct objective “Distinguish etcd persistence from running workload data”; it is not the most direct consequence of this shortcut. The relevant consequence is that sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
That outcome concerns the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
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 sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
Question 495
A university needs test Pods isolated from research databases except for an approved metrics path. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Acceptance evidence: Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection. This pairing is justified because networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
Incorrect Answers
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 apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Its confirming test is to check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
This action and check address the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” instead of the stated acceptance requirement. The matching action is to apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Its confirming test is to check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
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 apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Its confirming test is to check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
Question 496
A council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
The situation is that a council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. This resolves the issue because networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support. To verify, check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
Incorrect Answers
This option addresses the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, not the immediate requirement. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image. For the stated case, networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
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, networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
This option addresses the distinct objective “Understand readiness, liveness and startup probes as different signals”, not the immediate requirement. Readiness affects endpoint eligibility while liveness can cause restarts; a startup probe defers other probe checks until initialization succeeds. For the stated case, networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
Question 497
A council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support. It supports this action: Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. To confirm, check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
Incorrect Answers
That statement explains the distinct objective “Design a release rollback trigger from measurable service signals” rather than the cause in this case. The deciding mechanism here is that networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
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 networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
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 networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
Question 498
A council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection. This is the relevant test because networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
Incorrect Answers
This check would help evaluate the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, but not the required result. For this case, check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
This check would help evaluate the distinct objective “Define secure release governance with staged approvals and policy verification”, but not the required result. For this case, check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
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, check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
Question 499
A council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. The change review contains this proposal: “Write a default-deny NetworkPolicy and claim all cross-namespace traffic is blocked without testing plugin enforcement.” What risk matters most?
Explanation
Correct Answer
The situation is that a council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. Sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy. The shortcut creates this risk because networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
Incorrect Answers
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 sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
That outcome concerns the distinct objective “Identify reconciliation work performed by kube-controller-manager”; it is not the most direct consequence of this shortcut. The relevant consequence is that sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
That outcome concerns the distinct objective “Use Events and pod describe for failed volume mounting”; it is not the most direct consequence of this shortcut. The relevant consequence is that sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
Question 500
A council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a council sees cross-namespace packets despite a seemingly correct policy and must inspect CNI behavior. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Acceptance evidence: Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection. This pairing is justified because networkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
Incorrect Answers
This action and check address the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” instead of the stated acceptance requirement. The matching action is to apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Its confirming test is to check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
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 apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Its confirming test is to check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
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 apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Its confirming test is to check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 52 - 10 Questions (Last Reviewed 30-Sep-2026)