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 60

Question 590

A NodeLocal DNSCache daemon runs but DNS failures happen only on nodes with a stale link-local resolver entry. 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 applicable NetworkPolicies and permit explicitly required external traffic and DNS.
  3. Verify node-local DNS listener addresses and Pod resolv.conf propagation on affected nodes.
  4. Compare Service selectors, ready EndpointSlices and actual container listener ports.

Explanation

Correct Answer

C:

Verify node-local DNS listener addresses and Pod resolv.conf propagation on affected nodes. This corrects the specific failure because per-node DNS cache configuration can produce node-specific resolution failures. Verify it by checking: Fresh Pods on previously broken nodes resolve internal and external names through the configured listener.

Incorrect Answers

A:

Pod networking can work while the separate cluster DNS service path is unavailable. That is relevant to a different intervention. For the stated situation, the required action is: Verify node-local DNS listener addresses and Pod resolv.conf propagation on affected nodes. The governing reason is: Per-node DNS cache configuration can produce node-specific resolution failures.

B:

Egress isolation may deny flows independently of Service discovery and Pod health. That is relevant to a different intervention. For the stated situation, the required action is: Verify node-local DNS listener addresses and Pod resolv.conf propagation on affected nodes. The governing reason is: Per-node DNS cache configuration can produce node-specific resolution failures.

D:

DNS resolution and a Service object do not guarantee a valid ready backend endpoint. That is relevant to a different intervention. For the stated situation, the required action is: Verify node-local DNS listener addresses and Pod resolv.conf propagation on affected nodes. The governing reason is: Per-node DNS cache configuration can produce node-specific resolution failures.

Question 591

A Pod cannot land on one node even after resource capacity is added because the node has an unexpected NoSchedule taint. Following the proposed change—Inspect taints and remove the unintended taint or use narrowly authorized tolerations—which observation best demonstrates that the particular fault is resolved?

  1. A permitted workload schedules after the taint policy is corrected without relaxing other nodes.
  2. Node DiskPressure clears and new Pods are admitted without deleting active volume data.
  3. The relevant Pods schedule onto approved labeled nodes and node inventory matches policy.
  4. The workload completes under tested memory bounds and node pressure clears.

Explanation

Correct Answer

A:

A permitted workload schedules after the taint policy is corrected without relaxing other nodes. This validates the stated intervention—inspect taints and remove the unintended taint or use narrowly authorized tolerations.—rather than an unrelated cluster change. The relevant mechanism is: Scheduler taints are placement constraints distinct from raw allocatable capacity.

Incorrect Answers

B:

Kubelet disk-pressure signals can cause eviction and scheduling taints independent of CPU utilization. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A permitted workload schedules after the taint policy is corrected without relaxing other nodes.

C:

Hard placement rules require actual matching node labels at scheduling time. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A permitted workload schedules after the taint policy is corrected without relaxing other nodes.

D:

The kernel and kubelet can terminate memory-hungry containers independently of scheduler requests. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A permitted workload schedules after the taint policy is corrected without relaxing other nodes.

Question 592

A team adds an HPA to a Deployment whose Pods lack CPU requests, producing unknown CPU utilization. Which Kubernetes administration action most directly addresses the observed failure?

  1. Create a CPU-based HPA with matching resource requests and confirm metrics availability.
  2. Set defensible CPU requests and confirm metrics-server data before relying on percentage-based HPA.
  3. Use a suitable custom or external metrics source and scale target based on backlog with validated adapters.
  4. Increase the HPA target utilization while leaving CPU resource requests undefined.

Explanation

Correct Answer

B:

Set defensible CPU requests and confirm metrics-server data before relying on percentage-based HPA. This corrects the specific failure because cPU percentage targets use utilization relative to requested CPU, not just absolute node usage. Verify it by checking: The HPA stops reporting unknown metrics and scales within configured bounds.

Incorrect Answers

A:

HPA CPU utilization calculations depend on resource requests and relevant metrics API data. That is relevant to a different intervention. For the stated situation, the required action is: Set defensible CPU requests and confirm metrics-server data before relying on percentage-based HPA. The governing reason is: CPU percentage targets use utilization relative to requested CPU, not just absolute node usage.

C:

Different workload bottlenecks require appropriately supported HPA metrics. That is relevant to a different intervention. For the stated situation, the required action is: Set defensible CPU requests and confirm metrics-server data before relying on percentage-based HPA. The governing reason is: CPU percentage targets use utilization relative to requested CPU, not just absolute node usage.

D:

Changing the percentage target does not supply the Pod CPU requests needed for utilization calculations. Correct the resource requests and verify the metrics API instead.

Question 593

An operator changes the default StorageClass during a migration and discovers new PVCs use the wrong backend. 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. Use WaitForFirstConsumer binding for topology-constrained storage where supported.
  3. Define the correct CSI StorageClass parameters and verify the provisioned volume security properties.
  4. Use a compatible StorageClass that allows expansion and follow the driver-supported resize workflow.

Explanation

Correct Answer

A:

