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 15

Question 140

A student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. Which engineering change and test jointly addresses the scenario?

  1. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Acceptance evidence: Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.
  2. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Acceptance evidence: Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
  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. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Acceptance evidence: Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.

Explanation

Correct Answer

C:

The situation is that a student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. 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. This pairing is justified because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.

Incorrect Answers

A:

This action and check address the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

B:

This action and check address the distinct objective “Use labels and selectors to connect resources predictably” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

D:

This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.

Question 141

A nonprofit engineer alternates between staging and production clusters on one workstation. Which engineering approach is the most appropriate for this cloud-native case?

  1. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application.
  2. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks.
  3. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance.
  4. Inspect the active kubeconfig context and namespace before applying manifests to staging or production.

Explanation

Correct Answer

D:

Inspect the active kubeconfig context and namespace before applying manifests to staging or production. This resolves the issue because a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. To verify, run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

Incorrect Answers

A:

This option addresses the distinct objective “Define secure release governance with staged approvals and policy verification”, not the immediate requirement. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production. For the stated case, a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

B:

This option addresses the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, not the immediate requirement. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. For the stated case, a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

C:

This option addresses the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”, not the immediate requirement. A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count. For the stated case, a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

Question 142

A nonprofit engineer alternates between staging and production clusters on one workstation. What infrastructure principle makes the correct treatment effective?

  1. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.
  2. A quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.
  3. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests.
  4. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints.

Explanation

Correct Answer

A:

A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. It supports this action: Inspect the active kubeconfig context and namespace before applying manifests to staging or production. To confirm, run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

Incorrect Answers

B:

That statement explains the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance” rather than the cause in this case. The deciding mechanism here is that a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

C:

That statement explains the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” rather than the cause in this case. The deciding mechanism here is that a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

D:

That statement explains the distinct objective “Distinguish the CNI Pod network from Service discovery and routing” rather than the cause in this case. The deciding mechanism here is that a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

Question 143

A nonprofit engineer alternates between staging and production clusters on one workstation. What verification result would most convincingly distinguish a working solution from a claim?

  1. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  2. Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  3. Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  4. Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.

Explanation

Correct Answer

B:

Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace. This is the relevant test because a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

Incorrect Answers

A:

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 kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

C:

This check would help evaluate the distinct objective “Explain the container runtime interface without conflating it with the control plane”, but not the required result. For this case, run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

D:

This check would help evaluate the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, but not the required result. For this case, run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

Question 144

A nonprofit engineer alternates between staging and production clusters on one workstation. The change review contains this proposal: “Run a destructive cleanup command immediately after switching VPNs without checking current-context.” What risk matters most?

  1. Applications fail on migration when plugin behavior or provider-specific components were never evaluated.
  2. The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.
  3. The command can mutate production objects although the operator intended a disposable laboratory cluster.
  4. Compromised credentials can perform widespread cluster changes without attribution or least privilege.

Explanation

Correct Answer

C:

The command can mutate production objects although the operator intended a disposable laboratory cluster. The shortcut creates this risk because a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

Incorrect Answers

A:

That outcome concerns the distinct objective “Understand open standards and vendor-neutral community collaboration”; it is not the most direct consequence of this shortcut. The relevant consequence is that the command can mutate production objects although the operator intended a disposable laboratory cluster.

B:

That outcome concerns the distinct objective “Identify reconciliation work performed by kube-controller-manager”; it is not the most direct consequence of this shortcut. The relevant consequence is that the command can mutate production objects although the operator intended a disposable laboratory cluster.

D:

That outcome concerns the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”; it is not the most direct consequence of this shortcut. The relevant consequence is that the command can mutate production objects although the operator intended a disposable laboratory cluster.

Question 145

A nonprofit engineer alternates between staging and production clusters on one workstation. Which implementation together with matching acceptance evidence best meets this case?

  1. Inspect the active kubeconfig context and namespace before applying manifests to staging or production. Acceptance evidence: Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  2. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance. Acceptance evidence: Add a test worker node and inspect the corresponding DaemonSet agent Pod without scaling a Deployment.
  3. 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.
  4. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.

Explanation

Correct Answer

A:

Inspect the active kubeconfig context and namespace before applying manifests to staging or production. Acceptance evidence: Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace. This pairing is justified because a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

Incorrect Answers

B:

This action and check address the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts” instead of the stated acceptance requirement. The matching action is to inspect the active kubeconfig context and namespace before applying manifests to staging or production. Its confirming test is to run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

C:

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 the active kubeconfig context and namespace before applying manifests to staging or production. Its confirming test is to run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

D:

This action and check address the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” instead of the stated acceptance requirement. The matching action is to inspect the active kubeconfig context and namespace before applying manifests to staging or production. Its confirming test is to run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

Question 146

A college class uses shared kubectl instructions but every learner has different kubeconfig contexts. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API.
  2. Inspect the active kubeconfig context and namespace before applying manifests to staging or production.
  3. Require approved image registries, signature or digest verification and patch ownership when admitting production container images.
  4. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API.

Explanation

Correct Answer

B:

The situation is that a college class uses shared kubectl instructions but every learner has different kubeconfig contexts. Inspect the active kubeconfig context and namespace before applying manifests to staging or production. This resolves the issue because a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. To verify, run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

Incorrect Answers

A:

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, a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

C:

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 kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

D:

This option addresses the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift”, not the immediate requirement. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management. For the stated case, a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

Question 147

A college class uses shared kubectl instructions but every learner has different kubeconfig contexts. Which causal explanation supports the intended design choice?

  1. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.
  2. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
  3. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
  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

A:

The situation is that a college class uses shared kubectl instructions but every learner has different kubeconfig contexts. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. It supports this action: Inspect the active kubeconfig context and namespace before applying manifests to staging or production. To confirm, run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

Incorrect Answers

B:

That statement explains the distinct objective “Use an immutable image digest for exact deployment provenance” rather than the cause in this case. The deciding mechanism here is that a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

C:

That statement explains the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” rather than the cause in this case. The deciding mechanism here is that a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

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 a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

Question 148

A college class uses shared kubectl instructions but every learner has different kubeconfig contexts. Which test provides the strongest evidence of a correct implementation?

  1. Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  2. In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  3. Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  4. Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Explanation

Correct Answer

A:

The situation is that a college class uses shared kubectl instructions but every learner has different kubeconfig contexts. Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace. This is the relevant test because a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”, but not the required result. For this case, run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

C:

The situation is that a college class uses shared kubectl instructions but every learner has different kubeconfig contexts. This check would help evaluate the distinct objective “Explain the container runtime interface without conflating it with the control plane”, but not the required result. For this case, run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

D:

This check would help evaluate the distinct objective “Use annotations for tool metadata rather than workload selection”, but not the required result. For this case, run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

Question 149

A college class uses shared kubectl instructions but every learner has different kubeconfig contexts. A shortcut is proposed: “Run a destructive cleanup command immediately after switching VPNs without checking current-context.” Which technical consequence follows most closely?

  1. A scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.
  2. The command can mutate production objects although the operator intended a disposable laboratory cluster.
  3. A backend exception can remain hidden even when CPU load looks normal.
  4. Users may encounter failed requests because readiness and application-level health remain unverified.

Explanation

Correct Answer

B:

The situation is that a college class uses shared kubectl instructions but every learner has different kubeconfig contexts. The command can mutate production objects although the operator intended a disposable laboratory cluster. The shortcut creates this risk because a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

Incorrect Answers

A:

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 the command can mutate production objects although the operator intended a disposable laboratory cluster.

C:

That outcome concerns the distinct objective “Explain metrics, logs and traces as complementary observability signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that the command can mutate production objects although the operator intended a disposable laboratory cluster.

D:

That outcome concerns the distinct objective “Use kubectl get and describe for distinct inspection needs”; it is not the most direct consequence of this shortcut. The relevant consequence is that the command can mutate production objects although the operator intended a disposable laboratory cluster.

Question 150

A college class uses shared kubectl instructions but every learner has different kubeconfig contexts. Which combined solution and independent check are most directly justified?

  1. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Acceptance evidence: Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
  2. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Acceptance evidence: Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.
  3. Inspect the active kubeconfig context and namespace before applying manifests to staging or production. Acceptance evidence: Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  4. 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.

Explanation

Correct Answer

C:

The situation is that a college class uses shared kubectl instructions but every learner has different kubeconfig contexts. Inspect the active kubeconfig context and namespace before applying manifests to staging or production. Acceptance evidence: Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace. This pairing is justified because a kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

Incorrect Answers

A:

This action and check address the distinct objective “Use namespaces as organizational scopes without treating them as firewalls” instead of the stated acceptance requirement. The matching action is to inspect the active kubeconfig context and namespace before applying manifests to staging or production. Its confirming test is to run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

B:

This action and check address the distinct objective “Use kubectl get and describe for distinct inspection needs” instead of the stated acceptance requirement. The matching action is to inspect the active kubeconfig context and namespace before applying manifests to staging or production. Its confirming test is to run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

D:

This action and check address the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs” instead of the stated acceptance requirement. The matching action is to inspect the active kubeconfig context and namespace before applying manifests to staging or production. Its confirming test is to run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests