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 40

Question 390

A financial service team sees ImagePullBackOff because its namespace lacks valid image pull credentials. Which engineering change and test jointly addresses the scenario?

  1. Measure request latency and error rates, inspect application logs and correlate trace spans for the affected request before guessing which Pod is slow. Acceptance evidence: Generate a synthetic slow downstream call and verify a trace links frontend and backend spans while metrics show the latency change.
  2. Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Acceptance evidence: Deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
  3. Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image. Acceptance evidence: Compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
  4. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Acceptance evidence: Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.

Explanation

Correct Answer

B:

The situation is that a financial service team sees ImagePullBackOff because its namespace lacks valid image pull credentials. Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Acceptance evidence: Deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token. This pairing is justified because image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.

Incorrect Answers

A:

This action and check address the distinct objective “Use metrics, logs and traces together when investigating cross-service latency” instead of the stated acceptance requirement. The matching action is to use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Its confirming test is to deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.

C:

This action and check address the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling” instead of the stated acceptance requirement. The matching action is to use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Its confirming test is to deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.

D:

This action and check address the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” instead of the stated acceptance requirement. The matching action is to use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Its confirming test is to deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.

Question 391

A small museum's new image runs a batch script and exits instead of serving HTTP requests. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Inspect image default command and Pod command or args settings to determine what executable starts in the container.
  2. Define symptom-based Prometheus alerting rules with sensible durations and route alerts through Alertmanager to the responsible service team.
  3. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload.
  4. Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image.

Explanation

Correct Answer

A:

Inspect image default command and Pod command or args settings to determine what executable starts in the container. This resolves the issue because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. To verify, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

Incorrect Answers

B:

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, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

C:

This option addresses the distinct objective “Use kubectl get and describe for distinct inspection needs”, not the immediate requirement. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. For the stated case, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

D:

This option addresses the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, not the immediate requirement. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. For the stated case, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

Question 392

A small museum's new image runs a batch script and exits instead of serving HTTP requests. Which platform mechanism explains why the suitable approach works?

  1. The scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests.
  2. The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.
  3. CrashLoopBackOff reflects kubelet restart backoff after container failures; the underlying cause may be application configuration, exit code or a failed liveness probe.
  4. emptyDir is initialized for a Pod and its contents can be shared among containers but do not survive the Pod's removal.

Explanation

Correct Answer

B:

The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. It supports this action: Inspect image default command and Pod command or args settings to determine what executable starts in the container. To confirm, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

Incorrect Answers

A:

That statement explains the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes” rather than the cause in this case. The deciding mechanism here is that the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

C:

That statement explains the distinct objective “Diagnose CrashLoopBackOff from restart history and previous logs” rather than the cause in this case. The deciding mechanism here is that the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

D:

That statement explains the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence” rather than the cause in this case. The deciding mechanism here is that the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

Question 393

A small museum's new image runs a batch script and exits instead of serving HTTP requests. Which controlled observation would best validate the intended improvement?

  1. Deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
  2. Test the workload with and without a preferred zone and verify it still schedules when preferred nodes are busy.
  3. Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
  4. Send a synthetic request with a correlation ID and confirm it appears in the trace and relevant logs while latency metrics change.

Explanation

Correct Answer

C:

Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting. This is the relevant test because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, but not the required result. For this case, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

B:

This check would help evaluate the distinct objective “Distinguish preferred node affinity from required scheduling rules”, but not the required result. For this case, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

D:

This check would help evaluate the distinct objective “Explain metrics, logs and traces as complementary observability signals”, but not the required result. For this case, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

Question 394

A small museum's new image runs a batch script and exits instead of serving HTTP requests. An engineer proposes: “Increase ReplicaSet count to fix a container that immediately exits because its startup arguments are invalid.” What adverse outcome would be most direct?

  1. Operators can see the metadata but the Service cannot select the desired Pods using that annotation.
  2. The operator may deploy unsupported changes without release provenance or a responsible maintenance path.
  3. More replicas fail the same way because the process configuration, not desired replica count, caused the exit.
  4. The container may enter a restart loop before completing initialization, prolonging unavailability.

Explanation

Correct Answer

C:

More replicas fail the same way because the process configuration, not desired replica count, caused the exit. The shortcut creates this risk because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use annotations for tool metadata rather than workload selection”; it is not the most direct consequence of this shortcut. The relevant consequence is that more replicas fail the same way because the process configuration, not desired replica count, caused the exit.

B:

That outcome concerns the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”; it is not the most direct consequence of this shortcut. The relevant consequence is that more replicas fail the same way because the process configuration, not desired replica count, caused the exit.

D:

That outcome concerns the distinct objective “Understand readiness, liveness and startup probes as different signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that more replicas fail the same way because the process configuration, not desired replica count, caused the exit.

Question 395

A small museum's new image runs a batch script and exits instead of serving HTTP requests. What pair of supported action and practical verification should be approved?

  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. 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.
  3. Inspect image default command and Pod command or args settings to determine what executable starts in the container. Acceptance evidence: Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
  4. Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image. Acceptance evidence: Deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.

Explanation

Correct Answer

C:

