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 16

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.

Question 151

Several application replicas restart during traffic peaks with OOMKilled status but their restart count is not monitored. What is the most direct consequence if the underlying problem is left unresolved?

  1. Incorrect attribution may cause wasteful scaling and leave the true issue uncorrected.
  2. Repeated restarts can mask capacity problems and harm user availability.
  3. Tuning the wrong node resource may leave the slow service unchanged.
  4. Performance can degrade even when the host has unused CPU.

Explanation

Correct Answer

B:

Repeated restarts can mask capacity problems and harm user availability. This directly follows from the failed condition. The preventive correction is: Inspect last termination reasons and memory working-set trends, then right-size limits and alerting. The governing Kubernetes behavior is: OOMKilled is evidence of memory-limit or node memory pressure, not an ordinary successful exit.

Incorrect Answers

A:

Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Repeated restarts can mask capacity problems and harm user availability.

C:

Node-wide utilization can hide a throttled or memory-constrained application container. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Repeated restarts can mask capacity problems and harm user availability.

D:

CPU limits may cause throttling independent of overall node idle time. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Repeated restarts can mask capacity problems and harm user availability.

Question 152

A horizontal autoscaler stays at its maximum replica count after load subsides and no one checks its stabilization policy. What is the most direct consequence if the underlying problem is left unresolved?

  1. Insufficient replicas can cause latency and request failures.
  2. Backlogs can grow while autoscaling appears healthy on irrelevant CPU metrics.
  3. Overprovisioning or unstable replica churn can persist without conscious policy.
  4. An unverified rollout may leave production partially updated.

Explanation

Correct Answer

C:

Overprovisioning or unstable replica churn can persist without conscious policy. This directly follows from the failed condition. The preventive correction is: Inspect HPA behavior and scale-down stabilization windows before tuning them for the workload. The governing Kubernetes behavior 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. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Overprovisioning or unstable replica churn can persist without conscious policy.

B:

Different workload bottlenecks require appropriately supported HPA metrics. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Overprovisioning or unstable replica churn can persist without conscious policy.

D:

Desired-state changes are asynchronous and a successful API update is not proof of healthy Pods. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Overprovisioning or unstable replica churn can persist without conscious policy.

Question 153

A memory alert reports high node utilization while the application Pod's working set remains stable and disk cache grows. Following the proposed change—Correlate node memory metrics with Pod usage, cache and eviction conditions before resizing the app—which observation best demonstrates that the particular fault is resolved?

  1. Controlled peak tests show stable replicas without OOMKilled and dashboards show reduced restarts.
  2. The specific bottlenecking Pod is identified and its latency improves after targeted resource changes.
  3. The APIService is Available and kubectl top displays current node and Pod usage.
  4. Per-Pod and node metrics identify the actual source of growth and targeted action resolves pressure.

Explanation

Correct Answer

D:

Per-Pod and node metrics identify the actual source of growth and targeted action resolves pressure. This validates the stated intervention—correlate node memory metrics with Pod usage, cache and eviction conditions before resizing the app.—rather than an unrelated cluster change. The relevant mechanism is: Node memory usage includes multiple consumers and cannot be attributed to one Pod without evidence.

Incorrect Answers

A:

OOMKilled is evidence of memory-limit or node memory pressure, not an ordinary successful exit. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Per-Pod and node metrics identify the actual source of growth and targeted action resolves pressure.

B:

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: Per-Pod and node metrics identify the actual source of growth and targeted action resolves pressure.

C:

kubectl top relies on metrics.k8s.io aggregation and healthy scraper access to node statistics. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Per-Pod and node metrics identify the actual source of growth and targeted action resolves pressure.

Question 154

A team specifies both ingress and egress isolation in a policy but tests only inbound requests before release. An engineer recommends: Test both directions, protocols, and the actual CNI implementation after applying the NetworkPolicy. Which Kubernetes behavior best explains why this correction fits?

  1. An egress-isolated Pod needs an explicit permitted path to each required destination.
  2. Kubernetes accepts policy objects even when a CNI does not implement enforcement.
  3. Ingress and egress restrictions are evaluated independently and policy effects compose additively.
  4. NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation.

Explanation

Correct Answer

C:

Ingress and egress restrictions are evaluated independently and policy effects compose additively. This explains why the proposed action—test both directions, protocols, and the actual CNI implementation after applying the NetworkPolicy.—is appropriate. Direct confirmation is: Unauthorized ingress and egress probes fail while necessary bidirectional flows pass.

Incorrect Answers

A:

An egress-isolated Pod needs an explicit permitted path to each required destination. This does not establish the proposed intervention. The governing principle here is: Ingress and egress restrictions are evaluated independently and policy effects compose additively. Apply it by: Test both directions, protocols, and the actual CNI implementation after applying the NetworkPolicy.

B:

Kubernetes accepts policy objects even when a CNI does not implement enforcement. This does not establish the proposed intervention. The governing principle here is: Ingress and egress restrictions are evaluated independently and policy effects compose additively. Apply it by: Test both directions, protocols, and the actual CNI implementation after applying the NetworkPolicy.

D:

NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation. This does not establish the proposed intervention. The governing principle here is: Ingress and egress restrictions are evaluated independently and policy effects compose additively. Apply it by: Test both directions, protocols, and the actual CNI implementation after applying the NetworkPolicy.

Question 155

A newly initialized control plane displays NotReady nodes and CoreDNS Pods stay Pending before any CNI is installed. Following the proposed change—Install a compatible CNI after successful kubeadm initialization and validate its daemon components—which observation best demonstrates that the particular fault is resolved?

  1. The new control-plane node runs the expected static components and is part of the cluster topology.
  2. Pods receive addresses in the planned range and cross-node communication succeeds after CNI installation.
  3. CNI node agents become healthy and CoreDNS Pods start with working service discovery.
  4. The trusted API certificate chain passes discovery and the new node registers only with the target cluster.

Explanation

Correct Answer

C:

CNI node agents become healthy and CoreDNS Pods start with working service discovery. This validates the stated intervention—install a compatible CNI after successful kubeadm initialization and validate its daemon components.—rather than an unrelated cluster change. The relevant mechanism is: kubeadm bootstraps the control plane but does not provision a complete Pod network plugin by default.

Incorrect Answers

A:

Additional control-plane nodes require appropriate cluster certificates and an established shared control-plane endpoint. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: CNI node agents become healthy and CoreDNS Pods start with working service discovery.

B:

Cluster Pod CIDRs and CNI IPAM assumptions must agree for routable Pod addressing. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: CNI node agents become healthy and CoreDNS Pods start with working service discovery.

D:

kubeadm discovery pins the trust anchor so a worker does not enroll with the wrong control plane. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: CNI node agents become healthy and CoreDNS Pods start with working service discovery.

Question 156

A Pod can contact other Pods by IP but DNS queries time out after CoreDNS replicas were moved. Which Kubernetes administration action most directly addresses the observed failure?

  1. Inspect CoreDNS readiness, Service endpoints and the calling Pod's resolv.conf.
  2. Inspect EndpointSlice ready conditions and repair readiness before declaring the Service operational.
  3. Verify node-local DNS listener addresses and Pod resolv.conf propagation on affected nodes.
  4. Update serviceName and headless DNS records consistently with the StatefulSet network identity.

Explanation

Correct Answer

A:

Inspect CoreDNS readiness, Service endpoints and the calling Pod's resolv.conf. This corrects the specific failure because pod networking can work while the separate cluster DNS service path is unavailable. Verify it by checking: Known Service names resolve and CoreDNS Pods have ready endpoints with successful queries.

Incorrect Answers

B:

Services generally route only to endpoints considered ready, so Pod IP probes do not establish Service capacity. That is relevant to a different intervention. For the stated situation, the required action is: Inspect CoreDNS readiness, Service endpoints and the calling Pod's resolv.conf. The governing reason is: Pod networking can work while the separate cluster DNS service path is unavailable.

C:

Per-node DNS cache configuration can produce node-specific resolution failures. That is relevant to a different intervention. For the stated situation, the required action is: Inspect CoreDNS readiness, Service endpoints and the calling Pod's resolv.conf. The governing reason is: Pod networking can work while the separate cluster DNS service path is unavailable.

D:

StatefulSet per-Pod DNS identity depends on its governing headless Service and stable ordinal names. That is relevant to a different intervention. For the stated situation, the required action is: Inspect CoreDNS readiness, Service endpoints and the calling Pod's resolv.conf. The governing reason is: Pod networking can work while the separate cluster DNS service path is unavailable.

Question 157

A NodePort Service succeeds from one worker but fails from another because a host firewall blocks its allocated port. Following the proposed change—Validate permitted NodePort reachability and node firewall rules across required entry nodes—which observation best demonstrates that the particular fault is resolved?

  1. External probes reach the published port through each intended node address.
  2. A test client connects directly to a Pod IP on another node and network counters show the expected path.
  3. A test client connects over each supported IP family to healthy backends.
  4. The client resolves the current Service record and reaches a ready backend.

Explanation

Correct Answer

A:

External probes reach the published port through each intended node address. This validates the stated intervention—validate permitted NodePort reachability and node firewall rules across required entry nodes.—rather than an unrelated cluster change. The relevant mechanism is: NodePort connectivity depends on node networking and service-proxy dataplane behavior, not just a valid Service object.

Incorrect Answers

B:

Kubernetes expects Pod-to-Pod reachability without application-managed NAT across nodes. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: External probes reach the published port through each intended node address.

C:

Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: External probes reach the published port through each intended node address.

D:

Kubernetes Service DNS gives workloads a stable logical endpoint independent of Pod replacement. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: External probes reach the published port through each intended node address.

Question 158

CoreDNS Pods restart after a ConfigMap edit introducing an invalid Corefile directive. Following the proposed change—Restore a valid Corefile and validate the CoreDNS configuration before rollout—which observation best demonstrates that the particular fault is resolved?

  1. A test Pod resolves the target Service FQDN to its intended ClusterIP.
  2. New Pods on the worker receive the current cluster DNS IP and resolve known Services.
  3. Lookup returns the intended namespace's Service address and an HTTP probe succeeds.
  4. CoreDNS is Ready with clean logs and a test Pod resolves internal and external names.

Explanation

Correct Answer

D:

CoreDNS is Ready with clean logs and a test Pod resolves internal and external names. This validates the stated intervention—restore a valid Corefile and validate the CoreDNS configuration before rollout.—rather than an unrelated cluster change. The relevant mechanism is: CoreDNS must parse its plugin chain before it can serve cluster DNS queries.

Incorrect Answers

A:

Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: CoreDNS is Ready with clean logs and a test Pod resolves internal and external names.

B:

Pod DNS settings may be generated from kubelet node configuration and dnsPolicy. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: CoreDNS is Ready with clean logs and a test Pod resolves internal and external names.

C:

Pod DNS search domains are namespace-relative and short names are not globally unique. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: CoreDNS is Ready with clean logs and a test Pod resolves internal and external names.

Question 159

A cluster uses an internal Service named frontend but an Ingress backend references old-service after a rename. An engineer recommends: Update the Ingress backend service.name and the correct service port reference. Which Kubernetes behavior best explains why this correction fits?

  1. Ingress TLS termination depends on a usable referenced Secret and an active controller.
  2. Ingress API objects do not themselves implement HTTP routing; a controller supplies the dataplane.
  3. Ingress rules point to Services by name and port within their namespace.
  4. HTTP path matching and precedence affect which Service receives a request.

Explanation

Correct Answer

C:

Ingress rules point to Services by name and port within their namespace. This explains why the proposed action—update the Ingress backend service.name and the correct service port reference.—is appropriate. Direct confirmation is: Controller events clear missing-Service errors and the hostname reaches the new backend.

Incorrect Answers

A:

Ingress TLS termination depends on a usable referenced Secret and an active controller. This does not establish the proposed intervention. The governing principle here is: Ingress rules point to Services by name and port within their namespace. Apply it by: Update the Ingress backend service.name and the correct service port reference.

B:

Ingress API objects do not themselves implement HTTP routing; a controller supplies the dataplane. This does not establish the proposed intervention. The governing principle here is: Ingress rules point to Services by name and port within their namespace. Apply it by: Update the Ingress backend service.name and the correct service port reference.

D:

HTTP path matching and precedence affect which Service receives a request. This does not establish the proposed intervention. The governing principle here is: Ingress rules point to Services by name and port within their namespace. Apply it by: Update the Ingress backend service.name and the correct service port reference.

Question 160

Only Pods on one worker cannot resolve names and their resolv.conf points at an obsolete cluster DNS IP. What is the most direct consequence if the underlying problem is left unresolved?

  1. One malformed DNS configuration can disrupt discovery cluster-wide.
  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. Applications may appear network-isolated because they cannot resolve healthy destinations.

Explanation

Correct Answer

C:

DNS failures appear node-specific even when CoreDNS Pods are healthy. This directly follows from the failed condition. The preventive correction is: Correct the kubelet clusterDNS configuration or node DNS distribution and restart affected Pods as needed. The governing Kubernetes behavior is: Pod DNS settings may be generated from kubelet node configuration and dnsPolicy.

Incorrect Answers

A:

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: DNS failures appear node-specific even when CoreDNS Pods are healthy.

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: DNS failures appear node-specific even when CoreDNS Pods are healthy.

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: DNS failures appear node-specific even when CoreDNS Pods are healthy.