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 6

Question 50

A museum's deployment is scheduled yet containers on one node repeatedly fail to initialize. Which engineering change and test jointly addresses the scenario?

  1. Inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API. Acceptance evidence: Describe a scheduled Pod with ImagePullBackOff and compare its assigned node against kubelet-related Events.
  2. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Acceptance evidence: Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
  3. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
  4. Choose an available StorageClass with a compatible CSI provisioner and appropriate binding behavior when creating a PVC. Acceptance evidence: Create a claim using a named test StorageClass and compare provisioner events and binding timing with a non-existent class.

Explanation

Correct Answer

A:

The situation is that a museum's deployment is scheduled yet containers on one node repeatedly fail to initialize. Inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API. Acceptance evidence: Describe a scheduled Pod with ImagePullBackOff and compare its assigned node against kubelet-related Events. This pairing is justified because each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node.

Incorrect Answers

B:

This action and check address the distinct objective “Use namespaces as organizational scopes without treating them as firewalls” instead of the stated acceptance requirement. The matching action is to inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API. Its confirming test is to describe a scheduled Pod with ImagePullBackOff and compare its assigned node against kubelet-related Events.

C:

This action and check address the distinct objective “Explain desired state versus observed status in Kubernetes objects” instead of the stated acceptance requirement. The matching action is to inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API. Its confirming test is to describe a scheduled Pod with ImagePullBackOff and compare its assigned node against kubelet-related Events.

D:

This action and check address the distinct objective “Use StorageClass for dynamic volume provisioning rather than handcrafting every disk” instead of the stated acceptance requirement. The matching action is to inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API. Its confirming test is to describe a scheduled Pod with ImagePullBackOff and compare its assigned node against kubelet-related Events.

Question 51

A small bank migrates worker nodes to a supported runtime before upgrading Kubernetes. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Define appropriate HTTP routing through an installed Ingress controller or Gateway API controller rather than expecting the API object alone to provision a proxy.
  2. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling.
  3. Use container runtime namespaces to isolate views of processes and networks while using cgroups to account for and constrain resources.
  4. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count.

Explanation

Correct Answer

B:

Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. This resolves the issue because a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface. To verify, inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

Incorrect Answers

A:

This option addresses the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure”, not the immediate requirement. Ingress and Gateway API express routing intent, while an actual controller/dataplane implements TLS termination, listeners and backend forwarding. For the stated case, a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

C:

This option addresses the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms”, not the immediate requirement. Linux namespaces affect visibility and isolation boundaries, while cgroups organize and limit resource usage; neither automatically supplies a full virtual machine. For the stated case, a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

D:

This option addresses the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”, not the immediate requirement. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. For the stated case, a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

Question 52

A small bank migrates worker nodes to a supported runtime before upgrading Kubernetes. Which platform mechanism explains why the suitable approach works?

  1. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
  2. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
  3. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.
  4. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.

Explanation

Correct Answer

C:

A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface. It supports this action: Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. To confirm, inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

Incorrect Answers

A:

That statement explains the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” rather than the cause in this case. The deciding mechanism here is that a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

B:

That statement explains the distinct objective “Use labels and selectors to connect resources predictably” rather than the cause in this case. The deciding mechanism here is that a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

D:

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 a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

Question 53

A small bank migrates worker nodes to a supported runtime before upgrading Kubernetes. Which controlled observation would best validate the intended improvement?

  1. Describe a scheduled Pod with ImagePullBackOff and compare its assigned node against kubelet-related Events.
  2. Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  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. Deploy two synthetic Pods on different nodes and test direct Pod IP connectivity before testing the Service virtual IP.

Explanation

Correct Answer

B:

Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure. This is the relevant test because a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, but not the required result. For this case, inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

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, inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

D:

This check would help evaluate the distinct objective “Distinguish the CNI Pod network from Service discovery and routing”, but not the required result. For this case, inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

Question 54

A small bank migrates worker nodes to a supported runtime before upgrading Kubernetes. An engineer proposes: “Treat Docker's legacy dockershim as a required built-in runtime component on every modern Kubernetes release.” What adverse outcome would be most direct?

  1. An unsupported runtime assumption misdirects troubleshooting and may block node bootstrap.
  2. Containers gain broad host exposure and compromise blast radius becomes larger than the application's needs.
  3. Availability and rollout behavior diverge because no workload controller owns the independent Pods.
  4. Replacing a Pod can destroy state because no independent persistent volume was requested.

Explanation

Correct Answer

A:

An unsupported runtime assumption misdirects troubleshooting and may block node bootstrap. The shortcut creates this risk because a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

Incorrect Answers

B:

That outcome concerns the distinct objective “Run images with least-privilege runtime security contexts”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unsupported runtime assumption misdirects troubleshooting and may block node bootstrap.

C:

That outcome concerns the distinct objective “Distinguish Deployment desired state from a manually created Pod”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unsupported runtime assumption misdirects troubleshooting and may block node bootstrap.

D:

That outcome concerns the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unsupported runtime assumption misdirects troubleshooting and may block node bootstrap.

Question 55

A small bank migrates worker nodes to a supported runtime before upgrading Kubernetes. What pair of supported action and practical verification should be approved?

  1. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
  2. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod. Acceptance evidence: Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.
  3. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  4. Prefer documented Kubernetes APIs and interoperable telemetry formats when possible while identifying any platform-specific extensions needed for the real deployment. Acceptance evidence: Test a synthetic standard API manifest and OpenTelemetry trace export across two platforms, documenting any unsupported extensions.

Explanation

Correct Answer

C:

Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure. This pairing is justified because a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

Incorrect Answers

A:

This action and check address the distinct objective “Explain desired state versus observed status in Kubernetes objects” instead of the stated acceptance requirement. The matching action is to choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Its confirming test is to inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

B:

This action and check address the distinct objective “Identify reconciliation work performed by kube-controller-manager” instead of the stated acceptance requirement. The matching action is to choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Its confirming test is to inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

D:

This action and check address the distinct objective “Understand open standards and vendor-neutral community collaboration” instead of the stated acceptance requirement. The matching action is to choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Its confirming test is to inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

Question 56

A science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. Which supported Kubernetes practice directly addresses the stated requirement?

  1. Use Kubernetes controllers to keep replicas and other managed resources aligned with their declared specifications rather than manually re-creating each missing pod.
  2. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate.
  3. Package workloads in standard images and declarative manifests while documenting external dependencies and provider-specific integrations before claiming portability.
  4. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling.

Explanation

Correct Answer

D:

The situation is that a science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. This resolves the issue because a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface. To verify, inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

Incorrect Answers

A:

This option addresses the distinct objective “Identify reconciliation work performed by kube-controller-manager”, not the immediate requirement. The controller manager runs controllers that observe API resources and make changes so current state moves toward desired state. For the stated case, a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

B:

This option addresses the distinct objective “Distinguish ConfigMaps from Secrets and avoid storing credentials in public configuration”, not the immediate requirement. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy. For the stated case, a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

C:

This option addresses the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”, not the immediate requirement. Containers and Kubernetes APIs reduce some environment differences, but network load balancers, storage drivers and IAM integrations remain provider-specific. For the stated case, a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

Question 57

A science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. Which causal explanation supports the intended design choice?

  1. etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
  2. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.
  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. 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.

Explanation

Correct Answer

B:

The situation is that a science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface. It supports this action: Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. To confirm, inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

Incorrect Answers

A:

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 a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

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 a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

D:

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 a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

Question 58

A science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. Which test provides the strongest evidence of a correct implementation?

  1. Deploy a test sidecar and main container, verify localhost communication and compare their shared Pod IP with a separate Pod.
  2. Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.
  3. Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
  4. Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

Explanation

Correct Answer

D:

The situation is that a science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure. This is the relevant test because a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use Pods as the shared network and storage execution unit”, but not the required result. For this case, inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

B:

This check would help evaluate the distinct objective “Use kubectl get and describe for distinct inspection needs”, but not the required result. For this case, inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

C:

This check would help evaluate the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, but not the required result. For this case, inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

Question 59

A science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. A shortcut is proposed: “Treat Docker's legacy dockershim as a required built-in runtime component on every modern Kubernetes release.” Which technical consequence follows most closely?

  1. Replicas can collide on storage ownership and application state ordering assumptions fail.
  2. An unsupported runtime assumption misdirects troubleshooting and may block node bootstrap.
  3. The edit is invisible to the API and controller reconciliation, so subsequent node restarts or scheduling can discard it.
  4. Independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.

Explanation

Correct Answer

B:

The situation is that a science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. An unsupported runtime assumption misdirects troubleshooting and may block node bootstrap. The shortcut creates this risk because a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unsupported runtime assumption misdirects troubleshooting and may block node bootstrap.

C:

That outcome concerns the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unsupported runtime assumption misdirects troubleshooting and may block node bootstrap.

D:

That outcome concerns the distinct objective “Use Pods as the shared network and storage execution unit”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unsupported runtime assumption misdirects troubleshooting and may block node bootstrap.

Question 60

A science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. Which combined solution and independent check are most directly justified?

  1. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  2. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Acceptance evidence: Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
  3. Request persistent storage with a PVC and examine the bound PersistentVolume capacity, class and access mode before deploying a data-bearing Pod. Acceptance evidence: Create a small claim in a test StorageClass, inspect its Bound status and restart the consuming Pod to check data persistence.
  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

A:

The situation is that a science center asks why its cluster API shows a Pod scheduled while the container sandbox creation fails. Choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Acceptance evidence: Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure. This pairing is justified because a supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface.

Incorrect Answers

B:

This action and check address the distinct objective “Distinguish Deployment desired state from a manually created Pod” instead of the stated acceptance requirement. The matching action is to choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Its confirming test is to inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

C:

This action and check address the distinct objective “Understand PersistentVolumeClaim binding to persistent storage resources” instead of the stated acceptance requirement. The matching action is to choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Its confirming test is to inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

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 choose a CRI-compatible container runtime on worker nodes and investigate image and container creation separately from API scheduling. Its confirming test is to inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests