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 85

Question 840

A community clinic sees a Deployment with zero available replicas and needs to locate the first failing control step. What pair of supported action and practical verification should be approved?

  1. Measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Acceptance evidence: Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.
  2. Inspect kubectl describe node and reported conditions, taints, disk pressure and kubelet health before moving workloads. Acceptance evidence: Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.
  3. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Acceptance evidence: In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  4. Inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup. Acceptance evidence: Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.

Explanation

Correct Answer

D:

The situation is that a community clinic sees a Deployment with zero available replicas and needs to locate the first failing control step. Inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup. Acceptance evidence: Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status. This pairing is justified because different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings.

Incorrect Answers

A:

This action and check address the distinct objective “Use metrics, logs and traces together when investigating cross-service latency” instead of the stated acceptance requirement. The matching action is to inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup. Its confirming test is to create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.

B:

This action and check address the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” instead of the stated acceptance requirement. The matching action is to inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup. Its confirming test is to create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.

C:

This action and check address the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” instead of the stated acceptance requirement. The matching action is to inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup. Its confirming test is to create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.

Question 841

A financial application ships a distroless image without a shell and needs a scoped networking inspection. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing.
  2. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers.
  3. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism.
  4. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies.

Explanation

Correct Answer

B:

Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. This resolves the issue because an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration. To verify, in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

Incorrect Answers

A:

This option addresses the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”, not the immediate requirement. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port. For the stated case, an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

C:

This option addresses the distinct objective “Design a release rollback trigger from measurable service signals”, not the immediate requirement. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. For the stated case, an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

D:

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, an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

Question 842

A financial application ships a distroless image without a shell and needs a scoped networking inspection. Which causal explanation supports the intended design choice?

  1. NetworkPolicies select Pods and define allowed flows; when a Pod becomes isolated, traffic is allowed only as permitted by applicable rules and plugin behavior.
  2. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.
  3. kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.
  4. An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

Explanation

Correct Answer

D:

An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration. It supports this action: Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. To confirm, in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

Incorrect Answers

A:

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 an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

B:

That statement explains the distinct objective “Define secure release governance with staged approvals and policy verification” rather than the cause in this case. The deciding mechanism here is that an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

C:

That statement explains the distinct objective “Use kubectl logs and previous container logs to isolate application crashes” rather than the cause in this case. The deciding mechanism here is that an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

Question 843

A financial application ships a distroless image without a shell and needs a scoped networking inspection. Which test provides the strongest evidence of a correct implementation?

  1. Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.
  2. In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  3. Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
  4. Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Explanation

Correct Answer

B:

In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action. This is the relevant test because an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Correlate application rollout revisions with error spikes”, but not the required result. For this case, in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

C:

This check would help evaluate the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, but not the required result. For this case, in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

D:

This check would help evaluate the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”, but not the required result. For this case, in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

Question 844

A financial application ships a distroless image without a shell and needs a scoped networking inspection. A shortcut is proposed: “Install a permanent diagnostic SSH daemon inside every production Pod to avoid needing controlled debug access.” Which technical consequence follows most closely?

  1. Replacing a Pod can destroy state because no independent persistent volume was requested.
  2. The replacement also fails while operators lack the information needed to identify the application error.
  3. The workload gains unnecessary listening services and mutable changes that disappear on replacement.
  4. An application regression can remain live even though container and readiness probes are healthy.

Explanation

Correct Answer

C:

The workload gains unnecessary listening services and mutable changes that disappear on replacement. The shortcut creates this risk because an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

Incorrect Answers

A:

That outcome concerns the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload gains unnecessary listening services and mutable changes that disappear on replacement.

B:

That outcome concerns the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload gains unnecessary listening services and mutable changes that disappear on replacement.

D:

That outcome concerns the distinct objective “Correlate application rollout revisions with error spikes”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload gains unnecessary listening services and mutable changes that disappear on replacement.

Question 845

A financial application ships a distroless image without a shell and needs a scoped networking inspection. Which combined solution and independent check are most directly justified?

  1. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Acceptance evidence: In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  2. Measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Acceptance evidence: Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.
  3. Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance. Acceptance evidence: Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
  4. Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Acceptance evidence: Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

Explanation

Correct Answer

A:

Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Acceptance evidence: In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action. This pairing is justified because an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

Incorrect Answers

B:

This action and check address the distinct objective “Use metrics, logs and traces together when investigating cross-service latency” instead of the stated acceptance requirement. The matching action is to use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Its confirming test is to in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

C:

This action and check address the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” instead of the stated acceptance requirement. The matching action is to use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Its confirming test is to in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

D:

This action and check address the distinct objective “Correlate application rollout revisions with error spikes” instead of the stated acceptance requirement. The matching action is to use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Its confirming test is to in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

Question 846

A school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage.
  2. Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing.
  3. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers.
  4. Verify that the installed Container Storage Interface driver supports the requested persistent storage and inspect driver controller/node components when mounting fails.

Explanation

Correct Answer

C:

The situation is that a school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. This resolves the issue because an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration. To verify, in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

Incorrect Answers

A:

This option addresses the distinct objective “Separate CI build verification from CD environment promotion”, not the immediate requirement. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments. For the stated case, an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

B:

The situation is that a school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. This option addresses the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”, not the immediate requirement. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port. For the stated case, an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

D:

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, an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

Question 847

A school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. Which platform mechanism explains why the suitable approach works?

  1. An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.
  2. Helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist.
  3. 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.
  4. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Explanation

Correct Answer

A:

The situation is that a school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration. It supports this action: Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. To confirm, in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

Incorrect Answers

B:

That statement explains the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers” rather than the cause in this case. The deciding mechanism here is that an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

C:

That statement explains the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” rather than the cause in this case. The deciding mechanism here is that an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

D:

That statement explains the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend” rather than the cause in this case. The deciding mechanism here is that an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

Question 848

A school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. Which controlled observation would best validate the intended improvement?

  1. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  2. Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.
  3. In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  4. Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

Explanation

Correct Answer

C:

The situation is that a school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action. This is the relevant test because an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

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, in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

B:

This check would help evaluate the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”, but not the required result. For this case, in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

D:

The situation is that a school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. This check would help evaluate the distinct objective “Correlate application rollout revisions with error spikes”, but not the required result. For this case, in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

Question 849

A school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. An engineer proposes: “Install a permanent diagnostic SSH daemon inside every production Pod to avoid needing controlled debug access.” What adverse outcome would be most direct?

  1. The operator can interrupt healthy networking while the original admission or image problem persists.
  2. The workload gains unnecessary listening services and mutable changes that disappear on replacement.
  3. The replacement also fails while operators lack the information needed to identify the application error.
  4. Cross-service latency remains difficult to diagnose because spans cannot be tied to one request path.

Explanation

Correct Answer

B:

The situation is that a school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. The workload gains unnecessary listening services and mutable changes that disappear on replacement. The shortcut creates this risk because an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload gains unnecessary listening services and mutable changes that disappear on replacement.

C:

The situation is that a school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. That outcome concerns the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload gains unnecessary listening services and mutable changes that disappear on replacement.

D:

That outcome concerns the distinct objective “Instrument services with OpenTelemetry context propagation”; it is not the most direct consequence of this shortcut. The relevant consequence is that the workload gains unnecessary listening services and mutable changes that disappear on replacement.

Question 850

A school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. What pair of supported action and practical verification should be approved?

  1. Inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup. Acceptance evidence: Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.
  2. 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.
  3. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Acceptance evidence: In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.
  4. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments. Acceptance evidence: Run kubectl kustomize for development and production overlays and compare the resulting YAML objects before application.

Explanation

Correct Answer

C:

The situation is that a school cluster administrator wants to debug a Pod while preserving the image's minimal runtime footprint. Use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Acceptance evidence: In a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action. This pairing is justified because an ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration.

Incorrect Answers

A:

This action and check address the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors” instead of the stated acceptance requirement. The matching action is to use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Its confirming test is to in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

B:

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 use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Its confirming test is to in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

D:

This action and check address the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” instead of the stated acceptance requirement. The matching action is to use an authorized kubectl debug ephemeral container when an application image lacks troubleshooting tools and policy permits ephemeral containers. Its confirming test is to in a lab add a read-only debug container, inspect network conditions and verify audit logs record the ephemeral container action.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests