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 28

Question 270

An insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. What pair of supported action and practical verification should be approved?

  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. 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. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
  4. Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. Acceptance evidence: Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Explanation

Correct Answer

A:

The situation is that an insurer must enforce a regulated node pool while an optional app merely prefers cheaper workers. 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. This pairing is justified because a required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Incorrect Answers

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 use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

C:

This action and check address the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” instead of the stated acceptance requirement. The matching action is to use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

D:

This action and check address the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior” instead of the stated acceptance requirement. The matching action is to use requiredDuringSchedulingIgnoredDuringExecution for mandatory constraints and preferredDuringSchedulingIgnoredDuringExecution for a soft placement preference. Its confirming test is to test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.

Question 271

A community clinic wants identical front-end Pods distributed across at least two workers. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required.
  2. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate.
  3. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation.
  4. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads.

Explanation

Correct Answer

B:

Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. This resolves the issue because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. To verify, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

Incorrect Answers

A:

This option addresses the distinct objective “Understand taints and tolerations as repulsion controls”, not the immediate requirement. A NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node. For the stated case, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

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, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

D:

This option addresses the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”, not the immediate requirement. Kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events. For the stated case, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

Question 272

A community clinic wants identical front-end Pods distributed across at least two workers. 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. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.
  3. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.
  4. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

Explanation

Correct Answer

D:

Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. It supports this action: Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. To confirm, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

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 pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

B:

That statement explains the distinct objective “Correlate application rollout revisions with error spikes” rather than the cause in this case. The deciding mechanism here is that pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

C:

That statement explains the distinct objective “Explain the container runtime interface without conflating it with the control plane” rather than the cause in this case. The deciding mechanism here is that pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

Question 273

A community clinic wants identical front-end Pods distributed across at least two workers. Which controlled observation would best validate the intended improvement?

  1. Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
  2. Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.
  3. Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
  4. Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Explanation

Correct Answer

B:

Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers. This is the relevant test because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, but not the required result. For this case, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

C:

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, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

D:

This check would help evaluate the distinct objective “Distinguish Deployment desired state from a manually created Pod”, but not the required result. For this case, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

Question 274

A community clinic wants identical front-end Pods distributed across at least two workers. An engineer proposes: “Place all high-availability replicas on one worker and assume the ReplicaSet count alone protects against node loss.” What adverse outcome would be most direct?

  1. The image-pull issue stays unresolved because etcd is not the node component managing container starts.
  2. The workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
  3. A single node failure can take down all replicas despite a desired count greater than one.
  4. An untrusted dependency or replaced tag can run within otherwise well-configured Pods.

Explanation

Correct Answer

C:

A single node failure can take down all replicas despite a desired count greater than one. The shortcut creates this risk because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

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 a single node failure can take down all replicas despite a desired count greater than one.

B:

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 single node failure can take down all replicas despite a desired count greater than one.

D:

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 a single node failure can take down all replicas despite a desired count greater than one.

Question 275

A community clinic wants identical front-end Pods distributed across at least two workers. What pair of supported action and practical verification should be approved?

  1. Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Acceptance evidence: Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
  2. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Acceptance evidence: Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.
  3. 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.
  4. 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.

Explanation

Correct Answer

C:

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. This pairing is justified because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

Incorrect Answers

A:

This action and check address the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

B:

This action and check address the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

D:

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 configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

Question 276

A college live-stream service needs to avoid putting every replica on the same machine during exams. Which engineering approach is the most appropriate for this cloud-native case?

  1. Group tightly coupled containers that require the same Pod networking identity and optionally shared volumes into one Pod while keeping independently scalable services separate.
  2. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate.
  3. Require approved image registries, signature or digest verification and patch ownership when admitting production container images.
  4. Taint dedicated nodes and grant only intended workloads matching tolerations, combining node affinity when exclusive placement is required.

Explanation

Correct Answer

B:

The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. This resolves the issue because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. To verify, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

Incorrect Answers

A:

This option addresses the distinct objective “Use Pods as the shared network and storage execution unit”, not the immediate requirement. Containers in a Pod share a network namespace and IP address and can coordinate on localhost, while the Pod is scheduled as one unit. For the stated case, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

C:

This option addresses the distinct objective “Use image provenance and policy controls without trusting mutable tags”, not the immediate requirement. Image provenance reduces accidental or malicious image substitution; mutable tags alone cannot prove build integrity or content identity. For the stated case, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

D:

The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. This option addresses the distinct objective “Understand taints and tolerations as repulsion controls”, not the immediate requirement. A NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node. For the stated case, pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

Question 277

A college live-stream service needs to avoid putting every replica on the same machine during exams. What infrastructure principle makes the correct treatment effective?

  1. Healthy direct IP connectivity with failed name resolution suggests a DNS path issue; failed Pod-to-Pod IP traffic suggests a lower-level network problem.
  2. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
  3. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.
  4. The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.

Explanation

Correct Answer

C:

The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. It supports this action: Configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. To confirm, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

Incorrect Answers

A:

That statement explains the distinct objective “Diagnose cluster DNS separately from Pod network reachability” rather than the cause in this case. The deciding mechanism here is that pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

B:

That statement explains the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” rather than the cause in this case. The deciding mechanism here is that pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

D:

That statement explains the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” rather than the cause in this case. The deciding mechanism here is that pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

Question 278

A college live-stream service needs to avoid putting every replica on the same machine during exams. 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. Compare the governance and release activity of two projects and document which operational support and security tests are still required.
  3. Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  4. Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

Explanation

Correct Answer

A:

The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. Deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers. This is the relevant test because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

Incorrect Answers

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, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

C:

This check would help evaluate the distinct objective “Use nodeSelector to place a workload on nodes with required labels”, but not the required result. For this case, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

D:

This check would help evaluate the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, but not the required result. For this case, deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

Question 279

A college live-stream service needs to avoid putting every replica on the same machine during exams. The change review contains this proposal: “Place all high-availability replicas on one worker and assume the ReplicaSet count alone protects against node loss.” What risk matters most?

  1. The planned maintenance causes avoidable downtime because no safe application replica remains available.
  2. Priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption.
  3. The team may gain Pod access across all namespaces, expanding exposure beyond its job.
  4. A single node failure can take down all replicas despite a desired count greater than one.

Explanation

Correct Answer

D:

The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. A single node failure can take down all replicas despite a desired count greater than one. The shortcut creates this risk because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”; it is not the most direct consequence of this shortcut. The relevant consequence is that a single node failure can take down all replicas despite a desired count greater than one.

B:

That outcome concerns the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”; it is not the most direct consequence of this shortcut. The relevant consequence is that a single node failure can take down all replicas despite a desired count greater than one.

C:

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 single node failure can take down all replicas despite a desired count greater than one.

Question 280

A college live-stream service needs to avoid putting every replica on the same machine during exams. Which implementation together with matching acceptance evidence best meets this case?

  1. 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.
  2. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Acceptance evidence: In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  3. 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.
  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

A:

The situation is that a college live-stream service needs to avoid putting every replica on the same machine during exams. 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. This pairing is justified because pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes.

Incorrect Answers

B:

This action and check address the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

C:

This action and check address the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

D:

This action and check address the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability” instead of the stated acceptance requirement. The matching action is to configure anti-affinity against other Pods with a specific label so replicas prefer or require separate failure domains as appropriate. Its confirming test is to deploy replicas with hostname anti-affinity and inspect their node placements in a cluster with enough eligible workers.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests