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 64

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.

Question 631

A library's records service stays in ContainerCreating with a FailedMount warning. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies.
  2. Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints.
  3. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code.
  4. Combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane.

Explanation

Correct Answer

C:

Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. This resolves the issue because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. To verify, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

Incorrect Answers

A:

This option addresses the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”, not the immediate requirement. A namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces. For the stated case, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

B:

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, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

D:

This option addresses the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, not the immediate requirement. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. For the stated case, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

Question 632

A library's records service stays in ContainerCreating with a FailedMount warning. Which platform mechanism explains why the suitable approach works?

  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. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
  3. 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.
  4. Service meshes commonly use proxies or ambient dataplanes to control east-west traffic; ingress/gateway handling addresses entry routes and can integrate with the mesh.

Explanation

Correct Answer

B:

Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. It supports this action: Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. To confirm, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

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 kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

C:

That statement explains the distinct objective “Understand ports, targetPort and protocol mapping in a Service” rather than the cause in this case. The deciding mechanism here is that kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

D:

That statement explains the distinct objective “Distinguish service mesh traffic management from external ingress routing” rather than the cause in this case. The deciding mechanism here is that kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

Question 633

A library's records service stays in ContainerCreating with a FailedMount warning. Which controlled observation would best validate the intended improvement?

  1. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  2. Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
  3. Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.
  4. With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.

Explanation

Correct Answer

B:

Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim. This is the relevant test because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use Pods as the shared network and storage execution unit”, but not the required result. For this case, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

C:

This check would help evaluate the distinct objective “Investigate readiness failures separately from liveness-related restarts”, but not the required result. For this case, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

D:

This check would help evaluate the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, but not the required result. For this case, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

Question 634

A library's records service stays in ContainerCreating with a FailedMount warning. An engineer proposes: “Modify container application code to skip its database initialization when the real problem is an unbound PVC.” What adverse outcome would be most direct?

  1. A workload remains nonfunctional and the persistent data dependency is never satisfied.
  2. Healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.
  3. Secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.
  4. The claim remains Pending and dependent Pods cannot mount the missing volume.

Explanation

Correct Answer

A:

A workload remains nonfunctional and the persistent data dependency is never satisfied. The shortcut creates this risk because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

Incorrect Answers

B:

That outcome concerns the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload remains nonfunctional and the persistent data dependency is never satisfied.

C:

That outcome concerns the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload remains nonfunctional and the persistent data dependency is never satisfied.

D:

That outcome concerns the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload remains nonfunctional and the persistent data dependency is never satisfied.

Question 635

A library's records service stays in ContainerCreating with a FailedMount warning. 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. 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.
  3. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Acceptance evidence: List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
  4. 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.

Explanation

Correct Answer

A:

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. This pairing is justified because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

Incorrect Answers

B:

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 FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Its confirming test is to reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

C:

This action and check address the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership” instead of the stated acceptance requirement. The matching action is to inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Its confirming test is to reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

D:

This action and check address the distinct objective “Diagnose cluster DNS separately from Pod network reachability” instead of the stated acceptance requirement. The matching action is to inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Its confirming test is to reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

Question 636

A research group creates a Pod that references a PersistentVolumeClaim in another namespace. Which engineering approach is the most appropriate for this cloud-native case?

  1. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup.
  2. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data.
  3. Inspect the active kubeconfig context and namespace before applying manifests to staging or production.
  4. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code.

Explanation

Correct Answer

D:

The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. This resolves the issue because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. To verify, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

Incorrect Answers

A:

This option addresses the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs”, not the immediate requirement. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe. For the stated case, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

B:

This option addresses the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion”, not the immediate requirement. A PV reclaim policy controls how underlying storage is treated after claim release; deleting the Pod and deleting the PVC are distinct events with different effects. For the stated case, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

C:

This option addresses the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, not the immediate requirement. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. For the stated case, kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

Question 637

A research group creates a Pod that references a PersistentVolumeClaim in another namespace. What infrastructure principle makes the correct treatment effective?

  1. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
  2. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
  3. Service meshes commonly use proxies or ambient dataplanes to control east-west traffic; ingress/gateway handling addresses entry routes and can integrate with the mesh.
  4. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image.

Explanation

Correct Answer

B:

The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure. It supports this action: Inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. To confirm, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

Incorrect Answers

A:

That statement explains the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” rather than the cause in this case. The deciding mechanism here is that kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

C:

The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. That statement explains the distinct objective “Distinguish service mesh traffic management from external ingress routing” rather than the cause in this case. The deciding mechanism here is that kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

D:

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 kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

Question 638

A research group creates a Pod that references a PersistentVolumeClaim in another namespace. What verification result would most convincingly distinguish a working solution from a claim?

  1. With synthetic users verify a trusted API connection, denied privilege escalation and appropriate audit entries for failed requests.
  2. Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
  3. Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.
  4. Set an intentionally excessive memory request in a lab and inspect Pod Pending Events before adjusting it.

Explanation

Correct Answer

B:

The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim. This is the relevant test because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

Incorrect Answers

A:

The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. This check would help evaluate the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, but not the required result. For this case, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

C:

The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. This check would help evaluate the distinct objective “Investigate readiness failures separately from liveness-related restarts”, but not the required result. For this case, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

D:

This check would help evaluate the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, but not the required result. For this case, reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

Question 639

A research group creates a Pod that references a PersistentVolumeClaim in another namespace. The change review contains this proposal: “Modify container application code to skip its database initialization when the real problem is an unbound PVC.” What risk matters most?

  1. Healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.
  2. Requests fail after a replica is replaced because the client bypassed the Service abstraction.
  3. A workload remains nonfunctional and the persistent data dependency is never satisfied.
  4. A scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.

Explanation

Correct Answer

C:

The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. A workload remains nonfunctional and the persistent data dependency is never satisfied. The shortcut creates this risk because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

Incorrect Answers

A:

The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. That outcome concerns the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload remains nonfunctional and the persistent data dependency is never satisfied.

B:

That outcome concerns the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload remains nonfunctional and the persistent data dependency is never satisfied.

D:

That outcome concerns the distinct objective “Use nodeSelector to place a workload on nodes with required labels”; it is not the most direct consequence of this shortcut. The relevant consequence is that a workload remains nonfunctional and the persistent data dependency is never satisfied.

Question 640

A research group creates a Pod that references a PersistentVolumeClaim in another namespace. Which implementation together with matching acceptance evidence best meets this case?

  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. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  3. Inspect 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. Combine a default-deny baseline with narrow app-label and namespace-label NetworkPolicy rules for approved traffic. Acceptance evidence: Test synthetic frontend-to-backend reachability and deny a third unauthorized namespace while verifying DNS access is still deliberately allowed.

Explanation

Correct Answer

C:

The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. 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. This pairing is justified because kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.

Incorrect Answers

A:

The situation is that a research group creates a Pod that references a PersistentVolumeClaim in another namespace. 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 FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Its confirming test is to reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

B:

This action and check address the distinct objective “Explain the container runtime interface without conflating it with the control plane” instead of the stated acceptance requirement. The matching action is to inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Its confirming test is to reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

D:

This action and check address the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” instead of the stated acceptance requirement. The matching action is to inspect FailedMount and PVC events, then verify StorageClass, PVC binding and node driver prerequisites before rewriting application code. Its confirming test is to reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests