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 30

Question 290

A retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Which combined solution and independent check are most directly justified?

  1. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Acceptance evidence: In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.
  2. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Acceptance evidence: Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
  3. Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Acceptance evidence: Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
  4. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Acceptance evidence: Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

Explanation

Correct Answer

C:

The situation is that a retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Acceptance evidence: Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately. This pairing is justified because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.

Incorrect Answers

A:

This action and check address the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” instead of the stated acceptance requirement. The matching action is to choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Its confirming test is to apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

B:

This action and check address the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” instead of the stated acceptance requirement. The matching action is to choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Its confirming test is to apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

D:

This action and check address the distinct objective “Use Events and pod describe for failed volume mounting” instead of the stated acceptance requirement. The matching action is to choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Its confirming test is to apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.

Question 291

A university reserves certain machines for resource-intensive research tasks. Which engineering approach is the most appropriate for this cloud-native case?

  1. Taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required.
  2. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods.
  3. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance.
  4. Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected.

Explanation

Correct Answer

A:

Taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. This resolves the issue because a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node. To verify, taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

Incorrect Answers

B:

This option addresses the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, not the immediate requirement. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply. For the stated case, a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

C:

This option addresses the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”, not the immediate requirement. A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count. For the stated case, a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

D:

This option addresses the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, not the immediate requirement. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. For the stated case, a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

Question 292

A university reserves certain machines for resource-intensive research tasks. What infrastructure principle makes the correct treatment effective?

  1. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
  2. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node.
  3. A NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.
  4. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.

Explanation

Correct Answer

C:

A NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node. It supports this action: Taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. To confirm, taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

Incorrect Answers

A:

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 a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

B:

That statement explains the distinct objective “Recognize the kubelet role in local Pod lifecycle management” rather than the cause in this case. The deciding mechanism here is that a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

D:

That statement explains the distinct objective “Build meaningful alert rules and route notifications through Alertmanager” rather than the cause in this case. The deciding mechanism here is that a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

Question 293

A university reserves certain machines for resource-intensive research tasks. What verification result would most convincingly distinguish a working solution from a claim?

  1. Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
  2. Taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.
  3. Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
  4. Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Explanation

Correct Answer

B:

Taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration. This is the relevant test because a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, but not the required result. For this case, taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

C:

This check would help evaluate the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”, but not the required result. For this case, taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

D:

This check would help evaluate the distinct objective “Use an immutable image digest for exact deployment provenance”, but not the required result. For this case, taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

Question 294

A university reserves certain machines for resource-intensive research tasks. The change review contains this proposal: “Add a toleration to a Pod and claim the scheduler is now required to place it on the dedicated node.” What risk matters most?

  1. The Pod might schedule on any other feasible node because tolerance is not a selection constraint.
  2. A workload continues crashing because the root cause is memory exhaustion, not name resolution.
  3. A failed release can leave the service unavailable with no retained tested deployment revision.
  4. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.

Explanation

Correct Answer

A:

The Pod might schedule on any other feasible node because tolerance is not a selection constraint. The shortcut creates this risk because a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

Incorrect Answers

B:

That outcome concerns the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Pod might schedule on any other feasible node because tolerance is not a selection constraint.

C:

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 the Pod might schedule on any other feasible node because tolerance is not a selection constraint.

D:

That outcome concerns the distinct objective “Distinguish service mesh traffic management from external ingress routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Pod might schedule on any other feasible node because tolerance is not a selection constraint.

Question 295

A university reserves certain machines for resource-intensive research tasks. Which implementation together with matching acceptance evidence best meets this case?

  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. Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. Acceptance evidence: Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
  3. Pin validated production images by registry digest and promote the same signed artifact across environments. Acceptance evidence: Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.
  4. 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.

Explanation

Correct Answer

D:

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. This pairing is justified because a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

Incorrect Answers

A:

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 taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. Its confirming test is to taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

B:

This action and check address the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” instead of the stated acceptance requirement. The matching action is to taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. Its confirming test is to taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

C:

This action and check address the distinct objective “Use an immutable image digest for exact deployment provenance” instead of the stated acceptance requirement. The matching action is to taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. Its confirming test is to taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

Question 296

A hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. Which engineering approach is the most appropriate for this cloud-native case?

  1. 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.
  2. Taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required.
  3. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods.
  4. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload.

Explanation

Correct Answer

B:

The situation is that a hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. Taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. This resolves the issue because a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node. To verify, taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

Incorrect Answers

A:

This option addresses the distinct objective “Distinguish service mesh traffic management from external ingress routing”, not the immediate requirement. Service meshes commonly use proxies or ambient dataplanes to control east-west traffic; ingress/gateway handling addresses entry routes and can integrate with the mesh. For the stated case, a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

C:

The situation is that a hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. This option addresses the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, not the immediate requirement. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply. For the stated case, a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

D:

This option addresses the distinct objective “Use kubectl get and describe for distinct inspection needs”, not the immediate requirement. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. For the stated case, a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

Question 297

A hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. What infrastructure principle makes the correct treatment effective?

  1. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.
  2. A NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.
  3. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.
  4. A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.

Explanation

Correct Answer

B:

The situation is that a hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. A NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node. It supports this action: Taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. To confirm, taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

Incorrect Answers

A:

That statement explains the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability” rather than the cause in this case. The deciding mechanism here is that a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

C:

That statement explains the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” rather than the cause in this case. The deciding mechanism here is that a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

D:

That statement explains the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts” rather than the cause in this case. The deciding mechanism here is that a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

Question 298

A hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. 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. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  3. Set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.
  4. Taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

Explanation

Correct Answer

D:

The situation is that a hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. Taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration. This is the relevant test because a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

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, taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

B:

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, taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

C:

This check would help evaluate the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, but not the required result. For this case, taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

Question 299

A hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. The change review contains this proposal: “Add a toleration to a Pod and claim the scheduler is now required to place it on the dedicated node.” What risk matters most?

  1. The image-pull issue stays unresolved because etcd is not the node component managing container starts.
  2. An untrusted dependency or replaced tag can run within otherwise well-configured Pods.
  3. The Pod might schedule on any other feasible node because tolerance is not a selection constraint.
  4. The Pod remains unschedulable because requested capacity and node feasibility did not change.

Explanation

Correct Answer

C:

The situation is that a hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. The Pod might schedule on any other feasible node because tolerance is not a selection constraint. The shortcut creates this risk because a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

Incorrect Answers

A:

That outcome concerns the distinct objective “Recognize the kubelet role in local Pod lifecycle management”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Pod might schedule on any other feasible node because tolerance is not a selection constraint.

B:

That outcome concerns the distinct objective “Use image provenance and policy controls without trusting mutable tags”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Pod might schedule on any other feasible node because tolerance is not a selection constraint.

D:

That outcome concerns the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Pod might schedule on any other feasible node because tolerance is not a selection constraint.

Question 300

A hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. Which implementation together with matching acceptance evidence best meets this case?

  1. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Acceptance evidence: Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
  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. 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.
  4. Use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Acceptance evidence: Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Explanation

Correct Answer

C:

The situation is that a hosting provider taints maintenance workers and needs to distinguish tolerated jobs from guaranteed placement. 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. This pairing is justified because a NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

Incorrect Answers

A:

This action and check address the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” instead of the stated acceptance requirement. The matching action is to taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. Its confirming test is to taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

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 taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. Its confirming test is to taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

D:

This action and check address the distinct objective “Distinguish preferred node affinity from required scheduling rules” instead of the stated acceptance requirement. The matching action is to taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required. Its confirming test is to taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests