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 12

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.

Question 111

A rollout is blocked because a PodDisruptionBudget allows no voluntary disruption during the worker drain. What is the most direct consequence if the underlying problem is left unresolved?

  1. Abrupt interruption can break availability guarantees and lose in-flight work.
  2. Forcing eviction can violate the workload's minimum availability.
  3. Unsupported version skew can create API and scheduling failures.
  4. Effective cluster capacity remains reduced without an obvious node failure.

Explanation

Correct Answer

B:

Forcing eviction can violate the workload's minimum availability. This directly follows from the failed condition. The preventive correction is: Inspect the PodDisruptionBudget and safely increase available replicas or adjust policy before retrying drain. The governing Kubernetes behavior is: The eviction API respects PodDisruptionBudget limits for voluntary disruption.

Incorrect Answers

A:

A drain evicts eligible Pods through the API and respects disruption policies unlike abrupt host shutdown. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Forcing eviction can violate the workload's minimum availability.

C:

Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Forcing eviction can violate the workload's minimum availability.

D:

Cordon status prevents new scheduling even when the node is otherwise Ready. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Forcing eviction can violate the workload's minimum availability.

Question 112

A Pod stays Pending because required pod affinity points to a label that no existing Pod has. Which Kubernetes administration action most directly addresses the observed failure?

  1. Correct the label selector or intentionally seed the matching workload after validating the placement requirement.
  2. Replace preferred affinity with a required node affinity or other enforceable placement policy.
  3. Set a nodeSelector or required node affinity matching the available accelerator nodes.
  4. Use appropriate podAntiAffinity or topology spread constraints for the intended failure domains.

Explanation

Correct Answer

A:

Correct the label selector or intentionally seed the matching workload after validating the placement requirement. This corrects the specific failure because required pod affinity is a hard predicate and cannot match nonexistent target Pods. Verify it by checking: A matching eligible Pod exists in the specified topology and the new Pod schedules.

Incorrect Answers

B:

Preferred affinity influences scoring but is not a hard scheduling constraint. That is relevant to a different intervention. For the stated situation, the required action is: Correct the label selector or intentionally seed the matching workload after validating the placement requirement. The governing reason is: Required pod affinity is a hard predicate and cannot match nonexistent target Pods.

C:

The scheduler matches Pod node constraints to node labels and available resources. That is relevant to a different intervention. For the stated situation, the required action is: Correct the label selector or intentionally seed the matching workload after validating the placement requirement. The governing reason is: Required pod affinity is a hard predicate and cannot match nonexistent target Pods.

D:

Affinity and spread rules influence placement of replicas across nodes or zones. That is relevant to a different intervention. For the stated situation, the required action is: Correct the label selector or intentionally seed the matching workload after validating the placement requirement. The governing reason is: Required pod affinity is a hard predicate and cannot match nonexistent target Pods.

Question 113

A payment Pod can reach internal Services but egress to an external approved API is denied after a policy update. Following the proposed change—Add an egress rule that permits the required destination range and port while preserving other restrictions—which observation best demonstrates that the particular fault is resolved?

  1. Unauthorized ingress and egress probes fail while necessary bidirectional flows pass.
  2. The Pod resolves a Service name and reaches it while unrelated outbound access remains denied.
  3. The approved API endpoint is reachable and a disallowed destination remains blocked.
  4. Approved frontend traffic succeeds while an unrelated test Pod remains denied.

Explanation

Correct Answer

C:

The approved API endpoint is reachable and a disallowed destination remains blocked. This validates the stated intervention—add an egress rule that permits the required destination range and port while preserving other restrictions.—rather than an unrelated cluster change. The relevant mechanism is: An egress-isolated Pod needs an explicit permitted path to each required destination.

Incorrect Answers

A:

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: The approved API endpoint is reachable and a disallowed destination remains blocked.

B:

DNS name resolution is a separate network flow from the application connection. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The approved API endpoint is reachable and a disallowed destination remains blocked.

D:

NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The approved API endpoint is reachable and a disallowed destination remains blocked.

Question 114

A Pod cannot land on one node even after resource capacity is added because the node has an unexpected NoSchedule taint. An engineer recommends: Inspect taints and remove the unintended taint or use narrowly authorized tolerations. Which Kubernetes behavior best explains why this correction fits?

  1. Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization.
  2. Hard placement rules require actual matching node labels at scheduling time.
  3. Scheduler taints are placement constraints distinct from raw allocatable capacity.
  4. The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests.

Explanation

Correct Answer

C:

Scheduler taints are placement constraints distinct from raw allocatable capacity. This explains why the proposed action—inspect taints and remove the unintended taint or use narrowly authorized tolerations.—is appropriate. Direct confirmation is: A permitted workload schedules after the taint policy is corrected without relaxing other nodes.

Incorrect Answers

A:

Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. This does not establish the proposed intervention. The governing principle here is: Scheduler taints are placement constraints distinct from raw allocatable capacity. Apply it by: Inspect taints and remove the unintended taint or use narrowly authorized tolerations.

B:

Hard placement rules require actual matching node labels at scheduling time. This does not establish the proposed intervention. The governing principle here is: Scheduler taints are placement constraints distinct from raw allocatable capacity. Apply it by: Inspect taints and remove the unintended taint or use narrowly authorized tolerations.

D:

The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests. This does not establish the proposed intervention. The governing principle here is: Scheduler taints are placement constraints distinct from raw allocatable capacity. Apply it by: Inspect taints and remove the unintended taint or use narrowly authorized tolerations.

Question 115

An HTTPRoute selects a Gateway listener name that does not exist and no traffic reaches the route. Which Kubernetes administration action most directly addresses the observed failure?

  1. Configure the listener allowedRoutes namespaces policy or appropriate cross-namespace reference permissions.
  2. Inspect the GatewayClass controller and Gateway listener conditions before debugging application Pods.
  3. Change parentRefs sectionName or create the intended listener and confirm route attachment status.
  4. Adjust backendRefs weights and validate rollout percentages before production promotion.

Explanation

Correct Answer

C:

Change parentRefs sectionName or create the intended listener and confirm route attachment status. This corrects the specific failure because gateway API HTTPRoutes must attach to compatible allowed listeners through parent references. Verify it by checking: HTTPRoute status reports Accepted and traffic matches its intended listener.

Incorrect Answers

A:

Gateway API constrains route attachment and cross-namespace references through explicit policies. That is relevant to a different intervention. For the stated situation, the required action is: Change parentRefs sectionName or create the intended listener and confirm route attachment status. The governing reason is: Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references.

B:

Gateway API resources require an implementing controller to provision and program data-plane listeners. That is relevant to a different intervention. For the stated situation, the required action is: Change parentRefs sectionName or create the intended listener and confirm route attachment status. The governing reason is: Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references.

D:

Gateway API backend weights influence proportional HTTPRoute forwarding among valid backends. That is relevant to a different intervention. For the stated situation, the required action is: Change parentRefs sectionName or create the intended listener and confirm route attachment status. The governing reason is: Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references.

Question 116

A horizontal autoscaler stays at its maximum replica count after load subsides and no one checks its stabilization policy. Following the proposed change—Inspect HPA behavior and scale-down stabilization windows before tuning them for the workload—which observation best demonstrates that the particular fault is resolved?

  1. The HPA reports observed utilization and increases replicas during a controlled load.
  2. Controlled queue growth drives replica changes even when CPU remains low.
  3. Replicas decrease after the approved stabilization interval without oscillating under test load.
  4. The desired replica count is ready under the new image and old ReplicaSet replicas are reduced.

Explanation

Correct Answer

C:

Replicas decrease after the approved stabilization interval without oscillating under test load. This validates the stated intervention—inspect HPA behavior and scale-down stabilization windows before tuning them for the workload.—rather than an unrelated cluster change. The relevant mechanism is: HPA may delay downscaling to avoid flapping even after metrics fall.

Incorrect Answers

A:

HPA CPU utilization calculations depend on resource requests and relevant metrics API data. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Replicas decrease after the approved stabilization interval without oscillating under test load.

B:

Different workload bottlenecks require appropriately supported HPA metrics. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Replicas decrease after the approved stabilization interval without oscillating under test load.

D:

Desired-state changes are asynchronous and a successful API update is not proof of healthy Pods. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Replicas decrease after the approved stabilization interval without oscillating under test load.

Question 117

A worker pool must scale on queue depth but an engineer configures only a CPU utilization HPA. What is the most direct consequence if the underlying problem is left unresolved?

  1. Insufficient replicas can cause latency and request failures.
  2. Autoscaling can remain ineffective despite observed load spikes.
  3. Backlogs can grow while autoscaling appears healthy on irrelevant CPU metrics.
  4. Finite tasks may execute repeatedly or never report terminal completion.

Explanation

Correct Answer

C:

Backlogs can grow while autoscaling appears healthy on irrelevant CPU metrics. This directly follows from the failed condition. The preventive correction is: Use a suitable custom or external metrics source and scale target based on backlog with validated adapters. The governing Kubernetes behavior is: Different workload bottlenecks require appropriately supported HPA metrics.

Incorrect Answers

A:

HPA CPU utilization calculations depend on resource requests and relevant metrics API data. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Backlogs can grow while autoscaling appears healthy on irrelevant CPU metrics.

B:

CPU percentage targets use utilization relative to requested CPU, not just absolute node usage. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Backlogs can grow while autoscaling appears healthy on irrelevant CPU metrics.

D:

Jobs manage successful completion of finite work; Deployments maintain continuous desired replicas. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Backlogs can grow while autoscaling appears healthy on irrelevant CPU metrics.

Question 118

A Pod is repeatedly evicted from a worker reporting PIDPressure but memory and disk look healthy. What is the most direct consequence if the underlying problem is left unresolved?

  1. Repeated OOM kills can degrade both batch work and neighboring services.
  2. The kubelet may evict Pods when process capacity is exhausted.
  3. Pod evictions and admission failures may continue despite idle CPU.
  4. Workloads may be evicted or remain unschedulable on the affected node.

Explanation

Correct Answer

B:

The kubelet may evict Pods when process capacity is exhausted. This directly follows from the failed condition. The preventive correction is: Inspect process counts and runaway process creation, then cap or repair the offending workload. The governing Kubernetes behavior is: Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage.

Incorrect Answers

A:

The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: The kubelet may evict Pods when process capacity is exhausted.

C:

Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: The kubelet may evict Pods when process capacity is exhausted.

D:

A node's Ready condition depends on kubelet heartbeats and necessary local runtime services. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: The kubelet may evict Pods when process capacity is exhausted.

Question 119

A database Pod keeps landing on the same node as another replica despite the service's resilience goal. What is the most direct consequence if the underlying problem is left unresolved?

  1. A single node failure may remove every copy of the database.
  2. A misconfigured affinity rule can deadlock application startup.
  3. A sensitive workload may be placed on an unapproved node when capacity is tight.
  4. Specialized jobs may remain unschedulable despite available hardware.

Explanation

Correct Answer

A:

A single node failure may remove every copy of the database. This directly follows from the failed condition. The preventive correction is: Use appropriate podAntiAffinity or topology spread constraints for the intended failure domains. The governing Kubernetes behavior is: Affinity and spread rules influence placement of replicas across nodes or zones.

Incorrect Answers

B:

A misconfigured affinity rule can deadlock application startup. That outcome is tied more directly to this separate failure: A Pod stays Pending because required pod affinity points to a label that no existing Pod has. The stated gap instead most directly risks that a single node failure may remove every copy of the database.

C:

A sensitive workload may be placed on an unapproved node when capacity is tight. That outcome is tied more directly to this separate failure: A critical workload must never run on nodes missing a data-sovereignty label, yet a preferred affinity rule was used. The stated gap instead most directly risks that a single node failure may remove every copy of the database.

D:

The scheduler matches Pod node constraints to node labels and available resources. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A single node failure may remove every copy of the database.

Question 120

A storage policy requires encrypted volumes but an engineer creates a StorageClass without the provider's encryption parameters. Following the proposed change—Define the correct CSI StorageClass parameters and verify the provisioned volume security properties—which observation best demonstrates that the particular fault is resolved?

  1. A test PVC becomes Bound and the expected CSI volume is created.
  2. A test PV is created with the required encryption setting reported by the storage provider.
  3. The PVC is Bound and a consumer on each eligible worker mounts and reads the volume.
  4. A new PVC binds in the same topology as its consuming Pod and the Pod starts.

Explanation

Correct Answer

B:

A test PV is created with the required encryption setting reported by the storage provider. This validates the stated intervention—define the correct CSI StorageClass parameters and verify the provisioned volume security properties.—rather than an unrelated cluster change. The relevant mechanism is: StorageClass parameters are driver-specific and determine backend provisioning behavior.

Incorrect Answers

A:

Dynamic provisioning depends on a controller that recognizes the StorageClass provisioner identifier. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test PV is created with the required encryption setting reported by the storage provider.

C:

A controller may provision a volume while the node-side CSI plugin is still required to mount it. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test PV is created with the required encryption setting reported by the storage provider.

D:

Delayed volume binding allows scheduling constraints and storage topology to be considered together. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test PV is created with the required encryption setting reported by the storage provider.