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 2

Question 10

An HTTPRoute path match is exact but a team expects it to match nested paths under /api. Following the proposed change—Use the intended PathPrefix match semantics and verify path rewriting separately if required—which observation best demonstrates that the particular fault is resolved?

  1. Requests to /api and a child path reach the intended backend while unrelated paths do not.
  2. HTTPRoute status reports Accepted and traffic matches its intended listener.
  3. The intended route becomes Accepted only from an approved namespace.
  4. Gateway conditions become Programmed/Accepted and the assigned address receives requests.

Explanation

Correct Answer

A:

Requests to /api and a child path reach the intended backend while unrelated paths do not. This validates the stated intervention—use the intended PathPrefix match semantics and verify path rewriting separately if required.—rather than an unrelated cluster change. The relevant mechanism is: Exact and prefix path matches are different routing rules in Gateway API.

Incorrect Answers

B:

Gateway API HTTPRoutes must attach to compatible allowed listeners through parent references. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Requests to /api and a child path reach the intended backend while unrelated paths do not.

C:

Gateway API constrains route attachment and cross-namespace references through explicit policies. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Requests to /api and a child path reach the intended backend while unrelated paths do not.

D:

Gateway API resources require an implementing controller to provision and program data-plane listeners. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Requests to /api and a child path reach the intended backend while unrelated paths do not.

Question 11

A worker's kubeadm join attempt reports an expired bootstrap token obtained from an old onboarding note. An engineer recommends: Generate an appropriate short-lived join token and refreshed discovery command from the current control plane. Which Kubernetes behavior best explains why this correction fits?

  1. kubeadm discovery pins the trust anchor so a worker does not enroll with the wrong control plane.
  2. Additional control-plane nodes require appropriate cluster certificates and an established shared control-plane endpoint.
  3. kubeadm bootstraps the control plane but does not provision a complete Pod network plugin by default.
  4. Bootstrap tokens have limited lifetimes and support authenticated discovery during node enrollment.

Explanation

Correct Answer

D:

Bootstrap tokens have limited lifetimes and support authenticated discovery during node enrollment. This explains why the proposed action—generate an appropriate short-lived join token and refreshed discovery command from the current control plane.—is appropriate. Direct confirmation is: The worker joins using a current token and is visible with the intended node identity.

Incorrect Answers

A:

kubeadm discovery pins the trust anchor so a worker does not enroll with the wrong control plane. This does not establish the proposed intervention. The governing principle here is: Bootstrap tokens have limited lifetimes and support authenticated discovery during node enrollment. Apply it by: Generate an appropriate short-lived join token and refreshed discovery command from the current control plane.

B:

Additional control-plane nodes require appropriate cluster certificates and an established shared control-plane endpoint. This does not establish the proposed intervention. The governing principle here is: Bootstrap tokens have limited lifetimes and support authenticated discovery during node enrollment. Apply it by: Generate an appropriate short-lived join token and refreshed discovery command from the current control plane.

C:

kubeadm bootstraps the control plane but does not provision a complete Pod network plugin by default. This does not establish the proposed intervention. The governing principle here is: Bootstrap tokens have limited lifetimes and support authenticated discovery during node enrollment. Apply it by: Generate an appropriate short-lived join token and refreshed discovery command from the current control plane.

Question 12

A Service resolves to a ClusterIP but curl returns connection refused after a Deployment label change. An engineer recommends: Compare Service selectors, ready EndpointSlices and actual container listener ports. Which Kubernetes behavior best explains why this correction fits?

  1. Pod networking can work while the separate cluster DNS service path is unavailable.
  2. DNS resolution and a Service object do not guarantee a valid ready backend endpoint.
  3. Per-node DNS cache configuration can produce node-specific resolution failures.
  4. Ingress routing adds a separate HTTP match layer beyond normal Service reachability.

Explanation

Correct Answer

B:

