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 21

Question 200

A cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. What pair of supported action and practical verification should be approved?

  1. 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.
  2. Read a workload's spec and status separately and inspect conditions when determining whether an API change became healthy. Acceptance evidence: Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  3. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Acceptance evidence: Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.
  4. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy. Acceptance evidence: Check CNI capabilities, establish a default-deny test policy and verify one allowed and one denied connection.

Explanation

Correct Answer

C:

The situation is that a cooperative's workload uses API tokens and administrators propose putting them into a shared configuration map. Put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Acceptance evidence: Inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret. This pairing is justified because configMaps are ordinary configuration data; Secret objects have a separate API but base64 encoding alone is not encryption and access requires policy.

Incorrect Answers

A:

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 put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

B:

This action and check address the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” instead of the stated acceptance requirement. The matching action is to put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

D:

This action and check address the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” instead of the stated acceptance requirement. The matching action is to put non-sensitive application settings in ConfigMaps and put credentials in Secret objects with RBAC, encryption and external secret-management safeguards where appropriate. Its confirming test is to inspect synthetic ConfigMap and Secret manifests, then test that an unprivileged ServiceAccount cannot read the private Secret.

Question 201

A research institute gives student projects separate quotas on a shared teaching cluster. What technical action should the platform team take in this situation?

  1. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload.
  2. Apply ingress and egress NetworkPolicy to selected Pods and verify both permitted and denied synthetic flows under a network plugin that implements policy.
  3. Separate compile and runtime stages to retain only required binary and runtime dependencies in the deployed container image.
  4. Apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits.

Explanation

Correct Answer

D:

Apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits. This resolves the issue because a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings. To verify, create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

Incorrect Answers

A:

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, a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

B:

This option addresses the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it”, not the immediate requirement. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support. For the stated case, a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

C:

This option addresses the distinct objective “Build smaller images with multistage builds and remove unnecessary tooling”, not the immediate requirement. Multistage builds reduce image contents and potential attack surface by keeping build toolchains and source artifacts out of the final runtime layer. For the stated case, a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

Question 202

A research institute gives student projects separate quotas on a shared teaching cluster. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
  2. A quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.
  3. SecurityContext configures process identity and privilege boundaries, and unnecessary root privileges increase impact if an application is compromised.
  4. Healthy direct IP connectivity with failed name resolution suggests a DNS path issue; failed Pod-to-Pod IP traffic suggests a lower-level network problem.

Explanation

Correct Answer

B:

A quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings. It supports this action: Apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits. To confirm, create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

Incorrect Answers

A:

That statement explains the distinct objective “Use rollout status and undo to validate and recover a Deployment release” rather than the cause in this case. The deciding mechanism here is that a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

C:

That statement explains the distinct objective “Run images with least-privilege runtime security contexts” rather than the cause in this case. The deciding mechanism here is that a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

D:

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 a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

Question 203

A research institute gives student projects separate quotas on a shared teaching cluster. What acceptance check most directly confirms this requirement is met?

  1. Observe a controlled drain with replica owners and a PDB, then verify workloads move and uncordon restores eligibility.
  2. Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.
  3. Trigger a controlled error-rate alert, verify its pending/firing transition and confirm the correct team receives a grouped notification.
  4. Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.

Explanation

Correct Answer

B:

Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected. This is the relevant test because a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Use cordon and drain with disruption considerations for planned node maintenance”, but not the required result. For this case, create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

C:

This check would help evaluate the distinct objective “Build meaningful alert rules and route notifications through Alertmanager”, but not the required result. For this case, create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

D:

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, create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

Question 204

A research institute gives student projects separate quotas on a shared teaching cluster. The team suggests: “Assume a label called budget=small automatically prevents unlimited Pods and CPU consumption.” Which failure should the reviewer anticipate?

  1. A workload continues crashing because the root cause is memory exhaustion, not name resolution.
  2. A project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy.
  3. An unrelated object may be targeted or the intended workload may remain untouched and unavailable.
  4. The change unnecessarily exposes a data service externally while the original DNS problem remains unresolved.

Explanation

Correct Answer

B:

A project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy. The shortcut creates this risk because a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

Incorrect Answers

A:

That outcome concerns the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”; it is not the most direct consequence of this shortcut. The relevant consequence is that a project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy.

C:

That outcome concerns the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”; it is not the most direct consequence of this shortcut. The relevant consequence is that a project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy.

D:

That outcome concerns the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”; it is not the most direct consequence of this shortcut. The relevant consequence is that a project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy.

Question 205

A research institute gives student projects separate quotas on a shared teaching cluster. Which engineering change and test jointly addresses the scenario?

  1. 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.
  2. Give each Pod an appropriate ServiceAccount, disable automountServiceAccountToken where API access is unnecessary and test token audience and role scope. Acceptance evidence: Run a test web Pod without a token mount and verify service operation succeeds while in-cluster API calls are unavailable.
  3. Keep desired workload YAML in version control and use kubectl apply to reconcile supported object fields through the API. Acceptance evidence: Edit the test Deployment manifest image tag, apply it, and confirm the API spec and rollout reflect the reviewed change.
  4. 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.

Explanation

Correct Answer

D:

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

A:

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 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.

B:

This action and check address the distinct objective “Enforce workload service account token boundaries and avoid needless mounts” 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.

C:

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 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 206

A retailer allocates resources to regional teams and wants aggregate limits rather than a naming convention. What technical action should the platform team take in this situation?

  1. Apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits.
  2. Inspect the active kubeconfig context and namespace before applying manifests to staging or production.
  3. Set realistic CPU and memory requests for Pods and investigate FailedScheduling when no node has sufficient allocatable resources.
  4. Use ClusterIP for internal backends and a properly controlled NodePort or supported LoadBalancer integration for justified external access.

Explanation

Correct Answer

A:

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. This resolves the issue because a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings. To verify, create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

Incorrect Answers

B:

This option addresses the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster”, not the immediate requirement. A kubeconfig context binds cluster, identity and default namespace, so command syntax can be valid yet target the wrong environment. For the stated case, a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

C:

This option addresses the distinct objective “Use container resource requests to help the scheduler fit Pods on nodes”, not the immediate requirement. The scheduler evaluates requests against node allocatable capacity; limits govern runtime ceilings and do not substitute for scheduling requests. For the stated case, a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

D:

This option addresses the distinct objective “Choose ClusterIP, NodePort and LoadBalancer Service types for appropriate reachability”, not the immediate requirement. Service type determines how clients can reach a stable Service: ClusterIP is internal, NodePort exposes a port on nodes, and LoadBalancer integrates external infrastructure. For the stated case, a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

Question 207

A retailer allocates resources to regional teams and wants aggregate limits rather than a naming convention. What underlying Kubernetes behavior is most relevant to this technical decision?

  1. A quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.
  2. The spec describes requested behavior, while status is produced by controllers and node agents to report observed results and errors.
  3. NetworkPolicy declares traffic restrictions, but Kubernetes itself does not provide enforcement when the installed CNI lacks NetworkPolicy support.
  4. The API stores a desired spec while controllers asynchronously react to observations; status describes progress, not a guarantee of immediate convergence.

Explanation

Correct Answer

A:

The situation is that a retailer allocates resources to regional teams and wants aggregate limits rather than a naming convention. A quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings. It supports this action: Apply appropriate ResourceQuota and LimitRange policy to bound namespace consumption and guide default container resource requests or limits. To confirm, create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

Incorrect Answers

B:

That statement explains the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition” rather than the cause in this case. The deciding mechanism here is that a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

C:

That statement explains the distinct objective “Recognize NetworkPolicy isolation only when the CNI enforces it” rather than the cause in this case. The deciding mechanism here is that a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

D:

That statement explains the distinct objective “Explain desired state versus observed status in Kubernetes objects” rather than the cause in this case. The deciding mechanism here is that a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

Question 208

A retailer allocates resources to regional teams and wants aggregate limits rather than a naming convention. What acceptance check most directly confirms this requirement is met?

  1. Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.
  2. Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
  3. Apply a test manifest with impossible node constraints, then inspect the accepted spec and Pending status/Events.
  4. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.

Explanation

Correct Answer

A:

The situation is that a retailer allocates resources to regional teams and wants aggregate limits rather than a naming convention. Create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected. This is the relevant test because a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Use rollout status and undo to validate and recover a Deployment release”, but not the required result. For this case, create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

C:

This check would help evaluate the distinct objective “Interpret Kubernetes spec and status fields without confusing intent with condition”, but not the required result. For this case, create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

D:

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, create a controlled test namespace with a tiny quota and verify a request exceeding aggregate limits is rejected.

Question 209

A retailer allocates resources to regional teams and wants aggregate limits rather than a naming convention. The team suggests: “Assume a label called budget=small automatically prevents unlimited Pods and CPU consumption.” Which failure should the reviewer anticipate?

  1. A project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy.
  2. An unrelated object may be targeted or the intended workload may remain untouched and unavailable.
  3. A scheduled workload may violate performance expectations because the declared label was not backed by infrastructure inventory.
  4. The change is repeatedly reverted, making incident response and audit history inconsistent.

Explanation

Correct Answer

A:

The situation is that a retailer allocates resources to regional teams and wants aggregate limits rather than a naming convention. A project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy. The shortcut creates this risk because a quota constrains aggregate namespace resource usage, while a LimitRange validates or defaults eligible individual resource settings.

Incorrect Answers

B:

The situation is that a retailer allocates resources to regional teams and wants aggregate limits rather than a naming convention. That outcome concerns the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”; it is not the most direct consequence of this shortcut. The relevant consequence is that a project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy.

C:

That outcome concerns the distinct objective “Use nodeSelector to place a workload on nodes with required labels”; it is not the most direct consequence of this shortcut. The relevant consequence is that a project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy.

D:

That outcome concerns the distinct objective “Apply GitOps reconciliation with a version-controlled desired state”; it is not the most direct consequence of this shortcut. The relevant consequence is that a project can exhaust shared cluster capacity when declarative metadata is mistaken for enforced admission policy.

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?

  1. Select an access mode supported by the actual storage driver and workload placement requirements rather than assuming every volume supports concurrent writes from every node. Acceptance evidence: Use a synthetic two-node workload and compare expected attach behavior for an RWO volume with a documented RWX shared filesystem.
  2. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload. Acceptance evidence: Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.
  3. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure. Acceptance evidence: Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  4. 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.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

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.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests