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 7

Question 60

A science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. Which combined solution and independent check are most directly justified?

  1. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  2. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Acceptance evidence: Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
  3. Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Acceptance evidence: Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
  4. Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Acceptance evidence: Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Explanation

Correct Answer

A:

The situation is that a science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure. This pairing is justified because a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

Incorrect Answers

B:

This action and check address the distinct objective “Distinguish Deployment desired state from a manually created Pod” instead of the stated acceptance requirement. The matching action is to choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Its confirming test is to inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

C:

This action and check address the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources” instead of the stated acceptance requirement. The matching action is to choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Its confirming test is to inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

D:

This action and check address the distinct objective “Separate kube-scheduler decisions from kubelet execution” instead of the stated acceptance requirement. The matching action is to choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Its confirming test is to inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

Question 61

A platform team deploys an eBPF-based networking system that deliberately replaces kube-proxy. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Prefer documented Kubernetes APIs and interoperable telemetry formats when possible while identifying any platform-specific extensions needed for the real deployment.
  2. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC.
  3. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling.
  4. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior.

Explanation

Correct Answer

D:

Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. This resolves the issue because kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. To verify, read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Incorrect Answers

A:

This option addresses the distinct objective “Understand open standards and vendor-neutral community collaboration”, not the immediate requirement. Open standards and vendor-neutral governance reduce lock-in and support collaboration, but products can still differ in versions, implementations and operational capabilities. For the stated case, kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

B:

This option addresses the distinct objective “Distinguish etcd persistence from running workload data”, not the immediate requirement. Etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd. For the stated case, kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

C:

This option addresses the distinct objective “Explain the container runtime interface without conflating it with the control plane”, not the immediate requirement. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface. For the stated case, kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Question 62

A platform team deploys an eBPF-based networking system that deliberately replaces kube-proxy. Which causal explanation supports the intended design choice?

  1. etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
  2. kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.
  3. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
  4. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.

Explanation

Correct Answer

B:

Kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. It supports this action: Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. To confirm, read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Incorrect Answers

A:

That statement explains the distinct objective “Distinguish etcd persistence from running workload data” rather than the cause in this case. The deciding mechanism here is that kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

C:

That statement explains the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” rather than the cause in this case. The deciding mechanism here is that kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

D:

That statement explains the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” rather than the cause in this case. The deciding mechanism here is that kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Question 63

A platform team deploys an eBPF-based networking system that deliberately replaces kube-proxy. Which test provides the strongest evidence of a correct implementation?

  1. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  2. Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.
  3. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  4. Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Explanation

Correct Answer

D:

Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane. This is the relevant test because kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use Pods as the shared network and storage execution unit”, but not the required result. For this case, read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

B:

This check would help evaluate the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, but not the required result. For this case, read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

C:

This check would help evaluate the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, but not the required result. For this case, read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Question 64

A platform team deploys an eBPF-based networking system that deliberately replaces kube-proxy. A shortcut is proposed: “Declare the cluster broken solely because no kube-proxy DaemonSet exists in a documented proxy-replacement design.” Which technical consequence follows most closely?

  1. A workload remains nonfunctional and the persistent data dependency is never satisfied.
  2. A project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy.
  3. A working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.
  4. A control-plane restore might recover resource metadata while losing application records that were never backed up.

Explanation

Correct Answer

C:

A working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly. The shortcut creates this risk because kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Incorrect Answers

A:

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 a working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.

B:

That outcome concerns the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance”; it is not the most direct consequence of this shortcut. The relevant consequence is that a working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.

D:

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 a working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.

Question 65

A platform team deploys an eBPF-based networking system that deliberately replaces kube-proxy. Which combined solution and independent check are most directly justified?

  1. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Acceptance evidence: Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.
  2. Use a supported service mesh when fine-grained internal service-to-service security and telemetry are needed, while separately configuring north-south ingress or gateway exposure. Acceptance evidence: Test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.
  3. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Acceptance evidence: Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
  4. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate. Acceptance evidence: Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.

Explanation

Correct Answer

A:

Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Acceptance evidence: Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane. This pairing is justified because kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Incorrect Answers

B:

This action and check address the distinct objective “Distinguish service mesh traffic management from external ingress routing” instead of the stated acceptance requirement. The matching action is to identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Its confirming test is to read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

C:

This action and check address the distinct objective “Distinguish etcd persistence from running workload data” instead of the stated acceptance requirement. The matching action is to identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Its confirming test is to read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

D:

This action and check address the distinct objective “Use Pods as the shared network and storage execution unit” instead of the stated acceptance requirement. The matching action is to identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Its confirming test is to read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Question 66

A student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior.
  2. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image.
  3. Inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API.
  4. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup.

Explanation

Correct Answer

A:

The situation is that a student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. This resolves the issue because kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. To verify, read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Incorrect Answers

B:

This option addresses the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, not the immediate requirement. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. For the stated case, kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

C:

This option addresses the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, not the immediate requirement. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node. For the stated case, kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

D:

This option addresses the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, not the immediate requirement. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe. For the stated case, kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Question 67

A student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. Which causal explanation supports the intended design choice?

  1. etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
  2. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
  3. kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.
  4. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Explanation

Correct Answer

C:

The situation is that a student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. Kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. It supports this action: Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. To confirm, read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Incorrect Answers

A:

The situation is that a student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. That statement explains the distinct objective “Distinguish etcd persistence from running workload data” rather than the cause in this case. The deciding mechanism here is that kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

B:

That statement explains the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” rather than the cause in this case. The deciding mechanism here is that kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

D:

That statement explains the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend” rather than the cause in this case. The deciding mechanism here is that kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Question 68

A student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. Which test provides the strongest evidence of a correct implementation?

  1. Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
  2. Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.
  3. Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.
  4. Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.

Explanation

Correct Answer

B:

The situation is that a student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane. This is the relevant test because kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”, but not the required result. For this case, read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

C:

This check would help evaluate the distinct objective “Identify reconciliation work performed by kube-controller-manager”, but not the required result. For this case, read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

D:

This check would help evaluate the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”, but not the required result. For this case, read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Question 69

A student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. A shortcut is proposed: “Declare the cluster broken solely because no kube-proxy DaemonSet exists in a documented proxy-replacement design.” Which technical consequence follows most closely?

  1. Applications fail on migration when plugin behavior or provider-specific components were never evaluated.
  2. Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.
  3. A working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.
  4. The scheduler may legally use a non-preferred node, violating the policy that was mistakenly assumed mandatory.

Explanation

Correct Answer

C:

The situation is that a student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. A working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly. The shortcut creates this risk because kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Incorrect Answers

A:

That outcome concerns the distinct objective “Understand open standards and vendor-neutral community collaboration”; it is not the most direct consequence of this shortcut. The relevant consequence is that a working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.

B:

That outcome concerns the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”; it is not the most direct consequence of this shortcut. The relevant consequence is that a working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.

D:

That outcome concerns the distinct objective “Distinguish preferred node affinity from required scheduling rules”; it is not the most direct consequence of this shortcut. The relevant consequence is that a working dataplane may be needlessly modified, disrupting traffic that was already being forwarded correctly.

Question 70

A student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. Which combined solution and independent check are most directly justified?

  1. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Acceptance evidence: Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.
  2. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Acceptance evidence: Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.
  3. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
  4. Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Acceptance evidence: Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Explanation

Correct Answer

A:

The situation is that a student inspects a managed Kubernetes cluster where ClusterIP traffic works but kube-proxy Pods are absent. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Acceptance evidence: Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane. This pairing is justified because kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.

Incorrect Answers

B:

This action and check address the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts” instead of the stated acceptance requirement. The matching action is to identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Its confirming test is to read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

C:

This action and check address the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” instead of the stated acceptance requirement. The matching action is to identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Its confirming test is to read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

D:

This action and check address the distinct objective “Separate kube-scheduler decisions from kubelet execution” instead of the stated acceptance requirement. The matching action is to identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Its confirming test is to read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests