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 33

Question 320

A public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. Which engineering change and test jointly addresses the scenario?

  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. 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.
  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. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data. Acceptance evidence: Create a disposable PVC with test content, delete its consuming Pod and then the claim, observing actual PV and backing volume behavior.

Explanation

Correct Answer

A:

The situation is that a public service team sees uneven replica counts after scaling and wants a defined scheduler spreading policy. 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. This pairing is justified because topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.

Incorrect Answers

B:

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 define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Its confirming test is to deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.

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 define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Its confirming test is to deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.

D:

This action and check address the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” instead of the stated acceptance requirement. The matching action is to define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones. Its confirming test is to deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.

Question 321

A university wants essential monitoring agents scheduled ahead of batch notebooks during scarcity. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability.
  2. Inspect the active kubeconfig context and namespace before applying manifests to staging or production.
  3. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes.
  4. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods.

Explanation

Correct Answer

D:

Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. This resolves the issue because under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply. To verify, simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Incorrect Answers

A:

This option addresses the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”, not the immediate requirement. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific. For the stated case, under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

B:

This option addresses the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, not the immediate requirement. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. For the stated case, under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

C:

This option addresses the distinct objective “Use nodeSelector to place a workload on nodes with required labels”, not the immediate requirement. The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. For the stated case, under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Question 322

A university wants essential monitoring agents scheduled ahead of batch notebooks during scarcity. Which causal explanation supports the intended design choice?

  1. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific.
  2. A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count.
  3. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.
  4. Linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

Explanation

Correct Answer

C:

Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply. It supports this action: Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. To confirm, simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Incorrect Answers

A:

That statement explains the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” rather than the cause in this case. The deciding mechanism here is that under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

B:

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 under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

D:

That statement explains the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” rather than the cause in this case. The deciding mechanism here is that under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Question 323

A university wants essential monitoring agents scheduled ahead of batch notebooks during scarcity. Which test provides the strongest evidence of a correct implementation?

  1. With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
  2. Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.
  3. Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.
  4. Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.

Explanation

Correct Answer

B:

Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule. This is the relevant test because under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, but not the required result. For this case, simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

C:

This check would help evaluate the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance”, but not the required result. For this case, simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

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, simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Question 324

A university wants essential monitoring agents scheduled ahead of batch notebooks during scarcity. A shortcut is proposed: “Assign maximum priority to every department workload and expect that all competing Pods gain guaranteed capacity.” Which technical consequence follows most closely?

  1. A migration fails because backend volume classes and cloud authentication semantics differ.
  2. The Pod might schedule on any other feasible node because tolerance is not a selection constraint.
  3. Priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption.
  4. The emergency fix disappears when the Pod is replaced and cannot be reproduced reliably.

Explanation

Correct Answer

C:

Priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption. The shortcut creates this risk because under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Incorrect Answers

A:

That outcome concerns the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”; it is not the most direct consequence of this shortcut. The relevant consequence is that priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption.

B:

That outcome concerns the distinct objective “Understand taints and tolerations as repulsion controls”; it is not the most direct consequence of this shortcut. The relevant consequence is that priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption.

D:

That outcome concerns the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift”; it is not the most direct consequence of this shortcut. The relevant consequence is that priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption.

Question 325

A university wants essential monitoring agents scheduled ahead of batch notebooks during scarcity. Which combined solution and independent check are most directly justified?

  1. 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.
  2. Inspect the active kubeconfig context and namespace before applying manifests to staging or production. Acceptance evidence: Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  3. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Acceptance evidence: Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.
  4. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Acceptance evidence: Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Explanation

Correct Answer

D:

Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Acceptance evidence: Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule. This pairing is justified because under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Incorrect Answers

A:

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 apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

B:

This action and check address the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster” instead of the stated acceptance requirement. The matching action is to apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

C:

This action and check address the distinct objective “Separate CI build verification from CD environment promotion” instead of the stated acceptance requirement. The matching action is to apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Question 326

A municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Review Sandbox, Incubating and Graduated CNCF stages as community maturity signals while independently assessing a project's fitness, lifecycle and security.
  2. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods.
  3. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation.
  4. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes.

Explanation

Correct Answer

B:

The situation is that a municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. This resolves the issue because under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply. To verify, simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Incorrect Answers

A:

This option addresses the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, not the immediate requirement. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects. For the stated case, under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

C:

This option addresses the distinct objective “Explain desired state versus observed status in Kubernetes objects”, not the immediate requirement. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. For the stated case, under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

D:

The situation is that a municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. This option addresses the distinct objective “Use nodeSelector to place a workload on nodes with required labels”, not the immediate requirement. The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities. For the stated case, under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Question 327

A municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. Which platform mechanism explains why the suitable approach works?

  1. The scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
  2. The scheduler enforces required node label matches in addition to resource and other constraints; labels do not create actual hardware capabilities.
  3. Canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
  4. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Explanation

Correct Answer

D:

The situation is that a municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply. It supports this action: Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. To confirm, simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Incorrect Answers

A:

That statement explains the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes” rather than the cause in this case. The deciding mechanism here is that under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

B:

That statement explains the distinct objective “Use nodeSelector to place a workload on nodes with required labels” rather than the cause in this case. The deciding mechanism here is that under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

C:

That statement explains the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” rather than the cause in this case. The deciding mechanism here is that under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Question 328

A municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. Which controlled observation would best validate the intended improvement?

  1. Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
  2. With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
  3. Deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
  4. Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Explanation

Correct Answer

D:

The situation is that a municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule. This is the relevant test because under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”, but not the required result. For this case, simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

B:

The situation is that a municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. This check would help evaluate the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, but not the required result. For this case, simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

C:

This check would help evaluate the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, but not the required result. For this case, simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Question 329

A municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. An engineer proposes: “Assign maximum priority to every department workload and expect that all competing Pods gain guaranteed capacity.” What adverse outcome would be most direct?

  1. The change is repeatedly reverted, making incident response and audit history inconsistent.
  2. The scheduler may evaluate an unintended Pod group or fail to spread the intended replicas.
  3. Priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption.
  4. Replacing the Pod destroys the only copy of business state unless independent durable storage exists.

Explanation

Correct Answer

C:

The situation is that a municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. Priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption. The shortcut creates this risk because under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Incorrect Answers

A:

That outcome concerns the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”; it is not the most direct consequence of this shortcut. The relevant consequence is that priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption.

B:

That outcome concerns the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”; it is not the most direct consequence of this shortcut. The relevant consequence is that priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption.

D:

That outcome concerns the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”; it is not the most direct consequence of this shortcut. The relevant consequence is that priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption.

Question 330

A municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. What pair of supported action and practical verification should be approved?

  1. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Acceptance evidence: Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.
  2. 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.
  3. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Acceptance evidence: Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.
  4. 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.

Explanation

Correct Answer

A:

The situation is that a municipal services platform prioritizes emergency alerts while preserving a minimum capacity plan for ordinary workloads. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Acceptance evidence: Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule. This pairing is justified because under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Incorrect Answers

B:

This action and check address the distinct objective “Explain the container runtime interface without conflating it with the control plane” instead of the stated acceptance requirement. The matching action is to apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

C:

This action and check address the distinct objective “Investigate readiness failures separately from liveness-related restarts” instead of the stated acceptance requirement. The matching action is to apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

D:

This action and check address the distinct objective “Use nodeSelector to place a workload on nodes with required labels” instead of the stated acceptance requirement. The matching action is to apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Its confirming test is to simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests