Practice Exams:

Linux Foundation KCNA Dumps

EXAM: Kubernetes and Cloud Native Associate
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

KCNA Premium Bundle


  • Premium File 333 Questions & Answers
  • Training Course 54 Lectures
  • Study Guide 410 Pages

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?

  1. Run automated source tests, dependency checks and artifact signing during CI, then promote the vetted immutable artifact through a controlled delivery stage. Acceptance evidence: Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.
  2. 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.
  3. Identify whether the cluster uses kube-proxy or an alternative Service dataplane before diagnosing virtual Service IP forwarding behavior. Acceptance evidence: Read the cluster networking configuration, find a test Service and verify backend connectivity using the installed dataplane.
  4. Send cluster changes through the authenticated Kubernetes API and inspect the object returned by the API server rather than changing node processes directly. Acceptance evidence: Create a namespaced ConfigMap with kubectl, read it back through the API, and confirm no manual edit of a worker-node process was required.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Give clients a Service DNS name rather than hardcoding Pod IP addresses that can change when replicas are replaced.
  2. Give each workload an appropriate Kubernetes ServiceAccount and narrow RBAC permissions rather than embedding an administrator kubeconfig in its image.
  3. Define meaningful topology keys, matching label selectors and skew limits when balancing eligible replicas across nodes or zones.
  4. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. GitOps connects a versioned desired-state source with automated drift detection and reconciliation; direct manual changes may be reverted by the controller.
  2. kube-proxy can maintain node networking rules for Services, but supported network implementations may replace this function.
  3. A namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.
  4. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.
  2. Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
  3. Trace a test commit through build-test-image-digest and compare that digest between staging and production promotion records.
  4. In a training namespace inspect PID views and a controlled memory limit, noting which mechanism changes identity or resource behavior.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Sensitive workloads may remain reachable until actual identity and traffic controls are installed.
  2. The service can remain under capacity because a standalone Pod has no ReplicaSet controller to recreate it.
  3. Users may encounter failed requests because readiness and application-level health remain unverified.
  4. The operator can interrupt healthy networking while the original admission or image problem persists.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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?

  1. Label eligible nodes for a test hardware property and use nodeSelector when a Pod must run only on matching nodes. Acceptance evidence: Label one worker disk=ssd, apply a Pod requiring disk=ssd and confirm it binds only to the matching eligible worker.
  2. Use the scheduler's node-binding decision to explain initial Pod placement, then inspect the chosen node's kubelet for local container lifecycle status. Acceptance evidence: Inspect a new Pod's nodeName and Events, then compare scheduling events with kubelet-reported container status.
  3. Select a StatefulSet with volumeClaimTemplates for a stateful clustered application requiring stable Pod names and individual durable volumes. Acceptance evidence: Scale a test StatefulSet and inspect web-0, web-1 and each distinct PVC before deleting and recreating one Pod.
  4. 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.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching.
  2. Apply PriorityClasses sparingly for essential workloads and plan capacity so preemption does not unnecessarily evict useful lower-priority Pods.
  3. Assign related namespaced resources to a project namespace and enforce authorization and network isolation with separate policies.
  4. Keep a common base and targeted Kustomize overlays for namespace, image or replica differences across environments.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships.
  2. A rollout can be API-valid yet degrade business behavior; measured acceptance signals and a preserved prior revision make controlled rollback possible.
  3. Under pressure, a higher-priority pending Pod may preempt eligible lower-priority Pods, but constraints and eviction rules still apply.
  4. A namespace scopes many API object names and administrative boundaries, but merely creating it does not deny network communication across namespaces.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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?

  1. Inspect node runtime information and compare a Pod's scheduling success with a runtime-reported image or sandbox failure.
  2. Create matching Service names in two namespaces and test separately configured RBAC and NetworkPolicy access boundaries.
  3. Trigger a controlled process crash and confirm previous logs contain the error even after kubelet restarts the container.
  4. Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Healthy desired-state definitions are lost while the node connectivity or capacity cause remains unresolved.
  2. Operators can see the metadata but the Service cannot select the desired Pods using that annotation.
  3. Sensitive workloads may remain reachable until actual identity and traffic controls are installed.
  4. Independent rollout, scaling and failure isolation become difficult because the services are coupled to one scheduling unit.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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?

  1. 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.
  2. Use a Deployment for a replicated stateless application requiring rolling updates and replacement of failed Pods. Acceptance evidence: Scale a test Deployment and inspect its ReplicaSet and owned Pods, then compare deleting a standalone Pod.
  3. 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.
  4. Prefer documented Kubernetes APIs and interoperable telemetry formats when possible while identifying any platform-specific extensions needed for the real deployment. Acceptance evidence: Test a synthetic standard API manifest and OpenTelemetry trace export across two platforms, documenting any unsupported extensions.

Explanation

Correct Answer

A:

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

B:

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.

C:

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.

D:

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