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 66

Question 650

A small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. Which implementation together with matching acceptance evidence best meets this case?

  1. Configure readiness to stop sending Service traffic to an unready Pod, liveness to restart an unhealthy container and startup to allow slow initialization. Acceptance evidence: Delay a synthetic app response and compare EndpointSlice readiness with restart counts under controlled probe settings.
  2. Require verified API server certificates, properly scoped identities and audit policy rather than turning off certificate checks for convenience. Acceptance evidence: With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
  3. Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Acceptance evidence: Test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
  4. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Acceptance evidence: Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Explanation

Correct Answer

C:

The situation is that a small bank has cross-node Pod IP failures as well as DNS failures after changing the network plugin. Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Acceptance evidence: Test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails. This pairing is justified because 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.

Incorrect Answers

A:

This action and check address the distinct objective “Understand readiness, liveness and startup probes as different signals” instead of the stated acceptance requirement. The matching action is to run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Its confirming test is to test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.

B:

This action and check address the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” instead of the stated acceptance requirement. The matching action is to run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Its confirming test is to test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.

D:

This action and check address the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” instead of the stated acceptance requirement. The matching action is to run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints. Its confirming test is to test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.

Question 651

A hospital cluster loses one worker after a maintenance reboot and several Pods remain unavailable. What technical action should the platform team take in this situation?

  1. Review Sandbox, Incubating and Graduated CNCF stages as community maturity signals while independently assessing a project's fitness, lifecycle and security.
  2. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads.
  3. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used.
  4. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code.

Explanation

Correct Answer

B:

Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. This resolves the issue because a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid. To verify, simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

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, a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

C:

This option addresses the distinct objective “Understand ports, targetPort and protocol mapping in a Service”, not the immediate requirement. A Service exposes port to clients and forwards to targetPort on selected endpoints; a mismatched targetPort can break delivery even with valid DNS and selectors. For the stated case, a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

D:

This option addresses the distinct objective “Use Events and pod describe for failed volume mounting”, not the immediate requirement. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. For the stated case, a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Question 652

A hospital cluster loses one worker after a maintenance reboot and several Pods remain unavailable. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.
  2. 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.
  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. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

Explanation

Correct Answer

A:

A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid. It supports this action: Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. To confirm, simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Incorrect Answers

B:

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 a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

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 a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

D:

That statement explains the distinct objective “Use Events and pod describe for failed volume mounting” rather than the cause in this case. The deciding mechanism here is that a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Question 653

A hospital cluster loses one worker after a maintenance reboot and several Pods remain unavailable. What acceptance check most directly confirms this requirement is met?

  1. Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.
  2. In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  3. Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.
  4. Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.

Explanation

Correct Answer

A:

Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible. This is the relevant test because a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, but not the required result. For this case, simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

C:

This check would help evaluate the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, but not the required result. For this case, simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

D:

This check would help evaluate the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, but not the required result. For this case, simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Question 654

A hospital cluster loses one worker after a maintenance reboot and several Pods remain unavailable. The team suggests: “Delete every Deployment in the cluster because one node's kubelet cannot contact the control plane.” Which failure should the reviewer anticipate?

  1. The Service still has no ready endpoints and clients continue to encounter unavailable responses.
  2. Replacing the Pod destroys the only copy of business state unless independent durable storage exists.
  3. Healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.
  4. Sensitive traffic may remain allowed because the networking implementation does not enforce the declared policy.

Explanation

Correct Answer

C:

Healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved. The shortcut creates this risk because a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Incorrect Answers

A:

That outcome concerns the distinct objective “Investigate readiness failures separately from liveness-related restarts”; it is not the most direct consequence of this shortcut. The relevant consequence is that healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.

B:

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 healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.

D:

That outcome concerns the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”; it is not the most direct consequence of this shortcut. The relevant consequence is that healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.

Question 655

A hospital cluster loses one worker after a maintenance reboot and several Pods remain unavailable. Which engineering change and test jointly addresses the scenario?

  1. 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.
  2. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Acceptance evidence: Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.
  3. 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.
  4. Match a Service's exposed port and targetPort to the actual listening application container, checking protocol and named ports when used. Acceptance evidence: Inspect the container listener, Service port fields and a test Pod connection before changing unrelated firewall settings.

Explanation

Correct Answer

B:

Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Acceptance evidence: Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible. This pairing is justified because a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Incorrect Answers

A:

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 inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

C:

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 inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

D:

This action and check address the distinct objective “Understand ports, targetPort and protocol mapping in a Service” instead of the stated acceptance requirement. The matching action is to inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Question 656

A data science team sees DiskPressure on a node that stopped starting new containers. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads.
  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.
  3. Use a ClusterRole for cluster-scoped resources or reusable rule definitions, recognizing that a RoleBinding to a ClusterRole grants those rules only in one namespace for namespaced resources.
  4. Read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled.

Explanation

Correct Answer

A:

The situation is that a data science team sees DiskPressure on a node that stopped starting new containers. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. This resolves the issue because a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid. To verify, simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Incorrect Answers

B:

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, a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

C:

This option addresses the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, not the immediate requirement. ClusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole. For the stated case, a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

D:

This option addresses the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, not the immediate requirement. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image. For the stated case, a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Question 657

A data science team sees DiskPressure on a node that stopped starting new containers. Which platform mechanism explains why the suitable approach works?

  1. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image.
  2. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
  3. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.
  4. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.

Explanation

Correct Answer

C:

The situation is that a data science team sees DiskPressure on a node that stopped starting new containers. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid. It supports this action: Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. To confirm, simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Incorrect Answers

A:

That statement explains the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors” rather than the cause in this case. The deciding mechanism here is that a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

B:

That statement explains the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” rather than the cause in this case. The deciding mechanism here is that a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

D:

That statement explains the distinct objective “Separate kube-scheduler decisions from kubelet execution” rather than the cause in this case. The deciding mechanism here is that a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Question 658

A data science team sees DiskPressure on a node that stopped starting new containers. Which controlled observation would best validate the intended improvement?

  1. Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.
  2. Create two controlled faulty workloads, one requiring an impossible node label and one referencing a missing image tag, then compare Events.
  3. Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
  4. With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.

Explanation

Correct Answer

A:

The situation is that a data science team sees DiskPressure on a node that stopped starting new containers. Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible. This is the relevant test because a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, but not the required result. For this case, simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

C:

This check would help evaluate the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, but not the required result. For this case, simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

D:

This check would help evaluate the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, but not the required result. For this case, simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Question 659

A data science team sees DiskPressure on a node that stopped starting new containers. An engineer proposes: “Delete every Deployment in the cluster because one node's kubelet cannot contact the control plane.” What adverse outcome would be most direct?

  1. Healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.
  2. The actual capacity or node selection problem remains because no node was assigned.
  3. Replicas can collide on storage ownership and application state ordering assumptions fail.
  4. An unsupported runtime assumption misdirects troubleshooting and may block node bootstrap.

Explanation

Correct Answer

A:

The situation is that a data science team sees DiskPressure on a node that stopped starting new containers. Healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved. The shortcut creates this risk because a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Incorrect Answers

B:

That outcome concerns the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”; it is not the most direct consequence of this shortcut. The relevant consequence is that healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.

C:

That outcome concerns the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”; it is not the most direct consequence of this shortcut. The relevant consequence is that healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.

D:

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 healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.

Question 660

A data science team sees DiskPressure on a node that stopped starting new containers. What pair of supported action and practical verification should be approved?

  1. 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.
  2. Read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled. Acceptance evidence: Create two controlled faulty workloads, one requiring an impossible node label and one referencing a missing image tag, then compare Events.
  3. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Acceptance evidence: Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
  4. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Acceptance evidence: Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Explanation

Correct Answer

D:

The situation is that a data science team sees DiskPressure on a node that stopped starting new containers. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Acceptance evidence: Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible. This pairing is justified because a NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.

Incorrect Answers

A:

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 inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

B:

This action and check address the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors” instead of the stated acceptance requirement. The matching action is to inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

C:

This action and check address the distinct objective “Enforce workload service account token boundaries and avoid needless mounts” instead of the stated acceptance requirement. The matching action is to inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Its confirming test is to simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests