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 22

Question 210

A retailer allocates resources to regional teams and wants aggregate limits rather than a naming convention. Which engineering change and test jointly addresses the scenario?

  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.

Question 211

A nonprofit deploys a buggy customer portal image and needs to restore the last validated version. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Review requests, limits, QoS class and termination reasons rather than interpreting every restart as a scheduler failure.
  2. Use kubectl get for concise resource lists and kubectl describe for detailed status, conditions and Events when triaging a workload.
  3. Route a measured fraction of traffic to a canary or switch between separately verified blue and green environments using an appropriate routing controller.
  4. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks.

Explanation

Correct Answer

D:

Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. This resolves the issue because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. To verify, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

Incorrect Answers

A:

This option addresses the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, not the immediate requirement. CPU limits may throttle running processes, whereas exceeding memory constraints can cause OOM termination; Pod scheduling itself depends on requests. For the stated case, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

B:

This option addresses the distinct objective “Use kubectl get and describe for distinct inspection needs”, not the immediate requirement. Get returns selected object information, while describe adds human-readable state and related Events helpful for initial diagnosis. For the stated case, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

C:

This option addresses the distinct objective “Distinguish canary and blue-green delivery strategies from Kubernetes Deployment defaults”, not the immediate requirement. Canary release needs traffic steering and metrics for a subset; blue-green shifts a complete traffic target after validation, and neither is automatically provided by a plain Deployment update. For the stated case, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Question 212

A nonprofit deploys a buggy customer portal image and needs to restore the last validated version. Which platform mechanism explains why the suitable approach works?

  1. Pod affinity affects scheduler placement relative to labeled Pods in selected topology domains, not application authentication or firewall rules.
  2. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
  3. A PV reclaim policy controls how underlying storage is treated after claim release; deleting the Pod and deleting the PVC are distinct events with different effects.
  4. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Explanation

Correct Answer

D:

Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. It supports this action: Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. To confirm, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

Incorrect Answers

A:

That statement explains the distinct objective “Use Pod affinity for co-location without assuming it creates networking permissions” rather than the cause in this case. The deciding mechanism here is that deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

B:

That statement explains the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” rather than the cause in this case. The deciding mechanism here is that deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

C:

That statement explains the distinct objective “Compare PV reclaim policies and explain data retention on PVC deletion” rather than the cause in this case. The deciding mechanism here is that deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Question 213

A nonprofit deploys a buggy customer portal image and needs to restore the last validated version. Which controlled observation would best validate the intended improvement?

  1. Create a synthetic CPU-intensive workload with tight CPU limits and compare throttling metrics with an OOMKilled test Pod.
  2. Compare kubectl get pods -o wide with kubectl describe pod for a test image-pull failure and note which output shows recent Events.
  3. Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
  4. Deploy a controlled defective revision, record error rate before and after rollout and verify rollback restores the prior behavior.

Explanation

Correct Answer

C:

Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests. This is the relevant test because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Incorrect Answers

A:

This check would help evaluate the distinct objective “Distinguish memory limits from CPU throttling for scheduling and runtime symptoms”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

B:

This check would help evaluate the distinct objective “Use kubectl get and describe for distinct inspection needs”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

D:

This check would help evaluate the distinct objective “Correlate application rollout revisions with error spikes”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

Question 214

A nonprofit deploys a buggy customer portal image and needs to restore the last validated version. An engineer proposes: “Delete every healthy prior ReplicaSet immediately after starting a risky release so no rollback remains available.” What adverse outcome would be most direct?

  1. The edit is invisible to the API and controller reconciliation, so subsequent node restarts or scheduling can discard it.
  2. A failed release can leave the service unavailable with no retained tested deployment revision.
  3. Operators can see the metadata but the Service cannot select the desired Pods using that annotation.
  4. External routing remains absent or policy is misunderstood, and internal identity controls may be incomplete.

Explanation

Correct Answer

B:

A failed release can leave the service unavailable with no retained tested deployment revision. The shortcut creates this risk because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Incorrect Answers

A:

That outcome concerns the distinct objective “Trace Kubernetes API requests through the kube-apiserver entry point”; it is not the most direct consequence of this shortcut. The relevant consequence is that a failed release can leave the service unavailable with no retained tested deployment revision.

C:

That outcome concerns the distinct objective “Use annotations for tool metadata rather than workload selection”; it is not the most direct consequence of this shortcut. The relevant consequence is that a failed release can leave the service unavailable with no retained tested deployment revision.

D:

That outcome concerns the distinct objective “Distinguish service mesh traffic management from external ingress routing”; it is not the most direct consequence of this shortcut. The relevant consequence is that a failed release can leave the service unavailable with no retained tested deployment revision.

Question 215

A nonprofit deploys a buggy customer portal image and needs to restore the last validated version. What pair of supported action and practical verification should be approved?

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

Explanation

Correct Answer

C:

Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Acceptance evidence: Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests. This pairing is justified because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Incorrect Answers

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 observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

B:

This action and check address the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” instead of the stated acceptance requirement. The matching action is to observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

D:

This action and check address the distinct objective “Separate CI build verification from CD environment promotion” instead of the stated acceptance requirement. The matching action is to observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

Question 216

A training team practices kubectl rollout status and rollout undo with a purposely broken test container. Which Kubernetes or cloud-native implementation decision best solves the stated problem?

  1. Resolve an object's apiVersion, kind, metadata namespace and name before applying or deleting it.
  2. Apply stable application labels and ensure Services and controllers select the intended Pods by equality or set-based matching.
  3. Read Pod Events and node assignment to distinguish a Pod that cannot be scheduled from a scheduled Pod whose image cannot be pulled.
  4. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks.

Explanation

Correct Answer

D:

The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. This resolves the issue because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. To verify, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

Incorrect Answers

A:

This option addresses the distinct objective “Read the API resource model using namespaces and names rather than guessing ownership”, not the immediate requirement. Kubernetes API identity combines resource type, scope and object name; identical names can exist in distinct namespaces for namespaced kinds. For the stated case, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

B:

This option addresses the distinct objective “Use labels and selectors to connect resources predictably”, not the immediate requirement. Kubernetes labels are queryable object metadata, while selectors connect controllers and Services to matching endpoints; names alone do not create these relationships. For the stated case, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

C:

This option addresses the distinct objective “Separate Pending scheduling failures from ImagePullBackOff errors”, not the immediate requirement. FailedScheduling occurs before node binding; ImagePullBackOff occurs when a node's kubelet cannot obtain the container image. For the stated case, deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Question 217

A training team practices kubectl rollout status and rollout undo with a purposely broken test container. Which platform mechanism explains why the suitable approach works?

  1. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.
  2. Declarative apply records desired configuration and supports repeatable reviewed changes; ad hoc editing of running containers is not persistent configuration management.
  3. 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.
  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

A:

The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. Deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings. It supports this action: Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. To confirm, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

Incorrect Answers

B:

The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. That statement explains the distinct objective “Apply resource manifests declaratively instead of depending on imperative drift” rather than the cause in this case. The deciding mechanism here is that deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

C:

That statement explains the distinct objective “Diagnose cluster DNS separately from Pod network reachability” rather than the cause in this case. The deciding mechanism here is that deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

D:

That statement explains the distinct objective “Use namespaces as organizational scopes without treating them as firewalls” rather than the cause in this case. The deciding mechanism here is that deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Question 218

A training team practices kubectl rollout status and rollout undo with a purposely broken test container. Which controlled observation would best validate the intended improvement?

  1. Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.
  2. Test a staged Service with a mismatched selector and separately a healthy endpoint with the wrong targetPort to compare symptoms.
  3. Run a synthetic read-only Pod with a restricted ServiceAccount and verify one permitted API read and one forbidden Secret list.
  4. Annotate a Deployment with release notes and verify its Service still selects Pods using explicit app labels.

Explanation

Correct Answer

A:

The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests. This is the relevant test because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Incorrect Answers

B:

This check would help evaluate the distinct objective “Distinguish a failed Service selector from broken DNS or a failing backend”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

C:

This check would help evaluate the distinct objective “Differentiate ServiceAccounts from human kubeconfig identities”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

D:

This check would help evaluate the distinct objective “Use annotations for tool metadata rather than workload selection”, but not the required result. For this case, change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

Question 219

A training team practices kubectl rollout status and rollout undo with a purposely broken test container. An engineer proposes: “Delete every healthy prior ReplicaSet immediately after starting a risky release so no rollback remains available.” What adverse outcome would be most direct?

  1. Compromised credentials can perform widespread cluster changes without attribution or least privilege.
  2. A leaked image layer or build log can disclose credentials and grant unwanted registry access.
  3. A failed release can leave the service unavailable with no retained tested deployment revision.
  4. A trusted community label is misused as a substitute for secure configuration and maintenance.

Explanation

Correct Answer

C:

The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. A failed release can leave the service unavailable with no retained tested deployment revision. The shortcut creates this risk because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Incorrect Answers

A:

That outcome concerns the distinct objective “Use least-privilege kubectl authentication and authorization during routine administration”; it is not the most direct consequence of this shortcut. The relevant consequence is that a failed release can leave the service unavailable with no retained tested deployment revision.

B:

That outcome concerns the distinct objective “Handle private registry pulls with dedicated credentials instead of embedding secrets in images”; it is not the most direct consequence of this shortcut. The relevant consequence is that a failed release can leave the service unavailable with no retained tested deployment revision.

D:

That outcome concerns the distinct objective “Understand CNCF project maturity stages without equating them to security approval”; it is not the most direct consequence of this shortcut. The relevant consequence is that a failed release can leave the service unavailable with no retained tested deployment revision.

Question 220

A training team practices kubectl rollout status and rollout undo with a purposely broken test container. What pair of supported action and practical verification should be approved?

  1. Inspect the active kubeconfig context and namespace before applying manifests to staging or production. Acceptance evidence: Run kubectl config current-context and kubectl config view --minify, then perform a read-only lookup in the expected namespace.
  2. 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.
  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. Pin validated production images by registry digest and promote the same signed artifact across environments. Acceptance evidence: Resolve an approved image digest, deploy that reference in staging and verify the same digest exists in the production Pod spec.

Explanation

Correct Answer

C:

The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. Observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Acceptance evidence: Change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests. This pairing is justified because deployment rollout strategy gradually replaces Pods and preserves revision history, but success depends on availability and revision retention settings.

Incorrect Answers

A:

This action and check address the distinct objective “Manage kubectl contexts to avoid changes in the wrong cluster” instead of the stated acceptance requirement. The matching action is to observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

B:

The situation is that a training team practices kubectl rollout status and rollout undo with a purposely broken test container. This action and check address the distinct objective “Separate CI build verification from CD environment promotion” instead of the stated acceptance requirement. The matching action is to observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

D:

This action and check address the distinct objective “Use an immutable image digest for exact deployment provenance” instead of the stated acceptance requirement. The matching action is to observe rollout progression and use a reviewed rollback to a previous ReplicaSet revision when a new application build fails health checks. Its confirming test is to change a test image to a known failing build, inspect rollout status and rollback history, then verify the earlier healthy version serves requests.

Kubernetes and Cloud Native Associate (KCNA) Practice Tests