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 87

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.

Question 861

A public library web app resolves api.library.svc but receives no successful responses. Which engineering approach is the most appropriate for this cloud-native case?

  1. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments.
  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. Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources.

Explanation

Correct Answer

B:

Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. This resolves the issue because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port. To verify, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Incorrect Answers

A:

This option addresses the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”, not the immediate requirement. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files. For the stated case, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

C:

This option addresses the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, not the immediate requirement. An ephemeral container can join a Pod's namespaces for observation but is not a substitute for repairing the owning Deployment's desired configuration. For the stated case, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

D:

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, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Question 862

A public library web app resolves api.library.svc but receives no successful responses. What infrastructure principle makes the correct treatment effective?

  1. 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.
  2. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
  3. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.
  4. Metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

Explanation

Correct Answer

B:

A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port. It supports this action: Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. To confirm, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Incorrect Answers

A:

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 a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

C:

That statement explains the distinct objective “Explain metrics, logs and traces as complementary observability signals” rather than the cause in this case. The deciding mechanism here is that a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

D:

That statement explains the distinct objective “Use metrics, logs and traces together when investigating cross-service latency” rather than the cause in this case. The deciding mechanism here is that a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Question 863

A public library web app resolves api.library.svc but receives no successful responses. What verification result would most convincingly distinguish a working solution from a claim?

  1. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
  2. Create synthetic invalid quota, unschedulable node and missing-image cases and compare their event reasons and assigned node status.
  3. Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.
  4. Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.

Explanation

Correct Answer

A:

Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms. This is the relevant test because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Incorrect Answers

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, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

C:

This check would help evaluate the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, but not the required result. For this case, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

D:

This check would help evaluate the distinct objective “Identify reconciliation work performed by kube-controller-manager”, but not the required result. For this case, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Question 864

A public library web app resolves api.library.svc but receives no successful responses. The change review contains this proposal: “Recreate the CoreDNS deployment every time a Service resolves but still returns connection refused.” What risk matters most?

  1. The true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.
  2. DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.
  3. The observed rollout may expose far more users than intended because percentage routing was never configured.
  4. The reported reliability can look excellent while customer transactions routinely fail or exceed acceptable latency.

Explanation

Correct Answer

B:

DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged. The shortcut creates this risk because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”; it is not the most direct consequence of this shortcut. The relevant consequence is that DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.

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 DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.

D:

That outcome concerns the distinct objective “Use SLI and SLO measures to focus reliability objectives”; it is not the most direct consequence of this shortcut. The relevant consequence is that DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.

Question 865

A public library web app resolves api.library.svc but receives no successful responses. Which implementation together with matching acceptance evidence best meets this case?

  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. 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.
  3. Configure readiness to stop sending Service traffic to an unready Pod, liveness to restart an unhealthy container and startup to allow slow initialization. Acceptance evidence: Delay a synthetic app response and compare EndpointSlice readiness with restart counts under controlled probe settings.
  4. Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Acceptance evidence: Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Explanation

Correct Answer

D:

Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Acceptance evidence: Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms. This pairing is justified because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Incorrect Answers

A:

This action and check address the distinct objective “Use kubectl logs and previous container logs to isolate application crashes” instead of the stated acceptance requirement. The matching action is to check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

B:

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 check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

C:

This action and check address the distinct objective “Understand readiness, liveness and startup probes as different signals” instead of the stated acceptance requirement. The matching action is to check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Question 866

A regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. What technical action should the platform team take in this situation?

  1. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods.
  2. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped.
  3. Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing.
  4. Read current logs and --previous logs for the failing container and correlate timestamps with Pod restart counts before altering workloads.

Explanation

Correct Answer

C:

The situation is that a regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. This resolves the issue because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port. To verify, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Incorrect Answers

A:

This option addresses the distinct objective “Distinguish Deployment desired state from a manually created Pod”, not the immediate requirement. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object. For the stated case, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

B:

This option addresses the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, not the immediate requirement. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller. For the stated case, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

D:

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, a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Question 867

A regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Kubernetes object transitions and application telemetry must be correlated; a healthy rollout condition alone does not prove user-level functionality.
  2. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
  3. Authentication establishes who calls the API; RBAC authorization checks requested verb, resource and namespace before the API permits it.
  4. A deployment pipeline is a trust boundary; signed artifacts and automated policy tests reduce the risk of unreviewed configurations reaching production.

Explanation

Correct Answer

B:

The situation is that a regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port. It supports this action: Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. To confirm, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Incorrect Answers

A:

That statement explains the distinct objective “Correlate application rollout revisions with error spikes” rather than the cause in this case. The deciding mechanism here is that a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

C:

That statement explains the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” rather than the cause in this case. The deciding mechanism here is that a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

D:

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 a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Question 868

A regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. What acceptance check most directly confirms this requirement is met?

  1. Promote the same image digest into two test namespaces with different safe endpoints, verifying Secret values are not in image layers.
  2. Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.
  3. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
  4. Simulate an unavailable lab worker, inspect Ready condition and Pod Events, then confirm managed workloads are rescheduled where feasible.

Explanation

Correct Answer

C:

The situation is that a regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms. This is the relevant test because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Externalize application configuration from an image while protecting secrets”, but not the required result. For this case, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

B:

This check would help evaluate the distinct objective “Use metrics, logs and traces together when investigating cross-service latency”, but not the required result. For this case, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

D:

This check would help evaluate the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”, but not the required result. For this case, test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Question 869

A regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. The team suggests: “Recreate the CoreDNS deployment every time a Service resolves but still returns connection refused.” Which failure should the reviewer anticipate?

  1. The operator can interrupt healthy networking while the original admission or image problem persists.
  2. DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.
  3. Unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
  4. The application never becomes operational because packaging metadata is confused with cluster reconciliation.

Explanation

Correct Answer

B:

The situation is that a regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged. The shortcut creates this risk because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

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 DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.

C:

That outcome concerns the distinct objective “Diagnose cluster DNS separately from Pod network reachability”; it is not the most direct consequence of this shortcut. The relevant consequence is that DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.

D:

That outcome concerns the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”; it is not the most direct consequence of this shortcut. The relevant consequence is that DNS disruption may affect the whole cluster while the actual routing mismatch remains unchanged.

Question 870

A regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. Which engineering change and test jointly addresses the scenario?

  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. Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Acceptance evidence: Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
  3. 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.
  4. Use a ClusterRole for cluster-scoped resources or reusable rule definitions, recognizing that a RoleBinding to a ClusterRole grants those rules only in one namespace for namespaced resources. Acceptance evidence: Bind a synthetic ClusterRole through RoleBinding in namespace-a, then verify access fails in namespace-b.

Explanation

Correct Answer

B:

The situation is that a regional insurer fixes a selector typo but backend calls still fail because the container listens on another port. Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Acceptance evidence: Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms. This pairing is justified because a Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.

Incorrect Answers

A:

This action and check address the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” instead of the stated acceptance requirement. The matching action is to check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

C:

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 check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

D:

This action and check address the distinct objective “Distinguish ClusterRoles from Roles and binding scope” instead of the stated acceptance requirement. The matching action is to check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing. Its confirming test is to test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests