Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 45
Question 440
A university Dockerfile accidentally copies a private development configuration into a public runtime layer. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a university Dockerfile accidentally copies a private development configuration into a public runtime layer. Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Acceptance evidence: Compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts. This pairing is justified because multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer.
Incorrect Answers
This action and check address the distinct objective “Distinguish a container image from a running container and its writable layer” instead of the stated acceptance requirement. The matching action is to separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Its confirming test is to compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
This action and check address the distinct objective “Use namespaces as organizational scopes without treating them as firewalls” instead of the stated acceptance requirement. The matching action is to separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Its confirming test is to compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
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 separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Its confirming test is to compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
Question 441
A college test cluster starts two Pods on separate workers but direct Pod IP traffic fails. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names. This resolves the issue 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. To verify, deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
Incorrect Answers
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, Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
This option addresses the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”, not the immediate requirement. Service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure. For the stated case, Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
This option addresses the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, not the immediate requirement. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. For the stated case, Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
Question 442
A college test cluster starts two Pods on separate workers but direct Pod IP traffic fails. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints. It supports this action: Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names. To confirm, deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
Incorrect Answers
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 Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
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 Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
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 Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
Question 443
A college test cluster starts two Pods on separate workers but direct Pod IP traffic fails. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP. This is the relevant test 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 check would help evaluate the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, but not the required result. For this case, deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
This check would help evaluate the distinct objective “Distinguish Deployment desired state from a manually created Pod”, but not the required result. For this case, deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
This check would help evaluate the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, but not the required result. For this case, deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
Question 444
A college test cluster starts two Pods on separate workers but direct Pod IP traffic fails. The change review contains this proposal: “Assume creating a Service object itself installs and configures the missing cluster Pod network plugin.” What risk matters most?
Explanation
Correct Answer
Pods may start but remain unable to communicate across nodes because the CNI dataplane was never established. The shortcut creates this risk 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
That outcome concerns the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”; it is not the most direct consequence of this shortcut. The relevant consequence is that pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
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 pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
That outcome concerns the distinct objective “Use rollout status and undo to validate and recover a Deployment release”; it is not the most direct consequence of this shortcut. The relevant consequence is that pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
Question 445
A college test cluster starts two Pods on separate workers but direct Pod IP traffic fails. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
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 “Build meaningful alert rules and route notifications through Alertmanager” 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 “Distinguish Pod IPs from stable Services during rescheduling” 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 “Use EndpointSlices to connect Service selectors with actual backend Pods” 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 446
A regional retailer deploys networking add-ons and needs to distinguish CNI setup from Service object configuration. What technical action should the platform team take in this situation?
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. This resolves the issue 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. To verify, deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
Incorrect Answers
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, Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
This option addresses the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”, not the immediate requirement. Kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. For the stated case, Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
This option addresses the distinct objective “Understand CSI drivers and volume attachment responsibilities”, not the immediate requirement. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities. For the stated case, Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
Question 447
A regional retailer deploys networking add-ons and needs to distinguish CNI setup from Service object configuration. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a regional retailer deploys networking add-ons and needs to distinguish CNI setup from Service object configuration. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints. It supports this action: Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names. To confirm, deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
Incorrect Answers
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 Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
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 Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
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 Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
Question 448
A regional retailer deploys networking add-ons and needs to distinguish CNI setup from Service object configuration. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a regional retailer deploys networking add-ons and needs to distinguish CNI setup from Service object configuration. Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP. This is the relevant test 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 check would help evaluate the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”, but not the required result. For this case, deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
This check would help evaluate the distinct objective “Design a release rollback trigger from measurable service signals”, but not the required result. For this case, deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
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, deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
Question 449
A regional retailer deploys networking add-ons and needs to distinguish CNI setup from Service object configuration. The team suggests: “Assume creating a Service object itself installs and configures the missing cluster Pod network plugin.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a regional retailer deploys networking add-ons and needs to distinguish CNI setup from Service object configuration. Pods may start but remain unable to communicate across nodes because the CNI dataplane was never established. The shortcut creates this risk 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
That outcome concerns the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”; it is not the most direct consequence of this shortcut. The relevant consequence is that pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
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 pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
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 pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 43 - 10 Questions (Last Reviewed 09-Oct-2026)
- 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)