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 58

Question 570

A cluster admin enables NodeLocal DNSCache but leaves pods pointing to an inaccessible DNS address. Following the proposed change—Align the node-local cache listen IP and Pod resolver configuration with the deployed cache topology—which observation best demonstrates that the particular fault is resolved?

  1. CoreDNS is Ready with clean logs and a test Pod resolves internal and external names.
  2. New Pods on the worker receive the current cluster DNS IP and resolve known Services.
  3. Queries on affected nodes reach the cache and fall back to upstream CoreDNS appropriately.
  4. Lookup returns the intended namespace's Service address and an HTTP probe succeeds.

Explanation

Correct Answer

C:

Queries on affected nodes reach the cache and fall back to upstream CoreDNS appropriately. This validates the stated intervention—align the node-local cache listen IP and Pod resolver configuration with the deployed cache topology.—rather than an unrelated cluster change. The relevant mechanism is: Node-local DNS caching still requires Pod resolvers to reach the chosen local listener.

Incorrect Answers

A:

CoreDNS must parse its plugin chain before it can serve cluster DNS queries. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Queries on affected nodes reach the cache and fall back to upstream CoreDNS appropriately.

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: Queries on affected nodes reach the cache and fall back to upstream CoreDNS appropriately.

D:

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: Queries on affected nodes reach the cache and fall back to upstream CoreDNS appropriately.

Question 571

A team applies a Custom Resource manifest before its CustomResourceDefinition has been installed and established. Following the proposed change—Install the CRD and wait for its Established condition before applying dependent custom resources—which observation best demonstrates that the particular fault is resolved?

  1. Impersonated edits fail outside the permitted namespace while intended local access remains.
  2. kubectl api-resources lists the new kind and an instance is accepted under the correct group/version.
  3. The operator returns healthy and the managed Deployment appears with the expected owner references.
  4. Existing custom objects are readable and writable through the supported new version after migration.

Explanation

Correct Answer

B:

kubectl api-resources lists the new kind and an instance is accepted under the correct group/version. This validates the stated intervention—install the CRD and wait for its Established condition before applying dependent custom resources.—rather than an unrelated cluster change. The relevant mechanism is: The API server must register an extension type before it can accept objects of that kind.

Incorrect Answers

A:

New custom resource types participate in authorization using their API group and scope. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl api-resources lists the new kind and an instance is accepted under the correct group/version.

C:

A CRD defines the API schema while a running controller implements the desired behavior. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl api-resources lists the new kind and an instance is accepted under the correct group/version.

D:

CRD versioning separates served API versions from the storage version and may require conversion webhooks. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: kubectl api-resources lists the new kind and an instance is accepted under the correct group/version.

Question 572

A newly added control-plane node runs etcd but has not joined the expected quorum member set. Which Kubernetes administration action most directly addresses the observed failure?

  1. Follow the supported etcd snapshot restore topology and consistent member configuration.
  2. Use supported etcd member verification and safely add or reconcile the intended member.
  3. Inspect etcd membership and quorum health, then restore sufficient approved voting members.
  4. Restore the intended component identity and required API authorization rather than granting cluster-admin broadly.

Explanation

Correct Answer

B:

Use supported etcd member verification and safely add or reconcile the intended member. This corrects the specific failure because a running process is not necessarily a healthy voting member of the cluster's configured etcd topology. Verify it by checking: The membership list includes the new peer and quorum health remains good after failure testing.

Incorrect Answers

A:

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

C:

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: Use supported etcd member verification and safely add or reconcile the intended member. The governing reason is: A running process is not necessarily a healthy voting member of the cluster's configured etcd topology.

D:

Control-plane components need functional credentials and narrowly appropriate permissions to reconcile state. That is relevant to a different intervention. For the stated situation, the required action is: Use supported etcd member verification and safely add or reconcile the intended member. The governing reason is: A running process is not necessarily a healthy voting member of the cluster's configured etcd topology.

Question 573

A cluster permits dual-stack networking but a workload assumes every endpoint address is IPv4. Which Kubernetes administration action most directly addresses the observed failure?

  1. Inspect the CNI node agents, routes, and encapsulation between worker Pod CIDRs.
  2. Use a Service DNS name or other stable discovery mechanism instead of a Pod IP.
  3. Validate the Pod and Service IP family policy and ensure clients handle supported IPv4/IPv6 endpoint families.
  4. Use the fully qualified service name or an explicitly namespace-qualified DNS reference.

Explanation

Correct Answer

C:

Validate the Pod and Service IP family policy and ensure clients handle supported IPv4/IPv6 endpoint families. This corrects the specific failure because dual-stack Services and Pods may expose more than one IP family depending on cluster configuration. Verify it by checking: A test client connects over each supported IP family to healthy backends.

Incorrect Answers

A:

Kubernetes expects Pod-to-Pod reachability without application-managed NAT across nodes. That is relevant to a different intervention. For the stated situation, the required action is: Validate the Pod and Service IP family policy and ensure clients handle supported IPv4/IPv6 endpoint families. The governing reason is: Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration.

B:

Pods are replaceable and their IP addresses can change even when the application identity remains. That is relevant to a different intervention. For the stated situation, the required action is: Validate the Pod and Service IP family policy and ensure clients handle supported IPv4/IPv6 endpoint families. The governing reason is: Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration.

D:

Unqualified DNS lookups are affected by search domains in the caller's namespace. That is relevant to a different intervention. For the stated situation, the required action is: Validate the Pod and Service IP family policy and ensure clients handle supported IPv4/IPv6 endpoint families. The governing reason is: Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration.

Question 574

A Pod can resolve internal Services but outbound internet requests hang after a new default-deny egress policy. What is the most direct consequence if the underlying problem is left unresolved?

  1. Application integrations can fail despite healthy in-cluster routing.
  2. A one-sided policy fix may leave traffic denied by the opposite direction.
  3. Incident scope can remain node-specific despite healthy central CoreDNS.
  4. Traffic can become node-dependent and intermittent.

Explanation

Correct Answer

A:

Application integrations can fail despite healthy in-cluster routing. This directly follows from the failed condition. The preventive correction is: Inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS. The governing Kubernetes behavior is: Egress isolation may deny flows independently of Service discovery and Pod health.

Incorrect Answers

B:

Both source egress and destination ingress policies can restrict a cross-namespace flow. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Application integrations can fail despite healthy in-cluster routing.

C:

Per-node DNS cache configuration can produce node-specific resolution failures. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Application integrations can fail despite healthy in-cluster routing.

D:

Service reachability depends on node packet-forwarding rules and network acceptance at entry nodes. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Application integrations can fail despite healthy in-cluster routing.

Question 575

An Ingress resource declares TLS for shop.example.test but its Secret is missing from the Ingress namespace. Following the proposed change—Create the correctly typed TLS Secret in the same namespace and reference it in the Ingress—which observation best demonstrates that the particular fault is resolved?

  1. Controller events clear missing-Service errors and the hostname reaches the new backend.
  2. The controller reconciles the Ingress and an external host/path probe reaches the Service.
  3. The HTTPS listener presents the intended certificate for the host and forwards to the backend.
  4. Approved frontend traffic succeeds while an unrelated test Pod remains denied.

Explanation

Correct Answer

C:

The HTTPS listener presents the intended certificate for the host and forwards to the backend. This validates the stated intervention—create the correctly typed TLS Secret in the same namespace and reference it in the Ingress.—rather than an unrelated cluster change. The relevant mechanism is: Ingress TLS termination depends on a usable referenced Secret and an active controller.

Incorrect Answers

A:

Ingress rules point to Services by name and port within their namespace. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The HTTPS listener presents the intended certificate for the host and forwards to the backend.

B:

Ingress API objects do not themselves implement HTTP routing; a controller supplies the dataplane. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The HTTPS listener presents the intended certificate for the host and forwards to the backend.

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 HTTPS listener presents the intended certificate for the host and forwards to the backend.

Question 576

A controller-manager static Pod crashes after an administrator edits its command flags in place. Following the proposed change—Restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs—which observation best demonstrates that the particular fault is resolved?

  1. The controller-manager stays Running and a Deployment reconciles desired replicas.
  2. The API server static Pod starts and authenticated kubectl requests succeed.
  3. The specific controller resumes writes and unauthorized privileges remain denied.
  4. Local runtime state, kubelet logs and mirror Pod status reconcile after repair.

Explanation

Correct Answer

A:

The controller-manager stays Running and a Deployment reconciles desired replicas. This validates the stated intervention—restore valid flags in the kube-controller-manager manifest and check kubelet recreation logs.—rather than an unrelated cluster change. The relevant mechanism is: The kubelet restarts static control-plane Pods when their manifest changes.

Incorrect Answers

B:

kubeadm control-plane components often run as static Pods from local manifests. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The controller-manager stays Running and a Deployment reconciles desired replicas.

C:

Control-plane components need functional credentials and narrowly appropriate permissions to reconcile state. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The controller-manager stays Running and a Deployment reconciles desired replicas.

D:

Mirror Pods represent static Pods in the API but are not their source of truth on the node. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The controller-manager stays Running and a Deployment reconciles desired replicas.

Question 577

kubectl cannot reach a recently upgraded control plane and the kube-apiserver static Pod is not running. Following the proposed change—Inspect the kubelet-managed static Pod manifest and its container logs, then repair invalid API server flags—which observation best demonstrates that the particular fault is resolved?

  1. The API server static Pod starts and authenticated kubectl requests succeed.
  2. Local runtime state, kubelet logs and mirror Pod status reconcile after repair.
  3. The scheduler becomes healthy and newly created Pods receive node assignments.
  4. Worker kubelet connections and administrator requests succeed using current endpoints.

Explanation

Correct Answer

A:

The API server static Pod starts and authenticated kubectl requests succeed. This validates the stated intervention—inspect the kubelet-managed static Pod manifest and its container logs, then repair invalid API server flags.—rather than an unrelated cluster change. The relevant mechanism is: kubeadm control-plane components often run as static Pods from local manifests.

Incorrect Answers

B:

Mirror Pods represent static Pods in the API but are not their source of truth on the node. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The API server static Pod starts and authenticated kubectl requests succeed.

C:

The scheduler assigns unscheduled Pods to eligible nodes; other control-plane components cannot replace it. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The API server static Pod starts and authenticated kubectl requests succeed.

D:

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: The API server static Pod starts and authenticated kubectl requests succeed.

Question 578

An operations team begins worker maintenance by shutting down a node without cordoning or draining workloads. What is the most direct consequence if the underlying problem is left unresolved?

  1. Forcing eviction can violate the workload's minimum availability.
  2. Effective cluster capacity remains reduced without an obvious node failure.
  3. Upgrade work may stop partway through or leave incompatible components.
  4. Abrupt interruption can break availability guarantees and lose in-flight work.

Explanation

Correct Answer

D:

Abrupt interruption can break availability guarantees and lose in-flight work. This directly follows from the failed condition. The preventive correction is: Cordon and drain the node using disruption-safe options before maintenance, then uncordon after validation. The governing Kubernetes behavior is: A drain evicts eligible Pods through the API and respects disruption policies unlike abrupt host shutdown.

Incorrect Answers

A:

The eviction API respects PodDisruptionBudget limits for voluntary disruption. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Abrupt interruption can break availability guarantees and lose in-flight work.

B:

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: Abrupt interruption can break availability guarantees and lose in-flight work.

C:

kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Abrupt interruption can break availability guarantees and lose in-flight work.

Question 579

A controller installed by an operator enters a reconciliation loop because its ServiceAccount cannot update the custom resource status subresource. An engineer recommends: Grant the controller the minimum required update or patch permission for the status subresource. Which Kubernetes behavior best explains why this correction fits?

  1. Custom resource status updates are separately authorized from spec updates when status is enabled.
  2. A CRD defines the API schema while a running controller implements the desired behavior.
  3. New custom resource types participate in authorization using their API group and scope.
  4. The API server must register an extension type before it can accept objects of that kind.

Explanation

Correct Answer

A:

Custom resource status updates are separately authorized from spec updates when status is enabled. This explains why the proposed action—grant the controller the minimum required update or patch permission for the status subresource.—is appropriate. Direct confirmation is: Controller events show successful status reconciliation without allowing unwanted spec modification.

Incorrect Answers

B:

A CRD defines the API schema while a running controller implements the desired behavior. This does not establish the proposed intervention. The governing principle here is: Custom resource status updates are separately authorized from spec updates when status is enabled. Apply it by: Grant the controller the minimum required update or patch permission for the status subresource.

C:

New custom resource types participate in authorization using their API group and scope. This does not establish the proposed intervention. The governing principle here is: Custom resource status updates are separately authorized from spec updates when status is enabled. Apply it by: Grant the controller the minimum required update or patch permission for the status subresource.

D:

The API server must register an extension type before it can accept objects of that kind. This does not establish the proposed intervention. The governing principle here is: Custom resource status updates are separately authorized from spec updates when status is enabled. Apply it by: Grant the controller the minimum required update or patch permission for the status subresource.

Question 580

A worker pool must scale on queue depth but an engineer configures only a CPU utilization HPA. An engineer recommends: Use a suitable custom or external metrics source and scale target based on backlog with validated adapters. Which Kubernetes behavior best explains why this correction fits?

  1. Different workload bottlenecks require appropriately supported HPA metrics.
  2. HPA CPU utilization calculations depend on resource requests and relevant metrics API data.
  3. CPU percentage targets use utilization relative to requested CPU, not just absolute node usage.
  4. Jobs manage successful completion of finite work; Deployments maintain continuous desired replicas.

Explanation

Correct Answer

A:

Different workload bottlenecks require appropriately supported HPA metrics. This explains why the proposed action—use a suitable custom or external metrics source and scale target based on backlog with validated adapters.—is appropriate. Direct confirmation is: Controlled queue growth drives replica changes even when CPU remains low.

Incorrect Answers

B:

HPA CPU utilization calculations depend on resource requests and relevant metrics API data. This does not establish the proposed intervention. The governing principle here is: Different workload bottlenecks require appropriately supported HPA metrics. Apply it by: Use a suitable custom or external metrics source and scale target based on backlog with validated adapters.

C:

CPU percentage targets use utilization relative to requested CPU, not just absolute node usage. This does not establish the proposed intervention. The governing principle here is: Different workload bottlenecks require appropriately supported HPA metrics. Apply it by: Use a suitable custom or external metrics source and scale target based on backlog with validated adapters.

D:

Jobs manage successful completion of finite work; Deployments maintain continuous desired replicas. This does not establish the proposed intervention. The governing principle here is: Different workload bottlenecks require appropriately supported HPA metrics. Apply it by: Use a suitable custom or external metrics source and scale target based on backlog with validated adapters.