Set exactly the intended default class annotation and specify storageClassName explicitly for critical claims. This corrects the specific failure because pVCs without a specified class can inherit the cluster's default storage class. Verify it by checking: A test unqualified PVC picks the expected class and critical manifests remain explicit.

Incorrect Answers

B:

Delayed volume binding allows scheduling constraints and storage topology to be considered together. That is relevant to a different intervention. For the stated situation, the required action is: Set exactly the intended default class annotation and specify storageClassName explicitly for critical claims. The governing reason is: PVCs without a specified class can inherit the cluster's default storage class.

C:

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: Set exactly the intended default class annotation and specify storageClassName explicitly for critical claims. The governing reason is: PVCs without a specified class can inherit the cluster's default storage class.

D:

PVC size expansion depends on both StorageClass permission and storage-driver capabilities. That is relevant to a different intervention. For the stated situation, the required action is: Set exactly the intended default class annotation and specify storageClassName explicitly for critical claims. The governing reason is: PVCs without a specified class can inherit the cluster's default storage class.

Question 594

A Service forwards port 80 to an application listening on container port 8080, but targetPort was set to 8081. Which Kubernetes administration action most directly addresses the observed failure?

  1. Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required.
  2. Set the Service targetPort to the actual listener port or correctly named container port.
  3. Document and use headless DNS/endpoint discovery for per-Pod identities instead of VIP load balancing.
  4. Create and maintain appropriate EndpointSlice resources with correct labels and target addresses.

Explanation

Correct Answer

B:

Set the Service targetPort to the actual listener port or correctly named container port. This corrects the specific failure because service port and targetPort describe different ends of the virtual forwarding path. Verify it by checking: A request to Service port 80 reaches the Pod's 8080 listener.

Incorrect Answers

A:

NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. That is relevant to a different intervention. For the stated situation, the required action is: Set the Service targetPort to the actual listener port or correctly named container port. The governing reason is: Service port and targetPort describe different ends of the virtual forwarding path.

C:

A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. That is relevant to a different intervention. For the stated situation, the required action is: Set the Service targetPort to the actual listener port or correctly named container port. The governing reason is: Service port and targetPort describe different ends of the virtual forwarding path.

D:

Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. That is relevant to a different intervention. For the stated situation, the required action is: Set the Service targetPort to the actual listener port or correctly named container port. The governing reason is: Service port and targetPort describe different ends of the virtual forwarding path.

Question 595

A database Pod keeps landing on the same node as another replica despite the service's resilience goal. 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. Add narrowly scoped matching tolerations and appropriate node placement constraints to the authorized Pods.
  4. Use appropriate podAntiAffinity or topology spread constraints for the intended failure domains.

Explanation

Correct Answer

D:

Use appropriate podAntiAffinity or topology spread constraints for the intended failure domains. This corrects the specific failure because affinity and spread rules influence placement of replicas across nodes or zones. Verify it by checking: The replicas appear across the required topology domains after a controlled reschedule.

Incorrect Answers

A:

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: Use appropriate podAntiAffinity or topology spread constraints for the intended failure domains. The governing reason is: Affinity and spread rules influence placement of replicas across nodes or zones.

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: Use appropriate podAntiAffinity or topology spread constraints for the intended failure domains. The governing reason is: Affinity and spread rules influence placement of replicas across nodes or zones.

C:

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: Use appropriate podAntiAffinity or topology spread constraints for the intended failure domains. The governing reason is: Affinity and spread rules influence placement of replicas across nodes or zones.

Question 596

Pods can resolve external domains but fail to resolve the names of ClusterIP Services in their namespace. 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. An unnecessary public endpoint can expose a sensitive internal database.

Explanation

Correct Answer

B:

Cluster-internal discovery can break while public DNS continues to work. This directly follows from the failed condition. The preventive correction is: Inspect CoreDNS Kubernetes plugin configuration and its access to the cluster API and service domain. The governing Kubernetes behavior is: Cluster-local DNS records depend on CoreDNS observing Service and EndpointSlice resources.

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: Cluster-internal discovery can break while public DNS continues to work.

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: Cluster-internal discovery can break while public DNS continues to work.

D:

ClusterIP is intended for internal service discovery; LoadBalancer requests external integration where supported. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Cluster-internal discovery can break while public DNS continues to work.

Question 597

After restoring an etcd snapshot, an engineer starts two inconsistent members with mismatched cluster identifiers. Which Kubernetes administration action most directly addresses the observed failure?

  1. Use supported etcd member verification and safely add or reconcile the intended member.
  2. Inspect etcd membership and quorum health, then restore sufficient approved voting members.
  3. Follow the supported etcd snapshot restore topology and consistent member configuration.
  4. Correct the supported advertise-address and stable endpoint configuration with matching certificates.

Explanation

Correct Answer

C:

Follow the supported etcd snapshot restore topology and consistent member configuration. This corrects the specific failure because restored etcd members must agree on cluster identity and membership rather than mix prior data directories. Verify it by checking: Members form a healthy quorum and expected Kubernetes objects are visible before traffic is restored.

