Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 22
Question 210
A retailer allocates resources to regional teams and wants aggregate limits rather than a naming convention. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
The situation is that a retailer allocates resources to regional teams and wants aggregate limits rather than a naming convention. Apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits. Acceptance evidence: Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected. This pairing is justified because a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.
Incorrect Answers
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 apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits. Its confirming test is to create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.
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 apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits. Its confirming test is to create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.
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 apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits. Its confirming test is to create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.
Question 211
A nonprofit deploys a buggy customer portal image and needs to restore the last validated version. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
Explanation
Correct Answer
Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. This resolves the issue because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. To verify, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
Incorrect Answers
This option addresses the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, not the immediate requirement. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. For the stated case, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
This option addresses the distinct objective “Use kubectl get and describe for distinct inspection needs”, not the immediate requirement. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. For the stated case, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
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, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
Question 212
A nonprofit deploys a buggy customer portal image and needs to restore the last validated version. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. It supports this action: Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. To confirm, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
Incorrect Answers
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 deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
That statement explains the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” rather than the cause in this case. The deciding mechanism here is that deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
That statement explains the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” rather than the cause in this case. The deciding mechanism here is that deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
Question 213
A nonprofit deploys a buggy customer portal image and needs to restore the last validated version. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests. This is the relevant test because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
Incorrect Answers
This check would help evaluate the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
This check would help evaluate the distinct objective “Use kubectl get and describe for distinct inspection needs”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
This check would help evaluate the distinct objective “Correlate application rollout revisions with error spikes”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
Question 214
A nonprofit deploys a buggy customer portal image and needs to restore the last validated version. An engineer proposes: “Delete every healthy prior ReplicaSet immediately after starting a risky release so no rollback remains available.” What adverse outcome would be most direct?
Explanation
Correct Answer
A failed release can leave the service unavailable with no retained tested deployment revision. The shortcut creates this risk because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
Incorrect Answers
That outcome concerns the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”; it is not the most direct consequence of this shortcut. The relevant consequence is that a failed release can leave the service unavailable with no retained tested deployment revision.
That outcome concerns the distinct objective “Use annotations for tool metadata rather than workload selection”; it is not the most direct consequence of this shortcut. The relevant consequence is that a failed release can leave the service unavailable with no retained tested deployment revision.
That outcome concerns the distinct objective “Distinguish service mesh traffic management from external ingress routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that a failed release can leave the service unavailable with no retained tested deployment revision.
Question 215
A nonprofit deploys a buggy customer portal image and needs to restore the last validated version. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
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 “Understand resource quotas and LimitRanges for namespace capacity governance” 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 “Apply resource manifests declaratively instead of depending on imperative drift” 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 “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.
Question 216
A training team practices kubectl rollout status and rollout undo with a purposely broken test container. Which Kubernetes or cloud-native implementation decision best solves the stated problem?
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. This resolves the issue because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. To verify, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
Incorrect Answers
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, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
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, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
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, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
Question 217
A training team practices kubectl rollout status and rollout undo with a purposely broken test container. Which platform mechanism explains why the suitable approach works?
Explanation
Correct Answer
The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. It supports this action: Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. To confirm, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
Incorrect Answers
The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. That statement explains the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” rather than the cause in this case. The deciding mechanism here is that deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
That statement explains the distinct objective “Diagnose cluster DNS separately from Pod network reachability” rather than the cause in this case. The deciding mechanism here is that deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
That statement explains the distinct objective “Use namespaces as organizational scopes without treating them as firewalls” rather than the cause in this case. The deciding mechanism here is that deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
Question 218
A training team practices kubectl rollout status and rollout undo with a purposely broken test container. Which controlled observation would best validate the intended improvement?
Explanation
Correct Answer
The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests. This is the relevant test because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
Incorrect Answers
This check would help evaluate the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
This check would help evaluate the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
This check would help evaluate the distinct objective “Use annotations for tool metadata rather than workload selection”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
Question 219
A training team practices kubectl rollout status and rollout undo with a purposely broken test container. An engineer proposes: “Delete every healthy prior ReplicaSet immediately after starting a risky release so no rollback remains available.” What adverse outcome would be most direct?
Explanation
Correct Answer
The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. A failed release can leave the service unavailable with no retained tested deployment revision. The shortcut creates this risk because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
Incorrect Answers
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 a failed release can leave the service unavailable with no retained tested deployment revision.
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 a failed release can leave the service unavailable with no retained tested deployment revision.
That outcome concerns the distinct objective “Understand CNCF project maturity stages without equating them to security approval”; it is not the most direct consequence of this shortcut. The relevant consequence is that a failed release can leave the service unavailable with no retained tested deployment revision.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- 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)
- 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)