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 63

Question 620

A charity's Pod has a nodeName but fails to download a private image with incorrect credentials. Which implementation together with matching acceptance evidence best meets this case?

  1. Configure an HPA for an eligible scalable controller using available resource or custom metrics and sensible minimum/maximum replicas. Acceptance evidence: Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.
  2. 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.
  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. 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.

Explanation

Correct Answer

D:

The situation is that a charity's Pod has a nodeName but fails to download a private image with incorrect credentials. 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. This pairing is justified because failedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image.

Incorrect Answers

A:

This action and check address the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts” instead of the stated acceptance requirement. The matching action is to read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled. Its confirming test is to create two controlled faulty workloads, one requiring an impossible node label and one referencing a missing image tag, then compare Events.

B:

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 read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled. Its confirming test is to create two controlled faulty workloads, one requiring an impossible node label and one referencing a missing image tag, then compare Events.

C:

The situation is that a charity's Pod has a nodeName but fails to download a private image with incorrect credentials. 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 read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled. Its confirming test is to create two controlled faulty workloads, one requiring an impossible node label and one referencing a missing image tag, then compare Events.

Question 621

A government portal shows four Running Pods but zero ready backends during an upgrade. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled.
  2. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod.
  3. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing.
  4. Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints.

Explanation

Correct Answer

C:

Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. This resolves the issue because a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ. To verify, induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

Incorrect Answers

A:

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 failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

B:

This option addresses the distinct objective “Identify reconciliation work performed by kube-controller-manager”, not the immediate requirement. The controller manager runs controllers that observe API resources and make changes so current state moves toward desired state. For the stated case, a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

D:

This option addresses the distinct objective “Diagnose cluster DNS separately from Pod network reachability”, not the immediate requirement. 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. For the stated case, a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Question 622

A government portal shows four Running Pods but zero ready backends during an upgrade. Which causal explanation supports the intended design choice?

  1. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image.
  2. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout.
  3. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
  4. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Explanation

Correct Answer

D:

A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ. It supports this action: Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. To confirm, induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

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 failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

B:

That statement explains the distinct objective “Externalize application configuration from an image while protecting secrets” rather than the cause in this case. The deciding mechanism here is that a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

C:

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 failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Question 623

A government portal shows four Running Pods but zero ready backends during an upgrade. Which test provides the strongest evidence of a correct implementation?

  1. Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.
  2. Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  3. Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.
  4. Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.

Explanation

Correct Answer

C:

Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure. This is the relevant test because a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, but not the required result. For this case, induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

B:

This check would help evaluate the distinct objective “Define secure release governance with staged approvals and policy verification”, but not the required result. For this case, induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

D:

This check would help evaluate the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”, but not the required result. For this case, induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

Question 624

A government portal shows four Running Pods but zero ready backends during an upgrade. A shortcut is proposed: “Increase application replica count indefinitely while every Pod's readiness target references the wrong port.” Which technical consequence follows most closely?

  1. The actual capacity or node selection problem remains because no node was assigned.
  2. Name lookup may succeed but no usable endpoint exists to receive traffic.
  3. The Service still has no ready endpoints and clients continue to encounter unavailable responses.
  4. The true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.

Explanation

Correct Answer

C:

The Service still has no ready endpoints and clients continue to encounter unavailable responses. The shortcut creates this risk because a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Incorrect Answers

A:

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 the Service still has no ready endpoints and clients continue to encounter unavailable responses.

B:

That outcome concerns the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Service still has no ready endpoints and clients continue to encounter unavailable responses.

D:

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 Service still has no ready endpoints and clients continue to encounter unavailable responses.

Question 625

A government portal shows four Running Pods but zero ready backends during an upgrade. Which combined solution and independent check are most directly justified?

  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. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Acceptance evidence: Test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.
  3. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Acceptance evidence: Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
  4. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Explanation

Correct Answer

A:

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. This pairing is justified because a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Incorrect Answers

B:

This action and check address the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees” instead of the stated acceptance requirement. The matching action is to inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Its confirming test is to induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

C:

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 inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Its confirming test is to induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

D:

This action and check address the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” instead of the stated acceptance requirement. The matching action is to inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Its confirming test is to induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

Question 626

A hospital reports restart loops after making a liveness probe more aggressive than application initialization. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Require approved image registries, signature or digest verification and patch ownership when admitting production container images.
  2. Read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled.
  3. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window.
  4. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing.

Explanation

Correct Answer

D:

The situation is that a hospital reports restart loops after making a liveness probe more aggressive than application initialization. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. This resolves the issue because a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ. To verify, induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

Incorrect Answers

A:

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, a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

B:

The situation is that a hospital reports restart loops after making a liveness probe more aggressive than application initialization. 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 failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

C:

This option addresses the distinct objective “Use SLI and SLO measures to focus reliability objectives”, not the immediate requirement. A service level objective is a target for measured user-facing behavior; error budgets quantify allowed misses and help prioritize release risk. For the stated case, a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Question 627

A hospital reports restart loops after making a liveness probe more aggressive than application initialization. Which platform mechanism explains why the suitable approach works?

  1. CoreDNS watches Service objects and serves cluster-aware names; bare names normally resolve relative to the requesting Pod's namespace and search domains.
  2. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.
  3. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.
  4. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Explanation

Correct Answer

D:

The situation is that a hospital reports restart loops after making a liveness probe more aggressive than application initialization. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ. It supports this action: Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. To confirm, induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

Incorrect Answers

A:

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 failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

B:

That statement explains the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” rather than the cause in this case. The deciding mechanism here is that a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

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 a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Question 628

A hospital reports restart loops after making a liveness probe more aggressive than application initialization. Which controlled observation would best validate the intended improvement?

  1. Deploy a test hostname route, verify a compatible controller exists and inspect the programmed listener and backend status.
  2. List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
  3. Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.
  4. Test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.

Explanation

Correct Answer

C:

The situation is that a hospital reports restart loops after making a liveness probe more aggressive than application initialization. Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure. This is the relevant test because a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Incorrect Answers

A:

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, induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

B:

This check would help evaluate the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”, but not the required result. For this case, induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

D:

This check would help evaluate the distinct objective “Diagnose cluster DNS separately from Pod network reachability”, but not the required result. For this case, induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

Question 629

A hospital reports restart loops after making a liveness probe more aggressive than application initialization. An engineer proposes: “Increase application replica count indefinitely while every Pod's readiness target references the wrong port.” What adverse outcome would be most direct?

  1. A workload remains nonfunctional and the persistent data dependency is never satisfied.
  2. The Service still has no ready endpoints and clients continue to encounter unavailable responses.
  3. Unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
  4. The replacement also fails while operators lack the information needed to identify the application error.

Explanation

Correct Answer

B:

The situation is that a hospital reports restart loops after making a liveness probe more aggressive than application initialization. The Service still has no ready endpoints and clients continue to encounter unavailable responses. The shortcut creates this risk because a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use Events and pod describe for failed volume mounting”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Service still has no ready endpoints and clients continue to encounter unavailable responses.

C:

That outcome concerns the distinct objective “Diagnose cluster DNS separately from Pod network reachability”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Service still has no ready endpoints and clients continue to encounter unavailable responses.

D:

That outcome concerns the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Service still has no ready endpoints and clients continue to encounter unavailable responses.

Question 630

A hospital reports restart loops after making a liveness probe more aggressive than application initialization. What pair of supported action and practical verification should be approved?

  1. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Acceptance evidence: Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
  2. Send cluster changes through the authenticated Kubernetes API and inspect the object returned by the API server rather than changing node processes directly. Acceptance evidence: Create a namespaced ConfigMap with kubectl, read it back through the API, and confirm no manual edit of a worker-node process was required.
  3. Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access. Acceptance evidence: Create a ClusterIP test Service and validate internal access, then compare the reachable endpoints under an authorized LoadBalancer configuration.
  4. 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.

Explanation

Correct Answer

D:

The situation is that a hospital reports restart loops after making a liveness probe more aggressive than application initialization. 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. This pairing is justified because a failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ.

Incorrect Answers

A:

The situation is that a hospital reports restart loops after making a liveness probe more aggressive than application initialization. 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 inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Its confirming test is to induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

B:

This action and check address the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point” instead of the stated acceptance requirement. The matching action is to inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Its confirming test is to induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

C:

This action and check address the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” instead of the stated acceptance requirement. The matching action is to inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing. Its confirming test is to induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests