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 61

Question 600

A small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. Which engineering change and test jointly addresses the scenario?

  1. 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.
  2. Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected. Acceptance evidence: Attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.
  3. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade. Acceptance evidence: Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  4. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Acceptance evidence: Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.

Explanation

Correct Answer

A:

The situation is that a small SaaS platform runs customers' development environments in separate namespaces with resource and access limits. 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. This pairing is justified because namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads.

Incorrect Answers

B:

This action and check address the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations” instead of the stated acceptance requirement. The matching action is to combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

C:

This action and check address the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers” instead of the stated acceptance requirement. The matching action is to combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

D:

This action and check address the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” instead of the stated acceptance requirement. The matching action is to combine RBAC, Pod security policies, NetworkPolicy and resource quotas for teams that share a Kubernetes control plane. Its confirming test is to test that one synthetic tenant cannot list another namespace's Secrets, send blocked traffic or exceed quota.

Question 601

A campus attendance worker repeatedly starts then exits due to a missing environment variable. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup.
  2. Inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API.
  3. Inspect probe configuration, Pod Ready conditions and restart events to identify whether traffic eligibility or container execution is failing.
  4. Require approved image registries, signature or digest verification and patch ownership when admitting production container images.

Explanation

Correct Answer

A:

Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. This resolves the issue because crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe. To verify, run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

Incorrect Answers

B:

This option addresses the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, not the immediate requirement. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node. For the stated case, crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

C:

This option addresses the distinct objective “Investigate readiness failures separately from liveness-related restarts”, not the immediate requirement. A failed readiness probe removes a Pod from ready Service endpoints, while failed liveness checks can restart a process; their operational consequences differ. For the stated case, crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

D:

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, crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

Question 602

A campus attendance worker repeatedly starts then exits due to a missing environment variable. Which causal explanation supports the intended design choice?

  1. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.
  2. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
  3. kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.
  4. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.

Explanation

Correct Answer

A:

CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe. It supports this action: Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. To confirm, run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

Incorrect Answers

B:

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 crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

C:

That statement explains the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” rather than the cause in this case. The deciding mechanism here is that crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

D:

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 crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

Question 603

A campus attendance worker repeatedly starts then exits due to a missing environment variable. Which test provides the strongest evidence of a correct implementation?

  1. Test the same Service from a diagnostic Pod by fully qualified DNS name and known ClusterIP, then inspect CoreDNS logs if only resolution fails.
  2. Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
  3. Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
  4. Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

Explanation

Correct Answer

D:

Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path. This is the relevant test because crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Diagnose cluster DNS separately from Pod network reachability”, but not the required result. For this case, run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

B:

This check would help evaluate the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, but not the required result. For this case, run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

C:

This check would help evaluate the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”, but not the required result. For this case, run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

Question 604

A campus attendance worker repeatedly starts then exits due to a missing environment variable. A shortcut is proposed: “Delete the Service object repeatedly to resolve a container process crash without examining its process logs.” Which technical consequence follows most closely?

  1. The actual capacity or node selection problem remains because no node was assigned.
  2. The edit is invisible to the API and controller reconciliation, so subsequent node restarts or scheduling can discard it.
  3. Unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
  4. The Pod continues restarting because Service DNS configuration is not the cause of the process exit.

Explanation

Correct Answer

D:

The Pod continues restarting because Service DNS configuration is not the cause of the process exit. The shortcut creates this risk because crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

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 Pod continues restarting because Service DNS configuration is not the cause of the process exit.

B:

That outcome concerns the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Pod continues restarting because Service DNS configuration is not the cause of the process exit.

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 Pod continues restarting because Service DNS configuration is not the cause of the process exit.

Question 605

A campus attendance worker repeatedly starts then exits due to a missing environment variable. Which combined solution and independent check are most directly justified?

  1. 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. Acceptance evidence: Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.
  2. 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.
  3. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Acceptance evidence: Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.
  4. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.

Explanation

Correct Answer

C:

Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Acceptance evidence: Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path. This pairing is justified because crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

Incorrect Answers

A:

This action and check address the distinct objective “Distinguish ClusterRoles from Roles and binding scope” instead of the stated acceptance requirement. The matching action is to inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Its confirming test is to run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

B:

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 Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Its confirming test is to run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

D:

This action and check address the distinct objective “Explain desired state versus observed status in Kubernetes objects” instead of the stated acceptance requirement. The matching action is to inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Its confirming test is to run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

Question 606

A retail payments app enters CrashLoopBackOff after deploying a malformed startup flag. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope.
  2. Run controlled DNS queries and IP connectivity tests before changing service discovery, CNI routes or application endpoints.
  3. Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements.
  4. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup.

Explanation

Correct Answer

D:

The situation is that a retail payments app enters CrashLoopBackOff after deploying a malformed startup flag. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. This resolves the issue because crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe. To verify, run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

Incorrect Answers

A:

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, crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

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, crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

C:

This option addresses the distinct objective “Understand Prometheus pull-based metrics collection and exporters”, not the immediate requirement. Prometheus commonly pulls numeric samples from configured targets, stores them as labeled time series and supports PromQL queries over those samples. For the stated case, crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

Question 607

A retail payments app enters CrashLoopBackOff after deploying a malformed startup flag. Which platform mechanism explains why the suitable approach works?

  1. ClusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole.
  2. Metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.
  3. Kubelet cannot launch containers requiring unresolved or unmountable volumes, and Events often identify a storage provisioning or attachment failure.
  4. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

Explanation

Correct Answer

D:

The situation is that a retail payments app enters CrashLoopBackOff after deploying a malformed startup flag. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe. It supports this action: Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. To confirm, run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

Incorrect Answers

A:

That statement explains the distinct objective “Distinguish ClusterRoles from Roles and binding scope” rather than the cause in this case. The deciding mechanism here is that crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

B:

That statement explains the distinct objective “Use metrics, logs and traces together when investigating cross-service latency” rather than the cause in this case. The deciding mechanism here is that crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

C:

The situation is that a retail payments app enters CrashLoopBackOff after deploying a malformed startup flag. 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 crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

Question 608

A retail payments app enters CrashLoopBackOff after deploying a malformed startup flag. Which controlled observation would best validate the intended improvement?

  1. Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.
  2. Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
  3. Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
  4. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Explanation

Correct Answer

A:

The situation is that a retail payments app enters CrashLoopBackOff after deploying a malformed startup flag. Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path. This is the relevant test because crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”, but not the required result. For this case, run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

C:

This check would help evaluate the distinct objective “Use Events and pod describe for failed volume mounting”, but not the required result. For this case, run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

D:

This check would help evaluate the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, but not the required result. For this case, run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

Question 609

A retail payments app enters CrashLoopBackOff after deploying a malformed startup flag. An engineer proposes: “Delete the Service object repeatedly to resolve a container process crash without examining its process logs.” What adverse outcome would be most direct?

  1. The operator may deploy unsupported changes without release provenance or a responsible maintenance path.
  2. A workload remains nonfunctional and the persistent data dependency is never satisfied.
  3. Replicas can collide on storage ownership and application state ordering assumptions fail.
  4. The Pod continues restarting because Service DNS configuration is not the cause of the process exit.

Explanation

Correct Answer

D:

The situation is that a retail payments app enters CrashLoopBackOff after deploying a malformed startup flag. The Pod continues restarting because Service DNS configuration is not the cause of the process exit. The shortcut creates this risk because crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”; it is not the most direct consequence of this shortcut. The relevant consequence is that the Pod continues restarting because Service DNS configuration is not the cause of the process exit.

B:

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 Pod continues restarting because Service DNS configuration is not the cause of the process exit.

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 the Pod continues restarting because Service DNS configuration is not the cause of the process exit.

Question 610

A retail payments app enters CrashLoopBackOff after deploying a malformed startup flag. What pair of supported action and practical verification should be approved?

  1. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Acceptance evidence: Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.
  2. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced. Acceptance evidence: Delete and replace a Deployment Pod and verify a client continues to reach its Service DNS name despite changed backend Pod addresses.
  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. 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.

Explanation

Correct Answer

A:

The situation is that a retail payments app enters CrashLoopBackOff after deploying a malformed startup flag. Inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Acceptance evidence: Run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path. This pairing is justified because crashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.

Incorrect Answers

B:

This action and check address the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” instead of the stated acceptance requirement. The matching action is to inspect Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Its confirming test is to run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

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 Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Its confirming test is to run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

D:

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 Pod container last state, restart count and kubectl logs --previous when a process repeatedly exits after startup. Its confirming test is to run a synthetic app that exits with a nonzero code, then confirm describe, previous logs and restart data reveal the failure path.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests