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 37

Question 360

A retail site ships a signed image and wants equivalent runtime contents across nodes. Which engineering change and test jointly addresses the scenario?

  1. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Acceptance evidence: Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  2. 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.
  3. Recognize Kubernetes for orchestration, Prometheus for metrics, Envoy for data-plane proxying and Fluentd for log collection in the cloud-native landscape. Acceptance evidence: Build a study architecture diagram that connects each tool to its documented function and verify the expected data flow in a sample environment.
  4. Pin validated production images by registry digest and promote the same signed artifact across environments. Acceptance evidence: Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Explanation

Correct Answer

B:

The situation is that a retail site ships a signed image and wants equivalent runtime contents across nodes. 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. This pairing is justified because an image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage.

Incorrect Answers

A:

This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

C:

This action and check address the distinct objective “Identify CNCF ecosystem projects by their role rather than assuming all are Kubernetes core” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

D:

This action and check address the distinct objective “Use an immutable image digest for exact deployment provenance” instead of the stated acceptance requirement. The matching action is to build an OCI-compatible image with immutable packaged artifacts and treat running container writable state as ephemeral. Its confirming test is to build a test image, run a Pod and recreate it, verifying packaged files remain while an unmounted temporary file disappears.

Question 361

An engineering student compares ordinary Linux containers with full virtual machines during platform selection. Which engineering approach is the most appropriate for this cloud-native case?

  1. Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root.
  2. Define post-release checks for readiness, error rate and latency, and revert an unhealthy revision using an approved rollout mechanism.
  3. Run a logging or node monitoring agent as a DaemonSet when every eligible worker needs its own instance.
  4. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources.

Explanation

Correct Answer

D:

Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. This resolves the issue because linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine. To verify, in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

Incorrect Answers

A:

This option addresses the distinct objective “Run images with least-privilege runtime security contexts”, not the immediate requirement. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised. For the stated case, linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

B:

This option addresses the distinct objective “Design a release rollback trigger from measurable service signals”, not the immediate requirement. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible. For the stated case, linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

C:

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, linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

Question 362

An engineering student compares ordinary Linux containers with full virtual machines during platform selection. What infrastructure principle makes the correct treatment effective?

  1. Linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.
  2. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs.
  3. etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
  4. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop.

Explanation

Correct Answer

A:

Linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine. It supports this action: Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. To confirm, in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

Incorrect Answers

B:

That statement explains the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” rather than the cause in this case. The deciding mechanism here is that linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

C:

That statement explains the distinct objective “Distinguish etcd persistence from running workload data” rather than the cause in this case. The deciding mechanism here is that linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

D:

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 linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

Question 363

An engineering student compares ordinary Linux containers with full virtual machines during platform selection. What verification result would most convincingly distinguish a working solution from a claim?

  1. Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
  2. Compare the governance and release activity of two projects and document which operational support and security tests are still required.
  3. Inspect a failed Pod's last terminated reason and check whether an unintended command override prevented the server from starting.
  4. In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

Explanation

Correct Answer

D:

In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior. This is the relevant test because linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”, but not the required result. For this case, in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

B:

This check would help evaluate the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, but not the required result. For this case, in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

C:

This check would help evaluate the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”, but not the required result. For this case, in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

Question 364

An engineering student compares ordinary Linux containers with full virtual machines during platform selection. The change review contains this proposal: “Assume a container runs its own independent kernel identical to a full hypervisor guest, so host-kernel risk is irrelevant.” What risk matters most?

  1. A later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.
  2. Unnecessary networking changes can disrupt unrelated services while the original name lookup error persists.
  3. Security decisions overlook shared-kernel attack surfaces and workload-specific resource contention.
  4. Sensitive workloads may remain reachable until actual identity and traffic controls are installed.

Explanation

Correct Answer

C:

Security decisions overlook shared-kernel attack surfaces and workload-specific resource contention. The shortcut creates this risk because linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use an immutable image digest for exact deployment provenance”; it is not the most direct consequence of this shortcut. The relevant consequence is that security decisions overlook shared-kernel attack surfaces and workload-specific resource contention.

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 security decisions overlook shared-kernel attack surfaces and workload-specific resource contention.

D:

That outcome concerns the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”; it is not the most direct consequence of this shortcut. The relevant consequence is that security decisions overlook shared-kernel attack surfaces and workload-specific resource contention.

Question 365

An engineering student compares ordinary Linux containers with full virtual machines during platform selection. Which implementation together with matching acceptance evidence best meets this case?

  1. Inspect the active kubeconfig context and namespace before applying manifests to staging or production. Acceptance evidence: Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  2. Set runAsNonRoot, suitable user IDs and drop unneeded Linux capabilities rather than assuming every container requires root. Acceptance evidence: Deploy a test Pod with runAsNonRoot and verify its effective user and capability sets while confirming app file permissions work.
  3. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Acceptance evidence: In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.
  4. Require approved image registries, signature or digest verification and patch ownership when admitting production container images. Acceptance evidence: Deploy one signed approved image and one unverified synthetic image under a test admission policy, recording expected allow and deny results.

Explanation

Correct Answer

C:

Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Acceptance evidence: In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior. This pairing is justified because linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

Incorrect Answers

A:

This action and check address the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster” instead of the stated acceptance requirement. The matching action is to use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Its confirming test is to in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

B:

