Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 23
Question 220
A training team practices kubectl rollout status and rollout undo with a purposely broken test container. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. 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. This pairing is justified because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
Incorrect Answers
This action and check address the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster” instead of the stated acceptance requirement. The matching action is to observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. 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 observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
This action and check address the distinct objective “Use an immutable image digest for exact deployment provenance” instead of the stated acceptance requirement. The matching action is to observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
Question 221
A university has services named reports in three different namespaces. Which supported Kubernetes practice directly addresses the stated requirement?
Explanation
Correct Answer
Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. This resolves the issue because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. To verify, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
Incorrect Answers
This option addresses the distinct objective “Separate CI build verification from CD environment promotion”, not the immediate requirement. Continuous integration validates and packages changes; continuous delivery or deployment governs how an already-built artifact reaches target environments. For the stated case, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
This option addresses the distinct objective “Use annotations for tool metadata rather than workload selection”, not the immediate requirement. Labels are designed for selectors and filtering, whereas annotations hold descriptive metadata not intended as a resource-matching control. For the stated case, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
This option addresses the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, not the immediate requirement. EmptyDir is initialized for a Pod and its contents can be shared among containers but do not survive the Pod's removal. For the stated case, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
Question 222
A university has services named reports in three different namespaces. Which causal explanation supports the intended design choice?
Explanation
Correct Answer
Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. It supports this action: Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. To confirm, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
Incorrect Answers
That statement explains the distinct objective “Apply GitOps reconciliation with a version-controlled desired state” rather than the cause in this case. The deciding mechanism here is that Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
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 Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
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 Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
Question 223
A university has services named reports in three different namespaces. Which test provides the strongest evidence of a correct implementation?
Explanation
Correct Answer
List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object. This is the relevant test because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
Incorrect Answers
This check would help evaluate the distinct objective “Instrument services with OpenTelemetry context propagation”, but not the required result. For this case, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
This check would help evaluate the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”, but not the required result. For this case, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
This check would help evaluate the distinct objective “Understand emptyDir as Pod-lifetime shared storage, not durable application persistence”, but not the required result. For this case, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
Question 224
A university has services named reports in three different namespaces. A shortcut is proposed: “Issue a generic deletion by name without specifying resource kind or namespace on a shared cluster.” Which technical consequence follows most closely?
Explanation
Correct Answer
An unrelated object may be targeted or the intended workload may remain untouched and unavailable. The shortcut creates this risk because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
Incorrect Answers
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 an unrelated object may be targeted or the intended workload may remain untouched and unavailable.
That outcome concerns the distinct objective “Contrast cloud-native microservices with a monolith without treating either as inherently superior”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unrelated object may be targeted or the intended workload may remain untouched and unavailable.
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 an unrelated object may be targeted or the intended workload may remain untouched and unavailable.
Question 225
A university has services named reports in three different namespaces. Which combined solution and independent check are most directly justified?
Explanation
Correct Answer
Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Acceptance evidence: List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object. This pairing is justified because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
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 resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
This action and check address the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images” instead of the stated acceptance requirement. The matching action is to resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
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 resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
Question 226
A small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. What technical action should the platform team take in this situation?
Explanation
Correct Answer
The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. This resolves the issue because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. To verify, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
Incorrect Answers
This option addresses the distinct objective “Understand readiness, liveness and startup probes as different signals”, not the immediate requirement. Readiness affects endpoint eligibility while liveness can cause restarts; a startup probe defers other probe checks until initialization succeeds. For the stated case, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
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, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
This option addresses the distinct objective “Separate multi-tenant namespace governance from actual isolation guarantees”, not the immediate requirement. Namespaces alone partition naming but do not provide complete security isolation, capacity governance or protection from privileged node-level workloads. For the stated case, Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
Question 227
A small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. It supports this action: Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. To confirm, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
Incorrect Answers
The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. 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 Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
That statement explains the distinct objective “Distinguish a container image from a running container and its writable layer” rather than the cause in this case. The deciding mechanism here is that Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
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 Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
Question 228
A small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object. This is the relevant test because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
Incorrect Answers
This check would help evaluate the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, but not the required result. For this case, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
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, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
This check would help evaluate the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift”, but not the required result. For this case, list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
Question 229
A small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. The team suggests: “Issue a generic deletion by name without specifying resource kind or namespace on a shared cluster.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. An unrelated object may be targeted or the intended workload may remain untouched and unavailable. The shortcut creates this risk because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
Incorrect Answers
That outcome concerns the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unrelated object may be targeted or the intended workload may remain untouched and unavailable.
That outcome concerns the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unrelated object may be targeted or the intended workload may remain untouched and unavailable.
That outcome concerns the distinct objective “Understand taints and tolerations as repulsion controls”; it is not the most direct consequence of this shortcut. The relevant consequence is that an unrelated object may be targeted or the intended workload may remain untouched and unavailable.
Question 230
A small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a small manufacturer copies a manifest but confuses a ClusterRole with a namespaced Role of the same short name. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Acceptance evidence: List Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object. This pairing is justified because Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds.
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 resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
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 resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
This action and check address the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability” instead of the stated acceptance requirement. The matching action is to resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it. Its confirming test is to list Deployments with --all-namespaces and inspect one manifest's apiVersion and kind to target a specific test object.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- Linux Foundation KCNA Practice Test 23 - 10 Questions (Last Reviewed 29-Oct-2026)
- Linux Foundation KCNA Practice Test 24 - 10 Questions (Last Reviewed 28-Oct-2026)
- Linux Foundation KCNA Practice Test 25 - 10 Questions (Last Reviewed 27-Oct-2026)