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 16

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.

Question 151

A hospital trainee needs a fast overview of Pods and then a detailed explanation of one Pending Pod. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior.
  2. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload.
  3. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails.
  4. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy.

Explanation

Correct Answer

B:

Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. This resolves the issue because get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. To verify, compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Incorrect Answers

A:

This option addresses the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”, not the immediate requirement. Kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function. For the stated case, get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

C:

This option addresses the distinct objective “Understand CSI drivers and volume attachment responsibilities”, not the immediate requirement. CSI separates storage vendor implementation from Kubernetes core and manages provisioning, attachment and node mounting through driver-defined capabilities. For the stated case, get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

D:

This option addresses the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, not the immediate requirement. The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors. For the stated case, get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Question 152

A hospital trainee needs a fast overview of Pods and then a detailed explanation of one Pending Pod. Which causal explanation supports the intended design choice?

  1. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable.
  2. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.
  3. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
  4. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings.

Explanation

Correct Answer

B:

Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. It supports this action: Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. To confirm, compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Incorrect Answers

A:

That statement explains the distinct objective “Spread replicas across failure domains with topologySpreadConstraints” rather than the cause in this case. The deciding mechanism here is that get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

C:

That statement explains the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” rather than the cause in this case. The deciding mechanism here is that get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

D:

That statement explains the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” rather than the cause in this case. The deciding mechanism here is that get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Question 153

A hospital trainee needs a fast overview of Pods and then a detailed explanation of one Pending Pod. Which test provides the strongest evidence of a correct implementation?

  1. Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
  2. List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
  3. Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.
  4. Induce a temporary readiness failure in staging and verify traffic stops without a restart; then separately test controlled liveness failure.

Explanation

Correct Answer

C:

Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events. This is the relevant test because get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”, but not the required result. For this case, compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

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, compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

D:

This check would help evaluate the distinct objective “Investigate readiness failures separately from liveness-related restarts”, but not the required result. For this case, compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Question 154

A hospital trainee needs a fast overview of Pods and then a detailed explanation of one Pending Pod. A shortcut is proposed: “Treat a one-line Running phase in kubectl get as proof that every application endpoint is ready.” Which technical consequence follows most closely?

  1. The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.
  2. A migration fails because backend volume classes and cloud authentication semantics differ.
  3. Compromised credentials can perform widespread cluster changes without attribution or least privilege.
  4. Users may encounter failed requests because readiness and application-level health remain unverified.

Explanation

Correct Answer

D:

Users may encounter failed requests because readiness and application-level health remain unverified. The shortcut creates this risk because get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Incorrect Answers

A:

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 users may encounter failed requests because readiness and application-level health remain unverified.

B:

That outcome concerns the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”; it is not the most direct consequence of this shortcut. The relevant consequence is that users may encounter failed requests because readiness and application-level health remain unverified.

C:

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 users may encounter failed requests because readiness and application-level health remain unverified.

Question 155

A hospital trainee needs a fast overview of Pods and then a detailed explanation of one Pending Pod. Which combined solution and independent check are most directly justified?

  1. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image. Acceptance evidence: Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
  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. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Acceptance evidence: Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.

Explanation

Correct Answer

B:

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. This pairing is justified because get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Incorrect Answers

A:

This action and check address the distinct objective “Externalize application configuration from an image while protecting secrets” instead of the stated acceptance requirement. The matching action is to use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

C:

This action and check address the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster” instead of the stated acceptance requirement. The matching action is to use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

D:

This action and check address the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” instead of the stated acceptance requirement. The matching action is to use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Question 156

A shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. Which engineering approach is the most appropriate for this cloud-native case?

  1. Apply suitable Pod Security Admission labels such as baseline or restricted and test whether noncompliant synthetic Pod specs are rejected.
  2. Grant operators only required API verbs and resources using RBAC, then test with kubectl auth can-i and separate synthetic identities.
  3. Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources.
  4. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload.

Explanation

Correct Answer

D:

The situation is that a shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. This resolves the issue because get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. To verify, compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Incorrect Answers

A:

This option addresses the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, not the immediate requirement. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. For the stated case, get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

B:

This option addresses the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, not the immediate requirement. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it. For the stated case, get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

C:

This option addresses the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, not the immediate requirement. The scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests. For the stated case, get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Question 157

A shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. What infrastructure principle makes the correct treatment effective?

  1. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.
  2. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
  3. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.
  4. A required affinity expression blocks scheduling onto nonmatching nodes; a preferred expression influences scoring but permits fallback when necessary.

Explanation

Correct Answer

A:

The situation is that a shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. It supports this action: Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. To confirm, compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Incorrect Answers

B:

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 get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

C:

That statement explains the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” rather than the cause in this case. The deciding mechanism here is that get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

D:

That statement explains the distinct objective “Distinguish preferred node affinity from required scheduling rules” rather than the cause in this case. The deciding mechanism here is that get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Question 158

A shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. What verification result would most convincingly distinguish a working solution from a claim?

  1. Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.
  2. Inspect CSI driver registration, test provisioning a claim and review attachment/mount Events for a synthetic workload.
  3. With restricted identities, check get pods succeeds while delete secrets and create clusterroles are denied.
  4. Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Explanation

Correct Answer

D:

The situation is that a shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events. This is the relevant test because get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Incorrect Answers

A:

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, compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

B:

This check would help evaluate the distinct objective “Understand CSI drivers and volume attachment responsibilities”, but not the required result. For this case, compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

C:

This check would help evaluate the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, but not the required result. For this case, compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Question 159

A shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. The change review contains this proposal: “Treat a one-line Running phase in kubectl get as proof that every application endpoint is ready.” What risk matters most?

  1. Users may encounter failed requests because readiness and application-level health remain unverified.
  2. Customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
  3. The scheduler may evaluate an unintended Pod group or fail to spread the intended replicas.
  4. Compromised credentials can perform widespread cluster changes without attribution or least privilege.

Explanation

Correct Answer

A:

The situation is that a shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. Users may encounter failed requests because readiness and application-level health remain unverified. The shortcut creates this risk because get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Incorrect Answers

B:

That outcome concerns the distinct objective “Design a release rollback trigger from measurable service signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that users may encounter failed requests because readiness and application-level health remain unverified.

C:

That outcome concerns the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”; it is not the most direct consequence of this shortcut. The relevant consequence is that users may encounter failed requests because readiness and application-level health remain unverified.

D:

The situation is that a shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. 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 users may encounter failed requests because readiness and application-level health remain unverified.

Question 160

A shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. Which implementation together with matching acceptance evidence best meets this case?

  1. Expose appropriately labeled /metrics endpoints or exporters and configure Prometheus scrape targets to collect time-series measurements. Acceptance evidence: Verify a synthetic exporter is listed UP in Prometheus target status and query its request counter after generating traffic.
  2. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods. Acceptance evidence: Simulate controlled resource pressure with two priorities and inspect Events for whether a high-priority test Pod can schedule.
  3. 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.
  4. 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.

Explanation

Correct Answer

D:

The situation is that a shipping developer reads Ready 0/1 from kubectl get and wants conditions and Events before changing the image. 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. This pairing is justified because get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis.

Incorrect Answers

A:

This action and check address the distinct objective “Understand Prometheus pull-based metrics collection and exporters” instead of the stated acceptance requirement. The matching action is to use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

B:

This action and check address the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability” instead of the stated acceptance requirement. The matching action is to use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

C:

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 use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Its confirming test is to compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests