Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 20
Question 190
A university dashboard wants to find all application Pods by team while retaining long-form audit notes. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a university dashboard wants to find all application Pods by team while retaining long-form audit notes. Record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Acceptance evidence: Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels. This pairing is justified because labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control.
Incorrect Answers
This action and check address the distinct objective “Use kubectl get and describe for distinct inspection needs” instead of the stated acceptance requirement. The matching action is to record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.
This action and check address the distinct objective “Design a release rollback trigger from measurable service signals” instead of the stated acceptance requirement. The matching action is to record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.
This action and check address the distinct objective “Use Pod anti-affinity to reduce correlated replica failure” instead of the stated acceptance requirement. The matching action is to record non-identifying build or audit metadata as annotations and use labels for indexing, grouping and selector-based routing. Its confirming test is to annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.
Question 191
A school analytics app needs a harmless report interval and a private database credential. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. This resolves the issue because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy. To verify, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
Incorrect Answers
This option addresses the distinct objective “Distinguish a container image from a running container and its writable layer”, not the immediate requirement. An image contains layers and configuration; each container adds runtime state that can vanish on replacement unless data uses explicit persistent storage. For the stated case, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
This option addresses the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, not the immediate requirement. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. For the stated case, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
This option addresses the distinct objective “Use Pod Security Standards to deny overly privileged Pod configurations”, not the immediate requirement. Pod Security Standards establish common workload hardening profiles, and admission checks can enforce restricted capabilities and privilege use at API creation. For the stated case, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
Question 192
A school analytics app needs a harmless report interval and a private database credential. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy. It supports this action: Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. To confirm, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
Incorrect Answers
That statement explains the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” rather than the cause in this case. The deciding mechanism here is that configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
That statement explains the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” rather than the cause in this case. The deciding mechanism here is that configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
That statement explains the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors” rather than the cause in this case. The deciding mechanism here is that configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
Question 193
A school analytics app needs a harmless report interval and a private database credential. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret. This is the relevant test because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
Incorrect Answers
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, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
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, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
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, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
Question 194
A school analytics app needs a harmless report interval and a private database credential. An engineer proposes: “Embed production passwords in a ConfigMap because its YAML is easier to inspect and store in a public repository.” What adverse outcome would be most direct?
Explanation
Correct Answer
Secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments. The shortcut creates this risk because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
Incorrect Answers
That outcome concerns the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion”; it is not the most direct consequence of this shortcut. The relevant consequence is that secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.
That outcome concerns the distinct objective “Understand ENTRYPOINT and command overrides when a container exits immediately”; it is not the most direct consequence of this shortcut. The relevant consequence is that secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.
That outcome concerns the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift”; it is not the most direct consequence of this shortcut. The relevant consequence is that secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.
Question 195
A school analytics app needs a harmless report interval and a private database credential. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Acceptance evidence: Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret. This pairing is justified because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
Incorrect Answers
This action and check address the distinct objective “Distinguish a container image from a running container and its writable layer” instead of the stated acceptance requirement. The matching action is to put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
This action and check address the distinct objective “Use annotations for tool metadata rather than workload selection” instead of the stated acceptance requirement. The matching action is to put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
This action and check address the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments” instead of the stated acceptance requirement. The matching action is to put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
Question 196
A cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. This resolves the issue because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy. To verify, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
Incorrect Answers
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, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
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, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
This option addresses the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”, not the immediate requirement. Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. For the stated case, configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
Question 197
A cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. ConfigMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy. It supports this action: Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. To confirm, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
Incorrect Answers
The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. That statement explains the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” rather than the cause in this case. The deciding mechanism here is that configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
That statement explains the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” rather than the cause in this case. The deciding mechanism here is that configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
That statement explains the distinct objective “Use kubectl get and describe for distinct inspection needs” rather than the cause in this case. The deciding mechanism here is that configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
Question 198
A cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret. This is the relevant test because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
Incorrect Answers
This check would help evaluate the distinct objective “Correlate application rollout revisions with error spikes”, but not the required result. For this case, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. 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, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
This check would help evaluate the distinct objective “Use namespaces as organizational scopes without treating them as firewalls”, but not the required result. For this case, inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
Question 199
A cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. An engineer proposes: “Embed production passwords in a ConfigMap because its YAML is easier to inspect and store in a public repository.” What adverse outcome would be most direct?
Explanation
Correct Answer
The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments. The shortcut creates this risk because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
Incorrect Answers
That outcome concerns the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”; it is not the most direct consequence of this shortcut. The relevant consequence is that secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.
That outcome concerns the distinct objective “Recognize the kubelet role in local Pod lifecycle management”; it is not the most direct consequence of this shortcut. The relevant consequence is that secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.
That outcome concerns the distinct objective “Understand CSI drivers and volume attachment responsibilities”; it is not the most direct consequence of this shortcut. The relevant consequence is that secrets can be exposed to broadly authorized readers and source-control users despite apparently valid deployments.
Question 200
A cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Acceptance evidence: Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret. This pairing is justified because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.
Incorrect Answers
This action and check address the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance” instead of the stated acceptance requirement. The matching action is to put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
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 put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
This action and check address the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” instead of the stated acceptance requirement. The matching action is to put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 18 - 10 Questions (Last Reviewed 03-Nov-2026)
- Linux Foundation KCNA Practice Test 19 - 10 Questions (Last Reviewed 02-Nov-2026)
- Linux Foundation KCNA Practice Test 20 - 10 Questions (Last Reviewed 01-Nov-2026)
- Linux Foundation KCNA Practice Test 21 - 10 Questions (Last Reviewed 31-Oct-2026)
- Linux Foundation KCNA Practice Test 22 - 10 Questions (Last Reviewed 30-Oct-2026)