DNS resolution and a Service object do not guarantee a valid ready backend endpoint. This explains why the proposed action—compare Service selectors, ready EndpointSlices and actual container listener ports.—is appropriate. Direct confirmation is: EndpointSlices list ready Pods and a port-specific request succeeds after selector repair.

Incorrect Answers

A:

Pod networking can work while the separate cluster DNS service path is unavailable. This does not establish the proposed intervention. The governing principle here is: DNS resolution and a Service object do not guarantee a valid ready backend endpoint. Apply it by: Compare Service selectors, ready EndpointSlices and actual container listener ports.

C:

Per-node DNS cache configuration can produce node-specific resolution failures. This does not establish the proposed intervention. The governing principle here is: DNS resolution and a Service object do not guarantee a valid ready backend endpoint. Apply it by: Compare Service selectors, ready EndpointSlices and actual container listener ports.

D:

Ingress routing adds a separate HTTP match layer beyond normal Service reachability. This does not establish the proposed intervention. The governing principle here is: DNS resolution and a Service object do not guarantee a valid ready backend endpoint. Apply it by: Compare Service selectors, ready EndpointSlices and actual container listener ports.

Question 13

An outbound connection fails only for large requests after a change in CNI overlay encapsulation. Following the proposed change—Test path MTU and align overlay network settings with physical link limits—which observation best demonstrates that the particular fault is resolved?

  1. Both small and large test payloads traverse the affected route successfully.
  2. Approved external probes succeed while prohibited destinations remain blocked.
  3. The expected number of ready endpoints is present and Service load tests distribute successfully.
  4. The route becomes Accepted and requests to the matching host/path receive a valid backend response.

Explanation

Correct Answer

A:

Both small and large test payloads traverse the affected route successfully. This validates the stated intervention—test path MTU and align overlay network settings with physical link limits.—rather than an unrelated cluster change. The relevant mechanism is: Packet encapsulation overhead can create fragmented or dropped large packets while small probes pass.

Incorrect Answers

B:

Egress isolation may deny flows independently of Service discovery and Pod health. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Both small and large test payloads traverse the affected route successfully.

C:

Services generally route only to endpoints considered ready, so Pod IP probes do not establish Service capacity. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Both small and large test payloads traverse the affected route successfully.

D:

Gateway API status conditions identify attachment or match failures separate from backend Pod readiness. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Both small and large test payloads traverse the affected route successfully.

Question 14

A cluster service intermittently returns 500 errors but logs are split across multiple replicas with unsynchronized timestamps. Following the proposed change—Collect timestamped logs from the selected workload replicas and correlate by request identifier—which observation best demonstrates that the particular fault is resolved?

  1. A controlled failure appears in retrieved logs with sufficient timestamps and context.
  2. Logs from the failing sidecar reveal the error while the app container's normal output is distinguished.
  3. A failing request can be traced end-to-end through the expected replica logs.
  4. The captured output contains the incident window with reproducible source metadata.

Explanation

Correct Answer

C:

A failing request can be traced end-to-end through the expected replica logs. This validates the stated intervention—collect timestamped logs from the selected workload replicas and correlate by request identifier.—rather than an unrelated cluster change. The relevant mechanism is: Distributed troubleshooting needs consistent time context to distinguish one request across Pods.

Incorrect Answers

A:

kubectl logs primarily reads the container runtime's captured stdout and stderr streams. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A failing request can be traced end-to-end through the expected replica logs.

B:

Container logs belong to individual containers even within one Pod. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A failing request can be traced end-to-end through the expected replica logs.

D:

kubectl log filters help isolate relevant events and reduce diagnostic noise. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A failing request can be traced end-to-end through the expected replica logs.

Question 15

An administrator upgrades worker kubelets before evaluating the supported kubeadm control-plane version sequence. An engineer recommends: Follow Kubernetes version-skew rules and upgrade the control plane and workers in the supported order. Which Kubernetes behavior best explains why this correction fits?

  1. Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server.
  2. Cluster state durability requires more than rerunning kubeadm; an etcd snapshot protects API objects.
  3. kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command.
  4. Cordon status prevents new scheduling even when the node is otherwise Ready.

Explanation

Correct Answer

A:

Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. This explains why the proposed action—follow Kubernetes version-skew rules and upgrade the control plane and workers in the supported order.—is appropriate. Direct confirmation is: kubectl version and node reports confirm supported version relationships after the planned sequence.

Incorrect Answers

B:

Cluster state durability requires more than rerunning kubeadm; an etcd snapshot protects API objects. This does not establish the proposed intervention. The governing principle here is: Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. Apply it by: Follow Kubernetes version-skew rules and upgrade the control plane and workers in the supported order.

C:

kubeadm upgrade plan surfaces supported upgrade paths and potential blockers, not just an install command. This does not establish the proposed intervention. The governing principle here is: Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. Apply it by: Follow Kubernetes version-skew rules and upgrade the control plane and workers in the supported order.

D:

Cordon status prevents new scheduling even when the node is otherwise Ready. This does not establish the proposed intervention. The governing principle here is: Component version skew is constrained; a newer kubelet must not be assumed compatible with an older API server. Apply it by: Follow Kubernetes version-skew rules and upgrade the control plane and workers in the supported order.

Question 16

An application writes errors exclusively to a file inside its container rather than stdout/stderr, so kubectl logs is empty. Following the proposed change—Configure the app or log collector to expose relevant output streams and preserve needed files—which observation best demonstrates that the particular fault is resolved?

  1. kubectl logs --previous surfaces the original failure and event timestamps align.
  2. The exact Pending or waiting reason is found and the first successful start produces log output.
  3. The captured output contains the incident window with reproducible source metadata.
  4. A controlled failure appears in retrieved logs with sufficient timestamps and context.

Explanation

Correct Answer

D:

A controlled failure appears in retrieved logs with sufficient timestamps and context. This validates the stated intervention—configure the app or log collector to expose relevant output streams and preserve needed files.—rather than an unrelated cluster change. The relevant mechanism is: kubectl logs primarily reads the container runtime's captured stdout and stderr streams.

Incorrect Answers

A:

Restarted containers can have a previous log stream that is distinct from the current one. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A controlled failure appears in retrieved logs with sufficient timestamps and context.

B:

Containers that never start may have no runtime logs; scheduling and image events carry the relevant diagnosis. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A controlled failure appears in retrieved logs with sufficient timestamps and context.

C:

kubectl log filters help isolate relevant events and reduce diagnostic noise. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A controlled failure appears in retrieved logs with sufficient timestamps and context.

Question 17

A cluster uses an internal Service named frontend but an Ingress backend references old-service after a rename. Which Kubernetes administration action most directly addresses the observed failure?

  1. Create the correctly typed TLS Secret in the same namespace and reference it in the Ingress.
  2. Install and select a supported Ingress controller, then test its address and routing status.
  3. Update the Ingress backend service.name and the correct service port reference.
  4. Align ingressClassName with the intended controller or deploy the requested internal class.

Explanation

Correct Answer

C:

Update the Ingress backend service.name and the correct service port reference. This corrects the specific failure because ingress rules point to Services by name and port within their namespace. Verify it by checking: 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. That is relevant to a different intervention. For the stated situation, the required action is: Update the Ingress backend service.name and the correct service port reference. The governing reason is: Ingress rules point to Services by name and port within their namespace.

B:

Ingress API objects do not themselves implement HTTP routing; a controller supplies the dataplane. That is relevant to a different intervention. For the stated situation, the required action is: Update the Ingress backend service.name and the correct service port reference. The governing reason is: Ingress rules point to Services by name and port within their namespace.

D:

Ingress controllers commonly filter resources by configured IngressClass. That is relevant to a different intervention. For the stated situation, the required action is: Update the Ingress backend service.name and the correct service port reference. The governing reason is: Ingress rules point to Services by name and port within their namespace.

Question 18

CoreDNS Pods restart after a ConfigMap edit introducing an invalid Corefile directive. What is the most direct consequence if the underlying problem is left unresolved?

  1. Cluster-internal discovery can break while public DNS continues to work.
  2. DNS failures appear node-specific even when CoreDNS Pods are healthy.
  3. DNS queries may time out despite healthy central DNS replicas.
  4. One malformed DNS configuration can disrupt discovery cluster-wide.

Explanation

Correct Answer

D:

One malformed DNS configuration can disrupt discovery cluster-wide. This directly follows from the failed condition. The preventive correction is: Restore a valid Corefile and validate the CoreDNS configuration before rollout. The governing Kubernetes behavior 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. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: One malformed DNS configuration can disrupt discovery cluster-wide.

B:

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: One malformed DNS configuration can disrupt discovery cluster-wide.

C:

Node-local DNS caching still requires Pod resolvers to reach the chosen local listener. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: One malformed DNS configuration can disrupt discovery cluster-wide.

Question 19

A Pod uses a required key named DB_USER but the referenced Secret only contains username, causing startup failure. An engineer recommends: Align the Secret key name and the Pod's secretKeyRef with the application contract. Which Kubernetes behavior best explains why this correction fits?

  1. Secret key references are exact and missing mandatory keys prevent valid container configuration.
  2. Environment variables sourced from Secrets are fixed for the lifetime of a container process.
  3. Secrets are intended for sensitive values but still require RBAC and protection at rest and in use.
  4. ConfigMaps separate nonsecret configuration from the application container image.

Explanation

Correct Answer

A:

Secret key references are exact and missing mandatory keys prevent valid container configuration. This explains why the proposed action—align the Secret key name and the Pod's secretKeyRef with the application contract.—is appropriate. Direct confirmation is: The Pod starts and its injected environment contains the intended credential key value.

Incorrect Answers

B:

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: Secret key references are exact and missing mandatory keys prevent valid container configuration. Apply it by: Align the Secret key name and the Pod's secretKeyRef with the application contract.

C:

Secrets are intended for sensitive values but still require RBAC and protection at rest and in use. This does not establish the proposed intervention. The governing principle here is: Secret key references are exact and missing mandatory keys prevent valid container configuration. Apply it by: Align the Secret key name and the Pod's secretKeyRef with the application contract.

D:

ConfigMaps separate nonsecret configuration from the application container image. This does not establish the proposed intervention. The governing principle here is: Secret key references are exact and missing mandatory keys prevent valid container configuration. Apply it by: Align the Secret key name and the Pod's secretKeyRef with the application contract.

Question 20

A node's kubelet reports NetworkPluginNotReady after a CNI upgrade although the runtime is healthy. What is the most direct consequence if the underlying problem is left unresolved?

  1. A reachable API server cannot schedule useful workloads to a runtime-broken node.
  2. Workloads remain blocked even though container runtime queries succeed.
  3. Workloads may be evicted or remain unschedulable on the affected node.
  4. Application requests can hang selectively on larger transfers.

Explanation

Correct Answer

B:

Workloads remain blocked even though container runtime queries succeed. This directly follows from the failed condition. The preventive correction is: Restore the CNI node plugin and inspect CNI configuration files for incompatible changes. The governing Kubernetes behavior is: Node readiness can depend on successful Pod network initialization.

Incorrect Answers

A:

The kubelet must connect to the correct container runtime interface to manage Pod sandboxes. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Workloads remain blocked even though container runtime queries succeed.

C:

A node's Ready condition depends on kubelet heartbeats and necessary local runtime services. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Workloads remain blocked even though container runtime queries succeed.

D:

Overlay encapsulation adds overhead and mismatched MTU can break larger packets despite basic connectivity. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Workloads remain blocked even though container runtime queries succeed.