McAfee Secured

CNCF CKA Bundle

Exam Code: CKA

Exam Name Certified Kubernetes Administrator

Certification Provider: CNCF

Corresponding Certification: CKA

CNCF CKA Bundle $44.99

Pass CNCF CKA with Real Questions From Testking

Download Web's Best CKA Exam Preparation Materials Today

  • Questions & Answers

    CKA Questions & Answers

    58 Questions & Answers

    Questions & Answers Testing Engine software allows you to practice questions and answers in real CKA exam environment.

  • CKA Video Course

    CKA Video Course

    138 Video Lectures

    CKA Video Course is developed by CNCF Professionals to help you pass 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

    Study Guide will give you a practical experience regarding the subject and provide an academic background. CKA Study Guide is available in PDF format.

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

    Video Course

    138 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    268 PDF Pages

    $29.99

CNCF CKA Practice Test 11

Question 100

A namespace applies a default-deny ingress NetworkPolicy and legitimate frontend-to-backend requests begin timing out. Following the proposed change—Add a narrowly scoped ingress allow policy selecting the backend and trusted frontend Pods on the required port—which observation best demonstrates that the particular fault is resolved?

  1. Approved frontend traffic succeeds while an unrelated test Pod remains denied.
  2. Only the intended web client can connect to the protected backend.
  3. The approved API endpoint is reachable and a disallowed destination remains blocked.
  4. Unauthorized ingress and egress probes fail while necessary bidirectional flows pass.

Explanation

Correct Answer

A:

Approved frontend traffic succeeds while an unrelated test Pod remains denied. This validates the stated intervention—add a narrowly scoped ingress allow policy selecting the backend and trusted frontend Pods on the required port.—rather than an unrelated cluster change. The relevant mechanism is: NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation.

Incorrect Answers

B:

A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Approved frontend traffic succeeds while an unrelated test Pod remains denied.

C:

An egress-isolated Pod needs an explicit permitted path to each required destination. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Approved frontend traffic succeeds while an unrelated test Pod remains denied.

D:

Ingress and egress restrictions are evaluated independently and policy effects compose additively. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Approved frontend traffic succeeds while an unrelated test Pod remains denied.

Question 101

A filesystem volume is mounted read-only by a Pod even though the application needs to write state. Which Kubernetes administration action most directly addresses the observed failure?

  1. Use a ReadWriteMany-capable shared filesystem and a matching PV or StorageClass.
  2. Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access.
  3. Set the appropriate Retain policy before deleting the claim and plan explicit data recovery or disposal.
  4. Choose an access mode and storage backend compatible with the intended attach and sharing semantics.

Explanation

Correct Answer

B:

Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access. This corrects the specific failure because mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. Verify it by checking: The approved Pod writes a test file and unauthorized consumers remain restricted.

Incorrect Answers

A:

Kubernetes access modes express requested attachment semantics but cannot add capability to a backend. That is relevant to a different intervention. For the stated situation, the required action is: Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access. The governing reason is: Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities.

C:

Reclaim policy determines what happens to backend storage after a bound claim is released. That is relevant to a different intervention. For the stated situation, the required action is: Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access. The governing reason is: Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities.

D:

ReadWriteOnce restricts volume mounting to one node, not globally one Pod; multi-node sharing needs backend support. That is relevant to a different intervention. For the stated situation, the required action is: Correct the Pod volumeMount readOnly setting and validate the PV and backend's supported access. The governing reason is: Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities.

Question 102

An operator reconciles a custom resource but never creates the expected Deployment after its controller Pod crashes. An engineer recommends: Restore the controller/operator and check reconciliation logs and permissions before changing the custom object. Which Kubernetes behavior best explains why this correction fits?

  1. Custom resource status updates are separately authorized from spec updates when status is enabled.
  2. A CRD defines the API schema while a running controller implements the desired behavior.
  3. Finalizers block object deletion until the associated controller completes the required cleanup.
  4. New custom resource types participate in authorization using their API group and scope.

Explanation

Correct Answer

B:

A CRD defines the API schema while a running controller implements the desired behavior. This explains why the proposed action—restore the controller/operator and check reconciliation logs and permissions before changing the custom object.—is appropriate. Direct confirmation is: The operator returns healthy and the managed Deployment appears with the expected owner references.

Incorrect Answers

A:

Custom resource status updates are separately authorized from spec updates when status is enabled. This does not establish the proposed intervention. The governing principle here is: A CRD defines the API schema while a running controller implements the desired behavior. Apply it by: Restore the controller/operator and check reconciliation logs and permissions before changing the custom object.

C:

Finalizers block object deletion until the associated controller completes the required cleanup. This does not establish the proposed intervention. The governing principle here is: A CRD defines the API schema while a running controller implements the desired behavior. Apply it by: Restore the controller/operator and check reconciliation logs and permissions before changing the custom object.

D:

New custom resource types participate in authorization using their API group and scope. This does not establish the proposed intervention. The governing principle here is: A CRD defines the API schema while a running controller implements the desired behavior. Apply it by: Restore the controller/operator and check reconciliation logs and permissions before changing the custom object.

Question 103

A cluster uses an internal Service named frontend but an Ingress backend references old-service after a rename. What is the most direct consequence if the underlying problem is left unresolved?

  1. A healthy Service may remain unreachable because ingress references stale identity.
  2. Clients see TLS errors despite HTTP backend health.
  3. Operators may troubleshoot the backend while no entry controller exists.
  4. Traffic can fail to route or unintentionally reach an external frontend.

Explanation

Correct Answer

A:

A healthy Service may remain unreachable because ingress references stale identity. This directly follows from the failed condition. The preventive correction is: Update the Ingress backend service.name and the correct service port reference. The governing Kubernetes behavior is: Ingress rules point to Services by name and port within their namespace.

Incorrect Answers

B:

Ingress TLS termination depends on a usable referenced Secret and an active controller. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A healthy Service may remain unreachable because ingress references stale identity.

C:

Ingress API objects do not themselves implement HTTP routing; a controller supplies the dataplane. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A healthy Service may remain unreachable because ingress references stale identity.

D:

Ingress controllers commonly filter resources by configured IngressClass. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A healthy Service may remain unreachable because ingress references stale identity.

Question 104

An API endpoint appears slow but an administrator looks only at node CPU and never measures its container resource pressure. Which Kubernetes administration action most directly addresses the observed failure?

  1. Compare configured CPU limits and container throttling metrics before changing node size.
  2. Correlate node memory metrics with Pod usage, cache and eviction conditions before resizing the app.
  3. Inspect Pod-level CPU and memory use and component metrics with kubectl top and relevant monitoring.
  4. Verify the aggregated metrics APIService and metrics-server connectivity to kubelets.

Explanation

Correct Answer

C:

Inspect Pod-level CPU and memory use and component metrics with kubectl top and relevant monitoring. This corrects the specific failure because node-wide utilization can hide a throttled or memory-constrained application container. Verify it by checking: The specific bottlenecking Pod is identified and its latency improves after targeted resource changes.

Incorrect Answers

A:

CPU limits may cause throttling independent of overall node idle time. That is relevant to a different intervention. For the stated situation, the required action is: Inspect Pod-level CPU and memory use and component metrics with kubectl top and relevant monitoring. The governing reason is: Node-wide utilization can hide a throttled or memory-constrained application container.

B:

Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. That is relevant to a different intervention. For the stated situation, the required action is: Inspect Pod-level CPU and memory use and component metrics with kubectl top and relevant monitoring. The governing reason is: Node-wide utilization can hide a throttled or memory-constrained application container.

D:

kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. That is relevant to a different intervention. For the stated situation, the required action is: Inspect Pod-level CPU and memory use and component metrics with kubectl top and relevant monitoring. The governing reason is: Node-wide utilization can hide a throttled or memory-constrained application container.

Question 105

A cluster owner runs kubeadm upgrade plan but skips the reported component compatibility warnings. Which Kubernetes administration action most directly addresses the observed failure?

  1. Take, securely store, and verify an etcd backup as part of the documented upgrade rollback plan.
  2. Follow Kubernetes version-skew rules and upgrade the control plane and workers in the supported order.
  3. Resolve compatibility and required preflight conditions before applying the approved upgrade target.
  4. Run the supported uncordon action after validating the kubelet and desired workloads.

Explanation

Correct Answer

C:

Resolve compatibility and required preflight conditions before applying the approved upgrade target. This corrects the specific failure because kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command. Verify it by checking: The upgrade plan lists the expected target and preflight checks pass before apply.

Incorrect Answers

A:

Cluster state durability requires more than rerunning kubeadm; an etcd snapshot protects API objects. That is relevant to a different intervention. For the stated situation, the required action is: Resolve compatibility and required preflight conditions before applying the approved upgrade target. The governing reason is: kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command.

B:

Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. That is relevant to a different intervention. For the stated situation, the required action is: Resolve compatibility and required preflight conditions before applying the approved upgrade target. The governing reason is: kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command.

D:

Cordon status prevents new scheduling even when the node is otherwise Ready. That is relevant to a different intervention. For the stated situation, the required action is: Resolve compatibility and required preflight conditions before applying the approved upgrade target. The governing reason is: kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command.

Question 106

A planned kubeadm control-plane upgrade is attempted without first taking a recoverable etcd snapshot. An engineer recommends: Take, securely store, and verify an etcd backup as part of the documented upgrade rollback plan. Which Kubernetes behavior best explains why this correction fits?

  1. kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command.
  2. Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server.
  3. Cluster state durability requires more than rerunning kubeadm; an etcd snapshot protects API objects.
  4. The eviction API respects PodDisruptionBudget limits for voluntary disruption.

Explanation

Correct Answer

C:

Cluster state durability requires more than rerunning kubeadm; an etcd snapshot protects API objects. This explains why the proposed action—take, securely store, and verify an etcd backup as part of the documented upgrade rollback plan.—is appropriate. Direct confirmation is: The backup has the expected revision and an isolated restore rehearsal can list known objects.

Incorrect Answers

A:

kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command. This does not establish the proposed intervention. The governing principle here is: Cluster state durability requires more than rerunning kubeadm; an etcd snapshot protects API objects. Apply it by: Take, securely store, and verify an etcd backup as part of the documented upgrade rollback plan.

B:

Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. This does not establish the proposed intervention. The governing principle here is: Cluster state durability requires more than rerunning kubeadm; an etcd snapshot protects API objects. Apply it by: Take, securely store, and verify an etcd backup as part of the documented upgrade rollback plan.

D:

The eviction API respects PodDisruptionBudget limits for voluntary disruption. This does not establish the proposed intervention. The governing principle here is: Cluster state durability requires more than rerunning kubeadm; an etcd snapshot protects API objects. Apply it by: Take, securely store, and verify an etcd backup as part of the documented upgrade rollback plan.

Question 107

A manually managed Service without a selector has no EndpointSlice configured yet the Service IP is expected to proxy connections. Following the proposed change—Create and maintain appropriate EndpointSlice resources with correct labels and target addresses—which observation best demonstrates that the particular fault is resolved?

  1. EndpointSlices list the correct ready Pod addresses and Service calls succeed.
  2. The Service receives the expected load balancer ingress and end-to-end external probes succeed.
  3. The Service resolves to valid managed endpoints and a test client reaches its backing process.
  4. DNS lookups return the intended Pod endpoint addresses and stateful clients connect to them.

Explanation

Correct Answer

C:

The Service resolves to valid managed endpoints and a test client reaches its backing process. This validates the stated intervention—create and maintain appropriate EndpointSlice resources with correct labels and target addresses.—rather than an unrelated cluster change. The relevant mechanism is: Selectorless Services require explicitly associated endpoints because no controller infers backing Pods.

Incorrect Answers

A:

Selector-backed Services route through EndpointSlices populated from matching eligible Pods. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The Service resolves to valid managed endpoints and a test client reaches its backing process.

B:

NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The Service resolves to valid managed endpoints and a test client reaches its backing process.

D:

A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The Service resolves to valid managed endpoints and a test client reaches its backing process.

Question 108

A stateful cache requires a stable identity for each Pod but is currently managed as interchangeable Deployment replicas. Which Kubernetes administration action most directly addresses the observed failure?

  1. Configure rolling-update maxUnavailable and maxSurge according to available capacity and readiness requirements.
  2. Use rollout history to identify the last healthy revision and roll back the Deployment to it.
  3. Use a StatefulSet with the required stable identity and appropriately provisioned storage.
  4. Apply the intended image and observe rollout status and updated ReplicaSets before declaring success.

Explanation

Correct Answer

C:

Use a StatefulSet with the required stable identity and appropriately provisioned storage. This corrects the specific failure because statefulSets provide ordered identities and stable per-Pod names where identity matters. Verify it by checking: Pods retain stable ordinal network identities and corresponding storage across replacement.

Incorrect Answers

A:

The Deployment rollout strategy controls the allowed temporary excess and unavailable replicas. That is relevant to a different intervention. For the stated situation, the required action is: Use a StatefulSet with the required stable identity and appropriately provisioned storage. The governing reason is: StatefulSets provide ordered identities and stable per-Pod names where identity matters.

B:

Deployment revisions track supported rollout history and a rollback restores a previous Pod template. That is relevant to a different intervention. For the stated situation, the required action is: Use a StatefulSet with the required stable identity and appropriately provisioned storage. The governing reason is: StatefulSets provide ordered identities and stable per-Pod names where identity matters.

D:

Desired-state changes are asynchronous and a successful API update is not proof of healthy Pods. That is relevant to a different intervention. For the stated situation, the required action is: Use a StatefulSet with the required stable identity and appropriately provisioned storage. The governing reason is: StatefulSets provide ordered identities and stable per-Pod names where identity matters.

Question 109

A node is overrun by image garbage collection activity during every deployment wave. Following the proposed change—Inspect image filesystem consumption and kubelet garbage collection thresholds before changing policies—which observation best demonstrates that the particular fault is resolved?

  1. Image filesystem usage stabilizes and Pod starts remain timely during controlled releases.
  2. Throttle counters decline and application latency improves after a justified limit adjustment.
  3. Per-Pod and node metrics identify the actual source of growth and targeted action resolves pressure.
  4. The specific bottlenecking Pod is identified and its latency improves after targeted resource changes.

Explanation

Correct Answer

A:

Image filesystem usage stabilizes and Pod starts remain timely during controlled releases. This validates the stated intervention—inspect image filesystem consumption and kubelet garbage collection thresholds before changing policies.—rather than an unrelated cluster change. The relevant mechanism is: Image storage pressure and image garbage collection are distinct from application CPU demand.

Incorrect Answers

B:

CPU limits may cause throttling independent of overall node idle time. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Image filesystem usage stabilizes and Pod starts remain timely during controlled releases.

C:

Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Image filesystem usage stabilizes and Pod starts remain timely during controlled releases.

D:

Node-wide utilization can hide a throttled or memory-constrained application container. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Image filesystem usage stabilizes and Pod starts remain timely during controlled releases.

Question 110

A new HA control-plane node receives a certificate that omits the load-balanced API hostname from its SANs. An engineer recommends: Issue certificates that include the approved stable API endpoint and node identities. Which Kubernetes behavior best explains why this correction fits?

  1. Highly available control planes depend on load-balanced API access and durable quorum-backed state.
  2. A successful TCP handshake does not prove a particular API server is ready to serve requests.
  3. Quorum and replication do not protect against a common power or hypervisor failure domain.
  4. TLS clients verify the endpoint hostname against the presented certificate SANs.

Explanation

Correct Answer

D:

TLS clients verify the endpoint hostname against the presented certificate SANs. This explains why the proposed action—issue certificates that include the approved stable API endpoint and node identities.—is appropriate. Direct confirmation is: A TLS connection to the load-balanced hostname succeeds without insecure verification overrides.

Incorrect Answers

A:

Highly available control planes depend on load-balanced API access and durable quorum-backed state. This does not establish the proposed intervention. The governing principle here is: TLS clients verify the endpoint hostname against the presented certificate SANs. Apply it by: Issue certificates that include the approved stable API endpoint and node identities.

B:

A successful TCP handshake does not prove a particular API server is ready to serve requests. This does not establish the proposed intervention. The governing principle here is: TLS clients verify the endpoint hostname against the presented certificate SANs. Apply it by: Issue certificates that include the approved stable API endpoint and node identities.

C:

Quorum and replication do not protect against a common power or hypervisor failure domain. This does not establish the proposed intervention. The governing principle here is: TLS clients verify the endpoint hostname against the presented certificate SANs. Apply it by: Issue certificates that include the approved stable API endpoint and node identities.