McAfee Secure

CNCF CKA Bundle

Exam Code: CKA

Exam Name Certified Kubernetes Administrator

Certification Provider: CNCF

Corresponding Certification: CKA

CNCF CKA Bundle $44.99
CKA Sample 1 CKA Sample 2 CKA Sample 3 CKA Sample 4 CKA Sample 5 CKA Sample 6 CKA Sample 7 CKA Sample 8 CKA Sample 9 CKA Sample 10

100% CNCF CKA Guaranteed Success With Testking Training Materials

Get Real CKA Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    CKA Questions & Answers

    58 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual CKA exam while allowing you to hone and measure every aspect of your test-taking ability.

  • CKA Video Course

    CKA Training Course

    138 Video Lectures

    CKA Video Course is developed by CNCF Professionals to help you pass the CKA exam.

    Description

    This course will improve your knowledge and skills required to pass Certified Kubernetes Administrator exam.
  • Study Guide

    CKA Study Guide

    268 PDF Pages

    Developed by industry experts, this 268-page guide spells out in painstaking detail all of the information you need to ace CKA exam.

Certified Kubernetes Administrator (CKA) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    58 Questions

    $124.99
  • CKA Video Course

    Training Course

    138 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    268 PDF Pages

    $29.99

CNCF CKA Practice Test 34

Question 330

At Horizon observability, in a disposable simulated environment during a monitored release window: An operator needs to confirm rollout completion for Deployment metrics-api in namespace observability, not just see that its spec changed. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. HPA evaluates metrics relative to Pod resource requests; missing metrics or requests can leave desired replicas unknown.
  2. Rollout restart annotates the Pod template so the Deployment controller replaces Pods according to its rollout strategy.
  3. A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template.
  4. A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress.

Explanation

Correct Answer

D:

A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. This explains the stated condition. The corresponding action is: Run kubectl -n observability rollout status deployment/metrics-api --timeout=120s. The direct acceptance evidence is: Run kubectl -n observability get deployment metrics-api and confirm updated and available replicas match the desired count.

Incorrect Answers

A:

HPA evaluates metrics relative to Pod resource requests; missing metrics or requests can leave desired replicas unknown. That explanation applies to a different technical failure. Here the controlling principle is: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress.

B:

The offered statement is true for this other mechanism: Rollout restart annotates the Pod template so the Deployment controller replaces Pods according to its rollout strategy. It does not explain the facts described here, which follow from: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress.

C:

This principle describes a separate cause: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The reported condition is governed by: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The two mechanisms should not be conflated.

Question 331

At Horizon observability, in a disposable simulated environment during a monitored release window: An operator needs to confirm rollout completion for Deployment metrics-api in namespace observability, not just see that its spec changed. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n observability get deployment metrics-api and confirm updated and available replicas match the desired count.
  2. Run kubectl -n observability get deployment metrics-api -o yaml and inspect resource requests and limits for each container.
  3. Run kubectl -n ledger rollout status deployment/invoice-api and inspect the restored image and configuration.
  4. Run kubectl -n fulfillment rollout status deployment/dispatch-api and inspect new Pod creation timestamps.

Explanation

Correct Answer

A:

Run kubectl -n observability get deployment metrics-api and confirm updated and available replicas match the desired count. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The intended action is: Run kubectl -n observability rollout status deployment/metrics-api --timeout=120s.

Incorrect Answers

B:

This observation would test a different technical dependency: Requests inform scheduling and limits cap runtime consumption; the settings play different roles. The current issue is governed by: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Its decisive check is “Run kubectl -n observability get deployment metrics-api and confirm updated and available replicas match the desired count”.

C:

The alternative verifies a different condition: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The current case instead depends on: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Confirm that “Run kubectl -n observability get deployment metrics-api and confirm updated and available replicas match the desired count”.

D:

That test belongs to another control with this basis: Rollout restart annotates the Pod template so the Deployment controller replaces Pods according to its rollout strategy. In the current case, the governing reason is: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The direct verification is “Run kubectl -n observability get deployment metrics-api and confirm updated and available replicas match the desired count”.

Question 332

At Horizon observability, in a disposable simulated environment during a monitored release window: An operator needs to confirm rollout completion for Deployment metrics-api in namespace observability, not just see that its spec changed. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Pin reviewed image tags or digests and retain rollout history for recovery.
  2. Gate deployment promotion on observed rollout and readiness rather than API command exit alone.
  3. Retain meaningful revisions and perform health checks after every rollback.
  4. Check disruption budgets and readiness behavior before application restarts.

Explanation

Correct Answer

B:

Gate deployment promotion on observed rollout and readiness rather than API command exit alone. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n observability rollout status deployment/metrics-api --timeout=120s. The relevant mechanism is: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress.

Incorrect Answers

A:

This routine guards against another mechanism: Updating a Deployment Pod template triggers a controlled rollout; restarting Pods alone will not change the image reference. The recurring exposure in the current case is: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The matching preventive check is “Gate deployment promotion on observed rollout and readiness rather than API command exit alone”.

C:

That safeguard is relevant to: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The current failure instead follows from: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Its prevention measure is “Gate deployment promotion on observed rollout and readiness rather than API command exit alone”.

D:

This routine guards against another mechanism: Rollout restart annotates the Pod template so the Deployment controller replaces Pods according to its rollout strategy. The recurring exposure in the current case is: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The matching preventive check is “Gate deployment promotion on observed rollout and readiness rather than API command exit alone”.

Question 333

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An operator needs to confirm rollout completion for Deployment dispatch-api in namespace fulfillment, not just see that its spec changed. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl -n fulfillment create configmap dispatch-config --from-literal=MODE=uat after checking whether it already exists.
  2. Run kubectl -n fulfillment set image deployment/dispatch-api app=registry.example.test/dispatch-api:v4.
  3. Run kubectl -n fulfillment rollout undo deployment/dispatch-api after checking rollout history.
  4. Run kubectl -n fulfillment rollout status deployment/dispatch-api --timeout=120s.

Explanation

Correct Answer

D:

Run kubectl -n fulfillment rollout status deployment/dispatch-api --timeout=120s. This is the appropriate command-line action or first safe diagnostic. The technical reason is: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Validate the result with: Run kubectl -n fulfillment get deployment dispatch-api and confirm updated and available replicas match the desired count. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

The proposed action belongs to the mechanism: ConfigMaps hold ordinary configuration data; their existence does not automatically inject values into running Pods. Here the stated fault follows a different mechanism: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The corrective choice is “Run kubectl -n fulfillment rollout status deployment/dispatch-api --timeout=120s”.

B:

The offered action targets: Updating a Deployment Pod template triggers a controlled rollout; restarting Pods alone will not change the image reference. The case facts point instead to: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Implement “Run kubectl -n fulfillment rollout status deployment/dispatch-api --timeout=120s” to address that specific condition.

C:

This alternative is a response to another technical cause: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The reported case instead depends on: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The action that directly addresses it is “Run kubectl -n fulfillment rollout status deployment/dispatch-api --timeout=120s”.

Question 334

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An operator needs to confirm rollout completion for Deployment dispatch-api in namespace fulfillment, not just see that its spec changed. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress.
  2. Pod templates can reference Secret keys without copying literal secret values into the Deployment spec.
  3. Requests inform scheduling and limits cap runtime consumption; the settings play different roles.
  4. Node selectors constrain scheduling to nodes whose labels match all specified key/value pairs; patching the Pod template triggers a rollout.

Explanation

Correct Answer

A:

A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. This explains the stated condition. The corresponding action is: Run kubectl -n fulfillment rollout status deployment/dispatch-api --timeout=120s. The direct acceptance evidence is: Run kubectl -n fulfillment get deployment dispatch-api and confirm updated and available replicas match the desired count.

Incorrect Answers

B:

This principle describes a separate cause: Pod templates can reference Secret keys without copying literal secret values into the Deployment spec. The reported condition is governed by: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The two mechanisms should not be conflated.

C:

Requests inform scheduling and limits cap runtime consumption; the settings play different roles. That explanation applies to a different technical failure. Here the controlling principle is: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress.

D:

The offered statement is true for this other mechanism: Node selectors constrain scheduling to nodes whose labels match all specified key/value pairs; patching the Pod template triggers a rollout. It does not explain the facts described here, which follow from: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress.

Question 335

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An operator needs to confirm rollout completion for Deployment dispatch-api in namespace fulfillment, not just see that its spec changed. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n ledger rollout status deployment/invoice-api and inspect the restored image and configuration.
  2. Run kubectl -n fulfillment get deployment dispatch-api and confirm updated and available replicas match the desired count.
  3. Run kubectl -n fulfillment get deployment dispatch-api -o yaml and inspect resource requests and limits for each container.
  4. Run kubectl -n fulfillment get hpa dispatch-api and inspect observed utilization and replica bounds.

Explanation

Correct Answer

B:

Run kubectl -n fulfillment get deployment dispatch-api and confirm updated and available replicas match the desired count. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The intended action is: Run kubectl -n fulfillment rollout status deployment/dispatch-api --timeout=120s.

Incorrect Answers

A:

This observation would test a different technical dependency: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The current issue is governed by: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Its decisive check is “Run kubectl -n fulfillment get deployment dispatch-api and confirm updated and available replicas match the desired count”.

C:

That test belongs to another control with this basis: Requests inform scheduling and limits cap runtime consumption; the settings play different roles. In the current case, the governing reason is: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The direct verification is “Run kubectl -n fulfillment get deployment dispatch-api and confirm updated and available replicas match the desired count”.

D:

This observation would test a different technical dependency: HPA evaluates metrics relative to Pod resource requests; missing metrics or requests can leave desired replicas unknown. The current issue is governed by: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Its decisive check is “Run kubectl -n fulfillment get deployment dispatch-api and confirm updated and available replicas match the desired count”.

Question 336

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An operator needs to confirm rollout completion for Deployment dispatch-api in namespace fulfillment, not just see that its spec changed. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes.
  2. Record resume ownership and inspect currently active Jobs during planned suspensions.
  3. Gate deployment promotion on observed rollout and readiness rather than API command exit alone.
  4. Assess capacity for surge Pods and measure availability during upgrades.

Explanation

Correct Answer

C:

Gate deployment promotion on observed rollout and readiness rather than API command exit alone. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n fulfillment rollout status deployment/dispatch-api --timeout=120s. The relevant mechanism is: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress.

Incorrect Answers

A:

The suggested review tracks a different technical risk: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Here the sustained control must address: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Choose “Gate deployment promotion on observed rollout and readiness rather than API command exit alone”.

B:

That safeguard is relevant to: CronJob suspension prevents new scheduled Jobs but does not terminate existing Jobs already running. The current failure instead follows from: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Its prevention measure is “Gate deployment promotion on observed rollout and readiness rather than API command exit alone”.

D:

The suggested review tracks a different technical risk: Deployment rolling-update parameters govern how many old Pods may be unavailable and extra Pods may be created during replacement. Here the sustained control must address: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Choose “Gate deployment promotion on observed rollout and readiness rather than API command exit alone”.

Question 337

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: Deployment invoice-api in namespace ledger was just updated with a faulty Pod template and must return to its prior revision. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl -n ledger rollout undo deployment/invoice-api after checking rollout history.
  2. Run kubectl -n ledger rollout status deployment/invoice-api --timeout=120s.
  3. Run kubectl -n ledger patch deployment invoice-api --type=merge -p '{"spec":{"template":{"spec":{"tolerations":[{"key":"special","operator":"Equal","value":"dedicated","effect":"NoSchedule"}]}}}}' after checking existing tolerations.
  4. Run kubectl -n ledger set image deployment/invoice-api app=registry.example.test/invoice-api:v2.

Explanation

Correct Answer

A:

Run kubectl -n ledger rollout undo deployment/invoice-api after checking rollout history. This is the appropriate command-line action or first safe diagnostic. The technical reason is: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. Validate the result with: Run kubectl -n ledger rollout status deployment/invoice-api and inspect the restored image and configuration. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

B:

This alternative is a response to another technical cause: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The reported case instead depends on: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The action that directly addresses it is “Run kubectl -n ledger rollout undo deployment/invoice-api after checking rollout history”.

C:

The proposed action belongs to the mechanism: A toleration allows a Pod past a matching taint but does not ensure placement without node selection and capacity. Here the stated fault follows a different mechanism: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The corrective choice is “Run kubectl -n ledger rollout undo deployment/invoice-api after checking rollout history”.

D:

The offered action targets: Updating a Deployment Pod template triggers a controlled rollout; restarting Pods alone will not change the image reference. The case facts point instead to: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. Implement “Run kubectl -n ledger rollout undo deployment/invoice-api after checking rollout history” to address that specific condition.

Question 338

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: Deployment invoice-api in namespace ledger was just updated with a faulty Pod template and must return to its prior revision. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. Requests inform scheduling and limits cap runtime consumption; the settings play different roles.
  2. A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template.
  3. CronJob suspension prevents new scheduled Jobs but does not terminate existing Jobs already running.
  4. Rollout restart annotates the Pod template so the Deployment controller replaces Pods according to its rollout strategy.

Explanation

Correct Answer

B:

A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. This explains the stated condition. The corresponding action is: Run kubectl -n ledger rollout undo deployment/invoice-api after checking rollout history. The direct acceptance evidence is: Run kubectl -n ledger rollout status deployment/invoice-api and inspect the restored image and configuration.

Incorrect Answers

A:

This principle describes a separate cause: Requests inform scheduling and limits cap runtime consumption; the settings play different roles. The reported condition is governed by: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The two mechanisms should not be conflated.

C:

The offered statement is true for this other mechanism: CronJob suspension prevents new scheduled Jobs but does not terminate existing Jobs already running. It does not explain the facts described here, which follow from: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template.

D:

This principle describes a separate cause: Rollout restart annotates the Pod template so the Deployment controller replaces Pods according to its rollout strategy. The reported condition is governed by: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The two mechanisms should not be conflated.

Question 339

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: Deployment invoice-api in namespace ledger was just updated with a faulty Pod template and must return to its prior revision. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n ledger get deployment invoice-api -o jsonpath='{.spec.strategy.rollingUpdate}' and verify the values.
  2. Run kubectl -n ledger describe deployment invoice-api and inspect environment key references without printing secret values.
  3. Run kubectl -n ledger rollout status deployment/invoice-api and inspect the restored image and configuration.
  4. Run kubectl -n ledger get deployment invoice-api -o yaml and inspect spec.template.spec.tolerations before testing scheduling.

Explanation

Correct Answer

C:

Run kubectl -n ledger rollout status deployment/invoice-api and inspect the restored image and configuration. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The intended action is: Run kubectl -n ledger rollout undo deployment/invoice-api after checking rollout history.

Incorrect Answers

A:

The alternative verifies a different condition: Deployment rolling-update parameters govern how many old Pods may be unavailable and extra Pods may be created during replacement. The current case instead depends on: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. Confirm that “Run kubectl -n ledger rollout status deployment/invoice-api and inspect the restored image and configuration”.

B:

That test belongs to another control with this basis: Pod templates can reference Secret keys without copying literal secret values into the Deployment spec. In the current case, the governing reason is: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The direct verification is “Run kubectl -n ledger rollout status deployment/invoice-api and inspect the restored image and configuration”.

D:

The alternative verifies a different condition: A toleration allows a Pod past a matching taint but does not ensure placement without node selection and capacity. The current case instead depends on: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. Confirm that “Run kubectl -n ledger rollout status deployment/invoice-api and inspect the restored image and configuration”.

Question 340

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: Deployment invoice-api in namespace ledger was just updated with a faulty Pod template and must return to its prior revision. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Control privileged node labels and review availability before adding hard scheduling constraints.
  2. Track HPA metric availability and avoid simultaneous manual scaling policies that fight the controller.
  3. Check disruption budgets and readiness behavior before application restarts.
  4. Retain meaningful revisions and perform health checks after every rollback.

Explanation

Correct Answer

D:

Retain meaningful revisions and perform health checks after every rollback. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n ledger rollout undo deployment/invoice-api after checking rollout history. The relevant mechanism is: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template.

Incorrect Answers

A:

That safeguard is relevant to: Node selectors constrain scheduling to nodes whose labels match all specified key/value pairs; patching the Pod template triggers a rollout. The current failure instead follows from: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. Its prevention measure is “Retain meaningful revisions and perform health checks after every rollback”.

B:

This routine guards against another mechanism: HPA evaluates metrics relative to Pod resource requests; missing metrics or requests can leave desired replicas unknown. The recurring exposure in the current case is: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The matching preventive check is “Retain meaningful revisions and perform health checks after every rollback”.

C:

The suggested review tracks a different technical risk: Rollout restart annotates the Pod template so the Deployment controller replaces Pods according to its rollout strategy. Here the sustained control must address: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. Choose “Retain meaningful revisions and perform health checks after every rollback”.