Incorrect Answers

A:

A running process is not necessarily a healthy voting member of the cluster's configured etcd topology. That is relevant to a different intervention. For the stated situation, the required action is: Follow the supported etcd snapshot restore topology and consistent member configuration. The governing reason is: Restored etcd members must agree on cluster identity and membership rather than mix prior data directories.

B:

Etcd requires a majority of voters to commit changes; an API listener alone does not imply healthy storage. That is relevant to a different intervention. For the stated situation, the required action is: Follow the supported etcd snapshot restore topology and consistent member configuration. The governing reason is: Restored etcd members must agree on cluster identity and membership rather than mix prior data directories.

D:

Control-plane advertised addresses must be reachable through the cluster's intended topology. That is relevant to a different intervention. For the stated situation, the required action is: Follow the supported etcd snapshot restore topology and consistent member configuration. The governing reason is: Restored etcd members must agree on cluster identity and membership rather than mix prior data directories.

Question 598

A policy intended to permit only Pods labeled app=web selects the backend itself rather than the source peers. An engineer recommends: Separate the policy podSelector target from ingress from.podSelector peer matching. Which Kubernetes behavior best explains why this correction fits?

  1. An empty namespaceSelector matches all namespaces; namespace and Pod peers must be scoped deliberately.
  2. NetworkPolicies are additive for selected Pods; allow rules define permitted flows after isolation.
  3. DNS name resolution is a separate network flow from the application connection.
  4. A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources.

Explanation

Correct Answer

D:

A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. This explains why the proposed action—separate the policy podSelector target from ingress from.podSelector peer matching.—is appropriate. Direct confirmation is: Only the intended web client can connect to the protected backend.

Incorrect Answers

A:

An empty namespaceSelector matches all namespaces; namespace and Pod peers must be scoped deliberately. This does not establish the proposed intervention. The governing principle here is: A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. Apply it by: Separate the policy podSelector target from ingress from.podSelector peer matching.

B:

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: A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. Apply it by: Separate the policy podSelector target from ingress from.podSelector peer matching.

C:

DNS name resolution is a separate network flow from the application connection. This does not establish the proposed intervention. The governing principle here is: A NetworkPolicy's top-level podSelector selects protected Pods; ingress peers identify allowed sources. Apply it by: Separate the policy podSelector target from ingress from.podSelector peer matching.

Question 599

A NodePort Service is accessible through worker addresses but an operator expects it to create a cloud load balancer automatically. An engineer recommends: Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required. Which Kubernetes behavior best explains why this correction fits?

  1. NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning.
  2. ClusterIP is intended for internal service discovery; LoadBalancer requests external integration where supported.
  3. Selectorless Services require explicitly associated endpoints because no controller infers backing Pods.
  4. A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target.

Explanation

Correct Answer

A:

NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. This explains why the proposed action—use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required.—is appropriate. Direct confirmation is: The Service receives the expected load balancer ingress and end-to-end external probes succeed.

Incorrect Answers

B:

ClusterIP is intended for internal service discovery; LoadBalancer requests external integration where supported. This does not establish the proposed intervention. The governing principle here is: NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. Apply it by: Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required.

C:

Selectorless Services require explicitly associated endpoints because no controller infers backing Pods. This does not establish the proposed intervention. The governing principle here is: NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. Apply it by: Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required.

D:

A headless Service (clusterIP None) publishes endpoint records rather than a normal ClusterIP proxy target. This does not establish the proposed intervention. The governing principle here is: NodePort exposes a port on nodes, while LoadBalancer depends on provider or local controller provisioning. Apply it by: Use a LoadBalancer Service with the installed infrastructure integration when a managed external frontend is required.

Question 600

A web application must update one Pod at a time while retaining capacity during a routine release. Following the proposed change—Configure rolling-update maxUnavailable and maxSurge according to available capacity and readiness requirements—which observation best demonstrates that the particular fault is resolved?

  1. kubectl rollout status shows the prior revision fully available and application probes succeed.
  2. The desired replica count is ready under the new image and old ReplicaSet replicas are reduced.
  3. During a controlled rollout, the configured availability floor is maintained while new Pods become Ready.
  4. New Pods use the updated Secret value and old processes terminate in a controlled rollout.

Explanation

Correct Answer

C:

During a controlled rollout, the configured availability floor is maintained while new Pods become Ready. This validates the stated intervention—configure rolling-update maxUnavailable and maxSurge according to available capacity and readiness requirements.—rather than an unrelated cluster change. The relevant mechanism is: The Deployment rollout strategy controls the allowed temporary excess and unavailable replicas.

Incorrect Answers

A:

Deployment revisions track supported rollout history and a rollback restores a previous Pod template. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: During a controlled rollout, the configured availability floor is maintained while new Pods become Ready.

B:

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: During a controlled rollout, the configured availability floor is maintained while new Pods become Ready.

D:

Environment variables sourced from Secrets are fixed for the lifetime of a container process. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: During a controlled rollout, the configured availability floor is maintained while new Pods become Ready.