Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 2
Question 10
A logistics company has two worker machines but wants one authenticated entry point for declaring cluster objects. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a logistics company has two worker machines but wants one authenticated entry point for declaring cluster objects. 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. This pairing is justified because the kube-apiserver validates authorized API requests and exposes the declarative resource interface; kubelets and controllers subsequently reconcile the saved desired state.
Incorrect Answers
This action and check address the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” instead of the stated acceptance requirement. The matching action is to send cluster changes through the authenticated Kubernetes API and inspect the object returned by the API server rather than changing node processes directly. Its confirming test is to create a namespaced ConfigMap with kubectl, read it back through the API, and confirm no manual edit of a worker-node process was required.
This action and check address the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior” instead of the stated acceptance requirement. The matching action is to send cluster changes through the authenticated Kubernetes API and inspect the object returned by the API server rather than changing node processes directly. Its confirming test is to create a namespaced ConfigMap with kubectl, read it back through the API, and confirm no manual edit of a worker-node process was required.
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 send cluster changes through the authenticated Kubernetes API and inspect the object returned by the API server rather than changing node processes directly. Its confirming test is to create a namespaced ConfigMap with kubectl, read it back through the API, and confirm no manual edit of a worker-node process was required.
Question 11
A city library designs a cluster recovery plan that must restore deployments as well as its catalog database. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. This resolves the issue because etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd. To verify, inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
Incorrect Answers
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, etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
This option addresses the distinct objective “Distinguish ClusterRoles from Roles and binding scope”, not the immediate requirement. ClusterRole defines permissions while ClusterRoleBinding makes them cluster-wide; RoleBinding limits effective namespaced scope even when referencing a ClusterRole. For the stated case, etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
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, etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
Question 12
A city library designs a cluster recovery plan that must restore deployments as well as its catalog database. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
Etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd. It supports this action: Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. To confirm, inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
Incorrect Answers
That statement explains the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically” rather than the cause in this case. The deciding mechanism here is that etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
That statement explains the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” rather than the cause in this case. The deciding mechanism here is that etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
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 etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
Question 13
A city library designs a cluster recovery plan that must restore deployments as well as its catalog database. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup. This is the relevant test because etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
Incorrect Answers
This check would help evaluate the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions”, but not the required result. For this case, inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
This check would help evaluate the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”, but not the required result. For this case, inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
This check would help evaluate the distinct objective “Identify reconciliation work performed by kube-controller-manager”, but not the required result. For this case, inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
Question 14
A city library designs a cluster recovery plan that must restore deployments as well as its catalog database. The change review contains this proposal: “Assume a control-plane etcd snapshot contains all customer files written to an application's mounted data volume.” What risk matters most?
Explanation
Correct Answer
A control-plane restore might recover resource metadata while losing application records that were never backed up. The shortcut creates this risk because etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
Incorrect Answers
That outcome concerns the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”; it is not the most direct consequence of this shortcut. The relevant consequence is that a control-plane restore might recover resource metadata while losing application records that were never backed up.
That outcome concerns the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules”; it is not the most direct consequence of this shortcut. The relevant consequence is that a control-plane restore might recover resource metadata while losing application records that were never backed up.
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 a control-plane restore might recover resource metadata while losing application records that were never backed up.
Question 15
A city library designs a cluster recovery plan that must restore deployments as well as its catalog database. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
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. This pairing is justified because etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
Incorrect Answers
This action and check address the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards” instead of the stated acceptance requirement. The matching action is to treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Its confirming test is to inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
This action and check address the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities” instead of the stated acceptance requirement. The matching action is to treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Its confirming test is to inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
This action and check address the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms” instead of the stated acceptance requirement. The matching action is to treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Its confirming test is to inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
Question 16
A regional hospital confuses control-plane state snapshots with backups of its medical application files. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
The situation is that a regional hospital confuses control-plane state snapshots with backups of its medical application files. Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. This resolves the issue because etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd. To verify, inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
Incorrect Answers
The situation is that a regional hospital confuses control-plane state snapshots with backups of its medical application files. 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, etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
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, etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
This option addresses the distinct objective “Explain the container runtime interface without conflating it with the control plane”, not the immediate requirement. A supported runtime such as containerd executes container operations requested through kubelet using the Container Runtime Interface. For the stated case, etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
Question 17
A regional hospital confuses control-plane state snapshots with backups of its medical application files. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
The situation is that a regional hospital confuses control-plane state snapshots with backups of its medical application files. Etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd. It supports this action: Treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. To confirm, inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
Incorrect Answers
That statement explains the distinct objective “Use image provenance and policy controls without trusting mutable tags” rather than the cause in this case. The deciding mechanism here is that etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
That statement explains the distinct objective “Recognize the kubelet role in local Pod lifecycle management” rather than the cause in this case. The deciding mechanism here is that etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
That statement explains the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” rather than the cause in this case. The deciding mechanism here is that etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
Question 18
A regional hospital confuses control-plane state snapshots with backups of its medical application files. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
The situation is that a regional hospital confuses control-plane state snapshots with backups of its medical application files. Inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup. This is the relevant test because etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
Incorrect Answers
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 the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
This check would help evaluate the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”, but not the required result. For this case, inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
This check would help evaluate the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, but not the required result. For this case, inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
Question 19
A regional hospital confuses control-plane state snapshots with backups of its medical application files. An engineer proposes: “Assume a control-plane etcd snapshot contains all customer files written to an application's mounted data volume.” What adverse outcome would be most direct?
Explanation
Correct Answer
The situation is that a regional hospital confuses control-plane state snapshots with backups of its medical application files. A control-plane restore might recover resource metadata while losing application records that were never backed up. The shortcut creates this risk because etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
Incorrect Answers
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 a control-plane restore might recover resource metadata while losing application records that were never backed up.
That outcome concerns the distinct objective “Identify reconciliation work performed by kube-controller-manager”; it is not the most direct consequence of this shortcut. The relevant consequence is that a control-plane restore might recover resource metadata while losing application records that were never backed up.
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 control-plane restore might recover resource metadata while losing application records that were never backed up.
Question 20
A regional hospital confuses control-plane state snapshots with backups of its medical application files. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a regional hospital confuses control-plane state snapshots with backups of its medical application files. 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. This pairing is justified because etcd persists Kubernetes API objects and cluster configuration, while application records ordinarily live in workload-specific storage outside etcd.
Incorrect Answers
This action and check address the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment” instead of the stated acceptance requirement. The matching action is to treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Its confirming test is to inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
This action and check address the distinct objective “Choose ReadWriteOnce and ReadWriteMany access modes by backend capability” instead of the stated acceptance requirement. The matching action is to treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Its confirming test is to inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
This action and check address the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” instead of the stated acceptance requirement. The matching action is to treat etcd as Kubernetes control-plane state storage and protect its snapshots, keys, and access separately from an application's database or PVC. Its confirming test is to inspect the cluster backup policy for etcd snapshots and separately restore synthetic application data from its own backup.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 1 - 10 Questions (Last Reviewed 20-Nov-2026)
- Linux Foundation KCNA Practice Test 2 - 10 Questions (Last Reviewed 19-Nov-2026)
- Linux Foundation KCNA Practice Test 3 - 10 Questions (Last Reviewed 18-Nov-2026)
- Linux Foundation KCNA Practice Test 4 - 10 Questions (Last Reviewed 17-Nov-2026)