Inspect image default command and Pod command or args settings to determine what executable starts in the container. Acceptance evidence: Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting. This pairing is justified because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

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 inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

B:

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 inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

D:

This action and check address the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” instead of the stated acceptance requirement. The matching action is to inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

Question 396

A university lab accidentally overrides the entrypoint of a known-good container image. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image.
  2. Check that a supported CNI plugin assigns reachable Pod addresses across worker nodes before troubleshooting Service routing or DNS names.
  3. Use narrowly scoped imagePullSecrets or an approved node identity to authorize the runtime to pull a private image.
  4. Inspect image default command and Pod command or args settings to determine what executable starts in the container.

Explanation

Correct Answer

D:

The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. Inspect image default command and Pod command or args settings to determine what executable starts in the container. This resolves the issue because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. To verify, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

Incorrect Answers

A:

This option addresses the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling”, not the immediate requirement. Multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer. For the stated case, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

B:

This option addresses the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”, not the immediate requirement. Kubernetes expects a Pod network providing Pod-to-Pod connectivity; the CNI implementation configures networking while Services provide stable virtual access to changing endpoints. For the stated case, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

C:

The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. This option addresses the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, not the immediate requirement. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. For the stated case, the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

Question 397

A university lab accidentally overrides the entrypoint of a known-good container image. Which causal explanation supports the intended design choice?

  1. A NotReady or pressure-affected node can stop hosting healthy Pods even when their Deployment and Service definitions remain valid.
  2. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
  3. Readiness affects endpoint eligibility while liveness can cause restarts; a startup probe defers other probe checks until initialization succeeds.
  4. The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

Explanation

Correct Answer

D:

The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. It supports this action: Inspect image default command and Pod command or args settings to determine what executable starts in the container. To confirm, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

Incorrect Answers

A:

That statement explains the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads” rather than the cause in this case. The deciding mechanism here is that the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

B:

That statement explains the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration” rather than the cause in this case. The deciding mechanism here is that the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

C:

That statement explains the distinct objective “Understand readiness, liveness and startup probes as different signals” rather than the cause in this case. The deciding mechanism here is that the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

Question 398

A university lab accidentally overrides the entrypoint of a known-good container image. Which test provides the strongest evidence of a correct implementation?

  1. Compare SBOM and file inventory of the builder image with the published runtime stage and confirm the service still starts.
  2. Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
  3. Submit a reproducible synthetic issue and examine how maintainers triage, review and test a proposed patch before release.
  4. Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.

Explanation

Correct Answer

B:

The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting. This is the relevant test because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling”, but not the required result. For this case, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

C:

This check would help evaluate the distinct objective “Use open community governance and contribution processes for sustainable cloud-native projects”, but not the required result. For this case, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

D:

This check would help evaluate the distinct objective “Use labels and selectors to connect resources predictably”, but not the required result. For this case, inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

Question 399

A university lab accidentally overrides the entrypoint of a known-good container image. A shortcut is proposed: “Increase ReplicaSet count to fix a container that immediately exits because its startup arguments are invalid.” Which technical consequence follows most closely?

  1. Replacing the Pod destroys the only copy of business state unless independent durable storage exists.
  2. Customer requests may fail for minutes while operational dashboards report only that the configuration was accepted.
  3. The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.
  4. More replicas fail the same way because the process configuration, not desired replica count, caused the exit.

Explanation

Correct Answer

D:

The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. More replicas fail the same way because the process configuration, not desired replica count, caused the exit. The shortcut creates this risk because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

Incorrect Answers

A:

That outcome concerns the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”; it is not the most direct consequence of this shortcut. The relevant consequence is that more replicas fail the same way because the process configuration, not desired replica count, caused the exit.

B:

That outcome concerns the distinct objective “Design a release rollback trigger from measurable service signals”; it is not the most direct consequence of this shortcut. The relevant consequence is that more replicas fail the same way because the process configuration, not desired replica count, caused the exit.

C:

That outcome concerns the distinct objective “Identify reconciliation work performed by kube-controller-manager”; it is not the most direct consequence of this shortcut. The relevant consequence is that more replicas fail the same way because the process configuration, not desired replica count, caused the exit.

Question 400

A university lab accidentally overrides the entrypoint of a known-good container image. Which combined solution and independent check are most directly justified?

  1. Inspect image default command and Pod command or args settings to determine what executable starts in the container. Acceptance evidence: Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
  2. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Acceptance evidence: Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
  3. 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.
  4. Choose service boundaries around business capabilities and operational needs, documenting communication cost, ownership and fault tolerance. Acceptance evidence: Model a synthetic two-service checkout dependency and compare rollout independence with failure and latency overhead against a single service.

Explanation

Correct Answer

A:

The situation is that a university lab accidentally overrides the entrypoint of a known-good container image. Inspect image default command and Pod command or args settings to determine what executable starts in the container. Acceptance evidence: Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting. This pairing is justified because the container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement.

Incorrect Answers

B:

This action and check address the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” instead of the stated acceptance requirement. The matching action is to inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

C:

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 inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

D:

This action and check address the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior” instead of the stated acceptance requirement. The matching action is to inspect image default command and Pod command or args settings to determine what executable starts in the container. Its confirming test is to inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests