Linux Foundation KCNA Dumps
Linux Foundation KCNA Practice Test 11
Question 100
A medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. What pair of supported action and practical verification should be approved?
Explanation
Correct Answer
The situation is that a medical startup sees too many Pods and must identify whether they belong to the active or older ReplicaSet. Inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Acceptance evidence: Run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain. This pairing is justified because a Deployment creates or manages ReplicaSets, each ReplicaSet owns matching Pods, and selector consistency determines which Pods it counts.
Incorrect Answers
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 inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
This action and check address the distinct objective “Understand service proxy implementations without assuming kube-proxy is mandatory” instead of the stated acceptance requirement. The matching action is to inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
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 inspect Deployment, ReplicaSet and Pod owner references when verifying which controller maintains replica count. Its confirming test is to run kubectl get rs and kubectl describe deployment for a test rollout and verify the expected owner chain.
Question 101
A regional insurer separates testing and production resource names into different namespaces. What technical action should the platform team take in this situation?
Explanation
Correct Answer
Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. This resolves the issue because a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces. To verify, create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
Incorrect Answers
This option addresses the distinct objective “Distinguish Pod IPs from stable Services during rescheduling”, not the immediate requirement. Pods receive network identities that can be ephemeral, while a Service maintains a stable discovery and traffic abstraction over selected endpoints. For the stated case, a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
This option addresses the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, not the immediate requirement. ServiceAccounts provide workload identities for Kubernetes API access; human authentication and authorization are separately configured and should not be shared as static image secrets. For the stated case, a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
This option addresses the distinct objective “Spread replicas across failure domains with topologySpreadConstraints”, not the immediate requirement. Topology spread constraints compare Pod distribution in topology domains and can restrict or prefer placement depending on whenUnsatisfiable. For the stated case, a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
Question 102
A regional insurer separates testing and production resource names into different namespaces. What underlying Kubernetes behavior is most relevant to this technical decision?
Explanation
Correct Answer
A namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces. It supports this action: Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. To confirm, create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
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 a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
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 a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
That statement explains the distinct objective “Use labels and selectors to connect resources predictably” rather than the cause in this case. The deciding mechanism here is that a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
Question 103
A regional insurer separates testing and production resource names into different namespaces. What acceptance check most directly confirms this requirement is met?
Explanation
Correct Answer
Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries. This is the relevant test 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 check would help evaluate the distinct objective “Separate kube-scheduler decisions from kubelet execution”, but not the required result. For this case, create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
This check would help evaluate the distinct objective “Separate CI build verification from CD environment promotion”, but not the required result. For this case, create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
This check would help evaluate the distinct objective “Explain Linux namespaces and cgroups as distinct container isolation mechanisms”, but not the required result. For this case, create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
Question 104
A regional insurer separates testing and production resource names into different namespaces. The team suggests: “Assume creating a namespace named confidential automatically blocks every Pod in other namespaces from connecting to it.” Which failure should the reviewer anticipate?
Explanation
Correct Answer
Sensitive workloads may remain reachable until actual identity and traffic controls are installed. The shortcut creates this risk because a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
Incorrect Answers
That outcome concerns the distinct objective “Identify reconciliation work performed by kube-controller-manager”; it is not the most direct consequence of this shortcut. The relevant consequence is that sensitive workloads may remain reachable until actual identity and traffic controls are installed.
That outcome concerns the distinct objective “Use kubectl get and describe for distinct inspection needs”; it is not the most direct consequence of this shortcut. The relevant consequence is that sensitive workloads may remain reachable until actual identity and traffic controls are installed.
That outcome concerns the distinct objective “Use describe and Events to distinguish admission, scheduling and execution errors”; it is not the most direct consequence of this shortcut. The relevant consequence is that sensitive workloads may remain reachable until actual identity and traffic controls are installed.
Question 105
A regional insurer separates testing and production resource names into different namespaces. Which engineering change and test jointly addresses the scenario?
Explanation
Correct Answer
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 “Use nodeSelector to place a workload on nodes with required labels” 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 “Separate kube-scheduler decisions from kubelet execution” 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 StatefulSet for stable ordinal identity and persistent per-replica claims” 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 106
An educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. Which engineering approach is the most appropriate for this cloud-native 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. This resolves the issue because a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces. To verify, create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
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, a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
This option addresses the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability”, not the immediate requirement. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply. For the stated case, a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
This option addresses the distinct objective “Use Kustomize overlays to adapt manifests without copying whole deployments”, not the immediate requirement. Kustomize transforms declarative resource definitions, allowing reviewed variations while preserving a shared base instead of manually editing duplicate files. For the stated case, a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
Question 107
An educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. What infrastructure principle makes the correct treatment effective?
Explanation
Correct Answer
The situation is that an educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. A namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces. It supports this action: Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies. To confirm, create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
Incorrect Answers
The situation is that an educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. That statement explains the distinct objective “Use labels and selectors to connect resources predictably” rather than the cause in this case. The deciding mechanism here is that a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
That statement explains the distinct objective “Design a release rollback trigger from measurable service signals” rather than the cause in this case. The deciding mechanism here is that a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
That statement explains the distinct objective “Use PriorityClasses and understand preemption without assuming they guarantee availability” rather than the cause in this case. The deciding mechanism here is that a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
Question 108
An educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. What verification result would most convincingly distinguish a working solution from a claim?
Explanation
Correct Answer
The situation is that an educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries. This is the relevant test 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 check would help evaluate the distinct objective “Explain the container runtime interface without conflating it with the control plane”, but not the required result. For this case, create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
This check would help evaluate the distinct objective “Use kubectl logs and previous container logs to isolate application crashes”, but not the required result. For this case, create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
This check would help evaluate the distinct objective “Understand resource quotas and LimitRanges for namespace capacity governance”, but not the required result. For this case, create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
Question 109
An educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. The change review contains this proposal: “Assume creating a namespace named confidential automatically blocks every Pod in other namespaces from connecting to it.” What risk matters most?
Explanation
Correct Answer
The situation is that an educational platform wants department-specific resource organization and mistakenly expects namespace labels alone to stop traffic. Sensitive workloads may remain reachable until actual identity and traffic controls are installed. The shortcut creates this risk because a namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
Incorrect Answers
That outcome concerns the distinct objective “Use node conditions and allocatable capacity to diagnose NotReady workloads”; it is not the most direct consequence of this shortcut. The relevant consequence is that sensitive workloads may remain reachable until actual identity and traffic controls are installed.
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 sensitive workloads may remain reachable until actual identity and traffic controls are installed.
That outcome concerns the distinct objective “Use Pods as the shared network and storage execution unit”; it is not the most direct consequence of this shortcut. The relevant consequence is that sensitive workloads may remain reachable until actual identity and traffic controls are installed.
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.
Kubernetes and Cloud Native Associate (KCNA) Practice Tests
- Linux Foundation KCNA Practice Test 9 - 10 Questions (Last Reviewed 12-Nov-2026)
- 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)