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 10

Question 90

A university deploys several bare Pods and wonders why no replacement is created after one is deleted. Which implementation together with matching acceptance evidence best meets this case?

  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. Define a user-centered service level indicator and objective, such as percentage of successful requests within a latency threshold over a stated window. Acceptance evidence: Calculate a synthetic seven-day success ratio from request metrics and compare it to the agreed target before a risky rollout.
  3. 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.
  4. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Acceptance evidence: Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.

Explanation

Correct Answer

C:

The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. 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. This pairing is justified because a Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.

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 use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

B:

This action and check address the distinct objective “Use SLI and SLO measures to focus reliability objectives” instead of the stated acceptance requirement. The matching action is to use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

D:

The situation is that a university deploys several bare Pods and wonders why no replacement is created after one is deleted. This action and check address the distinct objective “Distinguish etcd persistence from running workload data” instead of the stated acceptance requirement. The matching action is to use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Its confirming test is to scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.

Question 91

A city ticketing app shows two ReplicaSets during a staged rollout. What technical action should the platform team take in this situation?

  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. Inspect kubelet-reported Pod and container conditions when a scheduled workload fails to start, while keeping cluster resources managed through the API.
  3. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count.
  4. Review Sandbox, Incubating and Graduated CNCF stages as community maturity signals while independently assessing a project's fitness, lifecycle and security.

Explanation

Correct Answer

C:

Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. This resolves the issue because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. To verify, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

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 Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

B:

This option addresses the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, not the immediate requirement. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node. For the stated case, a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

D:

This option addresses the distinct objective “Understand CNCF project maturity stages without equating them to security approval”, not the immediate requirement. CNCF maturity describes aspects of adoption and governance, not a blanket guarantee that every deployment or version is free of defects. For the stated case, a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

Question 92

A city ticketing app shows two ReplicaSets during a staged rollout. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
  2. A Deployment owns ReplicaSets that manage matching Pods and supports declarative rollout history, unlike an independent Pod object.
  3. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
  4. A NoSchedule taint repels Pods without a matching toleration; tolerance permits consideration but does not force placement on that node.

Explanation

Correct Answer

C:

A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. It supports this action: Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. To confirm, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Incorrect Answers

A:

That statement explains the distinct objective “Design a release rollback trigger from measurable service signals” rather than the cause in this case. The deciding mechanism here is that a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

B:

That statement explains the distinct objective “Distinguish Deployment desired state from a manually created Pod” rather than the cause in this case. The deciding mechanism here is that a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

D:

That statement explains the distinct objective “Understand taints and tolerations as repulsion controls” rather than the cause in this case. The deciding mechanism here is that a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

Question 93

A city ticketing app shows two ReplicaSets during a staged rollout. What acceptance check most directly confirms this requirement is met?

  1. Reproduce a missing PVC in a test namespace and confirm the Pod Events directly indicate the unavailable claim.
  2. Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.
  3. Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  4. Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Explanation

Correct Answer

D:

Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain. This is the relevant test because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use Events and pod describe for failed volume mounting”, but not the required result. For this case, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

B:

This check would help evaluate the distinct objective “Separate kube-scheduler decisions from kubelet execution”, but not the required result. For this case, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

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, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Question 94

A city ticketing app shows two ReplicaSets during a staged rollout. The team suggests: “Change labels on an unrelated Pod to manipulate replica counts without reviewing immutable selector expectations.” Which failure should the reviewer anticipate?

  1. Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.
  2. Name lookup may succeed but no usable endpoint exists to receive traffic.
  3. Incident diagnosis confuses placement failures with container startup errors and targets the wrong component.
  4. A leaked image layer or build log can disclose credentials and grant unwanted registry access.

Explanation

Correct Answer

A:

Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior. The shortcut creates this risk because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

Incorrect Answers

B:

That outcome concerns the distinct objective “Use EndpointSlices to connect Service selectors with actual backend Pods”; it is not the most direct consequence of this shortcut. The relevant consequence is that controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.

C:

That outcome concerns the distinct objective “Separate kube-scheduler decisions from kubelet execution”; it is not the most direct consequence of this shortcut. The relevant consequence is that controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.

D:

That outcome concerns the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”; it is not the most direct consequence of this shortcut. The relevant consequence is that controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.

Question 95

A city ticketing app shows two ReplicaSets during a staged rollout. Which engineering change and test jointly addresses the scenario?

  1. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
  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. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Acceptance evidence: Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
  4. Store approved declarative cluster manifests in Git and let a GitOps controller reconcile differences while keeping sensitive access appropriately scoped. Acceptance evidence: Change a test Deployment field outside Git, observe drift and confirm reconciliation restores the reviewed Git value.

Explanation

Correct Answer

A:

Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain. This pairing is justified because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

Incorrect Answers

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 inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

C:

This action and check address the distinct objective “Use rollout status and undo to validate and recover a Deployment release” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

D:

This action and check address the distinct objective “Apply GitOps reconciliation with a version-controlled desired state” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Question 96

A medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled.
  2. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count.
  3. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies.
  4. Cordon a worker to prevent new scheduling and drain safely under PodDisruptionBudgets and DaemonSet rules before maintenance.

Explanation

Correct Answer

B:

The situation is that a medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. This resolves the issue because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. To verify, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Incorrect Answers

A:

This option addresses the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, not the immediate requirement. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image. For the stated case, a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

C:

This option addresses the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”, not the immediate requirement. A namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces. For the stated case, a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

D:

This option addresses the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”, not the immediate requirement. Cordon marks a node unschedulable for new ordinary Pods; drain evicts managed workloads when policies and availability permit. For the stated case, a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

Question 97

A medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Which platform mechanism explains why the suitable approach works?

  1. StatefulSet manages stable ordinal identities and preserves PVC-associated storage per replica across routine Pod replacement, subject to retention policy.
  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 Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
  4. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment.

Explanation

Correct Answer

C:

The situation is that a medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. A Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts. It supports this action: Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. To confirm, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Incorrect Answers

A:

That statement explains the distinct objective “Use StatefulSet for stable ordinal identity and persistent per-replica claims” rather than the cause in this case. The deciding mechanism here is that a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

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 Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

D:

That statement explains the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster” rather than the cause in this case. The deciding mechanism here is that a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

Question 98

A medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Which controlled observation would best validate the intended improvement?

  1. Delete one test Deployment-owned Pod and observe a replacement appear without a new Deployment definition.
  2. Deploy a matching replica set across two labeled zones and inspect skew after adding a new Pod.
  3. Insert a deliberately unsigned test image into staging and confirm the release gate blocks production promotion while logging a reason.
  4. Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Explanation

Correct Answer

D:

The situation is that a medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain. This is the relevant test because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Identify reconciliation work performed by kube-controller-manager”, but not the required result. For this case, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

B:

This check would help evaluate the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, but not the required result. For this case, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

C:

This check would help evaluate the distinct objective “Define secure release governance with staged approvals and policy verification”, but not the required result. For this case, run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Question 99

A medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. An engineer proposes: “Change labels on an unrelated Pod to manipulate replica counts without reviewing immutable selector expectations.” What adverse outcome would be most direct?

  1. One application vulnerability can expose a credential allowing changes unrelated to its actual business function.
  2. Availability and rollout behavior diverge because no workload controller owns the independent Pods.
  3. The scheduler could place multiple replicas together, leaving a node without the intended local collector.
  4. Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.

Explanation

Correct Answer

D:

The situation is that a medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior. The shortcut creates this risk because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

Incorrect Answers

A:

That outcome concerns the distinct objective “Enforce workload service account token boundaries and avoid needless mounts”; it is not the most direct consequence of this shortcut. The relevant consequence is that controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.

B:

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 controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.

C:

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 controllers may fail to recognize intended Pods or adopt unwanted matches, producing confusing replacement behavior.

Question 100

A medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. What pair of supported action and practical verification should be approved?

  1. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Acceptance evidence: Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.
  2. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
  3. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Acceptance evidence: Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.
  4. Send cluster changes through the authenticated Kubernetes API and inspect the object returned by the API server rather than changing node processes directly. Acceptance evidence: Create a namespaced ConfigMap with kubectl, read it back through the API, and confirm no manual edit of a worker-node process was required.

Explanation

Correct Answer

B:

The situation is that a medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain. This pairing is justified because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.

Incorrect Answers

A:

This action and check address the distinct objective “Separate CI build verification from CD environment promotion” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

C:

This action and check address the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

D:

This action and check address the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests