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 38

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.

Question 371

A healthcare portal must deploy exactly the container tested by its validation team. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Pin validated production images by registry digest and promote the same signed artifact across environments.
  2. Review Retain versus Delete behavior for data-bearing PVs and test cleanup policy using synthetic non-sensitive data.
  3. Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image.
  4. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image.

Explanation

Correct Answer

A:

Pin validated production images by registry digest and promote the same signed artifact across environments. This resolves the issue because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. To verify, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Incorrect Answers

B:

This option addresses the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion”, not the immediate requirement. 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. For the stated case, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

C:

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, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

D:

This option addresses the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, not the immediate requirement. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. For the stated case, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Question 372

A healthcare portal must deploy exactly the container tested by its validation team. Which causal explanation supports the intended design choice?

  1. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.
  2. TLS establishes endpoint confidentiality and identity, while authentication and RBAC separately determine which API operations a caller may execute.
  3. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
  4. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.

Explanation

Correct Answer

A:

Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. It supports this action: Pin validated production images by registry digest and promote the same signed artifact across environments. To confirm, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Incorrect Answers

B:

That statement explains the distinct objective “Protect API server access using authenticated TLS clients and audited authorization” rather than the cause in this case. The deciding mechanism here is that tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

C:

That statement explains the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” rather than the cause in this case. The deciding mechanism here is that tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

D:

That statement explains the distinct objective “Run images with least-privilege runtime security contexts” rather than the cause in this case. The deciding mechanism here is that tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Question 373

A healthcare portal must deploy exactly the container tested by its validation team. Which test provides the strongest evidence of a correct implementation?

  1. Taint a lab worker dedicated=training:NoSchedule, then compare placement of Pods with and without the toleration.
  2. Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.
  3. Deploy a synthetic private image using an approved Secret and confirm unauthorized namespaces cannot reuse a broad registry token.
  4. Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Explanation

Correct Answer

D:

Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec. This is the relevant test because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Understand taints and tolerations as repulsion controls”, but not the required result. For this case, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

B:

This check would help evaluate the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”, but not the required result. For this case, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

C:

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, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Question 374

A healthcare portal must deploy exactly the container tested by its validation team. A shortcut is proposed: “Use latest for every critical Pod and assume it always refers to the tested build from last week.” Which technical consequence follows most closely?

  1. A later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.
  2. The container may enter a restart loop before completing initialization, prolonging unavailability.
  3. The team may gain Pod access across all namespaces, expanding exposure beyond its job.
  4. The Pod remains unschedulable because requested capacity and node feasibility did not change.

Explanation

Correct Answer

A:

A later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback. The shortcut creates this risk because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Incorrect Answers

B:

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 a later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.

C:

That outcome concerns the distinct objective “Distinguish ClusterRoles from Roles and binding scope”; it is not the most direct consequence of this shortcut. The relevant consequence is that a later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.

D:

That outcome concerns the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”; it is not the most direct consequence of this shortcut. The relevant consequence is that a later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.

Question 375

A healthcare portal must deploy exactly the container tested by its validation team. Which combined solution and independent check are most directly justified?

  1. 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.
  2. 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.
  3. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller. Acceptance evidence: In a staging gateway route 5 percent to a canary, inspect version-specific success rates and verify a rollback rule.
  4. Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Acceptance evidence: Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.

Explanation

Correct Answer

B:

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. This pairing is justified because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Incorrect Answers

A:

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 pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

C:

This action and check address the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults” instead of the stated acceptance requirement. The matching action is to pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

D:

This action and check address the distinct objective “Separate kube-scheduler decisions from kubelet execution” instead of the stated acceptance requirement. The matching action is to pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Question 376

A school district uses an image tag reused by many builds and needs provenance during incident response. Which engineering approach is the most appropriate for this cloud-native case?

  1. Pin validated production images by registry digest and promote the same signed artifact across environments.
  2. Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones.
  3. Check EndpointSlices and Pod readiness when a Service exists but connections reach no application backends.
  4. Inspect image default command and Pod command or args settings to determine what executable starts in the container.

Explanation

Correct Answer

A:

The situation is that a school district uses an image tag reused by many builds and needs provenance during incident response. Pin validated production images by registry digest and promote the same signed artifact across environments. This resolves the issue because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. To verify, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Incorrect Answers

