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 26

Question 250

A small university cluster has spare average CPU but a large requested burst prevents one job from scheduling. Which implementation together with matching acceptance evidence best meets this case?

  1. Taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. Acceptance evidence: Taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.
  2. Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. Acceptance evidence: Set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
  3. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Acceptance evidence: Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
  4. Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Acceptance evidence: Test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.

Explanation

Correct Answer

B:

The situation is that a small university cluster has spare average CPU but a large requested burst prevents one job from scheduling. Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. Acceptance evidence: Set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it. This pairing is justified because the scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.

Incorrect Answers

A:

This action and check address the distinct objective “Understand taints and tolerations as repulsion controls” instead of the stated acceptance requirement. The matching action is to set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. Its confirming test is to set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.

C:

This action and check address the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts” instead of the stated acceptance requirement. The matching action is to set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. Its confirming test is to set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.

D:

This action and check address the distinct objective “Diagnose cluster DNS separately from Pod network reachability” instead of the stated acceptance requirement. The matching action is to set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources. Its confirming test is to set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.

Question 251

A media service needs to run on the small set of verified SSD-backed workers. Which engineering approach is the most appropriate for this cloud-native case?

  1. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces.
  2. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure.
  3. Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root.
  4. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes.

Explanation

Correct Answer

D:

Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. This resolves the issue because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. To verify, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

Incorrect Answers

A:

This option addresses the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”, not the immediate requirement. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains. For the stated case, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

B:

This option addresses the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, not the immediate requirement. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. For the stated case, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

C:

This option addresses the distinct objective “Run images with least-privilege runtime security contexts”, not the immediate requirement. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised. For the stated case, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Question 252

A media service needs to run on the small set of verified SSD-backed workers. What infrastructure principle makes the correct treatment effective?

  1. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
  2. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings.
  3. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
  4. The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Explanation

Correct Answer

D:

The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. It supports this action: Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. To confirm, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

Incorrect Answers

A:

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 the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

B:

That statement explains the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” rather than the cause in this case. The deciding mechanism here is that the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

C:

That statement explains the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” rather than the cause in this case. The deciding mechanism here is that the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Question 253

A media service needs to run on the small set of verified SSD-backed workers. What verification result would most convincingly distinguish a working solution from a claim?

  1. Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  2. Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
  3. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  4. Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.

Explanation

Correct Answer

A:

Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker. This is the relevant test because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Incorrect Answers

B:

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, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

C:

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, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

D:

This check would help evaluate the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”, but not the required result. For this case, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

Question 254

A media service needs to run on the small set of verified SSD-backed workers. The change review contains this proposal: “Put disk=ssd on a node metadata record that has no SSD and assume labeling physically upgrades the disk.” What risk matters most?

  1. The team may gain Pod access across all namespaces, expanding exposure beyond its job.
  2. A control-plane restore might recover resource metadata while losing application records that were never backed up.
  3. The workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
  4. A scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.

Explanation

Correct Answer

D:

A scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory. The shortcut creates this risk because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Incorrect Answers

A:

That outcome concerns the distinct objective “Distinguish ClusterRoles from Roles and binding scope”; it is not the most direct consequence of this shortcut. The relevant consequence is that a scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.

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 a scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.

C:

That outcome concerns the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions”; it is not the most direct consequence of this shortcut. The relevant consequence is that a scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.

Question 255

A media service needs to run on the small set of verified SSD-backed workers. Which implementation together with matching acceptance evidence best meets this case?

  1. Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Acceptance evidence: Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
  2. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  3. Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Acceptance evidence: Deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
  4. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Acceptance evidence: Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.

Explanation

Correct Answer

B:

Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker. This pairing is justified because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Incorrect Answers

A:

This action and check address the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” instead of the stated acceptance requirement. The matching action is to label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

C:

This action and check address the distinct objective “Run images with least-privilege runtime security contexts” instead of the stated acceptance requirement. The matching action is to label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

D:

This action and check address the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts” instead of the stated acceptance requirement. The matching action is to label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

Question 256

A university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. Which engineering approach is the most appropriate for this cloud-native case?

  1. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes.
  2. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy.
  3. Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones.
  4. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior.

Explanation

Correct Answer

A:

The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. This resolves the issue because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. To verify, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

Incorrect Answers

B:

This option addresses the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, not the immediate requirement. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. For the stated case, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

C:

This option addresses the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, not the immediate requirement. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable. For the stated case, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

D:

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, the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Question 257

A university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. What infrastructure principle makes the correct treatment effective?

  1. A Service exposes port to clients and forwards to targetPort on selected endpoints; a mismatched targetPort can break delivery even with valid DNS and selectors.
  2. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
  3. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
  4. The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Explanation

Correct Answer

D:

The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. It supports this action: Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. To confirm, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

Incorrect Answers

A:

That statement explains the distinct objective “Understand ports, targetPort and protocol mapping in a Service” rather than the cause in this case. The deciding mechanism here is that the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

B:

The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. That statement explains the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” rather than the cause in this case. The deciding mechanism here is that the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

C:

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 the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Question 258

A university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. What verification result would most convincingly distinguish a working solution from a claim?

  1. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  2. Compare the governance and release activity of two projects and document which operational support and security tests are still required.
  3. Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.
  4. Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

Explanation

Correct Answer

D:

The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker. This is the relevant test because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Incorrect Answers

A:

The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. 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, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

B:

This check would help evaluate the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, but not the required result. For this case, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

C:

This check would help evaluate the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, but not the required result. For this case, label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

Question 259

A university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. The change review contains this proposal: “Put disk=ssd on a node metadata record that has no SSD and assume labeling physically upgrades the disk.” What risk matters most?

  1. The workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
  2. Teams can share unintended network and resource access while administrators believe the naming boundary is protective.
  3. Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.
  4. A scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.

Explanation

Correct Answer

D:

The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. A scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory. The shortcut creates this risk because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Incorrect Answers

A:

The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. That outcome concerns the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions”; it is not the most direct consequence of this shortcut. The relevant consequence is that a scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.

B:

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 a scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.

C:

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 scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.

Question 260

A university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. Which implementation together with matching acceptance evidence best meets this case?

  1. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Acceptance evidence: Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  2. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Acceptance evidence: List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
  3. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  4. 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.

Explanation

Correct Answer

C:

The situation is that a university GPU lab uses node labels to keep non-GPU tutorial Pods away from specialized compute nodes. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker. This pairing is justified because the scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.

Incorrect Answers

A:

This action and check address the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” instead of the stated acceptance requirement. The matching action is to label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

B:

This action and check address the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership” instead of the stated acceptance requirement. The matching action is to label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

D:

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 label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Its confirming test is to label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests