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 88

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.

Question 871

An insurance quote API is slow although its frontend Pod CPU usage remains low. What technical action should the platform team take in this situation?

  1. Check DNS lookup, EndpointSlice population, Pod readiness and actual process port in a deliberate sequence before modifying traffic routing.
  2. Inject environment-specific nonsecret values through ConfigMaps and secrets through guarded Secret references without rebuilding a different application image.
  3. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching.
  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

D:

Measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. This resolves the issue because metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question. To verify, generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

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, metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

B:

This option addresses the distinct objective “Externalize application configuration from an image while protecting secrets”, not the immediate requirement. Image immutability separates software from environment configuration; mounted or environment-provided configuration can be updated by approved mechanisms, sometimes requiring rollout. For the stated case, metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

C:

This option addresses the distinct objective “Use labels and selectors to connect resources predictably”, not the immediate requirement. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships. For the stated case, metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

Question 872

An insurance quote API is slow although its frontend Pod CPU usage remains low. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. 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.
  2. Metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.
  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. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files.

Explanation

Correct Answer

B:

Metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question. It supports this action: Measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. To confirm, generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

Incorrect Answers

A:

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 metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

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 metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

D:

That statement explains the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” rather than the cause in this case. The deciding mechanism here is that metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

Question 873

An insurance quote API is slow although its frontend Pod CPU usage remains low. What acceptance check most directly confirms this requirement is met?

  1. Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.
  2. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
  3. Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
  4. Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

Explanation

Correct Answer

D:

Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change. This is the relevant test because metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

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, generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

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, generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

C:

This check would help evaluate the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, but not the required result. For this case, generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

Question 874

An insurance quote API is slow although its frontend Pod CPU usage remains low. The team suggests: “Increase every Deployment's CPU limit merely because a user reports a slow request without examining downstream dependencies.” Which failure should the reviewer anticipate?

  1. The true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.
  2. Unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
  3. Credentials can leak through registries and the binaries cannot be compared as the same tested artifact.
  4. The replacement also fails while operators lack the information needed to identify the application error.

Explanation

Correct Answer

A:

The true database bottleneck remains and resource adjustments can increase cost without fixing service behavior. The shortcut creates this risk because metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

Incorrect Answers

B:

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 the true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.

C:

That outcome concerns the distinct objective “Externalize application configuration from an image while protecting secrets”; it is not the most direct consequence of this shortcut. The relevant consequence is that the true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.

D:

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 true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.

Question 875

An insurance quote API is slow although its frontend Pod CPU usage remains low. Which engineering change and test jointly addresses the scenario?

  1. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
  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. 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

B:

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. This pairing is justified because metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

Incorrect Answers

A:

This action and check address the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” instead of the stated acceptance requirement. The matching action is to measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Its confirming test is to generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

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 measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Its confirming test is to generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

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 measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Its confirming test is to generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

Question 876

A university's course search depends on three services and needs to identify which hop adds most latency. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Compare Deployment rollout history, changed image digests, readiness events and application error times to identify an introduced regression.
  2. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance.
  3. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments.
  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

D:

The situation is that a university's course search depends on three services and needs to identify which hop adds most latency. Measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. This resolves the issue because metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question. To verify, generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

Incorrect Answers

A:

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

B:

This option addresses the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”, not the immediate requirement. A DaemonSet controller targets eligible nodes for a Pod each, adapting to node additions and labels rather than maintaining a global arbitrary replica count. For the stated case, metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

C:

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, metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

Question 877

A university's course search depends on three services and needs to identify which hop adds most latency. Which platform mechanism explains why the suitable approach works?

  1. A namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
  2. Metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.
  3. A Service name may resolve successfully while its selector yields no ready endpoints, and both differ from a backend listening on the wrong port.
  4. HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.

Explanation

Correct Answer

B:

The situation is that a university's course search depends on three services and needs to identify which hop adds most latency. Metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question. It supports this action: Measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. To confirm, generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

Incorrect Answers

A:

That statement explains the distinct objective “Use namespaces as organizational scopes without treating them as firewalls” rather than the cause in this case. The deciding mechanism here is that metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

C:

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 metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

D:

That statement explains the distinct objective “Use HorizontalPodAutoscaler metrics rather than ad hoc instance scripts” rather than the cause in this case. The deciding mechanism here is that metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

Question 878

A university's course search depends on three services and needs to identify which hop adds most latency. Which controlled observation would best validate the intended improvement?

  1. Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.
  2. Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.
  3. Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.
  4. Attempt to create a privileged test Pod in a restricted namespace and inspect the admission rejection message.

Explanation

Correct Answer

A:

The situation is that a university's course search depends on three services and needs to identify which hop adds most latency. Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change. This is the relevant test because metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

Incorrect Answers

B:

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, generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

C:

This check would help evaluate the distinct objective “Separate CI build verification from CD environment promotion”, but not the required result. For this case, generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

D:

This check would help evaluate the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, but not the required result. For this case, generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

Question 879

A university's course search depends on three services and needs to identify which hop adds most latency. An engineer proposes: “Increase every Deployment's CPU limit merely because a user reports a slow request without examining downstream dependencies.” What adverse outcome would be most direct?

  1. The true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.
  2. The subject receives unnecessary authority to alter privileged resources or unrelated namespaces.
  3. The change is repeatedly reverted, making incident response and audit history inconsistent.
  4. An application regression can remain live even though container and readiness probes are healthy.

Explanation

Correct Answer

A:

The situation is that a university's course search depends on three services and needs to identify which hop adds most latency. The true database bottleneck remains and resource adjustments can increase cost without fixing service behavior. The shortcut creates this risk because metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

Incorrect Answers

B:

That outcome concerns the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”; it is not the most direct consequence of this shortcut. The relevant consequence is that the true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.

C:

That outcome concerns the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”; it is not the most direct consequence of this shortcut. The relevant consequence is that the true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.

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 true database bottleneck remains and resource adjustments can increase cost without fixing service behavior.

Question 880

A university's course search depends on three services and needs to identify which hop adds most latency. What pair of supported action and practical verification should be approved?

  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. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism. Acceptance evidence: Deploy a synthetic faulty image, monitor request errors and confirm the release controller or operator restores the last known healthy revision.
  3. Use cluster DNS records such as service.namespace.svc.cluster.local when a Pod connects to Services in other namespaces. Acceptance evidence: Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
  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

D:

The situation is that a university's course search depends on three services and needs to identify which hop adds most latency. 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. This pairing is justified because metrics reveal aggregate trends, logs record events and traces connect operations across services, so each signal answers a different debugging question.

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 measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Its confirming test is to generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

B:

This action and check address the distinct objective “Design a release rollback trigger from measurable service signals” instead of the stated acceptance requirement. The matching action is to measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Its confirming test is to generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

C:

This action and check address the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names” instead of the stated acceptance requirement. The matching action is to measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Its confirming test is to generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests