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 86

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.

Question 851

A municipal appointment API starts returning bad data immediately after a new image revision. Which engineering approach is the most appropriate for this cloud-native case?

  1. Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression.
  2. Use metrics for measurable trends, logs for event detail and distributed traces for individual transaction paths while sharing correlation identifiers.
  3. Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing.
  4. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement.

Explanation

Correct Answer

A:

Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. This resolves the issue because Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality. To verify, deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

Incorrect Answers

B:

This option addresses the distinct objective “Explain metrics, logs and traces as complementary observability signals”, not the immediate requirement. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop. For the stated case, Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

C:

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, Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

D:

This option addresses the distinct objective “Configure Deployment rolling updates with availability safeguards”, not the immediate requirement. A rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available. For the stated case, Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Question 852

A municipal appointment API starts returning bad data immediately after a new image revision. What infrastructure principle makes the correct treatment effective?

  1. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings.
  2. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload.
  3. A rolling Deployment temporarily creates and removes Pods within its surge and unavailable budgets, but readiness is required for new replicas to count as available.
  4. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Explanation

Correct Answer

D:

Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality. It supports this action: Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. To confirm, deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

Incorrect Answers

A:

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 Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

B:

That statement explains the distinct objective “Build meaningful alert rules and route notifications through Alertmanager” rather than the cause in this case. The deciding mechanism here is that Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

C:

That statement explains the distinct objective “Configure Deployment rolling updates with availability safeguards” rather than the cause in this case. The deciding mechanism here is that Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Question 853

A municipal appointment API starts returning bad data immediately after a new image revision. What verification result would most convincingly distinguish a working solution from a claim?

  1. Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
  2. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
  3. Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.
  4. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.

Explanation

Correct Answer

C:

Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior. This is the relevant test because Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift”, but not the required result. For this case, deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

B:

This check would help evaluate the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”, but not the required result. For this case, deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

D:

This check would help evaluate the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”, but not the required result. For this case, deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

Question 854

A municipal appointment API starts returning bad data immediately after a new image revision. The change review contains this proposal: “Dismiss customer errors because the Deployment reports availableReplicas equal to replicas after the release.” What risk matters most?

  1. An application regression can remain live even though container and readiness probes are healthy.
  2. More replicas fail the same way because the process configuration, not desired replica count, caused the exit.
  3. DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.
  4. An urgent fix is applied to only one environment and configuration drift grows difficult to audit.

Explanation

Correct Answer

A:

An application regression can remain live even though container and readiness probes are healthy. The shortcut creates this risk because Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Incorrect Answers

B:

That outcome concerns the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”; it is not the most direct consequence of this shortcut. The relevant consequence is that an application regression can remain live even though container and readiness probes are healthy.

C:

That outcome concerns the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”; it is not the most direct consequence of this shortcut. The relevant consequence is that an application regression can remain live even though container and readiness probes are healthy.

D:

That outcome concerns the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”; it is not the most direct consequence of this shortcut. The relevant consequence is that an application regression can remain live even though container and readiness probes are healthy.

Question 855

A municipal appointment API starts returning bad data immediately after a new image revision. Which implementation together with matching acceptance evidence best meets this case?

  1. 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.
  2. 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.
  3. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Acceptance evidence: Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  4. 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.

Explanation

Correct Answer

B:

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. This pairing is justified because Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Incorrect Answers

A:

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 compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Its confirming test is to deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

C:

This action and check address the distinct objective “Define secure release governance with staged approvals and policy verification” instead of the stated acceptance requirement. The matching action is to compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Its confirming test is to deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

D:

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 compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Its confirming test is to deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

Question 856

A retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. Which engineering approach is the most appropriate for this cloud-native case?

  1. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads.
  2. Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression.
  3. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team.
  4. Measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow.

Explanation

Correct Answer

B:

The situation is that a retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. This resolves the issue because Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality. To verify, deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

Incorrect Answers

A:

This option addresses the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”, not the immediate requirement. Kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events. For the stated case, Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

C:

This option addresses the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, not the immediate requirement. Alert rules evaluate time-series expressions while Alertmanager groups, routes and silences notifications; neither automatically fixes the underlying workload. For the stated case, Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

D:

This option addresses the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”, not the immediate requirement. Metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question. For the stated case, Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Question 857

A retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. What infrastructure principle makes the correct treatment effective?

  1. Canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update.
  2. Service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure.
  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. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Explanation

Correct Answer

D:

The situation is that a retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality. It supports this action: Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. To confirm, deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

Incorrect Answers

A:

That statement explains the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” rather than the cause in this case. The deciding mechanism here is that Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

B:

That statement explains the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” rather than the cause in this case. The deciding mechanism here is that Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

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 Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Question 858

A retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. What verification result would most convincingly distinguish a working solution from a claim?

  1. Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.
  2. Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.
  3. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  4. Test a synthetic internal service call with mutual TLS policy and separately inspect the public Gateway listener and route status.

Explanation

Correct Answer

B:

The situation is that a retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior. This is the relevant test because Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”, but not the required result. For this case, deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

C:

The situation is that a retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. This check would help evaluate the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”, but not the required result. For this case, deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

D:

This check would help evaluate the distinct objective “Distinguish service mesh traffic management from external ingress routing”, but not the required result. For this case, deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

Question 859

A retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. The change review contains this proposal: “Dismiss customer errors because the Deployment reports availableReplicas equal to replicas after the release.” What risk matters most?

  1. Users may encounter failed requests because readiness and application-level health remain unverified.
  2. The replacement also fails while operators lack the information needed to identify the application error.
  3. The observed rollout may expose far more users than intended because percentage routing was never configured.
  4. An application regression can remain live even though container and readiness probes are healthy.

Explanation

Correct Answer

D:

The situation is that a retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. An application regression can remain live even though container and readiness probes are healthy. The shortcut creates this risk because Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Incorrect Answers

A:

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 an application regression can remain live even though container and readiness probes are healthy.

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 an application regression can remain live even though container and readiness probes are healthy.

C:

That outcome concerns the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”; it is not the most direct consequence of this shortcut. The relevant consequence is that an application regression can remain live even though container and readiness probes are healthy.

Question 860

A retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. Which implementation together with matching acceptance evidence best meets this case?

  1. Build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Acceptance evidence: Build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.
  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. 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.
  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

D:

The situation is that a retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. 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. This pairing is justified because Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.

Incorrect Answers

A:

This action and check address the distinct objective “Distinguish a container image from a running container and its writable layer” instead of the stated acceptance requirement. The matching action is to compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Its confirming test is to deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

B:

The situation is that a retailer sees new checkout failures but the Kubernetes Deployment condition remains Available. 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 compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Its confirming test is to deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

C:

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 compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression. Its confirming test is to deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests