Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 12
Question 110
An educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that an educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Acceptance evidence: Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries. This pairing is justified because a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
Incorrect Answers
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 assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Its confirming test is to create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
This action and check address the distinct objective “Use rollout status and undo to validate and recover a Deployment release” instead of the stated acceptance requirement. The matching action is to assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Its confirming test is to create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
This action and check address the distinct objective “Understand open standards and vendor-neutral community collaboration” instead of the stated acceptance requirement. The matching action is to assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. Its confirming test is to create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
Question 111
An online newsroom increases desired replica count before a major live event. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. This resolves the issue because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. To verify, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
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, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
This option addresses the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions”, not the immediate requirement. RBAC evaluates API verbs, resources and scope; a Role is namespaced and does not grant cluster-wide access merely because the subject can authenticate. For the stated case, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
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, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
Question 112
An online newsroom increases desired replica count before a major live event. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. It supports this action: Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. To confirm, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
Incorrect Answers
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 the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
That statement explains the distinct objective “Build meaningful alert rules and route notifications through Alertmanager” rather than the cause in this case. The deciding mechanism here is that the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
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 the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
Question 113
An online newsroom increases desired replica count before a major live event. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge. This is the relevant test because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
Incorrect Answers
This check would help evaluate the distinct objective “Separate kube-scheduler decisions from kubelet execution”, but not the required result. For this case, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
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, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
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, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
Question 114
An online newsroom increases desired replica count before a major live event. The change review contains this proposal: “Read an updated spec and immediately assume every requested replica is serving traffic despite pending pulls or readiness failures.” What risk matters most?
Explanation
Correct Answer
A deployment is recorded as changed while the application is still below its service availability requirement. The shortcut creates this risk because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
Incorrect Answers
That outcome concerns the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”; it is not the most direct consequence of this shortcut. The relevant consequence is that a deployment is recorded as changed while the application is still below its service availability requirement.
That outcome concerns the distinct objective “Understand Prometheus pull-based metrics collection and exporters”; it is not the most direct consequence of this shortcut. The relevant consequence is that a deployment is recorded as changed while the application is still below its service availability requirement.
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 a deployment is recorded as changed while the application is still below its service availability requirement.
Question 115
An online newsroom increases desired replica count before a major live event. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge. This pairing is justified because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
Incorrect Answers
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 change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
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 change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
This action and check address the distinct objective “Choose Ingress or Gateway API with an implementing controller for HTTP exposure” instead of the stated acceptance requirement. The matching action is to change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
Question 116
A small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Which engineering approach is the most appropriate for this cloud-native case?
Explanation
Correct Answer
The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. This resolves the issue because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. To verify, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
Incorrect Answers
This option addresses the distinct objective “Recognize the kubelet role in local Pod lifecycle management”, not the immediate requirement. Each kubelet watches assigned Pod specifications and coordinates the container runtime, volumes and health information on its node. For the stated case, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
This option addresses the distinct objective “Understand ports, targetPort and protocol mapping in a Service”, not the immediate requirement. A Service exposes port to clients and forwards to targetPort on selected endpoints; a mismatched targetPort can break delivery even with valid DNS and selectors. For the stated case, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
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, the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
Question 117
A small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence. It supports this action: Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. To confirm, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
Incorrect Answers
That statement explains the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling” rather than the cause in this case. The deciding mechanism here is that the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
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 the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
That statement explains the distinct objective “Implement namespaced RBAC Roles for least-privilege resource permissions” rather than the cause in this case. The deciding mechanism here is that the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
Question 118
A small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge. This is the relevant test because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
Incorrect Answers
This check would help evaluate the distinct objective “Protect API server access using authenticated TLS clients and audited authorization”, but not the required result. For this case, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
This check would help evaluate the distinct objective “Identify reconciliation work performed by kube-controller-manager”, but not the required result. For this case, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. This check would help evaluate the distinct objective “Separate kube-scheduler decisions from kubelet execution”, but not the required result. For this case, set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
Question 119
A small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. The change review contains this proposal: “Read an updated spec and immediately assume every requested replica is serving traffic despite pending pulls or readiness failures.” What risk matters most?
Explanation
Correct Answer
The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. A deployment is recorded as changed while the application is still below its service availability requirement. The shortcut creates this risk because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
Incorrect Answers
That outcome concerns the distinct objective “Externalize application configuration from an image while protecting secrets”; it is not the most direct consequence of this shortcut. The relevant consequence is that a deployment is recorded as changed while the application is still below its service availability requirement.
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 deployment is recorded as changed while the application is still below its service availability requirement.
The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. 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 a deployment is recorded as changed while the application is still below its service availability requirement.
Question 120
A small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Which implementation together with matching acceptance evidence best meets this case?
Explanation
Correct Answer
The situation is that a small retailer scales its Deployment but reports success from spec alone while new Pods are still Pending. Change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Acceptance evidence: Set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge. This pairing is justified because the API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.
Incorrect Answers
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 change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
This action and check address the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance” instead of the stated acceptance requirement. The matching action is to change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
This action and check address the distinct objective “Use image provenance and policy controls without trusting mutable tags” instead of the stated acceptance requirement. The matching action is to change a workload's declared replicas and observe controllers update actual Pod count, understanding that status may lag behind spec during reconciliation. Its confirming test is to set replicas from two to four, inspect generation and observed generation and watch readyReplicas converge.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 10 - 10 Questions (Last Reviewed 11-Nov-2026)
- Linux Foundation KCNA Practice Test 11 - 10 Questions (Last Reviewed 10-Nov-2026)
- 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)