Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 29
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?
Explanation
Correct Answer
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
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.
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.
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.
Question 281
A small analytics service prefers being scheduled near a low-latency cache. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. This resolves the issue because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. To verify, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
Incorrect Answers
This option addresses the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”, not the immediate requirement. Pod anti-affinity considers labels on existing Pods and topology keys such as hostname; it does not directly guarantee unlimited nodes. For the stated case, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
This option addresses the distinct objective “Design a release rollback trigger from measurable service signals”, not the immediate requirement. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. For the stated case, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
This option addresses the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”, not the immediate requirement. The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. For the stated case, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
Question 282
A small analytics service prefers being scheduled near a low-latency cache. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. It supports this action: Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. To confirm, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
Incorrect Answers
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 pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
That statement explains the distinct objective “Run images with least-privilege runtime security contexts” rather than the cause in this case. The deciding mechanism here is that pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
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 pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
Question 283
A small analytics service prefers being scheduled near a low-latency cache. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately. This is the relevant test because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
Incorrect Answers
This check would help evaluate the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, but not the required result. For this case, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
This check would help evaluate the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, but not the required result. For this case, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
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, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
Question 284
A small analytics service prefers being scheduled near a low-latency cache. The change review contains this proposal: “Set podAffinity for a backend and treat same-node placement as authorization to read another Pod's private files.” What risk matters most?
Explanation
Correct Answer
The workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured. The shortcut creates this risk because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
Incorrect Answers
That outcome concerns the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
That outcome concerns the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
That outcome concerns the distinct objective “Explain the container runtime interface without conflating it with the control plane”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
Question 285
A small analytics service prefers being scheduled near a low-latency cache. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
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
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 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.
This action and check address the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” 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.
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 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 286
A retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
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. This resolves the issue because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. To verify, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
Incorrect Answers
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, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
This option addresses the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, not the immediate requirement. Mounted credentials can enable Kubernetes API calls from a compromised container; explicit token exposure and RBAC scope limit abuse. For the stated case, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
This option addresses the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”, not the immediate requirement. The kube-apiserver validates authorized API requests and exposes the declarative resource interface; kubelets and controllers subsequently reconcile the saved desired state. For the stated case, pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
Question 287
A retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
The situation is that a retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules. It supports this action: Choose Pod affinity only when co-locating related workloads is beneficial and verify independent network policies still govern traffic. To confirm, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
Incorrect Answers
That statement explains the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” rather than the cause in this case. The deciding mechanism here is that pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
That statement explains the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” rather than the cause in this case. The deciding mechanism here is that pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
That statement explains the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” rather than the cause in this case. The deciding mechanism here is that pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
Question 288
A retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
The situation is that a retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. Apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately. This is the relevant test because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
Incorrect Answers
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, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
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, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
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, apply a preferred Pod affinity against a cache Pod label and inspect node placement while testing access policy separately.
Question 289
A retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. A shortcut is proposed: “Set podAffinity for a backend and treat same-node placement as authorization to read another Pod's private files.” Which technical consequence follows most closely?
Explanation
Correct Answer
The situation is that a retailer considers co-locating a helper with a reporting service but must preserve namespace network isolation. The workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured. The shortcut creates this risk because pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
Incorrect Answers
That outcome concerns the distinct objective “Use Pod anti-affinity to reduce correlated replica failure”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
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 workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
That outcome concerns the distinct objective “Understand open standards and vendor-neutral community collaboration”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload may be placed nearby but access-control enforcement remains unchanged or incorrectly configured.
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?
Explanation
Correct Answer
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
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.
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.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 27 - 10 Questions (Last Reviewed 25-Oct-2026)
- Linux Foundation KCNA Practice Test 28 - 10 Questions (Last Reviewed 24-Oct-2026)
- Linux Foundation KCNA Practice Test 29 - 10 Questions (Last Reviewed 23-Oct-2026)
- Linux Foundation KCNA Practice Test 30 - 10 Questions (Last Reviewed 22-Oct-2026)
- Linux Foundation KCNA Practice Test 31 - 10 Questions (Last Reviewed 21-Oct-2026)