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 50

Question 490

A Pod can resolve internal Services but outbound internet requests hang after a new default-deny egress policy. Which Kubernetes administration action most directly addresses the observed failure?

  1. Check namespace and Pod selectors in ingress/egress NetworkPolicies on both sides of the connection.
  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. Inspect service proxy health, node firewall paths and the installed cluster dataplane implementation.

Explanation

Correct Answer

B:

Inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS. This corrects the specific failure because egress isolation may deny flows independently of Service discovery and Pod health. Verify it by checking: Approved external probes succeed while prohibited destinations remain blocked.

Incorrect Answers

A:

Both source egress and destination ingress policies can restrict a cross-namespace flow. That is relevant to a different intervention. For the stated situation, the required action is: Inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS. The governing reason is: Egress isolation may deny flows independently of Service discovery and Pod health.

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 applicable NetworkPolicies and permit explicitly required external traffic and DNS. The governing reason is: Egress isolation may deny flows independently of Service discovery and Pod health.

D:

Service reachability depends on node packet-forwarding rules and network acceptance at entry nodes. That is relevant to a different intervention. For the stated situation, the required action is: Inspect applicable NetworkPolicies and permit explicitly required external traffic and DNS. The governing reason is: Egress isolation may deny flows independently of Service discovery and Pod health.

Question 491

A rollout is blocked because a PodDisruptionBudget allows no voluntary disruption during the worker drain. Following the proposed change—Inspect the PodDisruptionBudget and safely increase available replicas or adjust policy before retrying drain—which observation best demonstrates that the particular fault is resolved?

  1. Non-DaemonSet workloads relocate and the maintained node accepts Pods only after uncordon.
  2. PDB allowedDisruptions increases and a retried drain succeeds without reducing healthy replicas below policy.
  3. kubectl version and node reports confirm supported version relationships after the planned sequence.
  4. The backup has the expected revision and an isolated restore rehearsal can list known objects.

Explanation

Correct Answer

B:

PDB allowedDisruptions increases and a retried drain succeeds without reducing healthy replicas below policy. This validates the stated intervention—inspect the PodDisruptionBudget and safely increase available replicas or adjust policy before retrying drain.—rather than an unrelated cluster change. The relevant mechanism is: The eviction API respects PodDisruptionBudget limits for voluntary disruption.

Incorrect Answers

A:

A drain evicts eligible Pods through the API and respects disruption policies unlike abrupt host shutdown. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: PDB allowedDisruptions increases and a retried drain succeeds without reducing healthy replicas below policy.

C:

Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: PDB allowedDisruptions increases and a retried drain succeeds without reducing healthy replicas below policy.

D:

Cluster state durability requires more than rerunning kubeadm; an etcd snapshot protects API objects. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: PDB allowedDisruptions increases and a retried drain succeeds without reducing healthy replicas below policy.

Question 492

An HTTPRoute path match is exact but a team expects it to match nested paths under /api. An engineer recommends: Use the intended PathPrefix match semantics and verify path rewriting separately if required. Which Kubernetes behavior best explains why this correction fits?

  1. Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references.
  2. Gateway API constrains route attachment and cross-namespace references through explicit policies.
  3. HTTP path matching and precedence affect which Service receives a request.
  4. Exact and prefix path matches are different routing rules in Gateway API.

Explanation

Correct Answer

D:

Exact and prefix path matches are different routing rules in Gateway API. This explains why the proposed action—use the intended PathPrefix match semantics and verify path rewriting separately if required.—is appropriate. Direct confirmation is: Requests to /api and a child path reach the intended backend while unrelated paths do not.

Incorrect Answers

A:

Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references. This does not establish the proposed intervention. The governing principle here is: Exact and prefix path matches are different routing rules in Gateway API. Apply it by: Use the intended PathPrefix match semantics and verify path rewriting separately if required.

B:

Gateway API constrains route attachment and cross-namespace references through explicit policies. This does not establish the proposed intervention. The governing principle here is: Exact and prefix path matches are different routing rules in Gateway API. Apply it by: Use the intended PathPrefix match semantics and verify path rewriting separately if required.

C:

HTTP path matching and precedence affect which Service receives a request. This does not establish the proposed intervention. The governing principle here is: Exact and prefix path matches are different routing rules in Gateway API. Apply it by: Use the intended PathPrefix match semantics and verify path rewriting separately if required.

Question 493

A release of a payment API introduces an invalid image tag and the Deployment cannot complete its rolling update. An engineer recommends: Use rollout history to identify the last healthy revision and roll back the Deployment to it. Which Kubernetes behavior best explains why this correction fits?

  1. The Deployment rollout strategy controls the allowed temporary excess and unavailable replicas.
  2. Deployment revisions track supported rollout history and a rollback restores a previous Pod template.
  3. Desired-state changes are asynchronous and a successful API update is not proof of healthy Pods.
  4. Jobs manage successful completion of finite work; Deployments maintain continuous desired replicas.

Explanation

Correct Answer

B:

Deployment revisions track supported rollout history and a rollback restores a previous Pod template. This explains why the proposed action—use rollout history to identify the last healthy revision and roll back the Deployment to it.—is appropriate. Direct confirmation is: kubectl rollout status shows the prior revision fully available and application probes succeed.

Incorrect Answers

A:

The Deployment rollout strategy controls the allowed temporary excess and unavailable replicas. This does not establish the proposed intervention. The governing principle here is: Deployment revisions track supported rollout history and a rollback restores a previous Pod template. Apply it by: Use rollout history to identify the last healthy revision and roll back the Deployment to it.

C:

Desired-state changes are asynchronous and a successful API update is not proof of healthy Pods. This does not establish the proposed intervention. The governing principle here is: Deployment revisions track supported rollout history and a rollback restores a previous Pod template. Apply it by: Use rollout history to identify the last healthy revision and roll back the Deployment to it.

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: Deployment revisions track supported rollout history and a rollback restores a previous Pod template. Apply it by: Use rollout history to identify the last healthy revision and roll back the Deployment to it.

Question 494

A policy permits application TCP egress but forgets DNS and Pods cannot resolve Service names. Following the proposed change—Permit DNS traffic to the intended cluster DNS endpoints under the egress policy—which observation best demonstrates that the particular fault is resolved?

  1. The approved API endpoint is reachable and a disallowed destination remains blocked.
  2. The Pod resolves a Service name and reaches it while unrelated outbound access remains denied.
  3. Approved frontend traffic succeeds while an unrelated test Pod remains denied.
  4. A disallowed Pod connection is denied on the network, not merely recorded as a policy object.

Explanation

Correct Answer

B:

The Pod resolves a Service name and reaches it while unrelated outbound access remains denied. This validates the stated intervention—permit DNS traffic to the intended cluster DNS endpoints under the egress policy.—rather than an unrelated cluster change. The relevant mechanism is: DNS name resolution is a separate network flow from the application connection.

Incorrect Answers

A:

An egress-isolated Pod needs an explicit permitted path to each required destination. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The Pod resolves a Service name and reaches it while unrelated outbound access remains denied.

C:

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 Pod resolves a Service name and reaches it while unrelated outbound access remains denied.

D:

Kubernetes accepts policy objects even when a CNI does not implement enforcement. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The Pod resolves a Service name and reaches it while unrelated outbound access remains denied.

Question 495

A hung HTTP worker remains Running but never recovers because only a readiness probe exists. An engineer recommends: Configure a liveness probe that detects a real nonrecovering state with appropriate thresholds. Which Kubernetes behavior best explains why this correction fits?

  1. A failed readiness probe removes Pod endpoints from Services without necessarily restarting the container.
  2. Startup probes suppress other probe evaluation until the startup check succeeds.
  3. Environment variables sourced from Secrets are fixed for the lifetime of a container process.
  4. Liveness failures restart a container; readiness failures alone only affect traffic eligibility.

Explanation

Correct Answer

D:

Liveness failures restart a container; readiness failures alone only affect traffic eligibility. This explains why the proposed action—configure a liveness probe that detects a real nonrecovering state with appropriate thresholds.—is appropriate. Direct confirmation is: A controlled hung-process test triggers a restart and normal traffic returns after readiness.

Incorrect Answers

A:

A failed readiness probe removes Pod endpoints from Services without necessarily restarting the container. This does not establish the proposed intervention. The governing principle here is: Liveness failures restart a container; readiness failures alone only affect traffic eligibility. Apply it by: Configure a liveness probe that detects a real nonrecovering state with appropriate thresholds.

B:

Startup probes suppress other probe evaluation until the startup check succeeds. This does not establish the proposed intervention. The governing principle here is: Liveness failures restart a container; readiness failures alone only affect traffic eligibility. Apply it by: Configure a liveness probe that detects a real nonrecovering state with appropriate thresholds.

C:

Environment variables sourced from Secrets are fixed for the lifetime of a container process. This does not establish the proposed intervention. The governing principle here is: Liveness failures restart a container; readiness failures alone only affect traffic eligibility. Apply it by: Configure a liveness probe that detects a real nonrecovering state with appropriate thresholds.

Question 496

A hung HTTP worker remains Running but never recovers because only a readiness probe exists. Which Kubernetes administration action most directly addresses the observed failure?

  1. Add a readiness probe that becomes successful only when the application can serve requests.
  2. Configure a liveness probe that detects a real nonrecovering state with appropriate thresholds.
  3. Add a startup probe with an adequate startup budget while retaining later liveness and readiness checks.
  4. Run the collector as a DaemonSet with the necessary tolerations and node targeting.

Explanation

Correct Answer

B:

Configure a liveness probe that detects a real nonrecovering state with appropriate thresholds. This corrects the specific failure because liveness failures restart a container; readiness failures alone only affect traffic eligibility. Verify it by checking: A controlled hung-process test triggers a restart and normal traffic returns after readiness.

Incorrect Answers

A:

A failed readiness probe removes Pod endpoints from Services without necessarily restarting the container. That is relevant to a different intervention. For the stated situation, the required action is: Configure a liveness probe that detects a real nonrecovering state with appropriate thresholds. The governing reason is: Liveness failures restart a container; readiness failures alone only affect traffic eligibility.

C:

Startup probes suppress other probe evaluation until the startup check succeeds. That is relevant to a different intervention. For the stated situation, the required action is: Configure a liveness probe that detects a real nonrecovering state with appropriate thresholds. The governing reason is: Liveness failures restart a container; readiness failures alone only affect traffic eligibility.

D:

DaemonSets ensure eligible nodes run a copy of the node-level workload. That is relevant to a different intervention. For the stated situation, the required action is: Configure a liveness probe that detects a real nonrecovering state with appropriate thresholds. The governing reason is: Liveness failures restart a container; readiness failures alone only affect traffic eligibility.

Question 497

A cluster permits dual-stack networking but a workload assumes every endpoint address is IPv4. An engineer recommends: Validate the Pod and Service IP family policy and ensure clients handle supported IPv4/IPv6 endpoint families. Which Kubernetes behavior best explains why this correction fits?

  1. Kubernetes expects Pod-to-Pod reachability without application-managed NAT across nodes.
  2. Pods are replaceable and their IP addresses can change even when the application identity remains.
  3. Kubernetes Service DNS gives workloads a stable logical endpoint independent of Pod replacement.
  4. Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration.

Explanation

Correct Answer

D:

Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration. This explains why the proposed action—validate the Pod and Service IP family policy and ensure clients handle supported IPv4/IPv6 endpoint families.—is appropriate. Direct confirmation is: 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. This does not establish the proposed intervention. The governing principle here is: Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration. Apply it by: Validate the Pod and Service IP family policy and ensure clients handle supported IPv4/IPv6 endpoint families.

B:

Pods are replaceable and their IP addresses can change even when the application identity remains. This does not establish the proposed intervention. The governing principle here is: Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration. Apply it by: Validate the Pod and Service IP family policy and ensure clients handle supported IPv4/IPv6 endpoint families.

C:

Kubernetes Service DNS gives workloads a stable logical endpoint independent of Pod replacement. This does not establish the proposed intervention. The governing principle here is: Dual-stack Services and Pods may expose more than one IP family depending on cluster configuration. Apply it by: Validate the Pod and Service IP family policy and ensure clients handle supported IPv4/IPv6 endpoint families.

Question 498

An automation script tries to join a node using a CA hash copied from a different Kubernetes cluster. Following the proposed change—Regenerate the token-based join command with the expected cluster CA public-key hash—which observation best demonstrates that the particular fault is resolved?

  1. The worker joins using a current token and is visible with the intended node identity.
  2. The new control-plane node runs the expected static components and is part of the cluster topology.
  3. The host has no stale static Pod manifests and the new cluster initializes without port conflicts.
  4. The trusted API certificate chain passes discovery and the new node registers only with the target cluster.

Explanation

Correct Answer

D:

The trusted API certificate chain passes discovery and the new node registers only with the target cluster. This validates the stated intervention—regenerate the token-based join command with the expected cluster CA public-key hash.—rather than an unrelated cluster change. The relevant mechanism is: kubeadm discovery pins the trust anchor so a worker does not enroll with the wrong control plane.

Incorrect Answers

A:

Bootstrap tokens have limited lifetimes and support authenticated discovery during node enrollment. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The trusted API certificate chain passes discovery and the new node registers only with the target cluster.

B:

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: The trusted API certificate chain passes discovery and the new node registers only with the target cluster.

C:

Resetting kubeadm state and deleting external CNI or persistent etcd artifacts are separate actions requiring care. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The trusted API certificate chain passes discovery and the new node registers only with the target cluster.

Question 499

New Pods remain Pending across the cluster because the kube-scheduler static Pod is in CrashLoopBackOff. Which Kubernetes administration action most directly addresses the observed failure?

  1. Repair the scheduler manifest or configuration after inspecting static Pod logs.
  2. Inspect the kubelet-managed static Pod manifest and its container logs, then repair invalid API server flags.
  3. Inspect actual local runtime containers and static manifest files as well as API mirror objects.
  4. Restore the intended component identity and required API authorization rather than granting cluster-admin broadly.

Explanation

Correct Answer

A:

Repair the scheduler manifest or configuration after inspecting static Pod logs. This corrects the specific failure because the scheduler assigns unscheduled Pods to eligible nodes; other control-plane components cannot replace it. Verify it by checking: The scheduler becomes healthy and newly created Pods receive node assignments.

Incorrect Answers

B:

kubeadm control-plane components often run as static Pods from local manifests. That is relevant to a different intervention. For the stated situation, the required action is: Repair the scheduler manifest or configuration after inspecting static Pod logs. The governing reason is: The scheduler assigns unscheduled Pods to eligible nodes; other control-plane components cannot replace it.

C:

Mirror Pods represent static Pods in the API but are not their source of truth on the node. That is relevant to a different intervention. For the stated situation, the required action is: Repair the scheduler manifest or configuration after inspecting static Pod logs. The governing reason is: The scheduler assigns unscheduled Pods to eligible nodes; other control-plane components cannot replace it.

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: Repair the scheduler manifest or configuration after inspecting static Pod logs. The governing reason is: The scheduler assigns unscheduled Pods to eligible nodes; other control-plane components cannot replace it.

Question 500

A Helm-managed monitoring release is modified by editing its generated Deployment directly in the cluster. An engineer recommends: Change the values or chart sources and run an approved Helm upgrade to preserve release state. Which Kubernetes behavior best explains why this correction fits?

  1. Helm's release history and desired manifests should remain the authoritative source for chart-managed resources.
  2. Template rendering plus a values diff exposes chart-side effects before they affect cluster resources.
  3. Helm tracks release objects, while some custom resources and cluster-scoped artifacts can outlive a namespace.
  4. Bases compose reusable manifests while overlays encode environment-specific differences.

Explanation

Correct Answer

A:

Helm's release history and desired manifests should remain the authoritative source for chart-managed resources. This explains why the proposed action—change the values or chart sources and run an approved Helm upgrade to preserve release state.—is appropriate. Direct confirmation is: helm get values and rendered manifests show the change, which survives the next upgrade.

Incorrect Answers

B:

Template rendering plus a values diff exposes chart-side effects before they affect cluster resources. This does not establish the proposed intervention. The governing principle here is: Helm's release history and desired manifests should remain the authoritative source for chart-managed resources. Apply it by: Change the values or chart sources and run an approved Helm upgrade to preserve release state.

C:

Helm tracks release objects, while some custom resources and cluster-scoped artifacts can outlive a namespace. This does not establish the proposed intervention. The governing principle here is: Helm's release history and desired manifests should remain the authoritative source for chart-managed resources. Apply it by: Change the values or chart sources and run an approved Helm upgrade to preserve release state.

D:

Bases compose reusable manifests while overlays encode environment-specific differences. This does not establish the proposed intervention. The governing principle here is: Helm's release history and desired manifests should remain the authoritative source for chart-managed resources. Apply it by: Change the values or chart sources and run an approved Helm upgrade to preserve release state.