B:

This option addresses the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, not the immediate requirement. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable. For the stated case, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

C:

This option addresses the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”, not the immediate requirement. EndpointSlices describe endpoint addresses and readiness associated with a Service, allowing its dataplane to route toward matching healthy Pods. For the stated case, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

D:

This option addresses the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”, not the immediate requirement. The container runtime starts the configured process, and a crash or early exit can terminate the container regardless of Kubernetes placement. For the stated case, tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Question 377

A school district uses an image tag reused by many builds and needs provenance during incident response. What infrastructure principle makes the correct treatment effective?

  1. The kube-apiserver validates authorized API requests and exposes the declarative resource interface; kubelets and controllers subsequently reconcile the saved desired state.
  2. emptyDir is initialized for a Pod and its contents can be shared among containers but do not survive the Pod's removal.
  3. Service meshes commonly use proxies or ambient dataplanes to control east-west traffic; ingress/gateway handling addresses entry routes and can integrate with the mesh.
  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

D:

The situation is that a school district uses an image tag reused by many builds and needs provenance during incident response. Tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label. It supports this action: Pin validated production images by registry digest and promote the same signed artifact across environments. To confirm, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Incorrect Answers

A:

That statement explains the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point” rather than the cause in this case. The deciding mechanism here is that tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

B:

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 tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

C:

That statement explains the distinct objective “Distinguish service mesh traffic management from external ingress routing” rather than the cause in this case. The deciding mechanism here is that tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Question 378

A school district uses an image tag reused by many builds and needs provenance during incident response. What verification result would most convincingly distinguish a working solution from a claim?

  1. Write a synthetic temporary file into emptyDir, restart a container and then recreate the Pod to compare lifetime semantics.
  2. Run nslookup for a Service using short and namespace-qualified names from test Pods in two different namespaces.
  3. Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
  4. Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Explanation

Correct Answer

D:

The situation is that a school district uses an image tag reused by many builds and needs provenance during incident response. Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec. This is the relevant test because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, but not the required result. For this case, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

B:

This check would help evaluate the distinct objective “Verify CoreDNS resolution and namespace-qualified Service names”, but not the required result. For this case, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

C:

This check would help evaluate the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”, but not the required result. For this case, resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Question 379

A school district uses an image tag reused by many builds and needs provenance during incident response. The change review contains this proposal: “Use latest for every critical Pod and assume it always refers to the tested build from last week.” What risk matters most?

  1. The scheduler could place multiple replicas together, leaving a node without the intended local collector.
  2. Untrusted images or privileged settings can enter production without an auditable approval decision.
  3. A later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.
  4. More replicas fail the same way because the process configuration, not desired replica count, caused the exit.

Explanation

Correct Answer

C:

The situation is that a school district uses an image tag reused by many builds and needs provenance during incident response. A later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback. The shortcut creates this risk because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Incorrect Answers

A:

That outcome concerns the distinct objective “Select DaemonSet for node-local agents rather than Deployment replica counts”; it is not the most direct consequence of this shortcut. The relevant consequence is that a later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.

B:

That outcome concerns the distinct objective “Define secure release governance with staged approvals and policy verification”; it is not the most direct consequence of this shortcut. The relevant consequence is that a later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.

D:

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 a later registry push can change deployed bits unexpectedly, defeating reproducible approval and rollback.

Question 380

A school district uses an image tag reused by many builds and needs provenance during incident response. Which implementation together with matching acceptance evidence best meets this case?

  1. 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.
  2. 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.
  3. 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.
  4. Review Sandbox, Incubating and Graduated CNCF stages as community maturity signals while independently assessing a project's fitness, lifecycle and security. Acceptance evidence: Compare the governance and release activity of two projects and document which operational support and security tests are still required.

Explanation

Correct Answer

B:

The situation is that a school district uses an image tag reused by many builds and needs provenance during incident response. 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. This pairing is justified because tags can move to a different image digest over time, while a digest identifies specific content independently of a mutable label.

Incorrect Answers

A:

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 pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

C:

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 pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

D:

This action and check address the distinct objective “Understand CNCF project maturity stages without equating them to security approval” instead of the stated acceptance requirement. The matching action is to pin validated production images by registry digest and promote the same signed artifact across environments. Its confirming test is to resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests