Practice Exams:

Linux Foundation KCNA Dumps

EXAM: Kubernetes and Cloud Native Associate
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

KCNA Premium Bundle


  • Premium File 333 Questions & Answers
  • Training Course 54 Lectures
  • Study Guide 410 Pages

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?

  1. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Acceptance evidence: Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
  2. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Acceptance evidence: Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
  3. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Acceptance evidence: Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.
  4. 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.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced.
  2. Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names.
  3. Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access.
  4. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding.
  2. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
  3. Pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints.
  4. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  2. Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
  3. Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
  4. Attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Replicas can collide on storage ownership and application state ordering assumptions fail.
  2. Name lookup may succeed but no usable endpoint exists to receive traffic.
  3. Pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
  4. A failed release can leave the service unavailable with no retained tested deployment revision.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team. Acceptance evidence: Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
  2. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Acceptance evidence: Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  3. 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.
  4. 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.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy.
  2. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior.
  3. Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names.
  4. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
  2. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
  3. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.
  4. A service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.
  2. Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
  3. Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
  4. Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Teams can share unintended network and resource access while administrators believe the naming boundary is protective.
  2. Pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
  3. The Pod might schedule on any other feasible node because tolerance is not a selection constraint.
  4. The change unnecessarily exposes a data service externally while the original DNS problem remains unresolved.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. 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.
  2. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Acceptance evidence: Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.
  3. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails. Acceptance evidence: Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
  4. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. Acceptance evidence: Inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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