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 15

Question 140

A control-plane host's clock drifts and kubelet and API authentication fail with certificate not yet valid errors. Following the proposed change—Restore accurate time synchronization before investigating certificate renewal—which observation best demonstrates that the particular fault is resolved?

  1. kubectl establishes a verified TLS session to the intended endpoint without insecure skipping.
  2. Worker kubelet connections and administrator requests succeed using current endpoints.
  3. Host clocks align and API clients authenticate with existing valid certificates.
  4. The controller-manager stays Running and a Deployment reconciles desired replicas.

Explanation

Correct Answer

C:

Host clocks align and API clients authenticate with existing valid certificates. This validates the stated intervention—restore accurate time synchronization before investigating certificate renewal.—rather than an unrelated cluster change. The relevant mechanism is: TLS certificate validity periods depend on reasonable clock agreement between peers.

Incorrect Answers

A:

Clients validate control-plane TLS certificate identity before trusting API responses. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Host clocks align and API clients authenticate with existing valid certificates.

B:

Control-plane advertised addresses must be reachable through the cluster's intended topology. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Host clocks align and API clients authenticate with existing valid certificates.

D:

The kubelet restarts static control-plane Pods when their manifest changes. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Host clocks align and API clients authenticate with existing valid certificates.

Question 141

A node reports DiskPressure and new Pods cannot be admitted although CPU and memory are available. What is the most direct consequence if the underlying problem is left unresolved?

  1. The kubelet may evict Pods when process capacity is exhausted.
  2. Repeated OOM kills can degrade both batch work and neighboring services.
  3. Pod evictions and admission failures may continue despite idle CPU.
  4. Capacity may sit unused while Pods remain Pending.

Explanation

Correct Answer

C:

Pod evictions and admission failures may continue despite idle CPU. This directly follows from the failed condition. The preventive correction is: Identify and clean safe image or container filesystem usage and expand capacity if needed. The governing Kubernetes behavior is: Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization.

Incorrect Answers

A:

Node PIDPressure reflects process-ID exhaustion rather than CPU, memory or disk usage. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Pod evictions and admission failures may continue despite idle CPU.

B:

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: Pod evictions and admission failures may continue despite idle CPU.

D:

Scheduler taints are placement constraints distinct from raw allocatable capacity. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Pod evictions and admission failures may continue despite idle CPU.

Question 142

A GPU training Pod remains Pending while GPUs exist on nodes carrying a dedicated accelerator label. What is the most direct consequence if the underlying problem is left unresolved?

  1. Specialized jobs may remain unschedulable despite available hardware.
  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. Dedicated capacity can remain unused or be accessed by unintended workloads.

Explanation

Correct Answer

A:

Specialized jobs may remain unschedulable despite available hardware. This directly follows from the failed condition. The preventive correction is: Set a nodeSelector or required node affinity matching the available accelerator nodes. The governing Kubernetes behavior is: The scheduler matches Pod node constraints to node labels and available resources.

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 specialized jobs may remain unschedulable despite available hardware.

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 specialized jobs may remain unschedulable despite available hardware.

D:

Tolerations permit scheduling onto tainted nodes but do not by themselves select those nodes. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Specialized jobs may remain unschedulable despite available hardware.

Question 143

A team deletes a PVC expecting to preserve its disk, but the dynamically created PV uses a Delete reclaim policy. Following the proposed change—Set the appropriate Retain policy before deleting the claim and plan explicit data recovery or disposal—which observation best demonstrates that the particular fault is resolved?

  1. The approved Pod writes a test file and unauthorized consumers remain restricted.
  2. A replacement Pod retrieves persistent data from its PVC while scratch data is disposable.
  3. After a Pod reschedule, the workload reads the correct data from its supported backend.
  4. After PVC deletion, the retained PV and backend volume still exist for approved recovery.

Explanation

Correct Answer

D:

After PVC deletion, the retained PV and backend volume still exist for approved recovery. This validates the stated intervention—set the appropriate Retain policy before deleting the claim and plan explicit data recovery or disposal.—rather than an unrelated cluster change. The relevant mechanism is: Reclaim policy determines what happens to backend storage after a bound claim is released.

Incorrect Answers

A:

Mount-level read-only settings can prohibit writes regardless of a backend's broader capabilities. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: After PVC deletion, the retained PV and backend volume still exist for approved recovery.

B:

emptyDir follows the Pod lifetime and is removed when that Pod ceases to exist. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: After PVC deletion, the retained PV and backend volume still exist for approved recovery.

C:

hostPath refers to a specific node filesystem and does not provide cluster-wide data mobility. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: After PVC deletion, the retained PV and backend volume still exist for approved recovery.

Question 144

An application uses nslookup for the short name payments from a different namespace and resolves the wrong object. What is the most direct consequence if the underlying problem is left unresolved?

  1. Short names can silently resolve to a different service or fail.
  2. Cluster-internal discovery can break while public DNS continues to work.
  3. DNS failures appear node-specific even when CoreDNS Pods are healthy.
  4. One malformed DNS configuration can disrupt discovery cluster-wide.

Explanation

Correct Answer

A:

Short names can silently resolve to a different service or fail. This directly follows from the failed condition. The preventive correction is: Use payments.<namespace>.svc.cluster.local or a valid namespace-qualified name. The governing Kubernetes behavior is: Pod DNS search domains are namespace-relative and short names are not globally unique.

Incorrect Answers

B:

Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Short names can silently resolve to a different service or fail.

C:

Pod DNS settings may be generated from kubelet node configuration and dnsPolicy. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Short names can silently resolve to a different service or fail.

D:

CoreDNS must parse its plugin chain before it can serve cluster DNS queries. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Short names can silently resolve to a different service or fail.

Question 145

A Pod requests 8 GiB of memory but each suitable node has only 4 GiB allocatable. Which Kubernetes administration action most directly addresses the observed failure?

  1. Set a nodeSelector or required node affinity matching the available accelerator nodes.
  2. Resize requests or provide sufficient eligible nodes based on actual allocatable capacity.
  3. Correct the label selector or intentionally seed the matching workload after validating the placement requirement.
  4. Add narrowly scoped matching tolerations and appropriate node placement constraints to the authorized Pods.

Explanation

Correct Answer

B:

Resize requests or provide sufficient eligible nodes based on actual allocatable capacity. This corrects the specific failure because the scheduler evaluates Pod requests against node allocatable resources, not observed averages alone. Verify it by checking: Events no longer report Insufficient memory and the Pod schedules after capacity is corrected.

Incorrect Answers

A:

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: Resize requests or provide sufficient eligible nodes based on actual allocatable capacity. The governing reason is: The scheduler evaluates Pod requests against node allocatable resources, not observed averages alone.

C:

Required pod affinity is a hard predicate and cannot match nonexistent target Pods. That is relevant to a different intervention. For the stated situation, the required action is: Resize requests or provide sufficient eligible nodes based on actual allocatable capacity. The governing reason is: The scheduler evaluates Pod requests against node allocatable resources, not observed averages alone.

D:

Tolerations permit scheduling onto tainted nodes but do not by themselves select those nodes. That is relevant to a different intervention. For the stated situation, the required action is: Resize requests or provide sufficient eligible nodes based on actual allocatable capacity. The governing reason is: The scheduler evaluates Pod requests against node allocatable resources, not observed averages alone.

Question 146

A new CNI DaemonSet is running, yet cross-node Pods cannot communicate because the chosen plugin does not match node routing. Following the proposed change—Validate the CNI dataplane and Pod CIDR routing requirements against the infrastructure before promoting the plugin—which observation best demonstrates that the particular fault is resolved?

  1. Representative policy and cross-node traffic tests pass under the new plugin before retirement of the old one.
  2. Pods on different nodes exchange traffic and routes or tunnels reflect the planned topology.
  3. Network connectivity and volume mount fixtures independently pass for their respective plugins.
  4. CSIDriver and plugin Pods are healthy and a test PVC mounts successfully.

Explanation

Correct Answer

B:

Pods on different nodes exchange traffic and routes or tunnels reflect the planned topology. This validates the stated intervention—validate the CNI dataplane and Pod CIDR routing requirements against the infrastructure before promoting the plugin.—rather than an unrelated cluster change. The relevant mechanism is: CNI controls Pod network setup but cross-node reachability also depends on encapsulation or underlay routes.

Incorrect Answers

A:

Network policy implementations and CNI-specific resources can differ despite common Pod-network requirements. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Pods on different nodes exchange traffic and routes or tunnels reflect the planned topology.

C:

CNI handles networking while CSI handles storage; shared namespaces do not imply interchangeable capabilities. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Pods on different nodes exchange traffic and routes or tunnels reflect the planned topology.

D:

CSI driver registration and controller/node capabilities are required for external volume provisioning and mounting. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Pods on different nodes exchange traffic and routes or tunnels reflect the planned topology.

Question 147

A NodePort Service is accessible through worker addresses but an operator expects it to create a cloud load balancer automatically. Following the proposed change—Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required—which observation best demonstrates that the particular fault is resolved?

  1. No external load-balancer address exists and internal client traffic succeeds.
  2. The Service resolves to valid managed endpoints and a test client reaches its backing process.
  3. DNS lookups return the intended Pod endpoint addresses and stateful clients connect to them.
  4. The Service receives the expected load balancer ingress and end-to-end external probes succeed.

Explanation

Correct Answer

D:

The Service receives the expected load balancer ingress and end-to-end external probes succeed. This validates the stated intervention—use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required.—rather than an unrelated cluster change. The relevant mechanism is: NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning.

Incorrect Answers

A:

ClusterIP is intended for internal service discovery; LoadBalancer requests external integration where supported. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The Service receives the expected load balancer ingress and end-to-end external probes succeed.

B:

Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The Service receives the expected load balancer ingress and end-to-end external probes succeed.

C:

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 receives the expected load balancer ingress and end-to-end external probes succeed.

Question 148

A team creates a NetworkPolicy resource but its chosen CNI has no policy enforcement feature enabled. What is the most direct consequence if the underlying problem is left unresolved?

  1. One direction may remain blocked or unintentionally open without end-to-end testing.
  2. A blanket allow would erase the intended namespace segmentation.
  3. A false sense of isolation can expose sensitive workloads.
  4. Applications may appear network-isolated because they cannot resolve healthy destinations.

Explanation

Correct Answer

C:

A false sense of isolation can expose sensitive workloads. This directly follows from the failed condition. The preventive correction is: Deploy or enable a NetworkPolicy-capable CNI dataplane and test actual packet enforcement. The governing Kubernetes behavior is: Kubernetes accepts policy objects even when a CNI does not implement enforcement.

Incorrect Answers

A:

Ingress and egress restrictions are evaluated independently and policy effects compose additively. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A false sense of isolation can expose sensitive workloads.

B:

NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A false sense of isolation can expose sensitive workloads.

D:

DNS name resolution is a separate network flow from the application connection. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A false sense of isolation can expose sensitive workloads.

Question 149

A cluster dedicates worker nodes to compliance workloads using NoSchedule taints, yet authorized Pods cannot use them. Which Kubernetes administration action most directly addresses the observed failure?

  1. Set a nodeSelector or required node affinity matching the available accelerator nodes.
  2. Add narrowly scoped matching tolerations and appropriate node placement constraints to the authorized Pods.
  3. Replace preferred affinity with a required node affinity or other enforceable placement policy.
  4. Use appropriate podAntiAffinity or topology spread constraints for the intended failure domains.

Explanation

Correct Answer

B:

Add narrowly scoped matching tolerations and appropriate node placement constraints to the authorized Pods. This corrects the specific failure because tolerations permit scheduling onto tainted nodes but do not by themselves select those nodes. Verify it by checking: Only intended workloads land on dedicated nodes while unapproved Pods remain excluded.

Incorrect Answers

A:

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: Add narrowly scoped matching tolerations and appropriate node placement constraints to the authorized Pods. The governing reason is: Tolerations permit scheduling onto tainted nodes but do not by themselves select those nodes.

C:

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: Add narrowly scoped matching tolerations and appropriate node placement constraints to the authorized Pods. The governing reason is: Tolerations permit scheduling onto tainted nodes but do not by themselves select those nodes.

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: Add narrowly scoped matching tolerations and appropriate node placement constraints to the authorized Pods. The governing reason is: Tolerations permit scheduling onto tainted nodes but do not by themselves select those nodes.

Question 150

A storage class uses Immediate binding in a multi-zone cluster and creates a disk before the Pod's node is selected. Which Kubernetes administration action most directly addresses the observed failure?

  1. Set exactly the intended default class annotation and specify storageClassName explicitly for critical claims.
  2. Select a StorageClass with an installed valid provisioner or install the required CSI driver.
  3. Use WaitForFirstConsumer binding for topology-constrained storage where supported.
  4. Define the correct CSI StorageClass parameters and verify the provisioned volume security properties.

Explanation

Correct Answer

C:

Use WaitForFirstConsumer binding for topology-constrained storage where supported. This corrects the specific failure because delayed volume binding allows scheduling constraints and storage topology to be considered together. Verify it by checking: A new PVC binds in the same topology as its consuming Pod and the Pod starts.

Incorrect Answers

A:

PVCs without a specified class can inherit the cluster's default storage class. That is relevant to a different intervention. For the stated situation, the required action is: Use WaitForFirstConsumer binding for topology-constrained storage where supported. The governing reason is: Delayed volume binding allows scheduling constraints and storage topology to be considered together.

B:

Dynamic provisioning depends on a controller that recognizes the StorageClass provisioner identifier. That is relevant to a different intervention. For the stated situation, the required action is: Use WaitForFirstConsumer binding for topology-constrained storage where supported. The governing reason is: Delayed volume binding allows scheduling constraints and storage topology to be considered together.

D:

StorageClass parameters are driver-specific and determine backend provisioning behavior. That is relevant to a different intervention. For the stated situation, the required action is: Use WaitForFirstConsumer binding for topology-constrained storage where supported. The governing reason is: Delayed volume binding allows scheduling constraints and storage topology to be considered together.