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 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?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped.
  2. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy.
  3. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced.
  4. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
  2. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.
  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. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.
  2. Compare a Service's label selector, EndpointSlices and Pod readiness conditions before changing external load-balancer settings.
  3. Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
  4. Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. Sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
  2. A control-plane restore might recover resource metadata while losing application records that were never backed up.
  3. Pods may start but remain unable to communicate across nodes because the CNI dataplane was never established.
  4. Packets reach the wrong destination socket and the Service appears unavailable despite healthy Pod processes.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. 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.
  2. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Acceptance evidence: In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  3. 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.
  4. 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.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled.
  2. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy.
  3. Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names.
  4. Configure readiness to stop sending Service traffic to an unready Pod, liveness to restart an unhealthy container and startup to allow slow initialization.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
  2. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
  3. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities.
  4. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.
  2. Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
  3. Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  4. Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Requests fail after a replica is replaced because the client bypassed the Service abstraction.
  2. The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.
  3. Sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.
  4. A workload remains nonfunctional and the persistent data dependency is never satisfied.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Acceptance evidence: Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
  2. Select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Acceptance evidence: Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  3. 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.
  4. 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.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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