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 83

Question 820

A college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. Which implementation together with matching acceptance evidence best meets this case?

  1. Choose an appropriate RollingUpdate strategy with maxSurge and maxUnavailable, and verify readiness and service traffic during replacement. Acceptance evidence: Upgrade a synthetic four-replica app, monitor old/new ReplicaSets and ready endpoints, then compare observed minimum availability.
  2. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  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. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Acceptance evidence: Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.

Explanation

Correct Answer

C:

The situation is that a college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. 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. This pairing is justified because a deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Incorrect Answers

A:

The situation is that a college shares a Kubernetes production cluster and wants an auditable promotion gate for student applications. This action and check address the distinct objective “Configure Deployment rolling updates with availability safeguards” instead of the stated acceptance requirement. The matching action is to require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Its confirming test is to insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

B:

This action and check address the distinct objective “Explain the container runtime interface without conflating it with the control plane” instead of the stated acceptance requirement. The matching action is to require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Its confirming test is to insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

D:

This action and check address the distinct objective “Separate CI build verification from CD environment promotion” instead of the stated acceptance requirement. The matching action is to require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application. Its confirming test is to insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.

Question 821

A shipping API starts and exits after reading an invalid configuration value. What technical action should the platform team take in this situation?

  1. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads.
  2. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation.
  3. Inspect the relevant object's conditions and timestamped Events to place the failure at API admission, scheduling, image pulling or runtime startup.
  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

A:

Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. This resolves the issue because kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events. To verify, trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

Incorrect Answers

B:

This option addresses the distinct objective “Explain desired state versus observed status in Kubernetes objects”, not the immediate requirement. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. For the stated case, kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

C:

This option addresses the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”, not the immediate requirement. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings. For the stated case, kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

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, kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

Question 822

A shipping API starts and exits after reading an invalid configuration value. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.
  2. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments.
  3. The scheduler selects a suitable node for an unscheduled Pod; kubelet on that node uses the runtime to start and monitor containers.
  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:

Kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events. It supports this action: Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. To confirm, trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

Incorrect Answers

B:

That statement explains the distinct objective “Separate CI build verification from CD environment promotion” rather than the cause in this case. The deciding mechanism here is that kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

C:

That statement explains the distinct objective “Separate kube-scheduler decisions from kubelet execution” rather than the cause in this case. The deciding mechanism here is that kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

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 kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

Question 823

A shipping API starts and exits after reading an invalid configuration value. What acceptance check most directly confirms this requirement is met?

  1. Taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.
  2. Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.
  3. Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.
  4. Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

Explanation

Correct Answer

D:

Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container. This is the relevant test because kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Understand taints and tolerations as repulsion controls”, but not the required result. For this case, trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

B:

This check would help evaluate the distinct objective “Separate CI build verification from CD environment promotion”, but not the required result. For this case, trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

C:

This check would help evaluate the distinct objective “Correlate application rollout revisions with error spikes”, but not the required result. For this case, trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

Question 824

A shipping API starts and exits after reading an invalid configuration value. The team suggests: “Delete a failing Pod immediately and discard its only useful previous startup log before capturing evidence.” Which failure should the reviewer anticipate?

  1. The image-pull issue stays unresolved because etcd is not the node component managing container starts.
  2. The replacement also fails while operators lack the information needed to identify the application error.
  3. The production binary can differ from the validated image even though the release version label matches.
  4. An application regression can remain live even though container and readiness probes are healthy.

Explanation

Correct Answer

B:

The replacement also fails while operators lack the information needed to identify the application error. The shortcut creates this risk because kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

Incorrect Answers

A:

That outcome concerns the distinct objective “Recognize the kubelet role in local Pod lifecycle management”; it is not the most direct consequence of this shortcut. The relevant consequence is that the replacement also fails while operators lack the information needed to identify the application error.

C:

That outcome concerns the distinct objective “Separate CI build verification from CD environment promotion”; it is not the most direct consequence of this shortcut. The relevant consequence is that the replacement also fails while operators lack the information needed to identify the application error.

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 replacement also fails while operators lack the information needed to identify the application error.

Question 825

A shipping API starts and exits after reading an invalid configuration value. Which engineering change and test jointly addresses the scenario?

  1. 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.
  2. 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.
  3. 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.
  4. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. Acceptance evidence: Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

Explanation

Correct Answer

D:

Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. Acceptance evidence: Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container. This pairing is justified because kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

Incorrect Answers

A:

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 read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. Its confirming test is to trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

B:

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 read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. Its confirming test is to trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

C:

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 read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. Its confirming test is to trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

Question 826

A school learning service restarts frequently while current logs show only a fresh startup message. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Require reviewed image provenance, admission policy checks and staged traffic validation before promoting a cloud-native application.
  2. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC.
  3. Measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow.
  4. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads.

Explanation

Correct Answer

D:

The situation is that a school learning service restarts frequently while current logs show only a fresh startup message. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. This resolves the issue because kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events. To verify, trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

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, kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

B:

This option addresses the distinct objective “Distinguish etcd persistence from running workload data”, not the immediate requirement. Etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd. For the stated case, kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

C:

The situation is that a school learning service restarts frequently while current logs show only a fresh startup message. 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, kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

Question 827

A school learning service restarts frequently while current logs show only a fresh startup message. Which platform mechanism explains why the suitable approach works?

  1. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
  2. Healthy direct IP connectivity with failed name resolution suggests a DNS path issue; failed Pod-to-Pod IP traffic suggests a lower-level network problem.
  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. Different Kubernetes components emit distinct Events; identifying the stage prevents changing unrelated network or application settings.

Explanation

Correct Answer

C:

The situation is that a school learning service restarts frequently while current logs show only a fresh startup message. Kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events. It supports this action: Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. To confirm, trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

Incorrect Answers

A:

The situation is that a school learning service restarts frequently while current logs show only a fresh startup message. 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 kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

B:

That statement explains the distinct objective “Diagnose cluster DNS separately from Pod network reachability” rather than the cause in this case. The deciding mechanism here is that kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

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 kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

Question 828

A school learning service restarts frequently while current logs show only a fresh startup message. Which controlled observation would best validate the intended improvement?

  1. Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.
  2. Generate controlled CPU load, verify HPA current/target metric reporting and observe replica changes within configured limits.
  3. Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.
  4. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Explanation

Correct Answer

A:

The situation is that a school learning service restarts frequently while current logs show only a fresh startup message. Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container. This is the relevant test because kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts”, but not the required result. For this case, trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

C:

This check would help evaluate the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core”, but not the required result. For this case, trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

D:

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, trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

Question 829

A school learning service restarts frequently while current logs show only a fresh startup message. An engineer proposes: “Delete a failing Pod immediately and discard its only useful previous startup log before capturing evidence.” What adverse outcome would be most direct?

  1. An application regression can remain live even though container and readiness probes are healthy.
  2. The operator can interrupt healthy networking while the original admission or image problem persists.
  3. The Service receives no intended ready endpoints even when healthy Pods exist.
  4. The replacement also fails while operators lack the information needed to identify the application error.

Explanation

Correct Answer

D:

The situation is that a school learning service restarts frequently while current logs show only a fresh startup message. The replacement also fails while operators lack the information needed to identify the application error. The shortcut creates this risk because kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

Incorrect Answers

A:

The situation is that a school learning service restarts frequently while current logs show only a fresh startup message. 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 replacement also fails while operators lack the information needed to identify the application error.

B:

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 replacement also fails while operators lack the information needed to identify the application error.

C:

That outcome concerns the distinct objective “Use labels and selectors to connect resources predictably”; it is not the most direct consequence of this shortcut. The relevant consequence is that the replacement also fails while operators lack the information needed to identify the application error.

Question 830

A school learning service restarts frequently while current logs show only a fresh startup message. What pair of supported action and practical verification should be approved?

  1. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. Acceptance evidence: Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.
  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. 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. 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.

Explanation

Correct Answer

A:

The situation is that a school learning service restarts frequently while current logs show only a fresh startup message. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. Acceptance evidence: Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container. This pairing is justified because kubectl logs retrieves container output and --previous can expose the prior terminated instance, but application output is not a substitute for cluster Events.

Incorrect Answers

B:

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 read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. Its confirming test is to trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

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 read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. Its confirming test is to trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

D:

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 read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads. Its confirming test is to trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests