Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 14
Question 130
A campus project renames Pods but does not update labels referenced by its existing Service. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a campus project renames Pods but does not update labels referenced by its existing Service. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Acceptance evidence: Compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload. This pairing is justified because Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
Incorrect Answers
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 apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
This action and check address the distinct objective “Distinguish Pod IPs from stable Services during rescheduling” instead of the stated acceptance requirement. The matching action is to apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
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 apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching. Its confirming test is to compare kubectl get pods -l app=inventory with Service selectors and EndpointSlices for a test workload.
Question 131
A compliance collector needs read-only access to its own namespace metadata. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. This resolves the issue because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. To verify, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
Incorrect Answers
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, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
This option addresses the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”, not the immediate requirement. Canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update. For the stated case, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
This option addresses the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, not the immediate requirement. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. For the stated case, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
Question 132
A compliance collector needs read-only access to its own namespace metadata. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. It supports this action: Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. To confirm, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
Incorrect Answers
That statement explains the distinct objective “Separate kube-scheduler decisions from kubelet execution” rather than the cause in this case. The deciding mechanism here is that serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
That statement explains the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms” rather than the cause in this case. The deciding mechanism here is that serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
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 serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
Question 133
A compliance collector needs read-only access to its own namespace metadata. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list. This is the relevant test because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
Incorrect Answers
This check would help evaluate the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, but not the required result. For this case, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
This check would help evaluate the distinct objective “Use ephemeral debugging containers only with appropriate permission and safeguards”, but not the required result. For this case, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
This check would help evaluate the distinct objective “Explain desired state versus observed status in Kubernetes objects”, but not the required result. For this case, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
Question 134
A compliance collector needs read-only access to its own namespace metadata. A shortcut is proposed: “Bake a cluster-admin kubeconfig into a reusable public container image so workloads can discover any object.” Which technical consequence follows most closely?
Explanation
Correct Answer
Credential reuse could expose all namespaces and persist after the original developer loses access. The shortcut creates this risk because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
Incorrect Answers
That outcome concerns the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”; it is not the most direct consequence of this shortcut. The relevant consequence is that credential reuse could expose all namespaces and persist after the original developer loses access.
That outcome concerns the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”; it is not the most direct consequence of this shortcut. The relevant consequence is that credential reuse could expose all namespaces and persist after the original developer loses access.
That outcome concerns the distinct objective “Distinguish etcd persistence from running workload data”; it is not the most direct consequence of this shortcut. The relevant consequence is that credential reuse could expose all namespaces and persist after the original developer loses access.
Question 135
A compliance collector needs read-only access to its own namespace metadata. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Acceptance evidence: Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list. This pairing is justified because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
Incorrect Answers
This action and check address the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
This action and check address the distinct objective “Define secure release governance with staged approvals and policy verification” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
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 give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
Question 136
A student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. This resolves the issue because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. To verify, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
Incorrect Answers
This option addresses the distinct objective “Use labels and selectors to connect resources predictably”, not the immediate requirement. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships. For the stated case, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
This option addresses the distinct objective “Explain metrics, logs and traces as complementary observability signals”, not the immediate requirement. Each telemetry type represents a different view of runtime state and links through context can connect a symptom to a specific service hop. For the stated case, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
This option addresses the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”, not the immediate requirement. Image-pull credentials are consumed before the application starts and should not be hardcoded into container layers or app logs. For the stated case, serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
Question 137
A student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. It supports this action: Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. To confirm, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
Incorrect Answers
That statement explains the distinct objective “Limit workload-to-workload access with explicit NetworkPolicy allow rules” rather than the cause in this case. The deciding mechanism here is that serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
That statement explains the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership” rather than the cause in this case. The deciding mechanism here is that serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
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 serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
Question 138
A student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list. This is the relevant test because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
Incorrect Answers
This check would help evaluate the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”, but not the required result. For this case, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
This check would help evaluate the distinct objective “Distinguish etcd persistence from running workload data”, but not the required result. For this case, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
This check would help evaluate the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, but not the required result. For this case, run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
Question 139
A student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. The team suggests: “Bake a cluster-admin kubeconfig into a reusable public container image so workloads can discover any object.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. Credential reuse could expose all namespaces and persist after the original developer loses access. The shortcut creates this risk because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
Incorrect Answers
That outcome concerns the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory”; it is not the most direct consequence of this shortcut. The relevant consequence is that credential reuse could expose all namespaces and persist after the original developer loses access.
That outcome concerns the distinct objective “Apply cloud-native portability and immutable infrastructure principles pragmatically”; it is not the most direct consequence of this shortcut. The relevant consequence is that credential reuse could expose all namespaces and persist after the original developer loses access.
That outcome concerns the distinct objective “Interpret ReplicaSet ownership and selectors in a Deployment”; it is not the most direct consequence of this shortcut. The relevant consequence is that credential reuse could expose all namespaces and persist after the original developer loses access.
Question 140
A student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a student wants to understand why kubectl credentials on a laptop differ from a Pod's in-cluster identity. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Acceptance evidence: Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list. This pairing is justified because serviceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets.
Incorrect Answers
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 give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
This action and check address the distinct objective “Use labels and selectors to connect resources predictably” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image. Its confirming test is to run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 12 - 10 Questions (Last Reviewed 09-Nov-2026)
- Linux Foundation KCNA Practice Test 13 - 10 Questions (Last Reviewed 08-Nov-2026)
- Linux Foundation KCNA Practice Test 14 - 10 Questions (Last Reviewed 07-Nov-2026)
- Linux Foundation KCNA Practice Test 15 - 10 Questions (Last Reviewed 06-Nov-2026)
- Linux Foundation KCNA Practice Test 16 - 10 Questions (Last Reviewed 05-Nov-2026)