This action and check address the distinct objective “Run images with least-privilege runtime security contexts” instead of the stated acceptance requirement. The matching action is to use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Its confirming test is to in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

D:

This action and check address the distinct objective “Use image provenance and policy controls without trusting mutable tags” instead of the stated acceptance requirement. The matching action is to use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Its confirming test is to in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

Question 366

A bank architect wants to explain why container CPU budgets and process visibility are configured separately. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Package reusable Kubernetes resource templates in a Helm chart and review rendered manifests and values before installation or upgrade.
  2. Configure readiness to stop sending Service traffic to an unready Pod, liveness to restart an unhealthy container and startup to allow slow initialization.
  3. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources.
  4. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC.

Explanation

Correct Answer

C:

The situation is that a bank architect wants to explain why container CPU budgets and process visibility are configured separately. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. This resolves the issue because linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine. To verify, in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

Incorrect Answers

A:

This option addresses the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”, not the immediate requirement. Helm renders and manages chart releases but depends on Kubernetes controllers to maintain actual Pods and networking after the API objects exist. For the stated case, linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

B:

This option addresses the distinct objective “Understand readiness, liveness and startup probes as different signals”, not the immediate requirement. Readiness affects endpoint eligibility while liveness can cause restarts; a startup probe defers other probe checks until initialization succeeds. For the stated case, linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

D:

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, linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

Question 367

A bank architect wants to explain why container CPU budgets and process visibility are configured separately. Which causal explanation supports the intended design choice?

  1. Linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.
  2. HPA adjusts desired replica count based on observed metric targets; it needs a functioning metrics source and cannot add missing node capacity itself.
  3. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.
  4. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Explanation

Correct Answer

A:

The situation is that a bank architect wants to explain why container CPU budgets and process visibility are configured separately. Linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine. It supports this action: Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. To confirm, in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

Incorrect Answers

B:

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 linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

C:

That statement explains the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability” rather than the cause in this case. The deciding mechanism here is that linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

D:

That statement explains the distinct objective “Use an immutable image digest for exact deployment provenance” rather than the cause in this case. The deciding mechanism here is that linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

Question 368

A bank architect wants to explain why container CPU budgets and process visibility are configured separately. Which test provides the strongest evidence of a correct implementation?

  1. Run helm template with staging values, inspect the generated Deployment and Service, and compare a revision's upgrade history.
  2. Delay a synthetic app response and compare EndpointSlice readiness with restart counts under controlled probe settings.
  3. Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  4. In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

Explanation

Correct Answer

D:

The situation is that a bank architect wants to explain why container CPU budgets and process visibility are configured separately. In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior. This is the relevant test because linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use Helm charts for parameterized application packages without equating them to cluster controllers”, but not the required result. For this case, in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

B:

This check would help evaluate the distinct objective “Understand readiness, liveness and startup probes as different signals”, but not the required result. For this case, in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

C:

This check would help evaluate the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, but not the required result. For this case, in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

Question 369

A bank architect wants to explain why container CPU budgets and process visibility are configured separately. A shortcut is proposed: “Assume a container runs its own independent kernel identical to a full hypervisor guest, so host-kernel risk is irrelevant.” Which technical consequence follows most closely?

  1. Priority differentiation is lost and capacity shortages still prevent scheduling or trigger avoidable disruption.
  2. Security decisions overlook shared-kernel attack surfaces and workload-specific resource contention.
  3. More replicas fail the same way because the process configuration, not desired replica count, caused the exit.
  4. The claim remains Pending and dependent Pods cannot mount the missing volume.

Explanation

Correct Answer

B:

The situation is that a bank architect wants to explain why container CPU budgets and process visibility are configured separately. Security decisions overlook shared-kernel attack surfaces and workload-specific resource contention. The shortcut creates this risk because linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”; it is not the most direct consequence of this shortcut. The relevant consequence is that security decisions overlook shared-kernel attack surfaces and workload-specific resource contention.

C:

That outcome concerns the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”; it is not the most direct consequence of this shortcut. The relevant consequence is that security decisions overlook shared-kernel attack surfaces and workload-specific resource contention.

D:

That outcome concerns the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk”; it is not the most direct consequence of this shortcut. The relevant consequence is that security decisions overlook shared-kernel attack surfaces and workload-specific resource contention.

Question 370

A bank architect wants to explain why container CPU budgets and process visibility are configured separately. Which combined solution and independent check are most directly justified?

  1. Use emptyDir for temporary sharing between containers within a Pod, and PVC-backed storage when data must survive Pod replacement. Acceptance evidence: Write a synthetic temporary file into emptyDir, restart a container and then recreate the Pod to compare lifetime semantics.
  2. 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.
  3. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Acceptance evidence: In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.
  4. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Acceptance evidence: Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.

Explanation

Correct Answer

C:

The situation is that a bank architect wants to explain why container CPU budgets and process visibility are configured separately. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Acceptance evidence: In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior. This pairing is justified because linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine.

Incorrect Answers

A:

This action and check address the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence” instead of the stated acceptance requirement. The matching action is to use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Its confirming test is to in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

B:

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 use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Its confirming test is to in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

D:

This action and check address the distinct objective “Use kubectl get and describe for distinct inspection needs” instead of the stated acceptance requirement. The matching action is to use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources. Its confirming test is to in a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests